-
Ooookay,
I know I am going to get flamed for this. But I am doing research on sysprep but still so confused.
I have a windows 10 computer with programs installed. Need to get that unto 48 different computers. What do I do now? Go into sysprep? I didn’t go into CTRL SHIFT F3 thing.
-
Why would you think that?
Once you setup your golden image exactly the way you want it then you need to prepare it for imaging. You do this with sysprep. This neutralizes the image in preparation for capture and cloning. There are plenty of good instructions on the internet that explain the sysprep process.
In regards to FOG specifically you need ensure the fog client is disabled before you capture the image. You will use a batch file called setupcomplete.cmd to re-enable the service after imaging.
When sysprep is used use the command line switch with sysprep to power off the computer after sysprep task is complete. This ensures that the computer is ready for cloning.
Then pxe boot into fog and capture your image.
Finally pxe boot your target computer to deploy the image to.
Typically when building your golden image, you will want to place the system in audit mode to ensure your system applications are installed correctly.
-
@george1421 So should I do a fresh install of windows 10 and go into audit mode and then reinstall my programs? This is where I get confused, as I know I’m supposed to take a presysprep image.
-
@jackiejack If you build your golden image by hand that is the proper way to create it, in audit mode. If you build by using MDT then MDT will take care of building your reference image properly.
-
@george1421 Yikes. Guess that’s why they use VMs and snapshots.
-
@george1421 said in Win 10 image:
.
When I run sysprep, I have to put the activation key in SIM? Then sysprep w/ answer file?
-
@jackiejack Yes vm and snapshots will save your butt many times over.
If you don’t have a virtualization infrastructure, I assume you can use somthing like virtualbox to build your VM on and then make snapshots at critical steps to ensure you can roll back the changes without having to rebuild.
Yes you can add the activation key into the answer file, or activate it afterwards, or if you are using the fog client, it can activate the target computer for you.
-
I’ve had luck with sysprep up until 1703, anyone else having issues or have successfully sysprepped Windows 10 Enterprise 1703?
-
@jackiejack said in Win 10 image:
Ooookay,
I know I am going to get flamed for this. But I am doing research on sysprep but still so confused.
I have a windows 10 computer with programs installed. Need to get that unto 48 different computers. What do I do now? Go into sysprep? I didn’t go into CTRL SHIFT F3 thing.
Are your 48 different computers the same model? If they are, then I would used one of them to create the image. If not, VirtualBox will work fine. My image was created in VirtualBox and runs on about 30 different models.
-
@avaryan No, different models. I have got to read up on that driver injection thing.
-
I would actually put the minimal amount of software and configuration on the image as possible… create the image with virtualbox and snapshot before every sysprep so you go go back and do windows updates regularly. Use a tool like WPI, or even better, config management tool like salt/puppet for post software install/config… but yes, you have the right idea… make sure to put the network drivers for each model on the image as well
-
@larosejm PDQ work good? Puppet is open source is it?
You mean windows updates on the virtual machine? -
@jackiejack PDQ is more of a remote deployment type deal, but I suppose it could work. Puppet is open source. I found Salt easier to use, which is open source as well, but beware that you need to know what your doing with these and make sure they are secure because they give ALOT of control, but if in place and once properly setup, can be used to automate everything. A simple free solution is create silent installers in a central network share and combine PDQ for remote deployment (free if you just run bat files from the central share) and WPI (http://www.majorgeeks.com/files/details/windows_post_install_wizard_(wpi).html) for locally running post installs/configs. The trick is, you have to create silent installers for everything. You may also have luck with Fog for post config and software.
-
@larosejm I have some more programs to install. Should I boot into sysprep audit mode and install programs?
-
@jackiejack yes, first thing you do is go into audit mode… do the windows updates in the virtualbox before sysprep (be sure to select bridged network adaptor) so you’ll be able to upload to fog. Put network drivers for all models in c:\windows\inf folder somewhere. You could install software before sysprep if you want. The only software we install before sysprep is Microsoft Office and do the rest post image.
-
@larosejm no I mean in my current real machine. Can I go into audit mode, then install the rest of my programs? Is that how it works?
-
@jackiejack you could use a physical machine, but virtualbox is easier and transerable… your machine doesn’t matter. I actually use virtualbox on a mac… from some notes… “install Windows using Audit Mode* in virtual box with 4gb ram, 2 processors, 50gb dynamic hard drive, bridged adapter”
-
@larosejm NO
I have a machine with some installed programs. I have more programs to install in it. Can I go into audit mode now and install the rest of the programs? Or do I have to start over (in a VM this time)? -
@jackiejack definitely start from scratch. Its quick enough, and if this is your image your gonna use on a bunch of machines, you want it to be perfect… plus it’ll be easier to document all the steps you do.
-
@larosejm Right. Hopefully I could get another machine somewhere…
