Network Folders Are Inaccessible in Management Console Connected to Agent
How to proceed if network folders are inaccessible in ManageEngine OS Deployer Management Console connected to an Agent
- Using ManageEngine OS Deployer Management Console you connect to a remote computer that has ManageEngine OS Deployer Agent installed;
- You try to access a network folder of the remote computer;
- Once you click on the "+" sign, it disappears and nothing happens: no login requests, no folders shown:
If you type in the address to the network folder manually, you will get an error message similar to the one below:
The issue might be caused by the inappropriate (most probably manually modified) settings of the User Rights Assignment category of Windows on the machine where ManageEngine OS Deployer Agent is installed.
On the machine where ManageEngine OS Deployer Agent is installed, do the following:
- Go to Control Panel -> Administrative Tools -> Local Security Policy;
- On the Local Security Settings screen select Local Policies -> User Rights Assignment;
- Make sure that the NETWORK SERVICE (or LOCAL SERVICE in Windows 2000) user is present in the following policies:
- Adjust memory quotas for a process (or increase quotas in Windows 2000)
- Replace a process level token
(!) To add the NETWORK SERVICE (or LOCAL SERVICE in Windows 2000) user you will need to do the following:
- Right-click on the service and select Properties;
- Click Add User or Group;
- In the new window type in NETWORK SERVICE;
- Click OK.
(!) If there is a Domain Controller, then the default domain controller security settings are to be changed:
- Go to Start -> All Programs -> Administrative Tools -> Domain Controller Security Policy -> Security Settings -> Local Policies -> User Rights Assignment
- Add the NETWORK SERVICE user as described above (if the user is not already there).
If adding the NETWORK SERVICE entry to both of those policies does not help, please export the User Rights Assignment settings to a Text (Tab Delimited) or Text (Comma Delimited) file and forward it to email@example.com along with a reference to this article.