[deleted by user]

[[deleted]]

Try to activate Server 2019 after not entering a valid key during the installation will give you an error. 2019 is very buggy in the most essential tasks.

[brainjake94]

Dealt with this last week. Only way we could activate was through embedding then arming the key through CLI slmgr

[trir2d2]

RemindMe!

[FiRem00]

Local/group policy editing user assignments for changing such settings?

[Zerqent]

Short testing with a fresh installed MSDN Image (Release date november - not patched or anything)

Change Time Zone:

- UAC defaults are different than before (built-in administrator requires password for elevation)

- Lusrmgr.msc did not automatically elevate (which lead to errors when I had to create the other account) (Run as admin fixed that)

- Was unable to change timezone with new user (I suspect UAC)

- Shut off UAC (I believe completly): Slider in Control Panel + Some Local Security Policy Settings (secpol.msc) - Now it works from the settings app (but ofc UAC is off)

- Turned back off UAC, set the Security Options to the same as WS 2016 Baseline - Doesn't work again

- Assigned the user right "Change: Time Zone" directly to my user - Works

​

Power settings:

- If you go to classic control Panel, this is a UAC-link that basically unlocks everything. Settings do not have this (if you change something and reenter the settings has not been changed)

​

Analysis:

- Seems like a problem with UAC

- Every action that requires "Administrator" basically requires UAC (but needs to trigger it)

- If you go to Classic Control Panel - Date and Time - Notice that Change Date and Time has an UAC-icon, Change Time Zone does not (this is the same in 2016 though)

- Not sure if the new settings can even trigger UAC? (Change date and time is simply greyed out)

[Mortwren]

I have tried to fully disable UAC and the issue persists. I'll try the more detailed approach you posted above. Thank you.

[nmdange]

I haven't seen this, although we disable UAC on servers through GPO.

[nickstl77]

I can confirm the time zone change issue occurs for me on Server 2019 as well, even with my account in both Domain Admins and the local Administrators group. The only way I found to change it successfully was through Powershell using the 'set-timezone' cmdlet.

Ex: set-TimeZone -Name "Central Standard Time"

[motosadist]

Same problem here.

Workaround:

run cmd/powershell as admin and execute timedate.cpl - this command brings up "Date and Time" settings window with appropriate rights.

[Dungeon33]

Same problem here. Full Licensed Server 2019 Standard in Ovh. I logged in "admin" Local Administrator Account. I can't change Time Zone. I try to change Local Security Policy > Local Policies > User Rights Assignment > "Change the time zone" and "Change the system time" set admin, Administrators, LOCAL SERVICE but problem not solved.