Scribbles which may prove useful: 2012

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipLocaleSelection=YES
SkipTimeZone=YES
UILanguage=en-US
UserLocale=en-GB
KeyboardLocale=en-GB
TimeZoneName=GMT Standard Time

Current application command line switches

Java: jre-6u31-windows-i586-s.exe /s ADDLOCAL=ALL
Mcafee agent: Framepkg.exe /install=agent /s
Google Chrome: msiexec.exe /qn /i googlechromestandaloneenterprise.msi
Flash player: flashplayer11-3_p2_install_win_ax_041812 -install
Office 2010: setup.exe /config ProPlus.WW\config.xml (see blog post above about customising Office 2010)
Office Communicator: msiexec.exe /i communicator.msi /qb! /norestart

Timezone stuff

I have solved my own issue. But I shall leave it up here, as another noob might find this useful.

The 'Userlocale' is required in a "en-US" type format. For all non-US types, the documentation wasnt' very helpful!

It's taken me a while to track down how this format hangs together.

The first part is the language - look up here ...

http://en.wikipedia.org/wiki/ISO_3166

The second part is your country - look it up here ....

http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2

e.g for the UK, I simply needed "en-GB" in my UserLocale section ...

This also worked for the "KeyboardLocale" ... so my final 'UK' settings are thus ...

SkipLocaleSelection=NO
SkipTimeZone=NO

KeyboardLocale=en-GB
UserLocale=en-US <<< this is the language - en-US is "English", there is no 'UK' option (even though they spell "colour" wrong ;) )
UILanguage=en-GB
TimeZoneName=GMT Standard Time

Sodding language settings Windows 7 MDT 2010 WinPE

It seems there are several comments heading in the right direction. I thought I would clarify and summarise.

The American language default is a common thing going back to XP and before. With a RIS install of XP you had to edit the dosnet.inf and txtsetup.sif files - anyone whats to know how to do that just email me.

Okay, lets get back on track. The first language in the Microsoft world is American or "English (United States)" as they call it. The operating system installation process has to be run using their Mother tongue.

Now, the UILanguage setting refers to the language used for the OS installation, NOT the language that the OS can be installed with. Got it? Great!

I don't believe the locale setting in bootstrap.ini makes an iota of difference. Anyone with knowledge to the contrary please let me know.

For clarity, I will two sets of settings for deploying Windows 7 / 2008 or XP / 2003 - do not use them both! Comments in {} can also be removed.

To deploy Windows 7 or 2008 with English as the only language:

SkipLocaleSelection=NO {so you can see that the settings are correct - after the first test run, change this to YES}

;The UILanguage setting is the language for the installation process and NOT the deployed OS. It has to be American.

UILanguage=en-US

UserLocale=en-GB

KeyboardLocale=en-GB

To deploy Windows XP or 2003 with English as the only language:

SkipLocaleSelection=NO {so you can see that the settings are correct - after the first test run, change this to YES}

;The UILanguage setting is the language for the installation process and NOT the deployed OS. It has to be American.

UILanguage=en-US

InputLocale=0809:00000809

KeyboardLocale=0809:00000809

Thats it. Simple when you know how!

Command line switches for installation

http://msdn.microsoft.com/en-us/library/windows/desktop/aa372024(v=vs.85).aspx

The executable program that interprets packages and installs products is Msiexec.exe.

Note Msiexec also sets an error level on return that corresponds to System Error Codes.

The following table identifies the standard command-line options for this program. Command-line options are case insensitive.

Windows Installer 2.0: The command-line options that are identified in this topic are available beginning with Windows Installer 3.0. The Windows Installer Command-Line Options are available with Windows Installer 3.0 and earlier versions.

Option	Parameters	Meaning
/help		Help and quick reference option. Displays the correct usage of the setup command including a list of all switches and behavior. The description of usage can be displayed in the user interface. Incorrect use of any option invokes this help option. Example: msiexec /help Note The equivalent Windows Installer Command-Line Option is /?.
/quiet		Quiet display option. The installer runs an installation without displaying a user interface. No prompts, messages, or dialog boxes are displayed to the user. The user cannot cancel the installation. Use the /norestart or /forcerestart standard command-line options to control reboots. If no reboot options are specified, the installer restarts the computer whenever necessary without displaying any prompt or warning to the user. Examples: msiexec /package Application.msi /quiet Msiexec /uninstall Application.msi /quiet Msiexec /update msipatch.msp /quiet Msiexec /uninstall msipatch.msp /package Application.msi / quiet Note The equivalent Windows Installer Command-Line Option is /qn.
/passive		Passive display option. The installer displays a progress bar to the user that indicates that an installation is in progress but no prompts or error messages are displayed to the user. The user cannot cancel the installation. Use the /norestart or /forcerestart standard command-line options to control reboots. If no reboot option is specified, the installer restarts the computer whenever necessary without displaying any prompt or warning to the user. Example: msiexec /package Application.msi /passive Note The equivalent Windows Installer Command-Line Option is /qb!- withREBOOTPROMPT=S set on the command line.
/norestart		Never restart option. The installer never restarts the computer after the installation. Example: msiexec /package Application.msi /norestart Note The equivalent Windows Installer command line has REBOOT=ReallySuppress set on the command line.
/forcerestart		Always restart option. The installer always restarts the computer after every installation. Example: msiexec /package Application.msi /forcerestart Note The equivalent Windows Installer command line has REBOOT=Force set on the command line.
/promptrestart		Prompt before restarting option. Displays a message that a restart is required to complete the installation and asks the user whether to restart the system now. This option cannot be used together with the /quiet option. Note The equivalent Windows Installer command line has REBOOTPROMPT = "" set on the command line.
/uninstall		Uninstall product option. Uninstalls a product. Note The equivalent Windows Installer Command-Line Option is /x.
/uninstall	/package /uninstall [;Update2.msp \| PatchGUID2]	Uninstall update option. Uninstalls an update patch. Note The equivalent Windows Installer Command-Line Option is /I withMSIPATCHREMOVE=Update1.msp \| PatchGUID1[;Update2.msp \| PatchGUID2] set on the command line.
/log		Log option. Writes logging information into a log file at the specified existing path. The path to the log file location must already exist. The installer does not create the directory structure for the logfile. The following information is entered into the log: Status messages Nonfatal warnings All error messages Start up of actions Action-specific records User requests Initial UI parameters Out-of-memory or fatal exit information Out-of-disk-space messages Terminal properties Note The equivalent Windows Installer Command-Line Option is /L. Note* For more information about all the methods that are available for setting the logging mode, see Normal Logging in the Windows Installer Logging section.
/package		Install product option. Installs or configures a product. Note The equivalent Windows Installer Command-Line Option is /I.
/update	[;Update2.msp]	Install patches option. Installs one or multiple patches. Note The equivalent Windows Installer command line has PATCH = [msipatch.msp]<;PatchGuid2> set on the command line.