Jump to content

Recommended Posts

Posted

Hi all.

This is my first time creating a master image using a vm (used hyperv). I have got to the point where i have installed windows and all the software in audit mode but i havent yet run any software, done any customizations or sysprepped.

What is the best way forward from this point so that i can come back and add any additional software in future. Do i copy the entire vm to a holding location before i customize and sysprep? Or do i use checkpoints? Im not sure the best way to go.

Any advice welcome :)

Posted

We generally install X amount of software and create a checkpoint then rinse and repeat until all the software is installed. We then revert back to the checkpoint with no software on it if we need to make a build with the same image.

 

I did read an article about checkpoints and why they are bad but honestly I have never had a problem with them.

Posted
Make a checkpoint right before you run Sysprep. If for whatever reason Sysprep fouls up you'll be glad of this. Also as you've already mentioned you can keep coming back to the image to update it in the future.
  • Thanks 1
Posted
Make a checkpoint right before you run Sysprep. If for whatever reason Sysprep fouls up you'll be glad of this. Also as you've already mentioned you can keep coming back to the image to update it in the future.

 

I also do this. There used to be a maximum number of syspreps you could do so this avoids hitting that limit (if it still applies).

Posted

Thanks for your advice guys. I also read a few articles on checkpoints and thinking it may not be what I need, but seeming as I'll only be running it for the purposes of sysprep I think it'll be fine too. After I have checkpointed, sysprepped and uploaded my master I may revert and export anyway as I think my pc is about to be pushing up the daisies.

Thanks again everyone!

Posted
Customise an image as little as possible by hand, because you're going to be doing it again in 6 months, auto install as much as possible post deployment, and automate your pre deployment customisations as much as possible, anything you can't automate make into a checklist.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...