Windows Server 2016, 2019, 2022, Windows 10 and Windows 11: Date and time "Some settings are managed by your organization".

When you're using the new "Modern" date and time settings in Windows Server 2016, 2019, 2022, Windows 10 and Windows 11 you may find that you can't set the correct date and time and the value "Some settings are managed by your organization".





- While you're here -
Why not check out our Windows Server Documentation and Audit Tool?




The simplest way around this is to go back to the proper control panel using Start, Run, "Control.exe" and searching for "Set the date".




 Within here you can set the date and time manually as required




If you try and click the Change time zone button you may again get access denied...

To resolve this open an elevated command prompt by right clicking the command prompt and selecting Run as Administrator 

From there run the command
rundll32.exe shell32.dll,Control_RunDLL timedate.cpl

This will open the Data and Time control panel app elevated as an Administrator.


Comments

  1. I had read many articles that talked about setting registry and group policy, but the solution is even simply as shown above.

    Thanks this worked perfectly.

    ReplyDelete
  2. i tried but APPLY is grey as shown in last screen, it did not worked for me.

    ReplyDelete
    Replies
    1. You need to be an Administrator to change the system time. Or you can logon as an Administrator goto gpedit.msc

      Computer Configuration > Windows Settings > Security Settings > User Rights Assignment > Change the system time

      You can give this right to non administrators too.

      Delete
    2. The built-in Windows Settings Microsoft Store app, though, seems to supersede group policy and changes made via Control Panel Date & Time. My login is an admin, has Change the system time authority in group policy, and can change the date in Control Panel; but this reverts to the current date in a second or two. In Windows Settings the 'Set time automatically option' can't be changed (i.e., is locked On) and still the message 'Some settings are managed by your organization' appears in the Settings.

      Not a biggie since my need to change the server date has abated but for future reference it might help to know how to do this. IMHO I've felt I have less control over a Windows Server once Microsoft added the mobile app layer on top of the existing interface (which we shouldn't be using anyway, favoring remote administration). This is an Azure VM hosting Microsoft Dynamics so it may be that some of that infrastructure is getting in the way.

      Thanks for responding!

      Delete
    3. Yup! Agree the multi layer of user interface that sort of supersede one another but not properly is annoying! I'll have another look I can't quite see why these UI's don't match up.

      Delete
    4. Is the Azure VM on an Active Directory domain? I'm wondering if the new UI is doing the time change or whether because you're on a domain all servers are syncing with the Primary Domain Controller FSMO role and the UI is just greying the button out to show you that (whereas the old UI lets you change the date and time only to reset it anyway)?

      Delete
    5. Also worth trying to run w32tm /query /configuration and see what it says...

      Delete
    6. You are definitely right about Windows AD. Although a standalone server the problem server has AD installed to test some configuration issues. On another server with a similar setup but without Windows AD, all is well. A good spot.

      And thanks for pointing me toward W32tm. I am a little reluctant to fiddle with it right now since the Dynamics hosted on the server is in use by students; there may be a dependency on W32tm I'm not aware of. But when the term ends and before I replace the server, I'll have the opportunity.

      Much appreciated; cheers!!

      Delete
  3. Right but if set time automatically is On in Settings (Windows Server 2016) then the date / time changes back. And since some organization(?) is managing that, still can't fix it. I know it's been awhile but any ideas?

    ReplyDelete
  4. thank you its really works

    ReplyDelete

Post a Comment

Popular posts from this blog

TFTPD32 or TFTPD64 reports Bind error 10013 An attempt was made to access a socket in a way forbidden by its access permissions.

Windows Server 2019 desktop icons such as My Computer, Windows cannot access the specified device, path, or file.