Azure / Azure/azure-quickstart-templates
Configure locale, format and culture settings from default en-US for Current User, Welcome Screen and New Users
- Dominant language
- Bicep
- Stars
- 14.9k
- Forks
- 16.2k
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 6
Description
**_Issue Details_**
Azure VMs come with default en-US locale, format and culture settings which isn't compatible with en-AU applications, databases, servers and scripts. This scenario allows us to continue to use the DEVOPS Pipeline without user interaction and can be executed during the start of the Windows build using Anisible->PowerShell via WinRM. This was verified on our pipeline.
**_Solution_**
Using PowerShell to script the following
1. Configure the current user with en-AU using “Set-Culture” & “Set-WinHomeLocation”
2. Capture the en-AU configuration in *.reg format for HKCU\System\Control Panel\International
3. Copy the *.reg file into 2 separate files
a. Replace the SID on first file to “.DEFAULT”
b. Replace the SID on second file to “DEFAULT_USER”
4. Load the default hive “C:\Users\Default\NTUSER.dat”
5. Import both *.reg files
6. Unload the default hive
This changes all 3 areas we needed and any new users who log in get the en-AU formats, locations and region settings.
1. Current user
2. Welcome screen
3. New users
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Windows VM build or startup entry point that runs Ansible and PowerShell through WinRM. Verify how the current-user, welcome-screen, and default-user registry hives are handled, then validate the en-AU settings in an Azure VM and confirm that the pipeline runs without interaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, azure, powershell
- Domain
- cloud, devops, infrastructure, internationalization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100