locked
Change system time and network configuration operators RRS feed

  • General discussion

  • On windows 7 Pro, I allow a specific local user to change systeme time.
    (SeSystemTimePrivilege)

    I also add this user to Network Configuration operators local Group.

    Then the user i unable to change system time.

    UAC ask for an administrator account to change system time.

    If i remove user from Network Configuration operators local Group, the user
    can change system time again.

    Is there a possible workaround to have a user with this privilege belonging
    to Network configuration operators group or is it a unresolve bug in Windows
    7?

    Thanks for your answers

    • Changed type Kim Zhou Monday, October 8, 2012 2:37 AM
    • Changed type Kim Zhou Monday, October 8, 2012 2:37 AM
    Tuesday, September 11, 2012 1:39 PM

All replies

  • Hi,


    How about turning off UAC feature for a test?


    Kim Zhou

    TechNet Community Support

    Wednesday, September 12, 2012 7:59 AM
  • Turning off UAC (LocalAccountTokenFilterPolicy = 1) or adding Network configuration Operator the right to change system time did'nt change anything.

    UAC always ask for an admin account to change system time????

    Wednesday, September 12, 2012 8:33 AM
  • When i us whoami /all on the user account, i see that i have loose the token SeSystemTimePrivilege when user account belongs to Network Configuration operator.

    I can see that i really belong to that group by this group has an attribute "Group used for deny only"!

    Is this that fact that filter my SeSystemTimePrivilege token prior to UAC?

    Wednesday, September 12, 2012 9:03 AM
  • Hi,


    Does the issue appears if we set this account as Administrator rights? 


    Kim Zhou

    TechNet Community Support

    Sunday, September 16, 2012 1:15 PM
  • This is old, but I might have found the solution. The UAC does not play nice with the network configuration operators group.  I bet you could change the time if you entered the credentials of the same user when prompted. Unfortunately, this is a bug in token filtering, and the only workarounds are to enter credentials at the UAC or to use a different account.
    Tuesday, November 3, 2015 9:03 PM