The region settings deployment still seems pretty broken. Haven’t tried Windows System Locale deployment yet. Does anyone know if it’s any better nowadays?
During onboarding, do you configure any local users? I had them add this bit to region settings because I found that if the user was created but wasn’t provisioned by Ensure-UserProfileExists then Region Settings would fail consistently.
# This script seems to work more reliably when we ensure the user profile exists and has been logged into at least once
if ($UserName) {
$User = Get-LocalUser -Name "$UserName"
Ensure-UserProfileExists -UserName $UserName -SID $User.SID
}
That’s why there’s a $username parameter now in region settings. If you have more than one created user, it might be worth seeing if we can get them to modify it to take an array of names
Only our local admin account. I also run the create profile deployment but I think that is different to creating a local user.
Yea, still no luck. Region isnt changing. Having to log into an account would also be annoying.
Any news on the progress?
Thanks,
I had hoped the Region (beta) deployment might be working, but its not. We are in Australia and the date and time is correct on the login screen after deployment but as soon as you login with an account it is USA region, timezone pacific. Would be great if this could be resolved.
Same here, I’m in Australia.
The TimeZone task works (usually when you run it after the deployment).
For the "Region (beta) " I had it working a few times still can’t figure it out why/how but most of the time it is not.
It is causing a lot of issues as the Regional setting like date format, currency… won’t match with Australia.
Any chance to have another look Immy team?
On the task, it is mentioned to enter a “UserName”.
Can we have a bit more explanation about it please?
Thank you very much to make our life easier!!
Still love ImmyBot
It just doesn’t work. We have given up and now run this on all PCs when deployment is complete. It sets location, region, time settings, and timezone (this is for Qld Australia no no daylight saving).:
Set-WinHomeLocation -GeoId 12 # 12 = Australia
Set-Culture en-AU
Set-WinSystemLocale en-AU
Set-WinUILanguageOverride en-AU
Set-WinUserLanguageList -LanguageList en-AU -Force
Set-TimeZone -Name “E. Australia Standard Time”
For east coast observing daylight saving, change last line to
Set-TimeZone -Name “AUS Eastern Standard Time”
3 Likes
Hello,
We would greatly appreciate the addition of features to set the default language and time zone. Being based in Montreal, the PC language must be set to French, and we currently have to modify this manually after each Immybot installation.
Hi Team,
We are still seeing an issue with Windows language/region configuration during onboarding.
The Windows System Locale/Culture/Language task either does not appear to be available now or is not working reliably for us. After deployment, the device defaults back to US settings, and we have to manually change it to UK.
Our requirement is for devices to be set to the following:
Region / format: English (United Kingdom)
System locale: en-GB
Location / Geo: United Kingdom
Could you please confirm:
Is the Windows System Locale / Culture / Language / GeoID task still supported and available?
Is there any updated recommended method in ImmyBot for forcing the UK region instead of defaulting to the US?
Are there known differences in behavior between Windows 10 and Windows 11 for this setting?
Is the issue expected to be handled at the system level, user profile level, or both during onboarding?
Currently, the only reliable workaround seems to be manually editing the settings after deployment, which is not ideal for onboarding.
Please let us know if there has been any update or best practice for this situation.
Thanks