Administer > SA Provisioning > OS sequence-based provisioning > Microsoft Windows installation profile requirements

Microsoft Windows installation profile requirements

If you are creating a Windows OS Installation Profile, the configuration file must be an unattended installation response file that conforms to the following:

  • The OemPreInstall key must be set to YES. If this key is not set, OS Provisioning will set it automatically.
  • A network configuration must be specified so that when the operating system boots for the first time, it will get a valid IP address.
  • Any dialog boxes that may appear during the Text and GUI mode portions of Windows setup must be set so that they do not appear during the OS Provisioning process.

See Sample response file for Windows Server 2003 below for an example of a valid Windows response file.

Sample response file for Windows Server 2003

The following sample response file shows typical valid responses for a Windows Server 2003 installation. This sample response file contains the required settings for Windows Server 2003 provisioning with SA Provisioning.

[Data]

AutoPartition=0

MsDosInitiated=0

UnattendedInstall=Yes

 

[GuiUnattended]

AdminPassword=3mbree0

OEMSkipRegional=1

OEMSkipWelcome=1

;004 Pacific Standard Time (GMT-08:00) Pacific Time (US and Canada); Tijuana

;See http://unattended.sourceforge.net/timezones.php

TimeZone=004

 

[Identification]

JoinWorkgroup=WORKGROUP

 

[LicenseFilePrintData]

AutoMode = PerSeat

 

[Networking]

 

[Unattended]

ExtendOemPartition=1

FileSystem=ConvertNTFS

OemPnPDriversPath=drivers\nic\intel

OemPreinstall=Yes

OemSkipEula=Yes

UnattendMode=FullUnattended

 

[UserData]

ComputerName=*

FullName="Windows Server 2003"

ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX