Client Management Suite

Hi, does anyone use vmware workstation to create ghost images. any issues with it. ?

I was maybe going to give it a try but dont want to waste my time if it doesn't work.

Joe.

Fully scripted install of XP and apps, shutdown, manually snapshot in case sysprep fails, sysprep and take image, job done.

Make sure you edit the vmx config file:

 scsi0.preesent="FALSE"
ethernet0.virtualdev="e1000"

VM to have one core, remove floppy, CD, soundcard in settings and disable floppy in BIOS.

 I find i have to keep changing the NIC in the vmx file if I'm going from windows to WinPE and vice versa. Is that normal ?

I can't remember if I had to do eiither. Usually the e1000 driver is recommended because it's quite widely supported.

But in Windows doesn't recognise with NIc is I use E1000.

Its no biggie - just have to mind and chnge the file every time I capture...

My brain dump on this is,

1. VMWare is the way to go for image creation. Well worth working through the niggles, as the benefits are huge here (snapshot, machine always available, can do it all remotely, more automation..).
    
2. The Intel NIC is *definently* the way to go. This should be the default for Windows 7 machines when you configure them in VMWare, but you'll get the generic AMD one for an XP machine.
    
3. WinPE2 doesn't natively support either the AMD or Intel NIC used in VMWare. So, you'll have to add drivers regardless (or suffer the endless 'restarting dhcp service' messages). Once you've added the Intel driver to WinPE though, you'll be good to go from that point. No need to chop and change for everytime you capture. Just keep the vmx as having the Intel NIC.
    
4. The scsi0.present="false" is required to boot XP with IDE disks. It prevents XP from detecting the scsi device and assuming that it should be booting from a scsi disk which isn't there. It's an Windows bug and this setting gets around it.

Good Luck!

Yep, been using it for a week now and its amazing the difference its making.

Cheers for the info.

@JoeShmo -I think you forgot to marked Andy's post as the answer here. Have done it for you!

Apologies, I realy should keep on top of my posts..

Thanks Ian.

Joe.