This is a highlighted sec of the following (Not including EXCHANGE Server or E-DIRECTORY Service)
Hardware Management
You can use Windows Remote Management (WinRM) to manage server hardware remotely across firewalls and monitor conditions on servers that are offline.
lol! )If you read IT Then you might find the Sans institute quite interesting)
Learn more about the new Windows Server 2003 R2 componentsMicrosoft® Windows Server™ 2003 R2, a software update to the Windows Server 2003 operating system, makes it easier and more cost effective to extend connectivity and control to identities, locations, data, and applications throughout and beyond your organization.
Built on Windows Server 2003 with Service Pack 1 (SP1), Windows Server 2003 R2 takes advantage of the stability and security of the code base while extending connectivity and control into new areas. With Windows Server 2003 R2, you get the following improvements:
Identity and access management
Branch office server management
Storage setup and management
Application development inside and outside your organization's traditional boundaries
For more information about Windows Server 2003 R2, see the Microsoft Web site. (
http://go.microsoft.com/fwlink/?LinkId=45560)
This topic describes the following new components that you can install with Windows Server 2003 R2. This topic also provides links to more information about each.
Server Manageability
Administration Tools Packs
Hardware Management
MMC 3.0
Features for Active Directory
Active Directory Application Mode (ADAM)
Active Directory Federation Services
Disk and File Management Features
Branch Office
Distributed File System (DFS)
Common Log File System (CLFS)
File Server Management
File Server Resource Manager
Microsoft Services for Network File System
Storage Management for SANs
Printer and Protocol Support
Print Management
Microsoft .NET Framework
Microsoft .NET Framework version 2.0
Internet and E-Mail Services and Features
Windows Sharepoint Services
UNIX Interoperability
Identity Management for UNIX
Subsystem for UNIX-based Applications
Server Manageability
To help you manage your server, Windows Server 2003 R2 provides Administration Tools Packs and the following improvements to hardware management and Microsoft Management Console (MMC) 3.0.
Administration Tools Packs
To make the remote management of your servers easier, you can install the Administration Tools Packs for Windows Server 2003 R2 located on Disc 2 in the \mgmttls directory. Each of the following components has an Administration Tools Pack:
Microsoft Management Console (MMC) 3.0
Print Management
File Server Resource Manager
DFS Replication
Identity Management for UNIX
File Server Management
In order to administer a component, you must first install the MMC 3.0 Administration Tools Pack. The Administration Tools Packs can be installed on computers running Windows® XP Professional with Service Pack 2 (SP2). For specific installation instructions, see the Microsoft Web site. (
http://go.microsoft.com/fwlink/?LinkId=54293)
Hardware Management
You can use Windows Remote Management (WinRM) to manage server hardware remotely across firewalls and monitor conditions on servers that are offline.
This new feature in Windows Server 2003 R2 is implemented using WS-Management, an industry-standard, Web services-based remoting protocol. WS-Management uses HTTPS as the secure transport that enables firewall traversal.
WinRM provides a command-line interface for common management tasks and a scripting application programming interface (API) for writing Windows Script Host-based system administration scripts.
Using WinRM, you can write scripts to monitor and control the state of server hardware by communicating with a Baseboard Management Controller (BMC). A BMC is a separate micro-controller with its own network adapter that is connected to the processor board of a server and can monitor conditions even when the server is off or malfunctioning. A new Windows Management Interface (WMI) provider for Intelligent Platform Management Interface (IPMI) exposes six new WMI classes for accessing BMC information with scripts.
WinRM is not installed by default with Windows Server 2003 R2. To install it, open Add or Remove Programs from Control Panel, and click Add/Remove Windows Components.
For more information about hardware management, see "Hardware Management in Microsoft Windows Server 2003 R2" on the Microsoft Web site. (
http://go.microsoft.com/fwlink/?LinkId=45204)
Back to Top
MMC 3.0
Microsoft Management Console (MMC) 3.0 supports richer functionality in snap-ins designed for the MMC 3.0 infrastructure. In addition, the following improvements apply to all MMC 3.0 consoles:
Action pane. The Action pane appears on the right side of the snap-in console. It lists the actions that are currently available to you, based on the currently selected items in the tree or the results pane.
To show or hide the action pane, click the Show/Hide Action Pane button on the toolbar, which is similar to the Show/Hide Console Tree button.
New Add or Remove Snap-in dialog box. The new Add or Remove Snap-in dialog box makes it easy to add, organize, and remove snap-ins. You can control which extensions are available, and whether to automatically enable snap-ins that may be installed later. You can nest snap-ins and rearrange the snap-ins in the tree.
To use this feature in this beta version, you must set a registry key manually.
Improved error handling. MMC 3.0 notifies you of errors in snap-ins that could cause MMC to fail and provides several options for responding to those errors.
MMC 3.0 is automatically installed when you install Windows Server 2003 R2.
For more information, seeMicrosoft Management Console.
Back to Top
Features for Active Directory
The following Active Directory components are now included in Server 2003 R2.
Active Directory Application Mode (ADAM)
Active Directory Application Mode (ADAM) is an independent mode of the Active Directory® directory service, without infrastructure features, that provides directory services for applications. It provides a data store and services for accessing the data store. It uses standard application programming interfaces (APIs) for accessing the application data. ADAM operates either as a standalone data store, or it operates with replication. Its independence enables local control and autonomy of directory services for specific applications. It also facilitates independent, flexible schemas and naming contexts.
For more information, seeActive Directory Application Mode (ADAM).
Back to Top
Active Directory Federation Services
The fundamental purpose of Active Directory Federation Services (ADFS) is to leverage single user sign-on to authenticate the user to multiple related Web applications over the life of a single online session. ADFS does this by securely sharing digital identity and entitlement rights across security and enterprise boundaries.
For more information, seeActive Directory Federation Services (ADFS).
Back to Top
Disk and File Management Features
Server 2003 R2 includes the following disk and file management features.
Branch Office
Branch offices are the remote locations of an organization that connect to a headquarters or hub over a wide-area network (WAN). The technologies included in Windows Server 2003 R2 can simplify how you manage a variety of activities and tasks in branch offices. These activities and tasks include:
Publishing files from centralized hubs to branch offices.
Replicating files from branch locations for backup, fault-tolerance, or cross-publishing.
Collaborating on documents that are shared among branches or between hubs and branches.
Efficiently managing printers, printer drivers, and print queues in branch offices.
These improvements are supported by the enhanced print-management tools in Windows Server 2003 R2. They are also supported by Distributed File System (DFS) in Windows Server 2003 R2.
For more information about these technologies in Windows Server 2003 R2, see the Microsoft Web site. (
http://go.microsoft.com/fwlink/?LinkId=51679)
Back to Top
Distributed File System (DFS)
The Distributed File System (DFS) solution in Windows Server 2003 R2 provides simplified, fault-tolerant access to files and WAN-friendly replication. Distributed File System consists of two technologies:
DFS Namespaces. Formerly known as Distributed File System, DFS Namespaces allows administrators to group shared folders located on different servers and present them to users as a virtual tree of folders known as a namespace. A namespace provides numerous benefits, including increased availability of data, load sharing, and simplified data migration.
DFS Replication. The successor to File Replication service (FRS), DFS Replication is a new state-based, multimaster replication engine that supports scheduling and bandwidth throttling. DFS Replication uses a new compression algorithm known as Remote Differential Compression (RDC). RDC is a "diff over the wire" protocol that can be used to efficiently update files over a limited-bandwidth network. RDC detects insertions, removals, re-arrangements of data in files, enabling DFS Replication to replicate only the deltas (changes) when files are updated.
For more information about Distributed File System in Windows Server 2003 R2, see the Microsoft Web site. (
http://go.microsoft.com/fwlink/?LinkId=51679)
Back to Top
Common Log File System (CLFS)
Common Log File System (CLFS) is a loadable driver that provides kernel- or user-mode applications with a robust logging subsystem. CLFS is a unique Windows technology that can be used to develop applications and middleware that depend on durably writing and reading sequential data. Examples include replication agents, auditing agents, databases, and other transactional resource managers.
s a comprehensive set of scripting utilities and a software development kit (SDK) designed to fully support the development capabilities of SUA.
SUA also supports case-sensitive file names, job control, compilation tools, and the use of over 300 UNIX commands, utilities, and shell scripts. Because the subsystem installs separately from the Windows kernel, it offers true UNIX functionality without any emulation.
Features include the ability to create log files with a single stream of data or with multiple streams of data for shared use by one or more clients; both circular and linear logging; guaranteed ability to flush buffered data by pre-reserving space in the log; policy-based log size and space management; sharing of a single log by both kernel and user clients; a notification mechanism to allow different users within the same log to coordinate their log use; flexible buffering of log data; archiving APIs do not interfere with normal operations; atomic multi-sector writes; and torn-write detection.
CLFS is optimized for performance. All writes to the log file are buffered until an explicit flush, an opportunity to share a write with another client, or the buffer is filled. Log data is written directly to the hard disk from the log buffers without copying. Multiple streams of data can be written during the same I/O operation, resulting in only one disk seek for what normally takes multiple seeks and writes. Reads are cached to save disk accesses during normal operation or bursts of read activity.
For more information, see the "Platform SDK" on the Microsoft Web site. (
http://go.microsoft.com/fwlink/?LinkId=44489)
Back to Top
File Server Management
You can use File Server Management to perform many tasks, such as formatting volumes, creating shares, defragmenting volumes, creating and managing shares, setting quota limits, creating storage utilization reports, replicating data to and from the file server, managing Storage Area Networks (SANs), and sharing files with UNIX and Macintosh systems.
For more information, seeFile Server Management Overview.
Back to Top
File Server Resource Manager
With the increasing demand on storage resources, as organizations rely more heavily on data than ever before, IT administrators face the challenge of overseeing a larger and more complex storage infrastructure, while at the same time, tracking the kind of information available in it.
File Server Resource Manager is a new Microsoft Management Console (MMC) snap-in that provides a suite of tools for administrators to understand, control, and manage the quantity and type of data stored on their servers. By using File Server Resource Manager, administrators can place quotas on folders and volumes, actively screen files, and generate comprehensive storage reports.
File Server Resource Manager quotas vs. NTFS disk quotas
The Windows 2000 and Windows Server 2003 operating systems support disk quotas, which are used to track and control disk usage per user on NTFS volumes. The following table outlines the advantages of using the quota management tools in File Server Resource Manager.
Quota features File Server Resource Manager NTFS disk quotas
Quota tracking By folder or by volume Per user on a volume
Disk usage calculation Actual disk space Logical file size
Notification mechanisms E-mail, custom reports, command execution, event logs Event logs only
For more information, seeFile Server Resource Manager.
Back to Top
Microsoft Services for Network File System
Microsoft Services for Network File System (NFS) is a component of Windows Server 2003 R2 that provides a file-sharing solution for enterprises that have a mixed Windows and UNIX environment. Microsoft Services for NFS allows users to transfer files between Windows Server 2003 R2 and UNIX computers using the Network File System (NFS) protocol.
Microsoft Services for NFS is an update to the NFS components that were previously available in Services for UNIX 3.5. Microsoft Services for NFS includes the following new features:
Support for 64-bit
Microsoft Services for NFS components can be installed on all editions of Windows Server 2003 R2, including 64-bit versions.
Updated Microsoft Management Console (MMC) Microsoft Services for NFS Administration snap-in
Enhanced reliability.
Support for UNIX special devices (mknod)
Microsoft Services for NFS allows you to support a mixed environment of Windows- and UNIX-based operating systems. It also allows you to update your organization's computers while supporting older technology during the transition phase. The following scenarios are examples of how enterprises can benefit from deploying Microsoft Services for NFS.
Allows UNIX clients to access resources on computers running Windows Server 2003 R2. Your company may have UNIX clients accessing resources, such as files, on UNIX file servers. To take advantage of new Windows Server 2003 features, such as Shadow Copies for Shared Folders, you can move resources from your UNIX servers to computers running Windows Server 2003 R2, and then set up Microsoft Services for NFS to enable access by UNIX clients that are running NFS software. All of your UNIX clients will be able to access the resources using the NFS protocol with no changes required.
Allows computers running Windows Server 2003 R2 to access resources on UNIX file servers. Your company may have a mixed Windows and UNIX environment with resources, such as files, stored on UNIX file servers. You can use Microsoft Services for NFS to enable computers running Windows Server 2003 R2 to access these resources when the file servers are running NFS software.
For more information, seeMicrosoft Services for Network File System.
Show Posts
Kinda like you and me 
LOL! ENJOY!!
