Domain Admin unable to access NTFS Drive
I have a Windows Server 2016 member server that has a C: and a F: drive.
As Part of our standard file server build we remove all permissions from the root of the F: drive except for:
SYSTEM (Full Control)
Administrators (Full Control)
I've created a new domain user 'jakeadmin' and granted it membership of the Domain Admins group.
Domain Admins is a member of the member server's local Administrators group.
When I logon (via RDP) to the member server FILESERVER-01 as the domain user 'jakeadmin' this user cannot access the F: drive. I then tried adding the Domain Admins group with full control to the root of the F: drive but my 'jakeadmin' user still cannot access the F: drive:
![Weird.png]()
If I logon to Fileserver-01 as a local machine administrator I have no trouble accessing the F: drive at all.
Why can't I browse my F: drive, even if I'm in the Administrators group?
I don't see turning off UAC as a solution - It's a terrible idea..
FYI: Effective Permissions below: (As you can see, everything is OK)
![wth.png]()
As Part of our standard file server build we remove all permissions from the root of the F: drive except for:
SYSTEM (Full Control)
Administrators (Full Control)
I've created a new domain user 'jakeadmin' and granted it membership of the Domain Admins group.
Domain Admins is a member of the member server's local Administrators group.
When I logon (via RDP) to the member server FILESERVER-01 as the domain user 'jakeadmin' this user cannot access the F: drive. I then tried adding the Domain Admins group with full control to the root of the F: drive but my 'jakeadmin' user still cannot access the F: drive:
If I logon to Fileserver-01 as a local machine administrator I have no trouble accessing the F: drive at all.
Why can't I browse my F: drive, even if I'm in the Administrators group?
I don't see turning off UAC as a solution - It's a terrible idea..
FYI: Effective Permissions below: (As you can see, everything is OK)
Start explorer elevated.
• start regedit.exe and go to the following key:
HKEY_CLASSES_ROOT\AppID\{C
• make a right click on Permissions and set your user as owner (click on advanced button to be able to take ownership) of the key and give your current user writing permissions.
• Next, rename the value RunAs to _Runas
Afterwards, you can righ clck explorer.exe and choose "run as administrator" and the problem is solved.
• start regedit.exe and go to the following key:
HKEY_CLASSES_ROOT\AppID\{C
• make a right click on Permissions and set your user as owner (click on advanced button to be able to take ownership) of the key and give your current user writing permissions.
• Next, rename the value RunAs to _Runas
Afterwards, you can righ clck explorer.exe and choose "run as administrator" and the problem is solved.
@McKnife Thank you for your input -
I have deployed Windows server 2012 file servers in the past and configured them the same yet I am able to browse the drive letter in question.. I'm reluctant to changing registry entries and accessing explorer using the 'Run as' mechanism ..
all administrators should be able to access all aspects of the file server.
Really can't get my head around this one..
Thanks again
I have deployed Windows server 2012 file servers in the past and configured them the same yet I am able to browse the drive letter in question.. I'm reluctant to changing registry entries and accessing explorer using the 'Run as' mechanism ..
all administrators should be able to access all aspects of the file server.
Really can't get my head around this one..
Thanks again
It was the same since UAC came up and this behavior is normal. If it worked on 2012 then either you used the built-in account "administrator", for which UAC is non-effective or UAC was even off. The registry editing is the best way, else, you will have to use a different explorer like total commander which can be run as administrator by default, or you will need to work with the account "administrator".
So if I was to access the server with the built in domain admin account DOMAIN\Administrator I would be able to see the drive?
If that is the case, would be be best practice to create a new group called Data Managers and assign the domain admin group to that? (Or individual members?)
If that is the case, would be be best practice to create a new group called Data Managers and assign the domain admin group to that? (Or individual members?)
Yes, administrator local and domain\administrator would both work right away.
No, that would not work, since the domain admin token needs elevation. You would need to add the individual account names to that group "data managers".
No, that would not work, since the domain admin token needs elevation. You would need to add the individual account names to that group "data managers".
Premium Content
You need an Expert Office subscription to comment.Start Free Trial