If you find that you are a server administrator but you still don’t have permission to a specific file or folder, you came to the right place.
This issue is extremely common among people that use VMs on their Windows Server machines.
People have been consulting among themselves on online forums and asked for help on multiple forums.
It seems the issue might be caused by the UAC of your PC or some wrongly assigned permissions on your server.
In today’s article, we will explore some of the best solutions for this problem.
Please make sure to follow the steps presented in this guide carefully to avoid causing any other issues.
What to do if the WindowsServer administrator doesn’t have permission?
1. Create another group for domain admins
- Open the Microsoft Management Console (MMC) snap-in.
- Right-click on the root connection of the domain that has issues -> select Properties.
- Click on the Group Policytab -> click New -> name it.
- Right-click the newly created GPO -> select Properties -> modify the settings to your desire -> click Ok.
- Inside the Properties dialog box for the domain root -> click Edit.
- Navigate to the MMC snap-in.
- Click on Computer Configuration -> Windows Settings -> assign group to specific folder.
2. Set full permission for Domain account
- Open MMC -> right-click the domain account -> select Properties.
- Click the Sharetab -> allow the user full permissions.
- Select the Security tab -> allow the admin full permission.
- Click Ok to save the settings.
Note: If the domain account is baned domain/admin 2, then use this name for the permissions in both categories.
3. Disable UAC completely
In order to disable the UAC completely, you will need to follow these steps:
- Click the Cortana search box -> type Regedit -> press Enter to open the Registry Editor.
- Navigate to the following location by using the left pane:
- Right-click on the right-side pane -> select New -> DWORD (32bit).
- Set the name EnableLUA and set the value to 0.
We hope this guide managed to help you solve the issue caused by the Windows Server administrator not having the required permissions.
The options presented in this list are ordered from the least to the most invasive, so please make sure to follow the steps carefully.
Please feel free to let us know if you found this guide helpful, by using the comment section below.