By default, Microsoft Deployment expects that the Windows Internet Naming Service (WINS) exists in the organization’s network infrastructure. Many organizations have removed all dependencies on WINS or are in the process of eliminating them. Some changes are required to support Microsoft Deployment in organizations without WINS.

The Microsoft Deployment scripts connect to network resources during the deployment process. Examples of these resources include:

• Shared folders on Microsoft Deployment distribution points.

• Systems Management Server 2003 or System Center Configuration Manager distribution points.

• Computers running SQL Server.

In environments without WINS, Windows Preinstallation Environment (Windows PE) uses Domain Name System (DNS) for IP address resolution. Ensure that the DNS services include both forward and reverse lookups for Microsoft Deployment servers. Additionally, configure DNS to perform WINS lookups. For guidance see WINS lookup integration at http://www.microsoft.com/windows/windows2000/en/advanced/help/sag_DNS_und_WinsLookupIntegration.htm.

To ensure that Microsoft Deployment operates correctly in an environment without WINS

1. Configure Dynamic Host Configuration Protocol (DHCP) with appropriate DNS scope entries.

2. Configure Lmhosts files for the Windows PE CD images.

3. Configure Systems Management Server 2003 with Active Directory® directory service schema extensions.

On This Page

Configure DHCP with Appropriate DNS Scope Entries
Configure Lmhosts Files for the Windows PE CD Images
Configure Active Directory Schema Extensions

Configure DHCP with Appropriate DNS Scope Entries

The organization must have an existing DHCP infrastructure to support Microsoft Deployment. Each DHCP scope must include primary and secondary pointers for DNS servers that support the domain in which Microsoft Deployment services and servers are hosted.

Note   In environments without WINS, the WINS settings in the DHCP scope are irrelevant and should be left blank.

Top of Page

Configure Lmhosts Files for the Windows PE CD Images

In some environments without WINS, DNS may be unavailable or not configurable by the development team. Although using DNS for name resolution is recommended, the team can use Lmhosts files to provide name resolution. Manually place the Lmhosts files into both Windows PE images.

To configure Lmhosts files for the Windows PE CD images

1. Modify the Windows PE Startnet.cmd files to include WINS resolution support (necessary for versions of Windows PE prior to version 2.0 ZTI using SMS 2003 Operating System Deployment (OSD) Feature Pack only).

2. Create the appropriate folder structure in the images.

3. Create the appropriate Lmhosts file.

Create the Appropriate Folder Structure

Create the appropriate folder structure to support Lmhosts files for Windows PE. Create the folder structure (\Drivers\Etc\) in the Computer Imaging System, as shown in Listing 5 where InstallPath is the path where the team installed Microsoft Deployment.

Listing 5. Folder Structure to Be Created for Lmhosts Files

InstallPath\Computer Imaging System\Boot Disks\WinPE\ExtraFiles\i386\System32\Drivers\Etc

Create the Appropriate Lmhosts File

Create an Lmhosts file that contains entries for the organization’s servers and domain. Listing 6 shows an example of an Lmhosts file.

Listing 6. Sample Lmhosts File

10.10.10.10    DomainController    #PRE #DOM:DomainName #at least 1 DC
10.10.10.20    BDDServer            #PRE #source server
10.10.10.30    AppServer            #PRE #holds apps
10.10.10.40    IMGServer            #PRE #hosts XP images

To create the appropriate Lmhosts file

1. Use a text editor to create the Lmhosts file.

2. Place the Lmhosts file in the \Etc folder created earlier in the process.

3. Create or refresh the Windows PE lab and deployment images by using the Microsoft Deployment computer imaging system.

   For more information, see the Image Engineering Feature Team Guide.

Update the Lmhosts file and, subsequently, the Windows PE images, if the environment changes.

Top of Page

Configure Active Directory Schema Extensions

Systems Management Server 2003 and System Center Configuration Manager Advanced Clients determine their appropriate assigned Systems Management Server 2003 sites and servers based on Active Directory and DNS when available. These are determined from management point and server locator point registrations if Active Directory schema extensions are installed. Ensure that the Active Directory schema is extended.

Top of Page

Download

Get the Microsoft Deployment Solution Accelerator

Update Notifications

Sign up to learn about updates and new releases

Feedback

Send us your comments or suggestions

Top of Page