Enabling Admin Share on Managed Devices

Admin shares are Windows defaults that provide access to every hard drive partition on a system. Barracuda RMM automation requires the Admin share to be available to push files needed for automation. Older versions of Windows may have these shares enabled by default, but on modern versions they are disabled.

See the instructions for each operating system.

Windows 8, 10, Server 2012, Server 2012 R2, and Server 2016

Add the following to the Windows registry:

Hive: HKEY_LOCAL_MACHINE
Key: Software\Microsoft\Windows\CurrentVersion\Policies\System
Name: LocalAccountTokenFilterPolicy
Data Type: REG_DWORD
Value: 1

The following is a list of Operating Systems that are no longer support by Barracuda RMM. These are purely informational.

Windows 7

Add the following to the Windows registry:

Hive: HKEY_LOCAL_MACHINE
Key: Software\Microsoft\Windows\CurrentVersion\Policies\System
Name: LocalAccountTokenFilterPolicy
Data Type: REG_DWORD
Value: 1

Windows Vista

Add the following to the Windows registry:

Hive: HKEY_LOCAL_MACHINE
Key: Software\Microsoft\Windows\CurrentVersion\Policies\System
Name: LocalAccountTokenFilterPolicy
Data Type: REG_DWORD
Value: 1

Windows XP

Add the following to the Windows registry:

Hive: HKEY_LOCAL_MACHINE
Key: System\CurrentControlSet\Services\LanManServer\Parameters
Name: AutoShareWks
Data Type: REG_DWORD
Value: 1

Windows 2003

Add the following to the Windows registry:

Hive: HKEY_LOCAL_MACHINE
Key: SYSTEM\CurrentControlSet\Services\LanManServer\Parameters
Name: AutoShareServer
Data Type: REG_DWORD
Value: 1

Windows 2008

Add the following to the Windows registry:

Hive: HKEY_LOCAL_MACHINE
Key: SYSTEM\CurrentControlSet\Services\LanManServer\Parameters
Name: AutoShareServer
Data Type: REG_DWORD
Value: 1

If the Admin share is still inaccessible after making the registry key change and restarting the system, run the Windows Prep Utility found in the Service Center under Site Management > Sites > {Site}. Resources can be downloaded and executed to automatically enable the Admin share along with any other prerequisites for monitoring and management.

Admin share access can be tested by logging into the Onsite Manager as MWService (or service account you have configured for the onsite manager to manage devices) and navigating in Windows Explorer to \\DEVICENAME\admin$ if you can reach the device, try again but this time with device IP, if the IP fails, reboot the end computer and try again, the OM has to be able to access the admin share by both IP and name of the computer, if rebooting does not work, reboot the Onsite Manager.

For additional information regarding editing registry keys, please see the following Microsoft Article.