Generic System Image?
I need to setup a new office and they have laptops/desktops that I don't have access to. That said, I'd like to use a System Image on a USB drive on both machines. I know that system images must usually be of the same exact system/hardware. The admin guide mentions a workaround to this, however.
Could someone fill me in on this workaround? I know on WDS we were able to just embed drivers into an image and it worked. Is that what we must do with the K2000? If so, how? Is it possible to do postinstall tasks with system images via a USB? I suppose then I could just do drivers via a postinstall task, assuming the image would allow me to get that far.
If this isn't possible on a K2000/easier with another app, does anyone have any recommendations?
Community Chosen Answer
Create your image on hardware you have, then sysprep it. Do *NOT* let it reboot into the sysprep process before imaging it. It will run sysprep once the image is deployed, and will manage to add hardware appropriately with native drivers. You can add drivers to the sysprep process if necessary.
You can certainly use post-install tasks with the USB key.
These are instructions for creating a new sysprep image off the original, but show you how to do the initial sysprep as well.
Beware formatting the drive in your preinstall tasks. You will specifically have to make sure you do not format the USB drive. Multiple drives / partitions will complicate things.
Beware images that require multiple / special boot partitions. I have noted sometimes the drives lay down reversed, or pick up reversed lettering. You may need to adjust your preinstall tasks appropriately to lay down the partitions / drives in the correct order.
- Log onto the K2K
- Under Deployments->Images choose the latest image
- Scroll to the bottom and select duplicate
- Rename the new imaging task as build (IE. W7SP1 Build)
- Remove all possible post-installation tasks from the new image task
- Deploy the image to a target machine
- Once deployment is complete, update the target with all possible updates
- Windows Updates
- Dell Updates
- Remove any Windows Update or Dell Update caches
- Ensure the KACE Agent and related software is removed from the machine
- Delete C:\Windows\setup\scripts\
- Ensure other post-installation software is removed from the machine
- Ensure all profiles are trimmed to the minimum required
- Ensure all caches are empty
- Ensure the registry looks clean
- Leave the domain
- Run disk cleanup
- Defragment the drive
- Reboot cleanly twice
- Image the machine and rename the imaging task as clean (IE. W7SP1 Clean)
- Skipping the above assumes you are perfect.
- Skipping the above also assumes all our vendors are perfect.
- You have been warned.
- Copy the unattend.xml file from C:\Windows\system32\sysprep\ to a different machine where you have installed the WAIK.
- Make sure you have a copy of the installation media. The file you need to open the unattend.xml is located on an installation DVD in the sources folder.
- Open the unattend.xml file in the WAIK and make any necessary adjustments. Usually this will include a change to the Administrator password.
- Save the new file and copy it to C:\Windows\system32\sysprep\ on the machine you plan to clone.
- Delete the sysprep_completed.tag file from C:\Windows\system32\sysprep\
- Open the C:\Windows\system32\sysprep\ directory in a command prompt.
- sysprep /generalize /oobe /shutdown /unattend:C:\Windows\system32\sysprep\unattend.xml
- Do not turn the machine back on until you are ready to capture the image
- Connect the computer to the K2K
- Boot the computer, and make sure it goes into PXE boot so the K2K can capture it.
- If the machine boots to the hard drive before capture, it will set up the machine, and you will have to start over.
- Choose imaging
- Upload an image to the KACE
- Name the image (IE. W7SP1 Sysprep)
- Once the machine has been imaged, reboot it and allow it to run the unattended setup
- Check that the OOBE is successful
- Note: We have not applied post-installation tasks. If these are required for functional boot, you can only test by deploying the new image below
- If OOBE is not sucessful, you will have to start over, or modify the unattend.xml file within the image
- Duplicate the new image and give it an RC name (IE. W7SP1 RC)
- Test the image
- Reapply all the post-installation tasks as appropriate
- Test the image
- Rename the RC image as the base OS name (IE. W7SP1)
- Delete the Clean and Sysprep images