Now select Control Panel Home. Follow that by Appearance and Personalization. We want to turn off sounds, and the screen saver. First access Change sound effects and change the profile to No Sounds. Next access Change screen saver and make sure it is set to none. Now select Taskbar and Start Menu. Change to the Start menu tab. The power button default should be Log Off. In the left menu, select Network and Internet. Follow this by selecting next Network and Sharing center.
In the left menu you will find change adapter settings. Now you will see the adapter. Here is mine. We want to remove some settings — like IPv6 and QoS so right click on the adapter and select Properties. We can select OK and exit back out to the desktop. Working from the Control Panel, select Programs. Follow that by selecting Turn Windows features on or off. Scroll through the list until you find Telnet Client , and select it.
We should remove the backups that were caused by the or more updates I did. We will use the Disk Cleanup tool. It is important to click on it and Run as Admin. If you forget to do this you will not see Windows Update Cleanup in it the list as you see below. It only shows MB in use but it is still good to clean it up. Use the OK button to start the cleaning. After this we should empty the trash — likely is but be sure..
We should disable the index on drive C:. You will see at the bottom of the screen the option to disable indexing — it is Allow files on this drive to have contents indexed — deselect the box for it. You can enable indexing on your data drives like H: or whatever using GPO. There may be a few files that cannot be removed from the index — just ignore them.
Now we should defragment the drive. This option is on the Tools tab. While you are here you should disable the weekly optimize option as it is not necessary.
Configuration — Installing Optional Software We only install software here that we really need and is useful for most users. Bginfo — find it here and info on making it work here.
Google Chrome Autoruns — a great tool to make sure you know what starts with your OS. Process Explorer — a great tool for troubleshooting. PowerCLI — from here — a very useful admin tool! If this is a desktop that admins are going to use, it may be good to add Adobe Flash to it. Something that many would consider not optional is antivirus software.
I would suggest you need to do a scan as one of the last actions too. The RVTools are handy too for admins — from here. Test Time — before Is this desktop ready for the prime time? Is there any errors when you log in using your admin account? Does your installed software all start? Does a restart cause anything odd to occur at log in or otherwise? Ready to Make it a template? We are ready to make this virtual machine a template now.
If necessary remove this VM from the domain and restart. I always like to check Windows Update before I finish and yes, today I did find a bunch of updates that I did not find earlier. So I update and restart as necessary. Make sure you are really ready to proceed! So I create and use an account that is admin equivilent and called temp. Log in as it and run the defprof command and delete the temp account. When that is done we remove the tool, And shut the VM down.
Once the VM is shut down we are ready to turn it into a template. If you did install anti-virus or anti-malware software you may need to do something so that when a VM is deployed from this template and starts up it is going to get its own identity for management purposes and not be the same as the installed copy on the template.
I generally now do an update in the Notes section to account for what I have done. Deploy from Template I suspect everyone knows how to deploy from this new template but remember that any passwords put into the customization script should be done using the vSphere Client and not the vSphere Web Client this is a bug and I am sure it will fixed. Test Time — after Now that we have deployed a VM from our template we need to make sure it all works.
Some things to check include: Did our VM join the domain? This is most important. Things to think about I like to create a customization spec before I deploy from template and that normally is just a copy and paste on an old one and small update for things like the IP address.
Troubleshooting Here is some miscellaneous things to think about if you have troubles. Check out this article of mine for ideas. Did you remove the VM from domain before you turned it into the template?
Did you confirm that the account credentials in the spec to join the domain work? Although it can be used locally, for faster deployment it's recommended to upload the file to a vSphere datastore or to vCenter content library. From PowerShell, install Chocolatey. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.
Click Yes to confirm key deletion. The key is no longer listed. Launching the sysprep once again, the process runs smoothly. Related Posts. Paolo, Thanks so much. I had tried a lot of other solutions. Yours worked.
0コメント