Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, November 23, 2017 9:30 PM
Hi,
I have a simple set up with a user on a workgroup that cannot change the system time:
And what privilege might this be?
Is this unique to WORKGROUPs?
Boyd
BDM
All replies (5)
Friday, November 24, 2017 9:19 AM
Hi Boyd,
Firstly, open CMD as administrator and run your command again.
If still no use, look at the following KB
You cannot change system time if RealTimeIsUniversal registry entry is enabled in Windows
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, November 27, 2017 2:58 PM
Sorry for the delay in responding.
Yes it works if I run the CMD as administrator.
This very odd given that I am logged in as the same administrator under which I launch CMD, but a bit of a diversion. Actually sounds like a bug.
I do require that people logged on as USER be able to set the time and do not have the Admin name/pw with which to launch CMD.
BDM
Tuesday, November 28, 2017 1:27 AM
>>I do require that people logged on as USER be able to set the time and do not have the Admin name/pw with which to launch CMD.
I am afraid that it can’t be done.
Standard user can’t make changes on computer, system will ask for admin permission. If user set system time via CMD directly, it does will show this error message “A required privilege is not held by the client”, only if User run CMD as Administrator and provide credential, system will accept change. It’s by design.
Please understand.
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, November 28, 2017 5:16 PM
Then I suggest the Microsoft team come up with a work around to this design RFN because this makes Win10IOTENT unfit for it's intended purpose: IOT embedded.
It is absolutely imperative that an embedded machine be able to be time synched by the running application running not-as-an-admin.
There is no discussion on this point of requirement.
It must be automatic. It cannot depend on WEB servers. It cannot depend on Ethernet connectivity. It cannot have Admin authority. It must be time-adjusted by the embedded application.
This one thing makes Win10 unusable as an embedded platform.
I cannot depend on W32TM.
BDM
Wednesday, November 29, 2017 3:38 PM
As a follow-up, what's the point of granting USERS permission in the Local Policies to change the time and zone if this action accomplishes nothing?
Boyd
BDM