
542
Configuring the File Server Role
Table 5-3 Special Shares
Share Name Description
drive$
The root directory of a drive.
ADMIN$
Used for remote administration of a computer. This share
points to the operating system folder (usually,
C: \Windows).
IPC$
Used by named pipes, a programming feature that lets pro-
cesses communicate with one another.
NETLOGON
Required in order for domain controllers to function.
SYSVOL
Another required domain controller share.
PRINT$
Used for remote administration of printers.
FAX$
Used by fax clients.
Notice that some of the special shares end with a dollar sign ($). These
shares are hidden shares that aren’t visible to users. However, you can still
access them by typing the complete share name (including the dollar sign)
when the share is needed. For example, the special share C$ is created to
allow you to connect to the root directory of the C: drive from a network
client. You wouldn’t want your users to see this share, would you? (Of
course, shares such as C$ are also protected by privileges so that if an
ordinary user finds out that C$ is the root directory of the server’s C: drive,
he or she still can’t access it.)
Configuring the File Server Role
To use Windows Server 2003 or 2008 as a file server, you must first enable
the file server role. In Windows Server 2003, you can do so by running
Manage Your Server (choose Start➪Administrative Tools➪Manage Your
Server). Then, choose Add or Remove a Role and select the File Server
role. In Windows Server 2008, choose Start➪Administrative Tools➪Server
Management, choose Roles, and then enable the File Services role.
Managing Your File Server
Windows Server 2008 includes a useful new management console called
Share and Storage Management, as shown in Figure 5-1. From this console,
you can easily create new shares, set up the permissions for a share,
remove a share, and so on. To summon the File Server Manager, choose
Start➪Administrative Tools➪Share and Storage Management.
53_625873-bk07ch05.indd 54253_625873-bk07ch05.indd 542 9/21/10 10:39 PM9/21/10 10:39 PM