Windows-itpro-docs: We had to add Administrator to the policy? Bug or feature ?

[i5513]

We needed to add "Administrator" user to this policy in order Administrator can shutdown system remotely via shutdown.exe /r /m \xxx command. But this policy has "Administrators" group as allowed. Administrator is in Administrators group.

Do you know what is happening here ?

If Administrator is not in the list of the policy "Access Denied (5)" is show and not action is taken.

Thank you very much

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: c1f6bded-a1b2-1ef0-90a8-f313afa73557
• Version Independent ID: 4a55f951-788c-cac1-5bd6-496ef533cfd6
• Content: Force shutdown from a remote system (Windows 10)
• Content Source: windows/security/threat-protection/security-policy-settings/force-shutdown-from-a-remote-system.md
• Product: w10
• Technology: windows
• GitHub Login: @Dansimp
• Microsoft Alias: dansimp

[MaratMussabekov]

Hello @i5513 ,
from my experience, there is no need to add Administrator account to the policy separately.
are you sure you are running command by account that has admin permission for the remote machine?
Thank you

[i5513]

I'm sure, When I add the user "administrador" to the policy it works.
Administrador user si in administrators group (Administradores) .

(Windows Spanish localization)

Thanks

El vie., 25 oct. 2019 8:42, MaratMussabekov [e-mail]
escribió:

Hello @i5513 https://github.com/i5513 ,
from my experience, there is no need to add Administrator account to the
policy separately.
are you sure you are running command by account that has admin permission
for the remote machine?
Thank you

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/windows-itpro-docs/issues/5152?email_source=notifications&email_token=AAATJXTAYT6OEZPZJBHFXY3QQKIMFA5CNFSM4I7NQZS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECHLOOY#issuecomment-546223931,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAATJXQKFS47QY2JLTY25ATQQKIMFANCNFSM4I7NQZSQ
.

[MaratMussabekov]

Hello @i5513 ,
I have made several checks and was unable to reproduce your issue (it worked fine without adding Administrator to the policy separately).
I would recommend you to check other applied GPOs (may be there are some conflicts?) and create a request in Microsoft Support
Thank you

[i5513]

Thanks Marat, I will escalate the issue, so maybe somebody at my organization open the request, or review the applied GPOs.

[e0i]

@i5513

The issue is being marked as resolved as the problematic behavior couldn't be reproduced.

Feel free to re-open this issue if there is still something you'd like to suggest to improve the document.

Thank you for taking the time to provide feedback and follow-up.