# Windows - Time Zone and Language Group Policy ### Configuring the time zone using Group Policy
**Supported operating systems:** Windows 2003/XP and higher, up to and including Windows 10 and Windows Server 2016 (all versions and builds). **Supported deployment methods:** all, including direct (*bare-metal*) installations and image-based deployments using technologies such as Citrix Machine Creation Services (MCS) and Citrix Provisioning Services (PVS). |
**Note:** all available time zones are also listed in the registry in the key *HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Time Zones*. |
**Note:** by default, the value name is used as the name of the registry item (as is visible in the image above). It is possible to rename the registry item afterwards, but please be aware that whenever you make changes to the registry item, it’s name will revert back to the value name. |
**Supported operating systems:** Windows 7 / Windows Server 2008 R2 and higher, up to and including Windows 10 and Windows Server 2016 (all versions and builds), with PowerShell 5.1 installed (this is a requirement!). |
1 | Set-TimeZone -Id "W. Europe Standard Time" |
1 2 3 4 5 6 7 | \[string\]$TimeZone = "W. Europe Standard Timeeeeeeee" try { Set-TimeZone -Id $TimeZone Write-Host "Success: the time zone $TimeZone has been set" } Catch { Write-Host "Error: the time zone $TimeZone does not exist!" } |
**Note:** running the *Set-TimeZone* PowerShell command as a startup script may end in error 5 “access denied”. At least that is what happened when I tested it on a server running Windows Server 2016 version 1607. I do not know why this happened, especially since the group policy is executed by the local system account. |
**Supported operating systems:** Windows 2003/XP and higher, up to and including Windows 10 and Windows Server 2016 (all versions and builds). |
**Supported operating systems:** Windows 2003/XP and higher, up to and including Windows 10 and Windows Server 2016 (all versions and builds). **Supported deployment methods:** all, including direct (*bare-metal*) installations and image-based deployments using technologies such as Citrix Machine Creation Services (MCS) and Citrix Provisioning Services (PVS). |
**Note:** in Windows, the code page is referred to as *system locale*. I am not in agreement with this, because the system locale also includes other components such as the display language (the Windows language) and the default input language (the keyboard layout) for the system user. These settings determine what a user sees at the Windows logon window (CTRL+ALT+DEL). In therefore in this article use the word code page and not system locale. |
**Note:** by default, the value name is used as the name of the registry item (as is visible in the image above). It is possible to rename the registry item afterwards, but please be aware that whenever you make changes to the registry item, it’s name will revert back to the value name. |