Finally, you can log on to the server using the Administrator user name and password.com-Initial Configuration After you have completed the Windows Server 2003 installation, the server s
Trang 1◆ UPN (user principal name) —The preferred naming convention for users in e-mail
and related Internet services A user’s UPN looks like a familiar Internet address,including the positioning of the domain name after the @ sign When you create a
user account, the user’s logon name is added to a UPN suffix, the portion of the
user’s UPN that follows the @ sign A user’s default UPN suffix is the domain name
of her root domain For example, if Mary Smith’s user name is msmith and her rootdomain is trinketmakers.com, her UPN suffix is trinketmakers.com, and her UPN is
msmith@trinketmakers.com.
In addition to these names, each object has a GUID (globally unique identifier), a 128-bit
number that ensures that no two objects have duplicate names The GUID is generated andassigned to an object upon its creation Rather than use any of the alphabetical names, networkapplications and services communicate with an object via the object’s GUID
Now that you have been introduced to the Windows Server 2003 Active Directory structureand naming conventions, you are ready to learn about installing the NOS
Planning for Installation
When installing and configuring an NOS, you must create a plan for your server and its place
in your network before you insert the installation CD You need to consider many factors,including organizational structure, server function, applications, number of users, LAN archi-tecture, and optional services (such as remote access) when developing this plan After you haveinstalled and configured the NOS, changing its configuration may prove difficult and cause ser-vice disruptions for users To begin, first ensure that your server hardware meets the WindowsServer 2003 requirements (see Table 8-2) Next, you must prepare answers to the following list
of critical preinstallation decisions
FIGURE 8-15 Distinguished name and relative distinguished name
Trang 2◆ How many, how large, and what kind of partitions will the server require? Windows
Server 2003 must be installed on a single partition When you install it, you willhave a choice of:
◆ Creating a new partition on a nonpartitioned portion of a hard disk
◆ Creating a new partition on a partitioned hard disk
◆ Installing Windows Server 2003 on an existing partition
◆ Removing an existing partition and creating a new one for installationThe option you choose will depend on how your server is currently partitioned, whether youwant to keep data on existing partitions, and how you want to subdivide your server’s harddisk If you know the number and size of the partitions you need (for example, on a 16-GBhard disk you might want to create a 6-GB system partition and a 10-GB data partition), it isbest to create them during installation
◆ What type of file system will the server use? Recall that the optimal file system for a
Windows Server 2003 computer is NTFS Choose NTFS unless your applicationsrequire a different file system NTFS must be used if you intend to use ActiveDirectory and the domain model for centralized resource and client management
◆ What will you name the server? You may use any name that includes a maximum of
15 characters, and that includes numerals, letters, and hyphens, but no spaces, ods, or other special characters (for example, ? or =) Choose a practical, descriptivename that distinguishes the server from others and that is easy for you and yourusers to remember For example, you might use geographical server names, such asBoston or Chicago Alternatively, you might name servers according to their func-tion, such as Marketing or Research If the server is a member of a large domain,you might identify it in relationship to its domain name For example, the Market-ing server in the Pittsburgh domain might be called Mktg-Pitts
peri-◆ Which protocols and network services should the server use? Before you begin installing
Windows Server 2003, you need to know which protocol (or protocols) your networkrequires On Windows Server 2003, TCP/IP is the default protocol, and depending onyour circumstances, you should probably leave it as such If your server runs Web services
or requires connectivity with UNIX, Linux, or Mac OS X Server systems, you must run
TCP/IP If your Windows Server 2003 must communicate with an older NetWareserver that relies on IPX/SPX, you should also install the NWLink IPX/SPX Com-patible Protocol and Gateway Services for NetWare For communication with Mac-intosh computers running the AppleTalk protocol, you need to install AppleTalk
◆ What will the Administrator password be? Use a strong password—in other words, one
that is difficult to crack In Windows Server 2003, network administrators canrequire users to choose stronger passwords than ever, which means, among otherthings, they must include a mix of different characters, including numbers, uppercase
letters, lowercase letters, and special characters (such as *, & !, @, and so on), and
they cannot contain any part of the user’s name, nor can they resemble any knownEnglish words The strongest passwords are also the longest The Administratorpassword should meet the most stringent criteria
Chapter 8 393
PLANNING FOR INSTALLATION
NET+
3.1
Trang 3◆ Should the network use domains or workgroups, and, if so, what will they be called? First
decide whether your network will use workgroups or domains During installationyou will be asked whether the server should join an existing workgroup, be a newworkgroup server, or join an existing domain As you learned, in a workgroup situa-tion, computers share network access in a peer-to-peer fashion It is more likely thatyour environment will require domains, in which the security for clients andresources is centralized If the server will be joining an existing domain, you mustknow the domain name, domain controller name, and the DNS server name.Domain names should describe the logical group of servers and users they support.You may use any name that includes numerals, letters, and hyphens, but no spaces,periods, or other special characters (for example, ? or =) Popular schemes for namingdomains incorporate geography and function into the names For example, in adomain model for a WAN spanning several cities, you might want to name yourdomains Boston, Chicago, Detroit, Pittsburgh, and so on In a very large organiza-tion, you may want to use a less limiting convention For example, if your company’sbusiness is chemical production, you might want to name your domains Hydrocar-bons, Resins, Solvents, and so on
◆ Will the server support additional services? During installation, you will be asked to
choose which services your server will support Of course, you must install certainprotocols and network services in order for clients to access the server You may alsowant to install optional services, such as: Remote Installation Services, TerminalServer, Windows Media Services, and Management and Monitoring Tools
Although it’s easiest to include additional services during the original installation,they can be added later as well
◆ Which licensing mode will you use? You may choose one of two licensing modes: per
seat or per server The per server licensing mode allows a limited number of clients
to access the server simultaneously (The actual number is determined by your dows Server 2003 purchase.) In per server mode, any of your organization’s clientsmay be capable of connecting to the server The number of concurrent connections
Win-is restricted Per server mode Win-is a popular choice in organizations that have a limitednumber of servers and many users, or where multiple users share workstations (forexample, a mail-order catalog’s call center) The per seat mode requires a license forevery client capable of connecting to the Windows Server 2003 In environmentsthat include multiple Windows Server 2003 computers and in which each user hashis own workstation, this choice is probably more economical than per serverlicensing
If you are running Windows Server 2003 as a Web or FTP server for anonymousclients (for example, Internet users from anywhere in the world), you do not needseparate Windows Server 2003 client licenses for these types of clients
NOTE
NET+
3.1
Trang 4◆ How can I remember all of this information? As you make these preinstallation
deci-sions, you should note your choices on a server installation form and keep the formwith you during installation Appendix D offers an example of such a form
The preceding list describes only the most significant installation options You should also beprepared to:
◆ Read and accept the license agreement
◆ Identify your organization
◆ Provide your Product Key (which can be found on the jacket of your Windows
Server 2003 CD-ROM)
◆ Select the appropriate time and date
◆ Specify display settings
◆ Identify and supply drivers for hardware components, such as video cards, NICs,
printers, and so on
If you are upgrading a server that currently runs an older Windows NOS, such as Windows
NT or Windows 2000 Server, you will have to follow a special upgrade process, as described
in the Microsoft documentation The following section walks you through a new WindowsServer 2003 installation
Installing and Configuring a Windows
Server 2003 Server
After you have devised a plan for your Windows Server 2003 installation, you can begin theactual installation process In this section, you will learn about the available options and thedecisions you must make when installing and initially configuring your Windows Server 2003server
The Installation Process
You can install Windows Server 2003 from a CD-ROM or remotely over the network If youuse the network method, be aware that this type of installation generates a high volume of net-work traffic and shouldn’t be performed while clients are attempting to use the network Youalso have the choice of performing a Windows Server 2003 installation in attended or unat-tended mode The term “attended mode” simply means that someone is at the computerresponding to installation prompts as they appear Unattended mode relies on a preprogrammedscript (which can be customized for different environments) to answer installation prompts.This mode prevents the need for a network administrator to be present during server installa-tion However, creating the script requires forethought and preparation
Now that you understand the variables and considerations for a Windows Server 2003 lation, you are prepared to install the NOS Following is a summary of the process, which
Trang 5assumes an attended installation using a CD-ROM (in other words, somebody will be ing to prompts, rather than allowing a script to respond to prompts automatically) It repre-sents a typical, simple installation for a small or home office The options you choose and theprompts you see during installation will depend on your network environment and your pre-installation decisions The time your installation requires will also depend on the options youchoose, in addition to your server’s processor speed and amount of memory.
respond-Insert the Windows Server 2003 CD-ROM in your server’s CD-ROM drive and restart theserver (making sure your computer is configured to boot from a CD-ROM) After booting,you may be prompted to press any key to install Windows Server 2003 After you press a key,the Windows Setup screen appears, and installation will proceed, with prompts, to:
◆ Inspect your hardware and load appropriate hardware drivers and other files
◆ Display the Windows Licensing Agreement, which you should read and then pressthe F8 key to accept if you want to continue
◆ Search the hard disk to determine whether any previous versions of Windows areinstalled
◆ Scan the hard disk to assess how many partitions and what type of partitions areavailable
◆ Select a partition for Windows Server 2003 installation (at this point, you may alsocreate a new partition or delete an existing partition)
◆ Format the disk partition you selected
◆ Copy files to the Windows installation folders on the hard disk
After the Windows installation files are copied to your server’s hard disk, the Setup processhas finished preparing your computer for the Windows Server 2003 installation Your com-puter restarts and returns to a graphical user interface screen During the next part of theprocess, you are prompted to:
◆ Customize regional and language options, which include how numbers should beformatted and what languages you want Windows Server 2003 to support
◆ Personalize your software by entering your name and your organization’s name
◆ Enter the 25-character Product Key that appears on your CD-ROM folder
◆ Select the licensing mode you want to use—either Per Server, Per Device, or PerUser
◆ Assign a name to your server and enter (and confirm) the password associated withthe Administrator user account
◆ Enter modem dialing information
◆ Enter date and time settings
◆ Choose whether you want to use typical network settings or manually configure yourserver’s networking components
◆ Indicate whether the server is part of a workgroup or a domain
NET+
3.1
Trang 6After gathering the preceding information, the setup program installs and registers the ponents you’ve selected, installs Start menu items, saves settings, and removes the temporaryfiles created during installation Then, your system restarts (or prompts you to click Finish torestart) Finally, you can log on to the server using the Administrator user name and password.
com-Initial Configuration
After you have completed the Windows Server 2003 installation, the server still isn’t ready tosupport clients on a network First, you must configure the software (for instance, assign it arole in the domain, if your network follows the domain model) The first time you log on tothe server using the Administrator ID, the Manage Your Server window will open, as shown
in Figure 8-16 Here you can establish the server’s role For example, you can designate theserver as a file server, print server, mail server, terminal server, and so on
Chapter 8 397
INSTALLING AND CONFIGURING A WINDOWS SERVER
FIGURE 8-16 Manage Your Server window
Suppose you want to assign the role of file server to a newly installed Windows Server 2003computer In that case, you would follow these steps:
1. If the Manage Your Server window is not open, click Start, and then click Manage
Your Server The Manage Your Server window opens.
2. Click Add or remove a role The Configure Your Server Wizard window opens,
reminding you to make sure that all of the server’s peripherals are installed, that it isconnected to the network and to the Internet, if Internet access is desired, and thatyou have the Windows Server 2003 installation CD handy
3. Click Next to continue.
NET+
3.1
Trang 74. The Configure Your Server Wizard detects your network connection settings Then, itprompts you to select the server’s role from a list of possibilities.
5. Click File server, then click Next to continue.
6. The Configure Your Server Wizard prompts you to set default disk quotas (a limit onhow much of the server’s hard disk space users’ personal files can occupy) for new
users, if desired After you have made your choice, click Next to continue.
7. Next, you are prompted to choose whether you want to enable the File Server ing Service, which allows users to search indexed files for specific words or characters.(By default, the Indexing Service is turned off.) After making your selection, click
Index-Next to continue.
8. Finally, you are presented with a summary of your selections Confirm that the
selec-tions are correct, and then click Next to continue.
9. The Share a Folder Wizard appears, prompting you to establish shared folders on the
server Click Next to continue.
10. Specify a folder path for the folder you want to share For example, you might want toshare the folder called “C:\Documents and Settings\All Users\Documents.” Then
click Next to continue.
11. You are prompted to name the share you have just created and, if you desire, provide adescription For example, you could name the share “Public documents” and enter a
description of “A directory available for file sharing among all users.” Click Next to
continue
12. The Share a Folder Wizard prompts you to indicate users’ permissions to the folder.The default selection allows users read-only access to files in the folder, as shown inFigure 8-17 (“Read-only access” means that users can view data files and execute pro-gram files within a folder, but they cannot modify, delete, or add files.) If you want
users to be able to save files to the folder, you could choose Administrators have full access; other users have read and write access Click Finish to continue.
FIGURE 8-17 Specifying permissions in the Share a Folder Wizard
NET+
3.1
Trang 813. The next screen announces that “Sharing was Successful.” Click Close to close the
Share a Folder Wizard
14. The Configure Your Server Wizard announces that “This Server is Now a File
Server.” Click Finish to close the wizard.
15. You have now made it possible for users to share files on this server In the next tion, you will learn how to create user accounts and make users part of a group
sec-Establishing Users and Groups
The installation process creates two accounts: Guest and Administrator The Guest account is
a predefined user account with limited privileges that allows a user to log on to the computer
The Administrator account is a predefined user account that has the most extensive privileges
for resources both on the computer and on the domain that it controls (if it is a domain troller) These two predefined user accounts are designed primarily to allow you to log on to acomputer after installation and before you have created any additional user accounts The Guestand Administrator accounts cannot be deleted; however, they may be disabled
con-Chapter 8 399
INSTALLING AND CONFIGURING A WINDOWS SERVER
To enhance security, at some point you should create a new user account withadministrative privileges to perform network administration, and disable the Adminis-trator user account If you keep the Administrator account active with full privileges,hackers have half the information they need to break into your system
To create a domain user account:
1. Make sure you are logged on as Administrator
2. Click Start, point to All Programs, point to Administrative Tools, and then click
Active Directory Users and Computers The Active Directory Users and Computers
snap-in opens
NET+
3.1
Trang 93. Double-click the Active Directory container in which you want to create the newuser This may be a domain or an OU.
4. Right-click the Users folder, point to New on the shortcut menu, and then click User The
New Object - User dialog box opens, as shown in Figure 8-18
5. Type the user’s last and first name in the appropriate text boxes You then see theuser’s full name in the Full name text box
6. Enter a user name in the User logon name text box This name uniquely identifies the
user in a domain or forest The domain name is provided automatically Click Next to
continue
7. In the New Object - User dialog box shown in Figure 8-19, enter a password for theuser Enter a strong password (one that consists of at least 10 characters, cannot befound in the dictionary, and contains numbers, letters, and special characters) Retypethe password in the Confirm password text box You may also select from four addi-tional options: User must change password at next logon, User cannot change pass-word, Password never expires, or Account is disabled It’s a good policy to force theuser to pick a new password the first time they log on, so that they have a passwordthat is meaningful to them and so that you, as the network administrator, don’t knowtheir password It is also a good policy to allow the password to periodically expire
With this in mind, make certain that the first option, User must change password at next logon, is checked, and then click Next.
8. The next New Object - User window displays the information you have entered
Click Finish to complete the creation of a new domain user account.
FIGURE 8-18 New Object–User dialog box
After you have created a new user, you can configure the properties associated with his account,including his address, telephone number, and e-mail address, his rights to use remote access,his position in the organization, his group memberships, what hours of the day he may log on
to the network, and so on To modify user account properties, you can use the Active tory Users and Computers snap-in In the snap-in window, double-click the user account in
Direc-FIGURE 8-19 Password settings in the New Object–User dialog box
NET+
3.1
Trang 10the right-hand pane The User Account Properties dialog box opens, with multiple tabs thatrepresent different categories of attributes you may change.
Before you add many users, you will probably want to establish groups into which you can lect user accounts But before creating a group, you must know what type of scope the groupwill have The group’s scope identifies how broadly across the Windows Server 2003 network
col-its privileges can reach The possible scopes are domain local, global, or universal A domain local group is one that allows its members access to resources within a single domain Domain
local groups are used to control access to certain folders, directories, or other resources They
may also contain global groups A global group allows its members access to resources within
a single domain also However, a global group usually contains user accounts and can be inserted
(or nested) into a domain local group to gain access to resources in other domains A sal group is one that allows its members access to resources across multiple domains and forests.
univer-To create a group in Windows Server 2003:
1. Make sure you are logged on as Administrator
2. Click Start, point to All Programs, point to Administrative Tools, and then click Active Directory Users and Computers The Active Directory Users and Computers
snap-in starts
3. Double-click the Active Directory container in which you want to create the new
group This may be a domain or an OU
4. Click Action on the menu bar, click New, and then click Group The New Object
-Group dialog box appears, as shown in Figure 8-20
Chapter 8 401
INSTALLING AND CONFIGURING A WINDOWS SERVER
FIGURE 8-20 New Object–Group dialog box
5. In the New Object - Group dialog box, enter the name of the group in the Group
name text box In case you are using Windows NT servers on your network, theGroup name (pre-Windows 2000) text box is automatically completed
6. Choose the group scope: Domain local, Global, or Universal
NET+
3.1
Trang 117. Select the type of group you want to create: Security or Distribution A Securitygroup is the type you would use to grant a group of users privileges to sharedresources, whereas Distribution groups are used solely for sending e-mail messages to
a group of users through mail server software such as the Microsoft Exchange Server
After you have made your selection, click OK to finish creating the new group.
Modifying the properties of a group account is similar to modifying the properties of a useraccount To modify the properties of your newly created group, double-click the group in theright pane of the Active Directory Users and Computers snap-in window This opens thegroup’s Properties dialog box, which contains four tabs: General, Members, Member Of, andManaged By Through this dialog box, you can add user accounts to the group, make thegroup a member of another group, and specify which user account will manage the group
As mentioned earlier, users and groups are virtually useless unless they have some rights to theserver’s data and system directories
Internetworking with Other Network
You might think that establishing communications between two NOSs is simply a matter ofinstalling the same protocol on both systems For example, you might think that because bothNetWare and Windows Server 2003 can run the TCP/IP protocol, the two should be able tocommunicate directly In fact, a protocol match is merely one part of the interoperability equa-tion
To enable clients connected to a NetWare server (version 5.x or 6.x) to view and access resources
managed by a Windows Server 2003 server, Microsoft recommends installing its File and Print Services for NetWare on the Windows server After this is installed, the Windows server will
appear to NetWare clients as simply another NetWare file or print server; users will not be able
to distinguish it from a NetWare server File and Print Services for NetWare is one application
belonging to the Microsoft Windows Services for NetWare package, a collection of software
that simplifies the integration of Windows Server 2003 servers and NetWare servers on the
same network Another application that belongs to this package is the MSDSS (Microsoft Directory Synchronization Services) When installed on a Windows Server 2003 server, this
Trang 12software can synchronize information between an Active Directory database and a NetWareeDirectory database On a network that runs both Windows and NetWare servers, synchro-nization means that objects and their attributes are identical across a network, no matter onwhich type of server they were created or modified Because both NetWare versions 5.x or 6.xand Windows Server 2003 rely on directories that follow the same LDAP standards, sharingdata is simple To run MSDSS, the Windows server must be configured as a domain controller.For NetWare clients that rely on the IPX/SPX protocol, additional software is necessary toaccess a Windows Server 2003 server One possibility is for clients that depend on the Win-
dows Server 2003 server to run Microsoft’s CSNW (Client Services for NetWare) CSNW
is a service that in conjunction with NWLink enables the client to log on directly to the Ware server to access its printers, files, and other resources If your network includes both Win-dows Server 2003 and NetWare servers, and both use TCP/IP as their preferred protocol, you
Net-do not necessarily have to install CSNW (nor Net-do you need to install NWLink) Instead, oneach workstation you could install Novell’s recommended client software to access NetWareservers in addition to Microsoft’s Client for Networks to access Windows Server 2003 com-puters Client Services for NetWare is not supported by the 64-bit versions of Windows Server
2003, such as the Enterprise Edition
When interconnecting UNIX, Linux, or Mac OS X Server with Windows Server 2003 works, you can assume that both rely on the TCP/IP protocol However, you cannot assumeboth use the same directory structure If a UNIX type of server does have an LDAP-compat-ible directory installed, Microsoft provides software for integrating the UNIX-type of direc-tory with Active Directory This software is installed on the Windows server and allows clientsattached to the UNIX-type of server to access Windows Server 2003 resources as if they were
net-resources on the UNIX-type of server It belongs to Microsoft’s Windows Services for UNIX.
Another application belonging to the Windows Services for UNIX package allows clients onWindows Server 2003 networks to access UNIX-type of servers and use their files and accountprivileges The Windows Services for UNIX include the ability for the client to be recognized
by a UNIX-type of server’s file system and utilities for manipulating files and directories.There are also other, simpler utilities that Microsoft clients can use to access UNIX-type ofservers (for example, a simple FTP client) In the next chapter, you will learn how UNIX-type
of clients can connect and act as clients to Windows servers
Trang 13◆ A redirector, which belongs to the Presentation layer of the OSI Model, is inherent
in both the NOS and the client operating system On the client side, it interceptsclient communications and decides whether the request is meant for the server or forthe client
◆ When a client attempts to log on, the NOS receives the client’s request for serviceand tries to match the user name and password with the name and password in itsuser database If the passwords match, the NOS grants the client access to resources
on the network, according to limitations This process is known as authentication
◆ A directory is an NOS’s method of organizing and managing objects, such as users,printers, server volumes, and applications It is sometimes compared to a tree,because it has one common starting point and branches into multiple containers,which may branch into additional containers
◆ A file system is an operating system’s method of organizing, managing, and ing its files through logical structures and software routines In general, wheninstalling Windows Server 2003, you will want to choose the NTFS file system
access-◆ For clients to share a server application, the network administrator must assign usersrights to the directories where the application’s files are installed Users will need atleast the rights to access and read files in those directories For some applications,users may also need rights to create, erase, or modify files associated with the appli-cation Users are organized into groups to streamline administration
◆ For clients to share a network printer, the printer must be created as an object,assigned a name and properties, and then shared among clients Users or groups may
be assigned different levels of privileges to operate printers
◆ The type of multitasking supported by NetWare, UNIX, Linux, Mac OS X Server,and Windows Server 2003 performs one task at a time, allowing one program to usethe processor for a certain period of time, and then suspending that program toallow another program to use the processor This is called preemptive multitasking
◆ Multiprocessing splits tasks among multiple processors to expedite the completion ofany single instruction It’s a great advantage for servers with high CPU utilization,because it improves performance
◆ Windows Server 2003 requires the following minimum hardware: Pentium processor with
a minimum clock speed of 133 MHz (though at least 550 MHz is recommended), 128
MB of RAM (though at least 256 MB is recommended), at least 1.5 GB free hard diskspace for system files, and a pointing device A CD-ROM and a NIC that are included
on the Microsoft HCL (Hardware Compatibility List) are optional
◆ The Windows Server 2003 memory model assigns each process its own 32-bit (or insome versions, 64-bit) memory area This memory area is a logical subdivision of theentire amount of memory available to the server Assigning processes separate areasmakes the processes less prone to interfering with each other when they run simulta-neously
◆ The description of object types, or classes, and their required and optional butes that are stored in Active Directory is known as a schema
Trang 14attri-◆ Domains define a group of systems and resources that share common security andmanagement policies The database that domains use to record their objects and
attributes is contained within Active Directory Domains are established on a work to make it easier to organize and manage resources and security
net-◆ To collect domains into logical groups, Windows Server 2003 uses a domain tree (orsimply, tree) At the base of the tree is the root domain From the root domain, childdomains branch out to separate objects with the same policies Underneath the childdomains, multiple organizational units branch out to further logically subdivide thenetwork’s systems and objects A collection of domain trees is known as a forest
◆ Each tree, domain, container, and object has a unique name that becomes part of thenamespace The names of these elements may be used in one of three different ways
to uniquely identify an object in a Windows Server 2003 tree: as a distinguished
name, as a relative distinguished name, and as a user principal name
◆ Prior to installation, you need to make a number of decisions regarding your serverand network pertaining to the domain or workgroup characteristics, file system, diskpartitioning, optional services to be installed, administrator password, protocols to beinstalled, and server name
◆ Adding users and groups is accomplished through an administrative tool called
Active Directory Users and Computers
◆ For integrating Windows Server 2003 clients and resources with NetWare 5.x or 6.xclients and server resources, Microsoft provides a suite of applications known as
Microsoft Windows Services for NetWare In this package are tools for ing Active Directory with NetWare’s directory database and for allowing NetWare-attached clients to view Windows file and print resources as if they belonged to aNetWare server
synchroniz-◆ For integrating Windows Server 2003 clients and resources with UNIX-type of
clients and server resources, Microsoft provides a suite of applications known as
Microsoft Windows Services for UNIX In this suite are tools for synchronizing
data between Active Directory and a UNIX-type of server’s directory (if one exists),and for allowing UNIX-attached clients to view Windows file and print resources as
if they belonged to a UNIX-type of server
Key Terms
3-tier architecture—A client/server environment that uses middleware to translate requests
between the client and server
account—A record of a user that contains all of her properties, including rights to resources,
password, user name, and so on
Active Directory—The Windows Server 2003 method for organizing and managing objects
associated with the network
Chapter 8 405
KEY TERMS
Trang 15Administrator—A user account that has unlimited privileges to resources and objects
man-aged by a server or domain The Administrator account is created during NOS installation
AFP (AppleTalk Filing Protocol or Apple File Protocol)—The native file access protocol
used by Macintosh computers
Apple File Protocol—See AFP.
AppleTalk Filing Protocol—See AFP.
asymmetric multiprocessing—A multiprocessing method that assigns each subtask to a
spe-cific processor
attribute—A variable property associated with a network object For example, a restriction on
the time of day a user can log on is an attribute associated with that user object
branch—A part of the organizational structure of an operating system’s directory that
con-tains objects or other organizational units
CDFS (CD-ROM File System)—The read-only file system used to access resources on a CD.
Windows Server 2003 supports this file system to allow CD-ROM file sharing
CD-ROM File System—See CDFS.
child domain—A domain established within another domain in a Windows Server 2003
domain tree
CIFS (Common Internet File System)—A file access protocol CIFS runs over TCP/IP and
is the standard file access protocol used by Windows operating systems
class—A type of object recognized by an NOS directory and defined in an NOS schema
Print-ers and usPrint-ers are examples of object classes
Client Services for NetWare (CSNW)—A Microsoft program that can be installed on
Win-dows clients to enable them to access NetWare servers and make full use of NetWare’s rectory, its objects, files, directories, and permissions
eDi-CN (common name)—In LDAP naming conventions, the name of an object.
Common Internet File System—See CIFS.
common name—See CN.
container—See organizational unit.
DC (domain component)—In LDAP naming conventions, the name of any one of the
domains to which an object belongs
digital versatile disc—See DVD.
directory—In general, a listing that organizes resources and correlates them with their
prop-erties In the context of network operating systems, a method for organizing and managingobjects