Phase 5: Set GhostCast Server to Accept an Imageġ. When done you should see it on the right. Give the image a sensible name and description > Next.Ħ. Browse to the Boot.wim file you created above.ģ. > Expand Windows Deployment Services > Servers > Your Server > Right Click Boot Images > Select “Add Boot Image”.Ģ. Start > Administrative Tools > Windows Deployment Services. Oscdimg -n -bc:winpe_ c:winpe_x86ISO c:winpe_x86winpe_x86.iso Phase 4: Add your new boot image to WDSġ.

Note: The image you need to give to WDS is called boot.wim, and you can find it hereĬ:winpe_x86ISOsources, You may wish to Copy it to your WDS Server to the directory you specified when setting up WDS (to hold Images).Īlso: You can create a bootable CD iso from the. Type “Yes” to overwrite > When finished it should say 1 file copied. To start with, you need to add WDS as a Windows component, Start > Run > appwiz.cpl ġ3. You need to download the WAIK (Windows Automated Installation Kit). The Server needs an installed and working DHCP Scope, WDS adds a PXE option to it.ģ. And Windows PE wont run in a Guest VM in VMware ESX, unless you set the client type to Vista (Even if it is another OS).ġ. But when using real machines it works fine – remember any drivers you need must be Windows Vista ones.

however people have invested heavily in Ghost over the years and rely on ghost images – also if you are using ghost to back up machines, then you may want to image them WITHOUT sysprep-ing then first (Which WDS does not seem to want to let you do.)ĭoing this in a virtual environment tends to be fraught with problems, with both with Microsoft and So yes I understand why people raise an eyebrow because you can achieve all your imaging needs with WDS alone. There’s very little about this that seems to be stored in one place out there on the Internet, Why would you want to use Ghost and WDS together anyway? Well once upon a time we used the PXE element is RIS, (WDS’s Predecessor) to use the Symantec GhostCast server.

How to install ghost 32.exe