Using Windows Deployment Services with Ghost Solution Suite 2.5
Created: 30 Oct 2008 | Updated: 08 Feb 2013 | 8 comments
This article addresses the need for a deployment solution using Windows Deployment Services (WDS) PXE (Preboot Execution Environment) in Native (non-RIS) mode. Currently, the Ghost Boot Wizard supports creating boot images for RIS and WDS in Legacy (RIS) mode. WDS requires a Windows Image (WIM, or *.wim file) to boot from. Ghost Solution Suite 2.5 and later creates WIMs when the Ghost Boot Wizard is used to create Windows PE-based boot media.
Article Filed Under:
Group Ownership:
Comments 8 Comments • Jump to latest comment
2008 Images
Hi there,
I apologize, but I'm not sure what you are asking. Are you asking if this works for taking/deploying Windows Server 2008 images?
Thank you,
Randall Newnham
My question is is ghost cast compatable with windows server 2008 R2 if so would the abouve steps work in the same way? also would I just need to have one license for the ghostcast server and not for the clients?
As I am a system builder and would like to use Ghostcast to deploy a windows image instead of installing it on each PC
Any advise would be most appreciated
Yes, that should work for Windows Server 2008 R2. Ghost is licensed by the number of clients, not the server. A license is required for each machine you plan on imaging or deploying. This method would definitely save a lot of time for image deployment.
Thank you,
Randall Newnham
Hey Randall,
So is this article stating that currently, this is only possible runnind WDS in legacy (RIS) mode? I'm currently running WDS on Windows Server 2008 R2, and running Ghost Solution Suite 2.5 on Server 2008 R2 as well.
When I try to import a WIM created by Ghost Boot Wizard, I get an error stating, "The file does not contain a valid boot image."
Thanks for your time,
Hi bl0ng
the Ghost boot image created with GBW is compatible with WDS in legacy mode ONLY as Randall mentioned above, this is why you are getting the error message.
However, you can cheat WDS in native mode following the easy steps below:
1. On WDS right click boot images > "Add boot image" and select a standard boot.wim image from a Windows 7 installation CD. The boot image will be then located in ...\Remote Install\Boot\x86\Images.
2. Create a TCP/IP Network Ghost Client Boot Image with your Ghost Boot Wizard.
3. Copy the boot.wim file generated by the Ghost Boot Wizard to your WDS under ...\Remote Install\Boot\x86\Images and replace the existing one.
4. PXE Boot your client and select the Windows 7 image. The client will load the boot.wim created by your GBW
and voila'.. you will be able to create/deploy ghost images from WDS in native mode
please note however that this procedure is provided "as-is"
Cheers
Marcello
Okay, maybe I'm a little slow, but where is the article? I'm not seeing a link or anything.
Hi bl0ng
the Ghost boot image created with GBW is compatible with WDS in legacy mode ONLY as Randall mentioned above, this is why you are getting the error message.
However, you can cheat WDS in native mode following the easy steps below:
1. On WDS right click boot images > "Add boot image" and select a standard boot.wim image from a Windows 7 installation CD. The boot image will be then located in ...\Remote Install\Boot\x86\Images.
2. Create a TCP/IP Network Ghost Client Boot Image with your Ghost Boot Wizard.
3. Copy the boot.wim file generated by the Ghost Boot Wizard to your WDS under ...\Remote Install\Boot\x86\Images and replace the existing one.
4. PXE Boot your client and select the Windows 7 image. The client will load the boot.wim created by your GBW
and voila'.. you will be able to create/deploy ghost images from WDS in native mode
please note however that this procedure is provided "as-is"
Cheers
Marcello
Would you like to reply?
Login or Register to post your comment.