Sever 2008 R2 WDS
WDS need to install below roles (Below is some tips for each server, service construction).
Before add role for service or server, set static ip for TCP/IPv4. (EX, 192.168.0.195)
1. AD DS service (Active Directory Domain Services)
2. DNS server -- DNS will add after ADDS installtion.
3. DHCP server
4. WDS (Windows deployment service)
WDS properties setting (Right click WDS -->server (WINXXXX)
After above installation and setting and there is no error for service and server from event viewer. you could start your WDS.
1. For Embedded Enterprise disk installation, insert Win XXX disk to ODD then choose "add install image from install images", point to file "install.wim" and follow instruction to add image.
2. Choose "add boot image from Boot images" and point to boot.wim and follow instruction to add image.
3. For customization image, add winpe 3.0 boot.wim or winpe 4.0 boot.wim to WDS. Create sharing directory from server and share the directory. Copy customization wim file to c:\share driectory.
3.a Boot PXE client then choose winpe 3.0, client will load boot.wim. From winpe command prompt, then run "net use z: \\192.168.0.195\share directory "password" "/USER:user@domain.org""
3.b Go to share directory and run imagex /apply to restore image to pxe client.
Known issue for Server 2008 R2 WDS with winpe 4.0 boot.wim, ---- if server hardware with Intel lan chipset, there is problem to boot winpe 4.0 boot.wim from Realtek lan PXE client and some intel lan pxe (with award bios). Server 2012 is ok for above combination.
4. Server 2012 WDS installation is almost same as Server 2008 R2.
Before add role for service or server, set static ip for TCP/IPv4. (EX, 192.168.0.195)
1. AD DS service (Active Directory Domain Services)
 |
| Run ADDS installation wizard |
 |
| Set new forest domain name, DNS will set later. |
2. DNS server -- DNS will add after ADDS installtion.
3. DHCP server
 | ||
| Add DHCP new scope |
 |
| DNS registration, run command from "cmd".. |
 |
| run "netsh dhcp server set dnscredentials" |
4. WDS (Windows deployment service)
 |
| Run Windows Deployment service configuration wizard. |
WDS properties setting (Right click WDS -->server (WINXXXX)
 |
| Advanced page |
 |
| PXE client always continuous pxe boot |
 | |||||
| PXE response |
After above installation and setting and there is no error for service and server from event viewer. you could start your WDS.
1. For Embedded Enterprise disk installation, insert Win XXX disk to ODD then choose "add install image from install images", point to file "install.wim" and follow instruction to add image.
2. Choose "add boot image from Boot images" and point to boot.wim and follow instruction to add image.
3. For customization image, add winpe 3.0 boot.wim or winpe 4.0 boot.wim to WDS. Create sharing directory from server and share the directory. Copy customization wim file to c:\share driectory.
3.a Boot PXE client then choose winpe 3.0, client will load boot.wim. From winpe command prompt, then run "net use z: \\192.168.0.195\share directory "password" "/USER:user@domain.org""
3.b Go to share directory and run imagex /apply to restore image to pxe client.
Known issue for Server 2008 R2 WDS with winpe 4.0 boot.wim, ---- if server hardware with Intel lan chipset, there is problem to boot winpe 4.0 boot.wim from Realtek lan PXE client and some intel lan pxe (with award bios). Server 2012 is ok for above combination.
4. Server 2012 WDS installation is almost same as Server 2008 R2.
留言