Zero Touch Installation Deployment Feature Team Guide
Appendix L: Operating BDD Enterprise Without WINS
By default, the Microsoft Solution Accelerator for Business Desktop Deployment (BDD) expects that Windows Internet Naming Service (WINS) exists in your organization’s network infrastructure. Many organizations have removed all dependencies on WINS or are in the process of eliminating WINS dependencies. Some changes are required to support Solution Accelerator for BDD in organizations without WINS. When you follow the recommend procedures in Solution Accelerator for BDD, you create the following bootable CD images:
Both of these images need to map drives to the:
In environments without WINS, Windows PE uses Domain Name System (DNS) for Internet protocol (IP) address resolution. You need to ensure that your DNS services include both forward and reverse lookups for Solution Accelerator for BDD servers. To ensure that Solution Accelerator for BDD operates correctly in an environment without WINS:
On This PageConfiguring DHCP with Appropriate DNS Scope EntriesYou must have an existing DHCP infrastructure to support the Solution Accelerator for BDD. Each DHCP scope needs to include primary and secondary pointers for DNS servers that support the domain in which the Solution Accelerator for BDD services and servers are hosted. Note In environments without WINS, the WINS settings in the DHCP scope are irrelevant and should be left blank. Configuring Forward and Reverse Lookup Zones in DNSYou must have an existing DNS infrastructure to support the Solution Accelerator for BDD in an environment without WINS. You need to:
Configuring LMHOSTS Files for the Windows PE CD ImagesIn some environments without WINS, DNS may be unavailable or not configurable by the development team. While it is recommended to use DNS for name resolution, you can use LMHOSTS files to provide name resolution. You need to manually place the LMHOSTS files into both Windows PE images. To configure LMHOSTS files for the Windows PE CD images:
Modifying Windows PE STARTNET.CMD FilesYou need to modify the STARTNET.CMD files in the following image folders (where InstallPath is the path where you installed the Solution Accelerator for BDD):
The STARTNET.CMD file in these folders needs to contain the syntax in Listing 99. regsvr32 /s netcfgx.dll factory -minint netcfg -v -winpe net start dhcp net start nla net start lmhosts Listing 99. Sample STARTNET.CMD file modified to enable WINS resolution The command net start lmhosts enables WINS resolution for Windows PE in the Solution Accelerator for BDD build and deploy processes. Creating the Appropriate Folder StructureYou need to create the appropriate folder structure to support LMHOSTS files for Windows PE. Create the folder structure (\Drivers\Etc\) in the folder structure in the Computer Imaging System as shown in Listing 100 (where InstallPath is the path where you installed the Solution Accelerator for BDD): Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line. InstallPath\Computer Imaging System\Boot Disks\WinPE \ExtraFiles\i386\System32\Drivers\Etc Listing 100. Folder structure to be created for LMHOSTS file Creating the Appropriate LMHOSTS FileCreate an LMHOSTS file that contains entries for your servers and domain. Listing 101 illustrates an example of an 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 Listing 101. Sample LMHOSTS file To create the appropriate LMHOSTS file:
Ensure that you update the LMHOSTS, and subsequently the Windows PE images, if your environment changes. Configuring SMS with Active Directory Schema ExtensionsSMS 2003 Advanced Clients determine their appropriate assigned SMS sites and servers based on Active Directory and DNS when available. These are determined from Management Point and Server Locator Point registrations if SMS Active Directory Extensions are installed. You need to ensure that Active Directory schema is extended with the SMS schema extensions.
|
In This Article
|
