Windows 7 / Getting Started

---

Share Files and Printers for Non-Windows Clients

Windows Server 2008 also supports printing and file sharing for non-Windows computers. These include the Macintosh as well as UNIX and Linux systems. Many networks contain either one or the other, or even both.

Windows NT has supported Macintosh connectivity since its earliest versions. Windows Server is no different. Macintosh connectivity used to be provided through Services for Macintosh, a service that included both File Services for Macintosh and Print Services for Macintosh and that had to be added to the file and print server. The service automatically added support for the AppleTalk protocol.

But with the advent of the newer Macintosh operating systems, Microsoft has deprecated this service because they no longer run custom Apple protocols since they run a version of UNIX. Rely on the UNIX connectivity tools in Windows Server to connect your Macintosh systems.

Windows Server supports UNIX integration at several levels. File and print integration was discussed earlier in the respective sections of this tutorial. File services are enabled through the NFS protocol, and print services rely on LPR printers. Each is relatively easy to work with. In terms of security, you can integrate Kerberos realms, including WS08 domains and UNIX networks, since Kerberos version 5 is a standard and is able to interoperate between the two environments. A Kerberos realm ensures that users can access files from both environments without having to use or remember two accounts and passwords.

TABLE-9 Resource Requirements per Server Role

Server Role	Processor Architecture	CPU	RAM	Drive D:	Drive E:	Network
File Server	x64	Low load	Required for Search service	Hosts shares	Hosts shadow copies and storage reports	Higher speeds or multiple cards required for file-sharing throughput
Print Server	x64	Medium load	Required for large print jobs	Not required	Hosts spool files	Multiple network interface cards (NICs) required for networked printers
Network Infrastructure Server (WDS role)	x64	High load	Required to support multiple system construction processes	Hosts WDS service and image files; use large, dedicated drives	Not required	High-speed network cards are required for better performance

Server Requirements

Now that you have reviewed the creation process for several server roles, you have an idea of the hardware requirements to construct them (see Table-9). You'll need to review the central processing unit (CPU), RAM, disk volumes, and network capabilities required for the server roles seen thus far. Use these guidelines to prepare your servers when you stage the parallel network for VSOs. Other tables of this type will be presented as we examine other roles.

Design the Virtual Service Offerings OU Structure

The final step of service preparation is the design of the Virtual Service Offerings OU structure and the application of proper delegation and Group Policy settings to each service (see Table-10). This OU structure is fairly flat, but it supports the ability to create substructures. Its purpose at that time was to identify the type of content you could expect in this OU structure. Now that you have had the opportunity to refine your understanding of the content for this OU structure. This OU structure presented the type of member server contained within the OU, it now presents the server role at the second level. This categorization allows further refinement. For example, if you find you need to further segregate collaboration servers because your policies for Exchange Server are not the same as those for SharePoint Portal Server (SPS), you can create a third level of OUs under collaboration servers and place Exchange and SPS servers in separate OUs.

One of the key aspects of this OU design is the preparation of appropriate security groups for server operators. This is called the services administration plan. Since it is mostly the preparation of special groups with limited administrative security rights.