Deployment Solution

Using sysprep is not easy. It often gives errors, and there are not many scripts that show how a sysprep.inf file is built. In my demo environment I need to roll out XP clients fast for demonstrations. Below you will find the script I'm using.

1. Copy the text to Notepad.
2. Change the environment settings, and save it as sysprep.inf.

[Unattended]
OEMSkipEula=YES
ExtendOemPartition=1
OemPnPDriversPath=\Sysprep\VMware\Drivers
UpdateInstalledDrivers=No
DriverSigningPolicy=Ignore

[GuiUnattended]
AdminPassword="*"
OEMSkipRegional=1
TimeZone=110
OEMSkipWelcome=1

[UserData]
ComputerName="*"
OrgName="DVSnet"
FullName="DVS demo network"
ProductKey=?????-?????-?????-?????-????? (place your XP serial # here)

[Identification]
JoinWorkgroup=DVStemp

[Display]
ConfigureAtLogon = 0
BitsPerPel = 16
XResolution = 1024
YResolution = 768
AutoConfirm = 1

[Networking]
InstallDefaultComponents=YES

[sysprepcleanup]

[GuiRunOnce]

The script is now complete.

I also have a script to rollout Windows 2003 terminal servers.

Below you will find that sysprep.inf.

[Unattended]
  DriverSigningPolicy=Ignore
  ExtendOemPartition=1
  InstallFilesPath=c:\i386
  OemPnPDriversPath=c:\$oem$\$1\drivers\scsi;c:\$oem$\$1\drivers\net
  OemSkipEula=Yes
; the settings below are for the mass storage 
;driver on a HP Dl320 computer. You have to 
;change it if you use other mass storage drivers. 
;But the general idea is correct.

[SysprepMassStorage]
  PCI\VEN_0E11&DEV_B060&SUBSYS_40700E11=C:\$OEM$\$1\drivers\scsi\cpqcissm.inf
  PCI\VEN_0E11&DEV_B178&SUBSYS_40800E11=C:\$OEM$\$1\drivers\scsi\cpqcissm.inf
  PCI\VEN_0E11&DEV_B178&SUBSYS_40820E11=C:\$OEM$\$1\drivers\scsi\cpqcissm.inf
  PCI\VEN_0E11&DEV_B178&SUBSYS_40830E11=C:\$OEM$\$1\drivers\scsi\cpqcissm.inf
  PCI\VEN_0E11&DEV_0046&SUBSYS_40910E11=C:\$OEM$\$1\drivers\scsi\cpqcissm.inf
  PCI\VEN_0E11&DEV_0046&SUBSYS_409A0E11=C:\$OEM$\$1\drivers\scsi\cpqcissm.inf
  PCI\VEN_0E11&DEV_0046&SUBSYS_409B0E11=C:\$OEM$\$1\drivers\scsi\cpqcissm.inf
  PCI\VEN_0E11&DEV_0046&SUBSYS_409C0E11=C:\$OEM$\$1\drivers\scsi\cpqcissm.inf
  PCI\VEN_0E11&DEV_0046&SUBSYS_409D0E11=C:\$OEM$\$1\drivers\scsi\cpqcissm.inf

  PCI\VEN_9005&DEV_00C0=c:\$oem$\$1\drivers\scsi\adpu160m.inf
  PCI\VEN_9005&DEV_0080=c:\$oem$\$1\drivers\scsi\adpu160m.inf

  PCI\VEN_1000&DEV_0010&SUBSYS_40400E11=c:\$oem$\$1\drivers\scsi\cpqarry2.inf
  PCI\VEN_1011&DEV_0046&SUBSYS_40500E11=c:\$oem$\$1\drivers\scsi\cpqarry2.inf
  PCI\VEN_1011&DEV_0046&SUBSYS_40510E11=c:\$oem$\$1\drivers\scsi\cpqarry2.inf
  PCI\VEN_1011&DEV_0046&SUBSYS_40580E11=c:\$oem$\$1\drivers\scsi\cpqarry2.inf

  PCI\VEN_1166&DEV_0213&SUBSYS_00E80E11=c:\$oem$\$1\drivers\scsi\lsicsb6.inf

  PCI\VEN_1095&DEV_0649&SUBSYS_005D0E11=c:\$oem$\$1\drivers\scsi\megaide.inf
  PCI\VEN_1095&DEV_0649&SUBSYS_007E0E11=c:\$oem$\$1\drivers\scsi\megaide.inf

  PCI\VEN_1000&DEV_0030=c:\$oem$\$1\drivers\scsi\symmpi.inf

[GuiUnattended]
  AdminPassword=password
  AutoLogon=Yes
  AutoLogonCount=1
  OEMSkipRegional=1
  OemSkipWelcome=1
  TimeZone=35

[UserData]
  ComputerName=*
  FullName="DVS demo network"
  OrgName=DVSnet
  ProductKey=?????-?????-?????-?????-????? (place your XP serial # here)


[Proxy]
  Proxy_Enable=0
  Use_Same_Proxy=0

[LicenseFilePrintData]
  AutoMode=PerServer
  AutoUsers=999

[Display]
  AutoConfirm=1
  BitsPerPel=16
  ConfigureAtLogon=0
  VRefresh=60
  Xresolution=1280
  Yresolution=1024

[RegionalSettings]
  Language=00000409
  LanguageGroup=1

[Components]
  iis_pwmgr=Off
  iis_inetmgr=Off
  iis_www=Off
  iis_ftp=Off
  TSClients=On
  TSEnable=On

[Networking]
  InstallDefaultComponents=Yes

[Identification]
  JoinWorkgroup=DVStemp

[NetOptionalComponents]
  SNMP=1
  WBEMSNMP=1
  SimpTCP=1

[SNMP]
  Community_Name=public
  Traps=localhost

[TerminalServices]
  ApplicationServer=0
  PermissionsSetting=0
  

You have to change the settings for your environment, and if you use non standard mass storage drivers, take notice of the location mentioned in the script. You have to burn a new disk with Windows 2003 and the scripts so the client sees it.

When you use the script in Altiris Deployment server, you have to place the mass storage drivers in the correct location.

Regards
Erik Westhovens