tag:blogger.com,1999:blog-7081198953811365039.post2690741852949561010..comments2021-10-21T07:22:42.233-07:00Comments on Four King Beach: Windows 2012 Deployment ServerJomebrewhttp://www.blogger.com/profile/15744855656606095896noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7081198953811365039.post-35792077555956786132012-11-20T13:43:43.320-08:002012-11-20T13:43:43.320-08:00It got worse, not better. WDS Discover client bas...It got worse, not better. WDS Discover client basically copied the VHD to the server and did not expand the files. It turned out to be an extremely poor choice to image and restore a system. Norton Ghost, with all it's challenges, would have been the much better choice.<br /><br />Eventually, I mounted the VHD as a drive on the WDS server, booted the client computer to command line (using a bootable flash drive with the Win2K8 install on it) and mapped a drive to the shared Drive/Mounted VHD on the WDS server. I then used xcopy to copy all the files. This takes forever but mostly worked. We had some issues with the recovery partition being assigned drive C: screwing up windows for a bit but the was quickly solved (reassigning drive letters). <br /><br />X64 seemed to worked quite well, but stay away from x86 systems!Jomebrewhttps://www.blogger.com/profile/15744855656606095896noreply@blogger.comtag:blogger.com,1999:blog-7081198953811365039.post-90832902336276715652012-11-16T13:46:14.250-08:002012-11-16T13:46:14.250-08:00I ran into a a problem where the client boot only ...I ran into a a problem where the client boot only displays the X64 images. I needed to install a X86 Windows 2003 server image. <br /><br />Turns out that the boot.wim I am using is X64 based so the client will only show X64 install images. I poked around the WDS 2012 server long enough to try right clicking the X86 boot image and creating a Discover Image. I created a new boot.wim and replaced the boot.wim on my bootable flash drive.<br /><br />Sure enough it boots to the X86 image. <br />Note: Make sure your hard disk is the first drive in the BIOS boot order. <br />Also Note: Drive cannot be partitioned or formatted. The WDS client will fail with the stupid Network Part not found error when it really means it needs a raw, partitions disk. Dumbass engineers and unhelpful error messages and not allowing me to delete the partitions from the client.<br />Jomebrewhttps://www.blogger.com/profile/15744855656606095896noreply@blogger.com