Hello,

i`am workinhg on a Vista Rollout with SCCM 2007, now i want to change the keyboard settings from US-International to Belgium (AZERTY).

i no with Lite-touch thats no problem, i can do it in the Customsetting.ini.

In de TaskSequencer from SCCM, i can t find nothing to change this.

i already trayed to do this with a RegTweak, no luck yet.

Need some help with this, any sugestions ?

Thanks,

Fred

you should be able to define that via windows SIM

have you tried it ?

To configure Windows settings

•

In the Answer File pane, all the settings you added are displayed. Select and configure each setting as specified in the following table.

Component Value

Microsoft-Windows-International-Core-WinPE

InputLocale = <Input Locale>

SystemLocale = <System Locale>

UILanguage = <UI Language>

UserLocale = <User Locale>

Microsoft-Windows-International-Core-WinPE\SetupUILanguage

UILanguage = <UI Language>

Edited April 21, 200818 yr by anyweb

Yep,

Try that already,

in SCCM you can make a package with a Customsettings.ini and a Unattended.xml, and you can use this files.

i changed the settings in the Unattended.xml throu the SIM, only gave me a error (0x00000001)

I doint no when i use the Unattended.xml or the Customsettings.ini in SCCM, i have to fill them with all the info or that the tasksequencer only takes that info and get the rest from wats supplied throu the Tasksequence it self

are you doing Zero Touch installs ?

Both,

fore the rollout we are gona use Lite-Touch (pxe) bud after the rollout, for maintenance, we will use zero-touch.

we are gona use Lite-touch for the rollout because first we have to install extra ram in de machines, so its easyer to do a pxe-boot and start the deployment, we doint want the machines to start before the hardware upgrade

Edited April 21, 200818 yr by omnifred

Both,

fore the rollout we are gona use Lite-Touch (pxe) bud after the rollout, for maintenance, we will use zero-touch.

we are gona use Lite-touch for the rollout because first we have to install extra ram in de machines, so its easyer to do a pxe-boot and start the deployment, we doint want the machines to start before the hardware upgrade

Did you find out a solution?