For SAS IT Staff
Windows XP Autobuild Procedure
Platform: Windows XP Professional
Level of Difficulty: Expert
· Make sure the computer is already licensed to run Windows XP Professional. Computers with Windows XP Home, Vista, or older versions can get licenses through the MS Campus Agreement at: software.rutgers.edu
· If the computer has been in use, make sure all user data has been backed up
· Make a list of all local users who will need accounts re-created
· Take note of any applications that need to be reinstalled after Windows XP is installed.
Getting the media:
· If you don't already have the media, burn a CD or DVD using the ISO images found at:
(The above locations are restricted to valid tech.sas users).
· When you burn the media, write the date of the image on the disc.
· Periodically check the dates of the versions stored at \\tech.sas.rutgers.edu\images\nomnt\autobuild\ to make sure you are using the latest version.
Install Windows XP:
· Connect the PC to the network
· Boot the computer with the Autobuild disc
Note: You may need to launch the Boot Menu or modify the BIOS to enable the system to boot from a CD.
· When the message appears, "Press any key to boot from CD...", press any key.
· A web page titled “SAS XP Autobuild” will launch.
· Log in using your tech.sas password.
If the computer is in DHCP already, or is connected to a network that accepts unknown hosts, you should obtain an IP address and move on the next screen (Source selection)
If not in DHCP, click the “Network issues” link on the left for more information
· At the next page, select the correct source:
CD version: “Server” should be selected for “Source.”
DVD version: “Local disc” should be selected for “Source.”
· Click “Next” to continue
· Select the following options:
o Partition size: leave “Use whole disk” selected unless a custom partition scheme is required. Leave “Quick format the drive” selected
o Computer Name: use the computer's serial number or service tag, or other unique identifier (e.g. Rutgers hostname)
o Workgroup: “SAS”
o Computer Description (optional): enter the make and model of computer
o Build Type: select "Fully customized" unless another option is specifically required
o Antivirus Software: select “ON-CAMPUS RADS” for on-campus computers or “OFF-CAMPUS RADS” for laptops and off-campus computers.
o Install Novell Client: select “Yes” unless the department does not have Novell, or if being deployed off-site
o Install Office: select “Yes” if the user has a valid Microsoft Office license. Select "Without Outlook".
o Enable Microsoft Remote Management Features: leave “Yes” and the list of IP addresses as the defaults unless additional IP addresses are specifically required.
· Click “Go!” to start the Autobuild.
· After Windows XP installation finishes, the computer will reboot
· After the computer reboots, the automated build will resume. Do not interrupt the scripts.
· The computer will reboot again.
· When the Windows Welcome screen or Novell client appears, log onto the workstation as “tech”
· At the dialog displaying “Registered Owner is SAS; Registered Organization is Rutgers University,” click “No” unless necessary
· At the “Windows Update” dialog box, click “Yes.”
· Follow the prompts at the Windows Update web page to install Critical Updates.
· Reboot the computer and re-run Windows Update as many times as necessary to obtain all critical updates.
After Windows XP is installed:
· Check Device Manager to make sure all devices have been properly installed:
Click on Start > Control Panel > Performance and Maintenance > System.
Click the Hardware tab
Click Device Manager
Look for any devices that have a red “X” or yellow “!”. The drivers for these devices will need to be installed. You can usually locate them on the driver CD that came with the PC, or on the manufacturer’s web site.
· Recreate user accounts as necessary.
Manually created local usernames must match the users’ Novell usernames (even if Novell is not installed on the computer). In most cases the Novell username will be in the format [firstinitial+lastname]. For example, Henry Rutgers would be "HRUTGERS". If you are unsure please check with the Novell administrator for the department’s name context.
If the Novell client is installed and the users’ department has Dynamic Local User creation, their local accounts will be automatically created the first time they log onto Novell.
If the department does not have Novell, create a local Windows username that matches the user’s NetID.
· If necessary, restore all user data after the accounts have been created and the user has logged in at least once to create their “Documents and settings” folder
· Reinstall applications as needed,
· Reinstall drivers for connected peripherals such as printers and scanners.
· IMPORTANT (If Novell is installed): Make sure the first person to log in to Novell is either the intended primary user of the computer, or a user within the Novell context where the system will be regularly used.
· Make sure that Wake On Lan (sometimes called "Remote Wakeup") is enabled. This is important for remote administration.
· Check boot sequence. Make sure hard drive comes first. Unless there's a reason not to, also disable all other boot devices.
· Enable the BIOS setup password so that users can't change the settings (not the prompt for password at startup -- we just want to prevent people from changing the bios settings). For the password, contact your supervisor.