Que microsoft windows server 2003 delta guide mar 2003 ISBN 0789728494

Administrative TemplatesFolders section New User Configuration policies Administrative Templatesindows Components section Computer Configuration policies Application Compatibility settin

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [J] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

JIT (just in time) compilation

Join Session Directory setting (Terminal Servers Session Directory group policies)

[ Team LiB ]

Like the book? Buy it!

[SYMBOL] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

[ SYMBOL ] [A] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

Administrative TemplatesFolders section (New User Configuration policies)

Administrative Templatesindows Components section (Computer Configuration policies) Application Compatibility settings

Windows Update settings

Administrative Templatesindows Components section (New User Configuration policies) Application Compatibility settings 2nd

Services tab

Affinity setting property (port ranges)

All Programs menu (Start menu)

Allow Time Zone Redirection setting (Terminal Services client/server data redirection policy setting

64-bit architectures

64-bit Windows

EPIC (Explicitly Parallel Instruction Computing) architecture (Intel) IIS (Internet Information Services) console

[ Team LiB ]

[ SYMBOL ] [ A ] [B] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

[ SYMBOL ] [ A ] [ B ] [C] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

[ Team LiB ]

[ SYMBOL ] [ A ] [ B ] [ C ] [D] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

Do Not Allow Smart Card Device Redirection setting (Terminal Services client/server data redirection 2nd

restrictions

domain-based DFS (distributed file system) automatic replication

manual replication

replication

DomainDNSZones (AD integrated zones) domains

AD/AM (Active Directory Application Mode) remote office logons (Active Directory) 2nd renaming

Active Directory administrative tools 2nd downloading

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [E] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [F] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [G] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [H] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [I] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [K] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [L] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

auditing

remote office logons (Active Directory) domains 2nd

loopback addresses (Ipv6 protocol)

low-bandwidth connections

RDP (Remote Desktop Protocol) 5.1 2nd

[ Team LiB ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [M] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [N] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

NET Enterprise Servers

Datacenter Servers

NLB (Network Load Balancing) 2nd 3rd 4th 5th

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [O] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [P] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

Limit Maximum Color Depth setting

Remove Disconnect Option from Shut Down Dialog setting 2nd

Remove Windows Security Item from Start Menu setting

Restrict Terminal Services Users to a Single Remote Session setting RPC Security PolicyServer (Require Security) group policy

Prevent License Upgrade setting (Terminal Services licensing policy settings) printer drivers

MSMQ (Microsoft Message Queue Service)

SOAP (Simple Object Access Protocol) protocol

Publish tab (Computer Management console)

[ Team LiB ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [Q] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

QFE (quick-fix engineering updates) [See hotfixes ]

QFE (quick-fix engineering) [See hotfixes ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [R] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

Remove Windows Security Item from Start Menu setting (Terminal Services group policy settings)

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [S] [ T ] [ U ] [ V ] [ W ] [ X ] [ Z ]

Security Settings extension (Group Policy) 2nd

Security Templates snap-in 2nd 3rd 4th 5th 6th

security databases

SCA (Security Configuration and Analysis) snap-in 2nd security holes

WebDAV (Web Distributed Authoring and Versioning) 2nd 3rd Security Configuration and Analysis snap-in (MMC)

specifying password policies

SCA (Security Configuration and Analysis) snap-in 2nd security templates, analyzing 2nd

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [T] [ U ] [ V ] [ W ] [ X ] [ Z ]

Terminal Server Session Directory 2nd

Terminal Server SID (Security Identifiers)

Limit Maximum Color Depth setting

Remove Disconnect Option from Shut Down Dialog setting 2nd

Remove Windows Security Item from Start Menu setting

Restrict Terminal Services Users to a Single Remote Session setting licensing policy settings

terminal services client component [See Remote Desktop Connection ]

typeperf command-line tool

[ Team LiB ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [U] [ V ] [ W ] [ X ] [ Z ]

[ Team LiB ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [V] [ W ] [ X ] [ Z ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [W] [ X ] [ Z ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [X] [ Z ]

xDSL

permanent virtual circuit encapsulation

[ Team LiB ]

[ SYMBOL ] [ A ] [ B ] [ C ] [ D ] [ E ] [ F ] [ G ] [ H ] [ I ] [ J ] [ K ] [ L ] [ M ] [ N ] [ O ] [ P ] [ Q ] [ R ] [ S ] [ T ] [ U ] [ V ] [ W ] [ X ] [Z]

zipped folders [See Compressed Folders feature (Windows Server 2003) ]

[ Team LiB ]

The NET Framework represents an entirely new way of thinkingabout software development You're probably familiareven ifyou don't realize itwith the "old way" of creating software

applications, which is illustrated in Figure 9.1 Developers woulduse a tool such as Visual Basic 6.0 to create software

in one form or another since the beginning of computer

programming and is capable of producing applications with verygood performance

Figure 9.1 Traditional software development produces executables for a specific operating

system and hardware platform.

programming model:

Executables produced in this fashion only run on a specific operating system and hardware platform As

enterprises continue to implement a wider variety of

hardware and operating systemsincluding portable deviceslike Pocket PCsdevelopers have to work harder to make

their programs run throughout the enterprise Each newoperating system/hardware combination requires

perform specific tasks and then easily reuse that code inseveral different projects A powerful object-oriented

language also allows developers to reuse functionality

inherent to the operating system, such as drawing windowsand buttons, accessing files and networks, and so forth

Different programming languages have different

strengths and weaknesses, and developers have to choose one and pretty much stick with it Each

language typically operates in a completely different

fashion, making it very difficult for developers to switch

back and forth between languages when working on

different projects As a result, developers tend to pick onelanguage and stick with it, even if it isn't ideal for the task

programming language from Sun Microsystems Although each

of these languages has a different syntax, or grammar, they all

offer the same basic capabilities For example, developers whowanted to interface closely with the operating system used tochoose Visual C++ as their language, often because languagessuch as Visual Basic didn't provide close operating system

integration Under NET, that's no longer true: Each of the NETlanguages provides the same capabilities, allowing developers

to work in whatever language they're most comfortable with.Even better, all the languages can be used from within the samedevelopment tools (such as Visual Studio NET), so that

developers can switch languages without having to learn anentirely new set of tools

The NET Framework's changes go beyond developer

application, developers produce an executable file In VisualBasic NET (or any other NET language), however, compiling issimply an automated process in which the NET Frameworktranslates the developer's program code into a universal

or less unchanged on any platform for which a CLR is available.Microsoft already provides a CLR for Windows and a CompactCLR for Pocket PCs and other Windows CE devices The futuremight bring Linux- or Unix-compatible CLRs, allowing NET

applications to run (hopefully) unchanged on a completely

different operating system This capability solves another

traditional development problem by allowing developers to writeone program that runs on all of an enterprise's various

computing devices

This business with the CLR and cross-platform compatibilityshould sound familiar because it's what Java advocates havebeen preaching since their product was introduced Java uses asimilar development model in which developers write Java-

specific code, which is executed by a Java Virtual Machine

(JVM) So long as a JVM is available for a specific platform, thatplatform can run virtually all Java applications If you've usedJava applications, however, you might have noticed that theydon't perform quite as quickly as native-code applications

written in Visual Basic 6.0, Visual C++ 6.0, or other traditionalprogramming languages That performance decrease is inherent

in any virtual machine technology: Rather than executing anapplication directly on the operating system, both Java and

.NET execute the application within a virtual machine (the CLR

in the case of NET), and the virtual machine itself is executed

by the operating system In other words, the virtual machinerepresents an extra layer of code that has to be executed,

which reduces performance

Although NET applications tend to perform pretty well, theycan't compete with native-code applications, especially thosewritten in Visual C++ (the language Windows itself is writtenin) For that reason, you won't see Microsoft using the NET

Framework to develop the next versions of its NET EnterpriseServers, such as Exchange Server and SQL Server Those will

powerful server applications to be written in NET, but that day

is probably a long way off

So, what does an administrator need to know about the NETFramework? Prior to Windows Server 2003, the NET

Framework itself had to be installed before NET applicationscould be installed and executed; Windows Server 2003,

however, comes with the NET Framework built right in, so yourdevelopers can immediately start installing and executing NETapplications on your servers So, although deployment is a

piece of cake, an additional administrative effort is involvedbecause the NET Framework adds whole new levels of securityand management to your servers In fact, Windows Server

supports an entirely new console called the NET FrameworkConfiguration Console, shown in Figure 9.3

Figure 9.3 The NET Framework Configuration console enables you to modify the behavior and

other properties of the NET Framework.

Assembly Cache Assemblies are basically modules of code

that are shared by several applications For example, a

developer might create a logon routine and use it in all hiscorporation's custom applications The Assembly Cache acts

Code Access Security Policy The NET CLR includes a

complete set of code access security policies that controlapplications' access to protected resources This extra layer

of security ensures that only authorized applications can get

application with its own set of configured assemblies andremoting services, customizing the behavior of each

application to meet your precise needs

You might find yourself wondering whether many of these tasksare more properly suited to a developer rather than an

administrator Only time will tell if that's the case, but we firmlybelieve that administrators are responsible for the overall

operation, efficiency, and security of the enterprise network,and that places these five configuration tasks firmly in the

administrator's realm Developers often become too focused on

a particular task and don't take the health and well-being of theentire network into consideration, leaving it to the administrator

provide those assemblies for installation on your server

of preinstalled assemblies.

policy and codebase information.

different versions of the assembly Multiple versions of an

assembly can reside in the assembly cache at the same time;which version an application gets when it requests the assemblydepends on the binding policy you set The example in Figure9.5 is for an assembly named Accessibility Any applicationrequesting version 1.0.0.1331.1.2.189 of the assembly is givenversion 1.2.0.239, which must reside in the assembly cache.Binding policy enables you to actively manage backward

compatibility because you can specify which version of the

assembly will be used with a given request for a particular

version