ConfigMgr
Apply Windows Settings
Topics: ConfigMgr
Task Sequence Steps
Apply Windows Settings
This post is part of our Task Sequence – Beyond the Docs series.
This page will be quite limited to specifics about the step itself, to see it integrated into OSD, check out the Combination Page. Capture, Apply, Network and Windows Settings
MS Docs
Variables
- OSDComputerName
- OSDLocalAdminPassword
- OSDProductKey
- OSDRandomAdminPassword
- OSDRegisteredOrgName
- OSDRegisteredUserName
- OSDServerLicenseConnectionLimit
- OSDServerLicenseMode
- OSDTimeZone
- OSDWindowsSettingsInputLocale
- OSDWindowsSettingsSystemLocale
- OSDWindowsSettingsUILanguage
- OSDWindowsSettingsUILanguageFallback
- OSDWindowsSettingsUserLocale
PowerShell
- Get-CMTSStepApplyWindowsSetting
- New-CMTSStepApplyWindowsSetting
- Remove-CMTSStepApplyWindowsSetting
- Set-CMTSStepApplyWindowsSetting
So many variables for this step. You can see how they compare to the step gui. This step is one of the essentials to allow you to customize your OSD to fit your environment. You need to assign a different language, keyboard layout, time zone, and so many more thing, this is the step that does it. It takes that information, slips it into the unattend.xml and it gets applied to the Windows Setup during Windows Setup Process. It’s pretty freaking sweet.
Step
NOTE: If you set a variable for these options in your TS, they will NOT be overwritten by the step. Your Pre-Set variables will trump what the steps options have available.
Find all of our Task Sequence – Beyond the Docs series posts here.
About Recast Software
1 in 3 organizations using Microsoft Configuration Manager rely on Right Click Tools to surface vulnerabilities and remediate quicker than ever before.
Download Free Tools
Request Pricing