Professional Documents
Culture Documents
FileandPrintServicesTechnicalOverview
Introduction
File and printer sharing, information retrieval, and data storage are among the most frequently used network services. They are therefore crucial factors to consider when choosing a
network operating system.
Microsoft built the Windows 2000 Server operating system from the ground up as an integrated, multipurpose operating system. The operating system design responds to customer
demands for sophisticated but easytomanage file and print services, for integration of Web and media content with file and print information sharing, and for meeting exponential
growth in storage requirements while lowering storage cost. In addition, its open architecture lets thirdparty developers provide additional functionality in response to everchanging
business requirements.
Microsoft developed specific file and print features to meet widespread customer needs:
Reduced cost. Remote Storage migrates infrequently used files to lowercost secondary storage, yet keeps that data available if needed. Removable Storage helps reduce costs by
letting multiple client applications share local libraries and tape or disk drives while ensuring that client applications do not corrupt each other's data.
Better manageability. The improved NTFS file system, distributed file system Dfs, and Indexing Service make it easier to find and access files across expanding networks. New
interfaces make operating system services easier to manage; for example, the new printer interface makes it simpler for both administrators and endusers to configure and manage
their printing needs.
http://msdn.microsoft.com/enus/library/cc750353.aspx
1/39
12/8/2014
FileandPrintServicesTechnicalOverview
Increased availability and reliability. Dfs replication and File Replication service FRS synchronization help keep data available to users, even if a server or disk drive fails or a
shared folder or file becomes corrupted. Dynamic volumes formatted with NTFS 5 allow fewer reboots when adding disks and creating, extending, or mirroring a volume.
Scalability. The Windows 2000 NTFS version 5 file system and the Windows 2000 storage subsystems let users efficiently store and retrieve everlarger quantities of data.
Organizations that install Windows 2000 file and print servers in their existing network can take advantage of several new features. When they upgrade to a Windows 2000 network,
additional file and print capabilities become available.
This overview focuses primarily on the Windows 2000 Server implementation of the standard file and print services components. However, it includes mention of several Webrelated
features where they are inextricably bound up with file and print services.
Top Of Page
File Services
The majority of network servers provide file service; that is, they offer centralized file storage that lets users easily share files. File servers often store private files as well as shared files, and
provide a single point of backup for both. File servers let users access their files even when they move to different workstations.
Windows 2000 Server introduces new and improved file services, including changes to the management of network shares and users and to the NTFS file system. In addition, Windows
2000 Server supports several other ondisk file system formats. Windows 2000 Dfs extends the capabilities present in Windows NT 4.0 Dfs. Not technically a file system driver, Dfs provides
what appears to users as a unified hierarchical file system, although the data actually resides on different servers across the network.
Network administrators typically install systems whose primary role is providing file service as member servers rather than as domain controllers. All file service features described in this
paper, except for domainbased Dfs and the FRS, are also available on standalone servers.
Windows 2000 Server filesystem related features include:
Managing shares, connected users, and open files
Distributed File System Dfs
NTFS and related enhancements
Other supported file systems
Each of these topics is covered in the following sections.
http://msdn.microsoft.com/enus/library/cc750353.aspx
2/39
12/8/2014
FileandPrintServicesTechnicalOverview
Figure 1: Shared Folders tool manages shares, connected users, and open files
For Windows 2000 Server, members of the Administrators, Server Operators, or Power Users groups can use the Shared Folders snapin. For Windows 2000 Professional, only members of
the Administrators or Power Users group can use Shared Folders.
The Shared Folders snapin lets you perform the following tasks:
Shares. Create, view, and set permissions for network shares, including shares running Windows NT 4.0.
Sessions. View and disconnect users connected to the computer over the network.
Files. View and close files opened by remote users.
Mac Shares. Configure Services for Macintosh so that Windows and Macintosh users can share volumes, files, and printers through a Windows 2000 Server. Mac clients can access
Macintosh volumes and printers using an Apple networking protocol. From the file server, you administer Mac shares from the Services and Applications node of the Computer
Management console tree2.
For Windows 2000 Server, the Shared Folders snapin also enables publishing a share as a Volume Object in the Active Directory directory service. Publishing an object in Active Directory
lets users query available resources and shares.
http://msdn.microsoft.com/enus/library/cc750353.aspx
3/39
12/8/2014
FileandPrintServicesTechnicalOverview
4/39
12/8/2014
FileandPrintServicesTechnicalOverview
name of the target shared folder or target Dfs root. When a Dfs client accesses a Dfs shared folder, the Dfs root server uses this mapping of a DNS name to a UNC name to return a
referral to the client so that it can locate the shared folder.
Mapping the DNS name to the UNC name makes the physical location of data transparent to users, who no longer have to remember on which server a folder is stored. If you move a file
or folder to another physical location, the user's view of it remains unchanged.
When a client machine requests a referral to a Dfs share, the Dfs root server uses the Partition Knowledge Table PKT to direct the client to the physical share. The PKT is stored in Active
Directory for domainbased Dfs and stored in the registry for standalone Dfs more about domainbased Dfs and standalone Dfs later. In a network environment, the PKT maintains all
information about Dfs topology, including its mappings to the underlying physical shares. After the Dfs root server refers the client to a list of replica shares that correspond to the
requested Dfs link, the client then uses Active Directory site topology3 to contact a replica within the same site or, if one is not available, a replica outside the site.
Figure 2 shows an example of how an administrator can set up Dfs composed of links from multiple servers, and it shows how an enduser would see the result:
Figure 2: Dfs topology from the point of view of the administrator and the enduser
Only Windows 2000based machines can host Dfs roots and Dfs links Dfs shared folders. NonWindows 2000based machines can be the target of a Dfs link but cannot contain additional
Dfs links although of course they can host filesystem subfolders. Dfs shared folders on downlevel volumes volumes on computers running an earlier operating system than Windows
2000 include those published on Windows NT 4.0 Workstation and Server, Windows 95, Windows 98, Windows for Workgroups, and all nonMicrosoft shared folders for which client
redirectors are available. If duplicates of a shared folder exist, each copy is a replica in a replica set see the section "Dfs Replication" for more about this.
The Dfs root can be one of two types:
Domainbased Dfs root. A domainbased Dfs root must be hosted on a domain member server or domain controller. Such servers, called root replicas, provide referrals to the Dfs
namespace for client machines. Domainbased Dfs stores its configuration information in Active Directory. If you have more than one domain controller to keep the Dfs
configuration information available and if you establish more than one Dfs server in the domain, domainbased Dfs can provide high availability for any Dfs file or folder in the
domain.
Standalone Dfs root. A standalone Dfs root can be hosted on three types of Windows 2000 servers: on a standalone server, a member server, or on a domain controller. A stand
alone Dfs server does not use Active Directory, cannot have rootlevel replicas, and can have only a single level of Dfs links. Standalone Dfs stores its configuration in the local
registry. Its purpose is to provide backward compatibility with earlier versions of Dfs. During an upgrade of Windows NT 4.0 to Windows 2000, any Dfs 4.x roots are converted
automatically to Windows 2000 standalone Dfs roots. You can manage Dfs 4.x implementations with the Windows 2000 Dfs Administrator. You can migrate standalone Dfs roots at
your own pace. Some roots can remain as standalone; others can be migrated to domainbased. Both can coexist in a Windows 2000 domain.
Each server that hosts a domainbased Dfs root obtains the PKT from the Active Directory4. Thus, each of these servers must stay in sync with the Active Directory. This synchronization of
the Dfs root and Active Directory not the same as synchronization among Dfs replicas, described below is triggered in three ways:
http://msdn.microsoft.com/enus/library/cc750353.aspx
5/39
12/8/2014
FileandPrintServicesTechnicalOverview
Startup. When a server hosting a domainbased Dfs root boots, the booting server obtains the PKT from an active domain controller.
Changes. When changes are made to the PKT changes are made in Active Directory itself, all participating Dfs root servers are notified that changes have occurred that the servers
must retrieve from the directory.
Set interval. Domainbased Dfs root servers poll the directory service for current PKT information every 24 hours.
Dfs Replication and FRS Synchronization
Users access certain files frequently over the network. When only one copy of a file exists on a single file server, if that server goes down, no one can access the file. A different problem
arises if many users access a single file simultaneouslythe server experiences a heavy processing load, resulting in slower access to files on that server. Using Dfs replication helps solve
these problems of availability and load. The following subsections describe how Dfs uses replication to accomplish these tasks:
Replica sets provide high availability
FRS keeps replicas that change synchronized
Replica sets help reduce file server load
Replica sets make file server maintenance easier
Replica Sets Provide High Availability
High availability refers to keeping important data available, even if a server or disk drive fails or a shared folder or file becomes corrupted. To ensure that the Dfs root server itself remains
available, you can use Dfs Administrator to create two kinds of replica sets. A replica set is two or more copies of a Dfs root or Dfs shared folder that participate in replication. Here are the
two types of replica sets:
Dfs root replicas replicate Dfs "knowledge." In domainbased Dfs, you can create Dfs root replicas, that is, two or more copies of the Dfs root, each on a different server. As stated
above, a Dfs root replica uses the PKT which contains the Dfs topology, including mappings from the Dfs logical namespace to the underlying physical shares to provide referrals to
clients. This is why replication of Dfs roots is also referred to as replication of Dfs knowledge.
Dfs link replicas replicate Dfs "content." When you create a Dfs link, you can create a replica set by specifying multiple shared folders for that link. Each copy must be located on a
separate computer, but all share the same logical Dfs name. The fact that more than one copy which can be readwrite copies exists is transparent to users. You can specify
hundreds of shared folders in a replica set. Just as Dfs root replicas support high availability for Dfs roots, Dfs link replicas support high availability for a portion of the Dfs
namespace.
In Figure 3, below, the box labeled "Replicating Dfs Root" shows two Dfs root servers. The two shares hosting the root are a replica set. Any new content local to those roots is kept
consistent by FRS; see the next subsection, "FRS Keeps Replicas That Change Synchronized." The box labeled "Replicating Dfs Links" shows two shares published as a single Dfs link.
Content on these two shares is also held consistent by a separate FRS replica set.
http://msdn.microsoft.com/enus/library/cc750353.aspx
6/39
12/8/2014
FileandPrintServicesTechnicalOverview
http://msdn.microsoft.com/enus/library/cc750353.aspx
7/39
12/8/2014
FileandPrintServicesTechnicalOverview
FRS & Active Directory. In an Active Directory environment that is, on a Windows 2000 domain controller, certain system files are not stored in the Windows 2000 directory
information tree DIT database and are therefore not replicated by Active Directory object replication. These system files are stored in a shared folder called the system volume
SYSVOL. SYSVOL is installed as a part of the domain controller promotion process Dcpromo.exe. FRS replicates the SYSVOL folder among participating domain controllers and
keeps the replicas synchronized. FRS replication of SYSVOL is an activity that is entirely independent of Active Directory object replication. Note also that, although Active Directory
uses FRS to replicate SYSVOL, Active Directory replication does not use FRS because FRS has its own replication engine.
Figure 4 summarizes features of Dfs and FRS:
8/39
12/8/2014
FileandPrintServicesTechnicalOverview
enforced by the file system underlying the network share referenced by Dfs. That is, when a user tries to access a Dfs shared folder or the files inside it, whether or not that access succeeds
depends on the underlying file system. A volume formatted with FAT is protected by sharelevel security; a volume formatted with NTFS has both sharelevel and filelevel NTFS
permissions.
IIS Can Use Dfs
Internet Information Services 5.0 IIS, which installs as a networking service of Windows 2000 Server, can take advantage of Dfs to make management of a Web site easier. If all the data for
a website is stored on a single machine, Dfs has no role to play. However, if the HTML files backing a Web server are stored on multiple machines, using Dfs can simplify Web site
management by grafting the multiple network shares into a unified namespace.
A Webmaster can now build a logical Dfs directory that includes the default Web pages of each department's Web server as a subdirectory of the main Internet or intranet Web. If a Web
page is physically moved from one server to another, the HTML links to other pages stored in Dfs do not have to be updated, provided an administrator reconfigures Dfs accordingly using
the Dfs Administrator tool. This means that if the server hosting a user's Web page is removed and the page is republished on a different server, the links pointing to that page do not
have to be reconfigured.
Windows 2000 Improvements to Dfs When Compared to Dfs 4.x
Dfs server enhancements7 include the following:
Windows 2000 installs the Dfs service automatically during installation of or upgrade to the Windows 2000 operating system.
You can pause or stop the Dfs service, but you cannot remove it from the administrative console.
The Dfs topology is stored in Active Directory for domainbased Dfs.
Dfs is integrated into the Active Directory namespace for domainbased Dfs.
Replicated Dfs roots eliminate the root as a single point of failure.
Support for FRS permits automatic replication of file changes between Dfs replicas.
The Dfs administrative tool is now graphical.
Status flags indicate the availability of replicas.
Dfs links can connect to other links on other Windows 2000based servers without a fresh referral.
The expiration of referrals that are cached by Dfs clients is configurable on an individual link basis.
Dfs now supports dynamic configuration of the Dfs topology.
Dfs now supports Cluster service.
9/39
12/8/2014
FileandPrintServicesTechnicalOverview
Windows 2000 Server continues to support the advanced features NTFS provided to earlier versions of the operating system, including:
Filelevel access control. NTFS governs which users and groups can access individual files and directories, and it can provide varying levels of access for different users. This is then
enforced by the core operating system. The NTFS file permissions are No Access, List, Read, Add, Add and Read, Change, Full Control, Special Directory Access, and Special File
Access which provides an even greater degree of granularity. Filelevel access control does not include file encryption; for Windows 2000 file encryption, see the section
"Encrypting File System."
Compression. NTFS compression allows for the compressed storage of files and directories so that less physical space is required. Compression is configurable on a volume,
directory, or file basis. With NTFS, if anything goes wrong physically with a portion of data in a compressed file, only that file is affected. This differs from earlier FAT compression on
Windows 95 and Windows 98, which could lose an entire volume of data if even one sector became corrupted.
Recovery log. NTFS logs all changes to the file system so that every file or directory update can be redone or undone to correct discrepancies caused by system failure or power
loss. NTFS cluster remappingcalled sector/cluster hot fixingrepairs hard disk failures on the fly without returning error messages to the calling application. If the data is corrupt,
NTFS flags that part of the hard disk as defective, and then rewrites the data to another location. Recovery log operations are fast and transparent to users.
POSIX support available only when running the POSIX subsystem. NTFS file names support the Portable Operating System Interface for UNIX POSIX standard for network
naming conventions, such as case sensitivity, lastaccess timestamping, and hard links.
New features in Windows 2000 Serverits directory service Active Directory, the IntelliMirror set of management features, and many new storage improvementsrequire an update to
the ondisk format for NTFS. Windows 2000 Server requires the use of the updated NTFS format on all domain controllers. Among the storagerelated improvements that use the new
NTFS format are volume mount points, remote storage, file system encryption, sparse files, disk quotas, and Microsoft Indexing Service all described later.
For existing NTFS volumes, the upgrade to the NTFS 5 ondisk format occurs automatically at the volume's first mount time; for volumes that setup uses, this conversion occurs during
installation. In addition, setup asks if you want to convert your FAT and FAT32 volumes, but doing so is optional. You can manually convert FAT and FAT32 volumes to NTFS 5 at any time.
Servers that dual boot Windows 2000 Server and Windows NT Server 4.0 must install Windows NT 4.0 Service Pack 4 or higher in order to access local NTFS 5 volumes when running
Windows NT 4.0. All network clients can remotely access NTFS volumes on Windows 2000 file and print servers. Whether a volume is formatted with NTFS 4 or NTFS 5 is transparent to the
network client.
Applications that assume knowledge of a volume's ondisk format must be updated. To learn more about how to do this, see the section "For More Information."
Enhancements that Windows 2000 Server adds to NTFS include:
NTFS reparse points and file system filter drivers
Encrypting File System EFS
NTFS volume mount points
NTFS sparse file support
Native property sets
Security ID SID searching and bulk access control list ACL checking
NTFS Change Journal
Distributed Link Tracking
http://msdn.microsoft.com/enus/library/cc750353.aspx
10/39
12/8/2014
FileandPrintServicesTechnicalOverview
http://msdn.microsoft.com/enus/library/cc750353.aspx
11/39
12/8/2014
FileandPrintServicesTechnicalOverview
As an alternative to assigning a drive letter to a mounted drive, Windows 2000 can assign a drive path. This means you are no longer limited to 26 drive letters for mounting and accessing
volumes. For example, if you have a CDROM drive currently assigned to the D: drive and you have an NTFSformatted C: drive, you can mount the CDROM drive at an empty folder with
the following path: C:\CDROM. You can then remove the drive letter D: or use it for something else and can access the CDROM through the mounted drive path.
This is made possible by NTFS volume mount points, which are new file system objects. Placing a mount point which is implemented as an NTFS reparse point on a directory maps one
disk volume under a directory of another volume. Because volume mount points are based on NTFS 5 reparse points, they work only on NTFS 5 volumes. Multiple volume mount points can
target any volume. Windows automatically prevents resolution problems due to changes in the internal device name of the target volume for example, changes due to hardware device
reconfiguration.
Say a laptop user has two logical volumes: he or she uses one to store operating system and personal files and the second to store workrelated data. Most personal productivity tools are
set to open/save work at a common directory such as C:\My Documents. It would be convenient not to have to change drives depending on whether personal or workrelated data is
being used. The user can use the Disk Management utility to place an NTFS volume mount point in the C:\My Documents\Work directory so that it and its subdirectories will use physical
disk space on drive 2. Changing directories to C:\My Documents\Personal, however, would access drive 1. Figure 5 depicts this situation.
12/39
12/8/2014
FileandPrintServicesTechnicalOverview
areas of 0 bits, and file compression compacted the nondata portions. However, file compression has its own drawbacks: access time may increase due to data compression and
decompression.
NTFS 5 introduces another solution to the problem of sparse data, which both conserves disk space and improves disk performance. An administrator or application can use a new user
controlled file system attribute to mark files containing large consecutive areas of 0 bits as sparse, and NTFS will then allocate physical space for only the meaningful data that is, to only
those portions of a sparse file that are actually written to. NTFS stores only range information that indicates where the sparse data would be if it were allocated. On file access, the file
system returns allocated data as actual and deallocated data as zeros. APIs let application developers bypass file expansion and read the allocated ranges directly. This enables applications
to avoid processing large streams of zeros yielded by the file system and to copy or move potentially huge files with sparse data streams in an efficient manner.
For example, if data is written to the first 64 KB and last 64 KB of a 42 GB file that is marked as a sparse file, NTFS uses only 128 KB of disk space, although in other respects the file
functions as if it were 42 GB.
Native Property Sets
Native property sets let any file or folder on an NTFS 5 volume have descriptive metadata associated with it. NTFS 5 supports native property sets on any file or folder. For example,
Component Object Model COM9 documents, such as Microsoft Word or Microsoft Excel files, have associated properties, including Author, Title, Subject, and Comment. With NTFS 5, any
file can have associated properties, even singlestream text files.
The new Indexing Service feature in Windows 2000 can index all properties on a file, including both NTFS native properties and COM document properties. The result is that users can
quickly search the index not only for files containing specified words in the file contents but also for properties of the filesfor example, they can search on properties such as document
author. To see the properties for a file or directory, rightclick on it and select Properties.
SID Searching and Bulk ACL Checking
In Windows 2000 and Windows NT a security ID, or SID, is a unique number that identifies each user, group, or computer account to the Windows security systems. Windows issues a SID
to every account on the network when the account is first created. Internal processes in Windows 2000 refer to an account's SID rather than to its user, group, or computer name.
NTFS 5 can perform a volumewide scan for files using the owner's SID. This feature lets administrators perform such tasks as finding all files that a given user owns and cleaning up a user's
files.
An access control list ACL allows or denies permissions also called access rights on a file or folder to specific users or groups. File permissions include Full Control, Modify, Read and
Execute, Read, and Write. Folder permissions include Full Control, Modify, Read and Execute, List Folder Contents, Read, and Write.
Windows 2000 offers substantially improved storage for ACLs. Because Windows 2000 uses an ACL index, unique ACLs are stored only once. Any files that use the same ACL share an index
entry, unlike Windows NT 4.0, which stored ACLs on each file. That is, NTFS stores unique ACLs only once even if ten objects share the ACL; in Windows NT 4.0, the ACL would be stored ten
times.
Indexing Service uses the Bulk ACL Checking feature to efficiently check security on all files returned by a search. Using Bulk ACL Checking ensures that a reference to a file the user cannot
read is not returned. In addition, NTFS 5 uses Bulk ACL Checking to test for authorization against multiple files at once. This lets you perform tasks such as determining what a given user
can do with given files or checking multiple ACLs simultaneously for file access.
NTFS Change Journal
Windows 2000 Server introduces the volumewide Change Journal10 to track modifications to NTFS 5 files over time and across system reboots. The Change Journal itself is a sparse
stream, which means that only a small active range of the file uses any disk allocation see the earlier section "NTFS Sparse File Support". As files, directories, and other NTFS objects are
added, deleted, and modified, NTFS enters records into the Change Journal in streams, one record for each volume on the computer. Each record indicates the type of change read, write,
move, and so on and the object that was changed. The offset from the beginning of the stream for a particular record is called the update sequence number USN. New records are
appended to the end of the stream.
http://msdn.microsoft.com/enus/library/cc750353.aspx
13/39
12/8/2014
FileandPrintServicesTechnicalOverview
The Change Journal logs the fact of the change to a file and the reason for it. However, it does not record enough information to reverse the change.
ISV developers of systemlevel applications such as file system indexing engines, content replication engines, and storage archiving and migration can make use of the Change Journal to
provide enhanced functionality: Applications that periodically scan the file system for changes can now, instead, use the Change Journal without resorting to namespace traversal. For large
volumes, this can reduce the time for scan operations from hours to seconds. For example, a backup application can consult the Change Journal to build its list of files before performing an
incremental backup.
Distributed Link Tracking
Distributed Link Tracking lets client applications track link sources that have been moved. NTFS 5 implements a volumewide indexed unique object identifier OID for each file. This OID
lets the new Distributed Link Tracking feature preserve shortcuts and object linking and embedding OLE linkssuch as a Microsoft Excel worksheet embedded in a Microsoft Word
documentto NTFS files that have undergone a name and/or path change, including a move to a different volume or computer. For example, a client application can continue to access a
linked database, even if the database location has changed.
http://msdn.microsoft.com/enus/library/cc750353.aspx
14/39
12/8/2014
FileandPrintServicesTechnicalOverview
Top Of Page
Indexing Service
Under Windows NT Server 4.0, Content Indexing Server shipped as part of the Microsoft Internet Information Server IIS, giving customers full text indexing and searching of documents
located on their Web sites. However, Windows 2000 Server ships Microsoft Indexing Service as part of the base operating system. This development extends the indexing and searching
services to locate information on file servers as well as on Web sites.
Windows 2000 Server and Professional Indexing Service indexes file system objects and intranet and Internet Web sites across volumes and machines so that they can be searched by
network, intranet, and Internet users alike. Making these search activities look similar to the user saves an organization time and money in training and supporting employees. All Indexing
Service operations are automatic, including index creation, index updating, and crash recovery in the event of a power failure.
To access Indexing Service in the Computer Management console, click Start, point to Settings, and then click Control Panel. Doubleclick Administrative Tools, and then doubleclick
Computer Management. Figure 6 shows Indexing Service under the Services and Applications node of the Computer Management console.
http://msdn.microsoft.com/enus/library/cc750353.aspx
15/39
12/8/2014
FileandPrintServicesTechnicalOverview
Mount/dismount tracking
Catalogs
Indexing Service builds and maintains catalogs of the contents of local and remote disk drives. A catalog consists of index information and stored properties for a particular group of
directories.
At installation, Indexing Service creates the following two catalogs by default:
System catalog. When Indexing Service is installed with Windows 2000 Server, it automatically builds the System catalog, which, by default, lists all directories on all permanently
attached disk drives. It contains an index for all file system documents except certain system and temporary files.
Web catalog. If Internet Information Services IIS is installed, Indexing Service also creates a Web catalog, which contains an index of the content of IIS, the default virtual server of
the World Wide Web for Web pages stored on a Windows 2000 Server server.
Using the Indexing Service snapin, you can configure existing catalogs and can add and remove additional catalogs at any time. After you add a catalog, you must add the directories to
be included within the catalog's scope. This is the set of directories that the catalog covers, both those to be indexed and those specifically excluded from being indexed. For each included
or excluded directory, all of its subdirectories are also included or excluded.
16/39
12/8/2014
FileandPrintServicesTechnicalOverview
Mount/Dismount Tracking
This feature lets indexing interact invisibly with the CHKDSK and format utilities. More important, it lets you index and store catalogs on removable disks, such as Jaz and Zip cartridges.
Top Of Page
17/39
12/8/2014
FileandPrintServicesTechnicalOverview
Defragmentation utility
Remote Storage service
Removable Storage service
Disk quotas
The Single Instance Store SIS
System File Protection
Storage support for hardware innovations
Each of these features is described in the following subsections.
In addition, Windows 2000 Server includes many enhancements that provide ISVs the infrastructure they need to write enterpriseclass storage applications and features. Also new in
Windows 2000 Server is the Microsoft Management Console MMC, which lets administrators and ISVs create the administrative tools called snapins that manage Windows 2000
components and services. ISVs should plan to write an MMC snapin as part of the administrative user interface for their storage solution.
http://msdn.microsoft.com/enus/library/cc750353.aspx
18/39
12/8/2014
FileandPrintServicesTechnicalOverview
a simple volume can be extended if NTFS 5; has a single dynamic disk partition, but cannot contain NT4 and
earlier partitions or logical drives
a simple volume
a spanned volume
a mirrored volume
a striped volume
a RAID5 volume
19/39
12/8/2014
FileandPrintServicesTechnicalOverview
Selfdescribing disks. The operating system keeps disk configuration metadata on each disk and replicates it. This is a change from Windows NT Server 4.0 and earlier, which stored
configuration metadata in the registry. Selfidentification of managed disks ensures that disk controller and other disk reconfigurations or cluster disk ownership transfers are error
free.
Volume mount points. You can use Disk Management to connect to, or mount, a local drive at any empty folder on a local NTFSformatted volume see the subsection "NTFS
Volume Mount Points".
Volume GUIDs support Plug and Play. Unique disk signatures identify both basic partitions and dynamic volumes. Disk signatures associate partitions or volumes with their
assigned logical names. The disk signature lets FT Disk or the LDM accurately identify a partition's or volume's presence or absence in environments that implement Plug and Play
storage devices.
Disk and Volume Management Tasks
The following table lists the specific operations you can perform with the Disk Management snapin:
DISK & VOLUME MANAGEMENT TASKS
Same for basic and dynamic disks
View properties.
Assign, change, or remove a drive letter you cannot change drive letter of system or boot volume
Create a mounted drive partition or volume is assigned a drive path, not a drive letter
Format a partition or volume.
Delete a partition or volume you cannot delete system volume, boot volume, or volume that contains the
active paging file.
Basic Disks
The management tasks listed in the left column are the same on basic disks, except that:
You cannot create new spanned, mirrored, or striped sets on basic disks, and you cannot
extend a spanned volume.
12/8/2014
FileandPrintServicesTechnicalOverview
Create, extend, and delete simple volumes. Simple volumes are the dynamic storage equivalent of Windows NT 4.0 and earlier primary
partitions. When you have only one dynamic disk, the only kind of volume you can create is a simple volume.
Defragmentation Utility
The disk defragmentation utility is another Windows 2000 Server enhancement that improves storage management. The utility tells the file system to move the data from one sector to
another. The fact that the file systemrather than the defragmentation utilitymoves the data makes the system far more robust.
Administrators or users can defragment volumes formatted for FAT, FAT32, or NTFS, which improves performance if the fragmentation is extensive. This utility can operate while the system
is up and running and disks are in active use. You can defragment only local volumes and only one volume at a time.
Remote Storage
The Remote Storage service, which is the Windows 2000 version of Hierarchical Storage Management HSM, helps manage the cost associated with large quantities of data that must be
kept accessible. The Remote Storage hierarchy consists of two layers:
Local storage refers to the NTFS volumes local to the Windows 2000 file server15 hosting the Remote Storage software.
Remote storage refers to data moved from the local hard disk to a remote storage device such as tape that can be recalled whenever needed.
If a file has not been used in the past thirty days, there is a high probability that it will not be accessed again. These infrequently used files consume the majority of disk space, and it is
these files that Remote Storage typically migrates to secondary storage. Remote Storage automatically moves data back and forth between highcost, faster disk drives and lowcost, high
capacity storage media tape library. Remote Storage monitors the amount of space available on local NTFS volumes, and when the amount of free space dips below the needed level,
eligible files are transferred from the hard disk to secondary storage. Yet, the user still sees and can still access these archived files. This frees up storage on the file server without requiring
the purchase and installation of additional hard disks.
Remote Storage storage media are not a substitute for primary backup media. Remote Storage is typically used to migrate infrequently used data, so frequently used data, which is more
likely to be urgently needed, is less likely to be stored on Remote Storage media. The purpose of Remote Storage is to ensure free space on file server volumes, not to protect enterprise
data.
Applications running on NTFS volumes that regularly open many files can cause a great deal of data to be recalled, and thus reduce the efficacy of Remote Storage. For best results, use
Remote Storageaware applications.
Managing Remote Storage
The Remote Storage service is not installed by default when you run Windows 2000 Server setup, but you can choose to install it during setup or afterwards. Before setting up Remote
Storage, you must ascertain that remote storage media are available for it to use. The local disk volumes on the file server that are under Remote Storage control, called managed volumes,
must be nonremovable. Administrators who intend to use data compression on managed volumes should compress the volumes before installing Remote Storage. Administrators who
intend to use content indexing must also first set up Microsoft Indexing Service.
The Remote Storage snapin is comprised of four components, all of which run on both Windows 2000 Server and Windows 2000 Professional the Remote Storage service runs only on
Windows 2000 Server computers, not on Windows 2000 Professional machines, but the Remote Storage user interface runs on both:
Recall Notification user interface. This interface lets an administrator cancel a recall of remote data, if the recall is invoked before the data transfer has started.
Windows Explorer component. Remote Storage adds a new page to the file and directory property sheets accessible through Windows Explorer to represent storage management
http://msdn.microsoft.com/enus/library/cc750353.aspx
21/39
12/8/2014
FileandPrintServicesTechnicalOverview
properties. These pages provide information on migration status, premigrated file data location in remote storage, premigrated date and time, and so on. Users have readonly
access to the new Remote Storage property pages; however, they can force immediate premigration of individual files or entire directories by setting a Premigrate Now option on
the Remote Storage page. For an explanation of premigration, see next subsection.
Disk Management component. This component includes a property sheet showing total used space, free space, premigrated file space, truncated files placeholders, untruncated
file disk usage, premigration space savings, truncated file compression ratio, percent of files that are placeholders, and other volume report information. For an explanation of
premigration, truncation, and placeholders, see the next subsection.
Remote Storage snapin. You can use the Remote Storage snapin one of the Administrative Tools, once it is installed to establish the following two administratordefined
guidelines for a managed volume:
Desired Free Space. This specifies the amount of free space to be kept on the managed volume and triggers an automatic file truncation when the free space is too low.
File Selection Criteria. This specifies which files can be migrated to secondary storage. These settings include minimum file size and time elapsed since the file was last accessed.
You can also specify file inclusion and exclusion rules. For example, you might specify that only files not accessed for at least three days should be migrated, and that executable files
should be excluded from migration. Remote Storage cannot copy hidden, system, extended attribute, encrypted, or sparse files to remote storage. The selection criteria decision
engine is extensible using a Component Object Model COM interface.
Premigration, Truncation, and Placeholders
Remote Storage scans a managed volume periodically for eligible data, premigrates copies eligible files to secondary storage, and attaches an NTFS reparse point to each copied file, but
it does not otherwise modify the file at this point. More frequently than the scan that results in the copying of eligible files, Remote Storage also checks whether free space on the volume is
at or above the specified threshold. If it drops below the threshold, Remote Storage then creates free space by truncating files that have already been premigrated to secondary storage.
Before each file is truncated, Remote Storage uses the NTFS Change Journal to determine whether the data in secondary storage still represents the data in primary storage primary
storage refers to the NTFS volume local to the server running Remote Storage or mapped locally to that server by Dfs. If the primary data has changed, the file is not truncatedit is no
longer considered premigrated and is returned to normal status.
After a file is truncated, what remains on the primary storage deviceso that migrated files can be viewed in directories and recalled as neededis an NTFS file, called a placeholder. The
placeholder points to the complete copy now in remote storage. A placeholder has the systemdefined $REPARSE POINT attribute set with information that can identify and retrieve the
data from remote storage. The placeholder is marked FILE_ATTRIBUTE_OFFLINE. Although Remote Storage has changed the physical size of the file on local storage, the file's logical size
and the date/time create, last modified, last accessed remain unchanged.
When a user or application reads, writes, or makes a memory map request for a truncated file, Remote Storage recalls the removed data from secondary storage and reconstructs the
primary data stream. This operation is transparent to users and to applications for example, it does not affect the Windows 2000 disk quotas feature, which monitors and limits disk space,
except that I/O operations are blocked for several minutes until the requested data has been restored from tape.
Remote Storage initiates Automatic File Truncation whenever a managed volume's free space level goes below the specified Desired Free Space setting. You can also force the truncation of
premigrated files to placeholders using Schedule File Truncation. In this case, premigrated files that have not been modified, and that meet the File Selection Criteria, are truncated
regardless of the volume's free space level. You might do this in advance of a volumeintensive event, such as the installation of a large application.
In addition, you can use Validate Managed Files to ensure that all files on your managed volumes point to valid data in remote storage. Validation also detects files that have been moved
from one local volume to another, or that have been modified. Validation is automatically performed two hours after a backup program is used to restore a remote storage file. You should
also perform validation on a regular basis to correct inconsistencies, especially after restoring files on a local volume or after disk errors have occurred on a volume.
You can rename premigrated files and placeholders only on the same volume. Renaming does not cause the data to be recalled. If you copy or move placeholders between volumes, the
data is recalled and the entire file including the migrated data is copied. At the completion of a move operation, the original placeholder file is deleted. You can also move a placeholder
to another volume on the same system by using Windows 2000 Backup to backup the placeholder and then restore it to another volume. In this case, the moved placeholder correctly
points to remote storage and can initiate a recall.
http://msdn.microsoft.com/enus/library/cc750353.aspx
22/39
12/8/2014
FileandPrintServicesTechnicalOverview
Removable Storage
The new Windows 2000 Removable Storage service manages removable storage media tapes and optical disks and robotic storage libraries attached to a computer running Windows
2000 Server or Professional. Removable Storage moves media around within and between libraries and controls access to that media. Removable Storage consists of a user interface
implemented as an MMC snapin, a Windows 2000 service with API, and a database.
Removable Storage lets administrators perform the following tasks:
Create media pools groups of media and set media pool properties.
Insert and eject media in a robotic library.
Mount and dismount media.
View the operations state of media and libraries.
Perform library inventories.
Set security parameters for users.
http://msdn.microsoft.com/enus/library/cc750353.aspx
23/39
12/8/2014
FileandPrintServicesTechnicalOverview
Figure 8 illustrates the components of Removable Storage, managed devices, and Windows 2000 Server. Windows 2000 Removable Storage components are shown in white.
24/39
12/8/2014
FileandPrintServicesTechnicalOverview
status information.
25/39
12/8/2014
FileandPrintServicesTechnicalOverview
Data management applications use media pools to gain access to specific tapes or disks within libraries managed by Removable Storage.
Media pools control the selection of media and media type, let media be shared across applications Removable Storage moves media between media pools to provide the amount of data
storage an application requires, and track such sharing. Four types of media pool existthree types of system media pool and one type of application media pool. Removable Storage
creates system media pools for its own use. Applications create application media pools to group media, a feature that is especially important when several applications are sharing the
libraries attached to a system.
Access permissions associated with each media pool control access to the media that belong to that pool. These permissions control the manipulation of the media; they do not control
access to the data on the media.
The functions of each type of media pool are as follows:
System: Unrecognized media pools are a temporary holding place for new blank but unrecognized media. If Removable Storage does not recognize the media's format, it adds
the media to the unrecognized pool. You should move a new medium from an unrecognized media pool to a free media pool so that the medium can be used by applications, or
remove it from the library if placed there in error.
System: Import media pools are a temporary holding place for media newly added to the system for which Removable Storage can identify the format or associated application.
They contain media that Removable Storage recognizes in the database but that have not been used before in a particular Removable Storage system. For example, if you put a tape
written by Backup on one system into a library attached to a second system, the instance of Removable Storage on the second system recognizes that the tape was written using
Microsoft Tape Format MTF and places it in the proper media type import pool.
System: Free media pools contain media that are not currently in use by applications and are therefore available to any application.
Application: Application media pools are created by administrators or by data management applications. Applications that use media managed by Removable Storage create
application pools to hold media for their own use. For example, the Windows 2000 Server Backup utility and its Remote Storage service each creates its own application pool.
Applications move media from the import or unrecognized media pools into either the system free pool or into an application pool.
A media pool can contain media, or it can contain other media pools. Removable Storage uses this hierarchical capability for its system pools. For example, within the free pool is a media
pool for each media type. An application can group media of several types into one collection by creating an application media pool for the whole collection and additional media pools
within it, one for each media type.
Work Queue
When applications make a library request, Removable Storage places these requests in a queue and processes them as resources become available. For example, a request to mount a tape
in a library results in a mount work queue item, which, if necessary, waits until a drive is available to process the request.
Operator Requests
Even with robotic libraries, manual assistance is sometimes required to complete a request or to perform maintenance. For example, if an application requests that a medium in the offline
media physical location be mounted, Removable Storage generates a request to the operator to enter the cartridge.
Security
To provide security for itself, media pools, and libraries, the Removable Storage service contains an access control list ACL that controls who can connect to the services and who can work
with operator requests. In addition, each library and pool has an ACL that governs who can perform specific tasks.
For detailed information about Removable Storage, see "Data Storage and Management" in the section "For More Information."
http://msdn.microsoft.com/enus/library/cc750353.aspx
26/39
12/8/2014
FileandPrintServicesTechnicalOverview
Disk Quotas
Disk quotas, a new feature for NTFS 5 volumes, provide enhanced control of networkbased storage in a distributed environment. Disk quotas give administrators a powerful tool for
managing storage growth.
Members of the Administrators Group can see a Quota tab on the Properties dialog box of an NTFSformatted volume. You can use this tab to set disk quotas to monitor and limit disk
space use on NTFS volumes on a peruser basis. You can set disk quotas on both local and remote volumes. Quotas are tracked independently for different volumes, even if the volumes
are different partitions on the same physical drive. However, if you have shares on the same volume, the quotas assigned to that volume apply to all of these shares collectively, and users'
utilization of the shares cannot exceed the assigned quota on that volume.
Disk quotas apply only to volumes and are independent of folder structures. That is, if a user moves a file from one folder to another on the same volume, volume space usage does not
change. But if the user copies the file to a different folder on the same volume, the volume space usage doubles.
Within the NTFS file system, volume usage data is stored by user security ID SID, not by user account name. Administrators can set two values: a warning threshold and a hard quota.
Using the warning threshold is useful when tracking disk space use on a peruser basis is the goal rather than limiting disk space usage. In this case, once the warning level is reached, you
can have the system generate a system log file entry without sending an error message.
Once the hard quota limit is reached, the user cannot move or copy any more data onto the storage device, just as if the user had really run out of disk space. You can configure the system
to log an event and return an "insufficient disk space" error when the user has hit his or her quota limit. When this happens, the user cannot write additional data to the volume without
first deleting or moving files.
When you enable disk quotas, you can set both the disk quota limit and the disk quota warning level.
When you enable disk quotas for a volume, volume usage is automatically tracked for new users a new user receives the default quota unless you establish a quota specifically for that
user, but existing volume users have no disk quotas applied to them. You apply disk quotas to existing users by adding new quota entries in the Quota Entries window on an NTFS volume.
Besides being able to implement the quota on an individual user basis, you can use group policy to set the disk quota globally. For where to find information about using Windows 2000
group policy settings, see the section "For More Information."
On a computer configured to dual boot Windows NT Server 4.0 and Windows 2000 Server, users can exceed their limit when running Windows NT Server 4.0. However, when the user
subsequently runs Windows 2000 Server, he or she must then move files to a different partition or delete files to accommodate the quota limitation.
Windows system files are included in the volume usage of the person who installed Windows on the local computer. If a nonadministrator user has installed Windows on his or her
machine, an administrator setting a disk quota for that user should take into account the disk space used by the Windows files. This is not a concern if an administrator installed Windows,
because administrators cannot be denied disk space use even if they surpass their disk quota limit.
Setting disk quotas can cause a slight reduction in the performance of the file server, so you may choose to periodically enable and then disable quotas. After enabling disk quotas for a
period of time, you can contact users who are using more disk space than they should.
The disk quota feature includes other storage featuressuch as Remote Storage and sparse filesin its calculations. File compression does not affect quota statistics.
The introduction by Windows 2000 Server of Dfs, NTFS directory junctions, and volume mount points means that logical directories do not necessarily belong to the same physical volume.
For administrators and application developers, this means that disk space should not be assumed based on space queries made in directories other than the current one.
27/39
12/8/2014
FileandPrintServicesTechnicalOverview
SIS consists of a base tracking service, a kernelmode file system filter driver, reparse points, and sparse files. SIS replaces the duplicate files with a sparse file and an SISspecific reparse
point. The file containing the actual data is renamed with a 128bit globally unique identifier GUID when it is migrated to the common store.
28/39
12/8/2014
FileandPrintServicesTechnicalOverview
versions.
Printing Services
A print server can be any computer running Windows 2000 Server or Windows 2000 Professional that manages printers, or it can be a specialized print server unit. A printer can be
connected to a server, a client computer, or directly to the network. However the printer is connected, it is software on the print server that makes the physical printer visible to the network
and that accepts print jobs from client computers.
As with file servers, administrators typically install print servers as member servers rather than domain controllers to avoid the administrative overhead associated with the logon and
security roles performed by a domain controller. Often, one server acts as both file and print server.
With Windows 2000 Server, organizations can share printing resources across their entire network. Clients on a variety of platforms can send print jobs to printers attached locally to a
Windows 2000 print server, across the Internet/intranet, or to printers connected to the network using internal network interface cards, external network adapters, or another server.
Printing features that Windows 2000 Server carries over from Windows NT include:
Printer pools. One logical printer printing software component on the print server, represented by the print icon is set up to send a print job to the first available member of this
group of identical physical printers.
Printer priority. When several logical printers are set up to send print jobs to one physical printer, an administrator can establish which print jobs take precedence.
Printing improvements introduced by Windows 2000 Server include the following:
More printers supported
Easier installation of local printers Plug and Play
More types of clients
Enhanced printing features
http://msdn.microsoft.com/enus/library/cc750353.aspx
29/39
12/8/2014
FileandPrintServicesTechnicalOverview
30/39
12/8/2014
FileandPrintServicesTechnicalOverview
To avoid having to reboot the computer when you connect a parallel printer, use a printer manufactured to include hot swapping technology.
Infraredenabled IR port printers. Infraredenabled printers are also Plug and Play installed, assuming the printer and computer are within one meter of the infrared transceiver
in the computer. If the system is not infraredenabled, you can add the infrared transceiver from the Add Hardware wizard. Once that is done, the IR port automatically appears in
the list of printer ports, and Plug and Play installation of printers triggers automatically.
NonPlug and Play printers. Printers connected through a serial port COM port and printers connected directly to the network with a Network Interface Card are not Plug and
Play and are not detected or installed automatically. You must install these printers using the Add Printers wizard.
http://msdn.microsoft.com/enus/library/cc750353.aspx
31/39
12/8/2014
FileandPrintServicesTechnicalOverview
32/39
12/8/2014
FileandPrintServicesTechnicalOverview
User Settings
The ability to change personal document defaults already available for Windows 95/98 users has now been extended to Windows 2000 Server and Windows 2000 Professional clients. In
Windows NT Server 4.0 and earlier, only an administrator could modify global document settings.
http://msdn.microsoft.com/enus/library/cc750353.aspx
33/39
12/8/2014
FileandPrintServicesTechnicalOverview
http://msdn.microsoft.com/enus/library/cc750353.aspx
34/39
12/8/2014
FileandPrintServicesTechnicalOverview
Internet Printing
The Windows 2000 Server printing architecture is now seamlessly integrated with the Internet:
URL format for printer name. When installing a printer from the Internet, the printer's Uniform Resource Locator URL is the name of the printer. Administrators can also choose
to use the URL format within an intranet. For a Windows 2000 Serverbased server to process print jobs that contain URLs, it must be running IIS. For print servers implemented on
Windows 2000 Professional, Microsoft Peer Web Services PWS must be running.
IIS or PWS print server security. Print server security is provided by IIS or PWS. To support all browsers and all Internet clients, you must choose basic authentication. Basic
authentication also called cleartext authentication encodes the user name and password data transmissions, but can be decoded by anyone with a freely available decoding utility.
Alternatively, for more restricted security, you can specify one of the following:
Microsoft challenge/response authentication, which encrypts communication between a host server and client and is supported by Internet Explorer.
Kerberos authentication, which is the basis of Windowsbased security for both internal and intranet logon and is also supported by Internet Explorer.
Digest authentication, which sends the user name and password information over the network as a hash value. A hash message authentication code is an IP security
function that verifies that the information received is identical to the information that was sent.
Secure Sockets Layer SSL 3 authentication, which was developed by Netscape for transmitting private documents over the Internet.
Web pointandprint. Users on Windows 2000 or Windows 95/98 client computers can connect to printers on the network using Web pointandprint for singleclick installation of
a printer shared by a Windows 2000 Serverbased server.
Use a URL to print. Users can print over the Internet or an intranet from a Windows 2000 Server or Professional or Windows 95/98 with at least Internet Explorer 4 client to a
Windows 2000 print server using a URL. For example, a mailorder company can send its new catalog directly to the publisher's printer, provided they have permission from the
publisher and the URL of the publisher's printer.
View or connect to printer from browser. Administrators or users can view and manage printers from any browser. They can pause, resume, or delete a print job and can view the
printer and print job's status from any browser. In addition, if they use Internet Explorer IE version 4.0 or higher, they can connect to a printer using a browser.
Top Of Page
http://msdn.microsoft.com/enus/library/cc750353.aspx
35/39
12/8/2014
FileandPrintServicesTechnicalOverview
Incremental Deployment
The interoperability features of Windows 2000 Server lets member servers coexist in today's Windows NT 3.51 and Windows NT 4.0 server environments, providing customers with the
flexibility to do the following:
Perform server upgrades in incremental stages.
Implement specific Windows 2000based services and stabilize them.
Upgrade to Windows 2000 Server at their own pace.
For customers who are already running Windows NT Server 3.51 or 4.0, a good starting point is to upgrade existing Windows NT file and print member servers as well as Web servers. File
servers can experience a considerable increase in file access, and print servers can gain significant performance improvement. In addition to improved performance, upgrading an older file
or print server also improves manageability immediately for organizations not yet ready to implement an infrastructurewide deployment of Active Directory.
Once file and print member servers have been upgraded to Windows 2000 Server and the new NTFS 5 file system, an organization can take immediate advantage of several enhanced file
and print services even while continuing to run these machines in a Windows NT 3.51 or 4.0 domain. The Windows 2000 setup process automatically upgrades NTFS 4 volumes on
Windows NT machines to NTFS 5; installers can choose to upgrade FAT16 or FAT32 volumes.
Key new features offered by the new Windows 2000 Serverbased member servers running in the existing Windows NT environment include:
File services in a Windows NT environment. Disk quota management, content indexing, and distributed link tracking each described earlier in this paper become operational.
Print services in a Windows NT environment. Internet Printing Protocol IPP is available.
Summary
Fast file and printer sharing are network services that virtually all users require on an internal network. The Windows 2000 Server operating system has updated many features of traditional
file and print services and has added new ones. Information search and retrieval capabilities have also been expanded. In addition, Windows 2000 Server includes a new dynamic disk
architecture and significant new and improved storagerelated capabilities. Organizations can take advantage of several new features if they use Windows 2000 file and print servers in a
Windows NTbased or other legacy network, and they acquire additional new features when they upgrade to a Windows 2000 Serverbased network.
All of these changes have been made with both network administrators and application developers in mind. Network administration is more efficient, and the open architecture of
http://msdn.microsoft.com/enus/library/cc750353.aspx
36/39
12/8/2014
FileandPrintServicesTechnicalOverview
Windows 2000 Server is designed to facilitate thirdparty developers' efforts to provide additional functionality in response to evolving business needs.
Where Available
http://www.microsoft.com/windows2000/techinfo/howitworks/activedirectory/adarch.asp
"Group Policy"
http://www.microsoft.com/windows2000/techinfo/howitworks/management/grouppolicy.asp
EFS
http://www.microsoft.com/windows2000/techinfo/howitworks/security/encrypt.asp
http://technet.microsoft.com/enus/desktopdeployment/default.aspx
http://msdn.microsoft.com/library/psdk/winbase/fsys_538t.htm
Currently scheduled to be published by Microsoft Press in the first half of the year 2000. Also
located on the Windows 2000 Server and Advanced Server CDs as part of Support Tools.
http://www.microsoft.com/windows2000/techinfo/howitworks/fileandprint/storage.asp
Currently scheduled to be published by Microsoft Press in the first half of the year 2000. Also
located on the Windows 2000 Server and Advanced Server CDs as part of Support Tools.
You can find the Hardware Compatibility List Hcl.txt on the root directory of the Windows 2000
compact disk, or online at
http://www.microsoft.com/windows2000/server/howtobuy/upgrading/compat/default.asp
Storage Information
http://msdn.microsoft.com/enus/library/cc750353.aspx
37/39
12/8/2014
FileandPrintServicesTechnicalOverview
http://msdn.microsoft.com/default.asp
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook/cookintr.mspx
http://crk/docs/GettingReady/DeploymentAids/Upgrading_FPW.doc
Windows NT MixedMode
and Migration Information
1 Windows 2000 introduces the Microsoft Management Console MMC, which is a framework for hosting administrative tools called snapins. The main MMC window provides commands
and tools for authoring consoles.
2 In Windows NT version 4.0 and earlier, the Macfile program handled Macintosh file administration, including the creation of Macintosh volumes, passwords, security options, user limits,
and permissions. You accessed the Macfile menu from Control Panel, File Manager, and Server Manager.
3 Note that site topology refers to Active Directory replication topology both within a site within a LAN and between sites within a WAN. Although Dfs makes use of site topology set up
for Active Directory replication, Active Directory replication itself is unrelated to Dfs replication. Active Directory replication replicates network objects, whereas Dfs replication replicates Dfs
shared folders and files. For more about Active Directory replication, see the "For More Information" section at the end of this paper.
4 For a standalone Dfs root, the one and only copy of the PKT is stored on the server itself.
5 Domain controllers which, by definition, have Active Directory installed use multimaster replication separate from the multimaster replication used by FRS, described below to replicate
and synchronize Active Directory objectsincluding the PKT which stores Dfs topology informationamong peer domain controllers, each of which has a readandwrite copy of the
directory. This is a change from Windows NT Server 4.0, in which only the Primary Domain Controller PDC had a readandwrite copy of the directory the Backup Domain Controllers, or
BDCs, received readonly copies from the PDC. For more about Active Directory replication, see the white paper Active Directory in the section "For More Information" at the end of this
paper.
6 Active Directory replication is a multimaster objectbased replication service.
7 Client improvements in Windows 2000 Dfs depend on the host platform.
8 You can encrypt or decrypt files and folders located on a remote computer that has been enabled for remote encryption. However, if you open the encrypted file over the network, the
data that is transmitted over the network by this process is not encrypted. Other protocols, such as Secure Sockets Layer/ Private Communications Technology SSL/PCT or Internet
Protocol Security IPSEC must be used to encrypt data over the wire.
9 COM lets programmers develop objects that can be accessed by any COMcompliant application.
10 The NTFS Journal is also referred to as the Reliable Change Journal or Change Log not to be confused with the NTFS recovery log, which is a log of disk activities that helps you restore
information quickly in the event of power failure or other system problems.
11 OEM also called valueadded reseller stands for original equipment manufacturer. OEMs buy computers in bulk and customize them for a particular application. They then sell the
customized computer under their own name. The term can be confusing because OEMs are not the original manufacturersthey are the customizers.
http://msdn.microsoft.com/enus/library/cc750353.aspx
38/39
12/8/2014
FileandPrintServicesTechnicalOverview
12 ISO, though not an acronym, stands for the International Organization for Standardization, an international organization that defines standards for designing networks.
13 OSTA is an international trade association that promotes the use of writeable optical technology for storing computer data and images.
14 DVD is a new type of CDROM that supports disks with capacities from 4.7 GB to 17 GB. DVD drives are backward compatible with CDROMs; that is, they can play old CDROMs, CDI
disks, and video CDs as well as the new DVDROMs.
15 Windows 2000 Server offers Remote Storage; Windows 2000 Professional does not. Remote Storage does not support clustering.
16 Founded in 1918, ANSI is a voluntary organization composed of over 1,300 members including all the large computer companies that creates standards for the computer industry.
17 OSI is an ISO standard for worldwide communications that defines a networking framework for implementing protocols in seven layers.
Top Of Page
2014 Microsoft
http://msdn.microsoft.com/enus/library/cc750353.aspx
39/39