Deploy Unattended XP Using WDS Server

Hello Guys!

We Will See how to deploy unattained XP using WDS server

Requirements:
Windows Server 2003 or 2008 (Domain Controller, DNS, DHCP, WDS Server)
Windows 7 PE DVD (Windows Automated Installation Kit).
Windows 7 DVD (for Boot.wim file).
Windows XP CD (for Sysprep.exe)
Drivers (I’m demonstrate in VMWare workstation 9.0.1 so I’m gonna need VMware NIC Drivers) .

I’m using Windows 7 PE (Preinstallation Environment) instead of Vista PE or you can use Vista PE, I just want you guys to demonstrate another method of injecting drivers in Image.wim file.

Task to DO
1.    Install and Configure DHCP and WDS server
2.    Install windows 7 PE (Window AIK)
3.    Copy Boot.wim file from Windows 7 DVD located in SOURCES folder.
4.    Inject drivers into Boot.wim file
5.    Add boot.wim on WDS server for Deploying and Capture
6.    Preparing XP installed machine for Unattended Installation.
7.    Configure Client to boot from network card
8.    Capture prepared  XP machine image From client and upload to WDS server
9.    Deploy captured XP image from WDS server to client machine

Step 4 - Injecting Drivers into Boot.wim file.
First you need to know how many indexes are contain in boot.wim file.
To get index Information from boot.wim file
Dism.exe /Get-WimInfo /WimFile:C:\Boot.wim

To mount Boot.wim File.
Dism /Mount-Wim /WimFile:C:\Boot.wim /Index:2 /MountDir:C:\Mount

To inject driver
Dism /image:E:\Mount /Add-Driver /Driver:E:\Drivers\vmxnet\win2008\32bit\vmware-nic.inf
Dism /image:E:\Mount /Add-Driver /Driver:E:\Drivers\vmxnet\win2008\32bit\vmxnet.inf
To save changes and unmounts image

Dism /Unmount-Wim /MountDir:E:\Mount /Commit

For More Help Type: Dism /Image:E:\Mount /?
Note: in order to see help first you must mount image.

Step 6 - Preparing XP installed machine for Unattended Installation.

On client machine create a folder in C:\ drive sysprep

Note: Make sure the folder name in drive C:\sysprep

Note: It is highly recommended that you to copy i386 folder from XP CD into C:\sysprep, this action may avoid some issues with the missing files. You can delete i386 folder after unattended installation, or simply add DOS command in answer file, that is “rd /s /q C:\sysprep”.

Step 8 - Capture prepared XP machine image from client and upload to WDS server

There are some problem occurs while you connecting to WDS server, the problem is the Network Card Driver missing in the boot.wim file. We can add the driver in the boot.wim file. Which is I already did or if you don’t want to inject the drivers into boot.wim file. You can load the driver at capturing time simply using “drvload” command. So download the NIC driver for your network card, and put it on floppy, CD/DVD or USB flash drive and start command prompt with pressing Shift+F10, and Load the driver.

E.g. drvload E:\lan_drivers\driver-nic.inf

After driver loading with positive massage, you have to initialize the network service with the command.
That is “wpeutil.exe InitializeNetwork”

Secure DNS dynamic updates from DHCP client

How to Register Secure DNS Dynamic Updates from DHCP client using DNSUpdateProxy-Group on Server 2003 Sp2

Server Side
1. Install DHCP server and Configure
2. Add DHCP Server System and Admin Account into DNSUpdateProxy Security Group

Client Side
1. Obtain an Ip address automatically (don’t forget to turn off XP firewall)
2. ipconfig /release
3. ipconfig /renew
4. ipconfig /registerdns

Server Side
3. Set DNS dynamic updates registration credentials using Netsh.exe command
    a. Netsh
    b. Dhcp server dhcp_server_iIp
    c. Set dnscredentials UserName DomainName Password
    d. Quit
4. ping xp1
5. ipconfig /flushdns
6. ping xp1

How to Rename a Domain Controller

How to rename my Windows 2003 Domain Controllers?

There are 2 methods for performing the rename procedure. One is easier and done through the GUI; the other is more complex and requires the installation of the Windows Server 2003 Support Tools.

Method #1 - Through the GUI

Although easier to implement, if you rename a domain controller through the System Properties dialog box, DNS and Active Directory replication latency may delay the ability of clients to locate or authenticate to the renamed domain controller. The length of this latency depends on your network design and the replication topology of your organization.

Method #2 - By using Netdom.exe

Netdom.exe (Windows Domain Manager) this command-line tool enables renames a domain controller in a Windows Server 2003 domain, and also administrators to manage Windows Server 2003 and Windows 2000 domains and trust relationships from the command line.

Netdom.exe It only requires one reboot of the DC that had its name renamed.

Note: Domain Controllers running Microsoft's Certificate Authority services (CA) can never be renamed.

Important: To rename a domain controller using the Netdom.exe tool, the domain functional level must be set to Windows Server 2003.

You must install the Windows Server 2003 Support Tools. Click here to Download: 2003 Support Tools.

To rename a DC with the name from Server1 in the SAHaseeb.edu domain to Server001 follow the next steps:

Syntax

Open Command Prompt and type:

1. Netdom Computername Server1.SAHaseeb.edu /Add:Server001.SAHaseeb.edu

You can verify the new name was indeed added to the computer object by viewing it through Adsiedit.msc

msDS-AdditionalDnsHostName:

Ensure the computer account updates and DNS registrations are completed, then type:

2. Netdom Computername Server1.SAHaseeb.edu /Makeprimary:Server001.SAHaseeb.edu

After restart your computer, you can see lists of primary and/or any alternate names.

Open Command Prompt and type:

Netdom Computername Server1.SAHaseeb.edu /Enumerate

Last syntax

3. Netdom Computername Server001.SAHaseeb.edu /Remove:Server1.SAHaseeb.edu