Tag Archives: Windows

Windows – Creating a Sysprep answer file

Sysprep allows you to image a customized windows installation and “clone” that to other similar systems.  It is described in detail by Microsoft at: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep–system-preparation–overview

I have always used sysprep answer files when using sysprep. The process to create these answer files is a bit obtuse.

You first need to install the Windows WAIK that matches the version of windows you intend to image.  This installs as a windows kit and includes the “Deployment and Imaging Tools” command line need to create a WinPE installation environment.

You also need a copy of the installer for the windows version you intend to deploy on a burned DVD.

Then with the windows installer DVD in the drive, open the “Windows System Image Manger” in the Windows WAIK kit.

Now the trick to creating a good sysprep file is to ONLY include the components and packages from the windows installation DVD in the answer file that you absolutely need (There are thousands of components!). See the Sysprep best practices at: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/hh825023(v=win.10)

Basically, you should expend out the components in the DVD in the bottom left window above.  Select the ones you really need and drag copy them into the sysprep step in the middle of the window above you want them in. Then once they are there, one can set the settings or parameters as you need to.

The complete sysprep technical reference is at: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/hh825209(v=win.10)

There are also many examples of creating sysprep answer files on many different websites.  One that is a little older is at: http://sybaspot.com/the-complete-guide-to-preparing-a-windows-7-deployment-image-using-audit-mode-and-sysprep-with-an-unattend-xml-answer-file/

It is important in any of these to not blindly copy the sysprep settings that other people use.  You need to review the required settings and select only the optional ones you really need.  (For Williams College people – get a copy of the sysprep files that Lynna has on the winlab file server that netsys maintains at: \\winlab\images\Lab Image Work\Sysprep\).

Once you have a sysprep file you think you want to test load your windows version on a clean system.  Then:

Before sysprepping a computer make a backup image!
Incorrect Sysprep answer files can and often do result in an unbootable/unfixable windows install.

Be sure to completely shutdown the computer (not just reboot)

If using “CopyProfile” —- Log into the ProfileUser account and set it up the way you want it. Do not log into any other accounts.
(If you do log into other accounts you should shutdown the system completely before continuing to sysprep.)

Make sure the correct sysprep answer file is copied to “c:\windows\system32\sysprep\unattend.xml”

From the ProfileUser account:
Right click on cmd.exe and select “run as administrator” (type “cmd.exe” in the search windows)

Then use these commands:

cd c:\windows\system32\sysprep

sysprep /generalize /oobe /shutdown /unattend:c:\windows\system32\sysprep\unattend.xml

 

Since it can be a vector to compromise windows system security, After deploying computers using a sysprep answer file, a post-cloning task should be to remove the sysprep answer file from the cloned systems

Windows – Self-extracting installer with auto-install

With the application WinRar from: http://www.rarlab.com/

Select files, right click and select Add to Archive
Use Browse.. to create the archive in the folder above
Change Archive Format to Zip
Enable Create Archive Format
Select Advanced tab
Select SFX Options
Select Setup tab
Enter setup.exe or msiexec /i xxx.msi into the Run after Extraction field ( No quotes or other stuff … )
Select Modes tab
Enable Unpack to temporary folder
Select text and Icon tab
Enter a more appropriate title for your task
Select OK
Select OK

This was mostly swiped from the bottom of:
http://stackoverflow.com/questions/27904532/how-do-i-make-a-self-extract-and-running-installer

k2000 – Update Drivers

There are several places where you can “update” drivers in the Windows K2000 deployment server.  In “Library’ — “Driver Feed”  –  search for then click on a model and there is a drivers ‘download and install’ function which may be all you need …

driverk2000

If you need to add drivers that aren’t available through the driver feed mechanism you can add them to folders on the K2000 server …  My location is at:

\\k2000\drivers\kbe_windows_x64\lynna

Just connecting to \\k2000

giving the username  k2000\admin and the password that is set on the server for

“Settings – Maintenance” — “General Settings” —  “Driver/Restore Share password”

 

Windows – Change computer decsription from command line

Sometimes it’s useful to use the computer description field to store information like the the image version.  I typically do this in automated post imaging tasks, however, it is sometime necessary to manually reset this description field.

The command line to do that is:

net config server /srvcomment:computer_description

See: http://lifeofageekadmin.com/changing-windows-computer-description-from-a-command-prompt/

Software – VectorWorks nethasp.ini network license file locations

For VectorWorks we use a “dongle” attached to a network license server.  To configure this on the clients use the “nethasp.ini” file pointed to our license server. That file needs to live in /etc on Macs and in the program directory on windows.  For more information see:

http://kbase.vectorworks.net/questions/469/NetHASP.ini+Configuration+Guide