Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Ghosting with Windows Deployment Services (WDS)

Created: 31 May 2007 • Updated: 21 May 2010 | 2 comments
I have used Ghost Image Casting for some years, though primary only the Create and Restore Image part of Ghost.

After updating to Ghost Solution Suite (GSS) 2.0 I plan to use the Console part of Ghost much more the before.
I use Windows Remote Installation Service (RIS) to boot computers up over LAN and through RIS, run an image with Ghost Client, which I then connect to my Ghostcast server.

After I have upgraded to GSS 2.0, I have tried to make a Ghost Console Client to work over RIS, and got it finally to work. Then we updated our Windows 2003 servers with SP2, in which RIS becomes WDS.

And now I can’t make a Ghost console boot image or for that matter a Ghost client boot image through WDS.
Is there anyone who has installed GSS in a windows environment running WDS in native mode. (Not  over RIS) I’ll be very to hear from any of you, with any help you can give me.

The only alternative left, if I can’t get Ghost to boot through WDS, is to use some other image and application distribution program, like Windows BDD. But I kinder like Ghost .
 
- Poul
Discussion Filed Under:

Comments 2 CommentsJump to latest comment

Nathaniel McFarland's picture
I'm running into the same issue. All the documents say that Ghost is compatible with Vista, but nothing about deployment. How do I make Ghost compatible with WDS? Or, how do I roll WDS back to RIS?
Nathaniel McFarland's picture
I finally figured it out. In short, WDS is garbage if you're implementing Ghost. Here's what I did:
 
1. Remove WDS completely from the server through Add/Remove Components in Add/Remove Programs.
2. Install the 3COM tools from the GSS CD.
3. Follow the Quick Start guide almost verbatim, minus the part about creating CMD files.
4. When you get to the part about creating a TCP/IP boot disk, when it asks for Ghost command line parameters, I put the following:
-z9 -ib -sure -ja=<GhostCast_session_name> -jaddr=<server_ip> -jm=d -rb
from left to right:
(highest compression) (image w/ boot record) (confirmation box disabled) (join the GhostCast session of your choice) (GhostCast server IP) (mode of transmission: multicast/directed broadcast/unicast) (reboot when finished).
 
This worked for me.