Drive not accessible through the Administrative Share

On the server which was rebuilt a couple of weeks ago all the Maintenance Jobs started failing with the error message that the path on which the scripts were located could not be accessed. Since the jobs are run from a third party Job Scheduling Agent, the job parameters were configured to use the script from the network share in format \servernamedrive$scriptfilename.

We were not able to access this path from the Windows Explorer as well. This was the error message.

Any share that has the $ symbol at the end of it, is called an Administrative Share. These shares are hidden in Windows Explorer. This share is accessible to only the users who are members of Local Administrators group on the Windows Server which hosts this share. The permissions for this share cannot be modified.

In this case, the account starting the job and the DBA team were part of Local Administrators group still they were getting the error related to permissions. The reason for this error could have been that the E$ share was removed by someone. But the drive had that share.

The other drives on this server were accessible through the Administrative share except for this drive. Hence it was confirmed that something was wrong with the configuration of this share. Clicking on the Share Name drop down lead to the resolution of this issue.

Someone had shared this drive with the name E. The permissions for the share were set as Read for Everyone.

Out of the two shares which had the same name the permissions for the E share which were the least, were taking precedence. Hence even an Administrator on the server was denied access to the Administrative share.

This issue was intimated to the Windows Administrators who deleted the E share. As expected the E$ was accessible to the Administrators now and all the jobs completed successfully.

4 thoughts on “Drive not accessible through the Administrative Share

  1. Denny Cherry

    Network shares with a $ at the end are not admin only shares. They are hidden shares. The default hidden shares on the root of each hard drive and the C:\Windows share (admin$) are the only ones which are admin shares and are accessible only by members of the local administrators group. Any other hidden share (with a $) at the end of it can have the permissions changed just like any other network share can.

  2. PradeepAdiga Post author

    Hi Denny,
    Thanks for the comment! In the example that I quoted above, the share permissions for the root drive (E). AFAIK, the permissions for the root shares with $ at the end of their names cannot be set “after” the share is created which results in the below error message
    This has been shared for administrative purposes. The permissions cannot be set.
    You are right in stating that the permissions can be set to this share “while” creating it.

    1. santhu

      Hi pradeep, it may sound stupid, i just wonder is it beacause only mountpoint were brought up in -bk server and not C: and D: from original server ?

      1. PradeepAdiga Post author

        No Santhu. Not because of the Mount Point, it was due to fact that someone had created a new “E” share


Leave a Reply