1. Unable to Add Domains in the Scope of Management?

 This could hapen in any of the following cases:

1. When an incorrect Domain name is specified. Check for spelling errors.
2. When the supplied credential do not have admin privileges in all the client computers.
3. When the administrator password specified is incorrect. Check for password case, spelling errors, etc.
4. The specified domain controller is down or inaccessible.

2. Desktop Central Agent installation has failed in client computers? Why ?

Desktop Central Agent installation might fail due to various reasons like invalid credential, blocking by firewalls etc. In most cases, executing the script below will fix the problem. This is applicable for Active Directory based network setup.

Run the script as explained here in all the client machines to configure the Windows Firewall and to install the agent.

If running the script doesn't help, check the following reasons based on the error messages that you see in the remarks column:

2.1 The network path was not found

This error will be shown in any of the following cases:

2.1.1. If the client computer is down or not accessible

Check the client computer is switched on and connected in the network properly and try installing the agent. Also ensure that the computer name is specified correctly.

2.1.2. If the "File and Printer Sharing for Microsoft Networks" is not enabled in the network adapter of the client computers.

Enable this in all the client computers as below and try installing the agent:

1. Select Start --> Settings --> Network Connections.
2. Right-click the network connection and select Properties.
3. In the connection properties dialog, select the General tab.
4. Select the "File and Printer Sharing for Microsoft Networks" and click OK.
5. If you do not find this option, click Install button.
6. In the network component type, select Service and click Add.
7. Select File and Printer Sharing for Microsoft Networks and click OK.
8. Click Close to exit the properties dialog

2.1.3. If a third-party Firewall blocks the agent installtion

Run the script as explained here in all the client machines to configure the Firewall and to install the agent.

2.2 Logon failure : unknown username or password

This error is shown in any of the following cases:

2.2.1. If the specified admin credential is no longer valid

If the admin credential specified during defining Scope of Management is no longer valid, use the Edit Credential link to update and try installing the agent.

2.2.2. In case of Workgroup setup, if simple file sharing is enabled

If simple file sharing is enabled, you will get as Access Denied error. Make the following change in all the client computers and try installing the agent:

1. Start --> Run--> explorer
2. Select Tools --> Folder Options
3. Select the View tab.
4. Unselect the option "Use simple file sharing" and click OK

2.3 No Network provider accepted the given Network Path

The possible reasons for this error include:

2.3.1 When you do not have access to admin$ of the client computer

From the computer where Desktop Central Server is installed, select Start --> Run and type \\<client Computer Name>\admin$. If you get the same error, enable Remote Administration Exception in the client computers as below:

1. From the client computer, select Start --> Run and type gpedit.msc and hit enter
2. Expand the Administrative Templates -> Network Connections -> Windows Firewall
3. Click the Domain Profile and double click the Windows Firewall : Allow remote administration exception
4. Select Enabled and click OK

2.3.2 Make sure you are able to ping the client computer by FQDN

Ensure that you are able to ping the client computers from the computer where Desktop Central Server is installed using the Fully Qualified Domain Name (eg. hostname.domainname.com)

2.3.3 When File and Print Sharing For Microsoft Networks is not enabled

Enable File and Print Sharing For Microsoft Networks in the client computers as below:

1. Select Start --> Settings --> Network Connections.
2. Right-click the network connection and select Properties.
3. In the connection properties dialog, select the General tab.
4. Select the "File and Printer Sharing for Microsoft Networks" and click OK.
5. If you do not find this option, click Install button.
6. In the network component type, select Service and click Add.
7. Select File and Printer Sharing for Microsoft Networks and click OK.
8. Click Close to exit the properties dialog.

2.3.4 If File and Printer Sharing is disabled in the Windows Firewall of the client computers.

Enable File and Printer Sharing the in client computers as below:

1. Open the Windows Firewall and select the Exceptions tab
2. Select the File and Printer Sharing check box and click OK.

If you still get the same error, verify that you are configuring File and Printer Sharing in the same profile that the Desktop Central Server computer is using. If you enable File and Printer Sharing in the domain profile, but the Desktop Central Server computer is using the standard profile, then File and Printer Sharing might not be enabled. You can use the Netsh tool to determine which profile the Desktop Central Server computer is currently using and which profile has File and Printer Sharing enabled. To enable File and Printer Sharing for all profiles, use the following command:

From the command prompt, type netsh firewall set service type = FILEANDPRINT mode = ENABLE scope = ALL profile = ALL and press enter.

2.3.5 Configre Security Policy

1. Select Start --> Settings --> Control Panel --> Administrative Tools --> Local Security Policies
2. In Security Options  -> local policies -> Security Options -> Change the Network security: LAN Manager authentication level: Send LM & NTLM responses

2.3.6 If the "Workstation Service" is not running in the Client Computers

1. Select Start --> Settings --> Control Panel --> Administrative Tools --> Services.msc
2. Right-click Workstation service and then click start

2.3.7 If the "TCP/IP NetBIOS Helper" service is not running in the Client Computers

1. Select Start --> Settings --> Control Panel --> Administrative Tools --> Services.msc
2. Right-clickTCP/IP NetBIOS Helper service and then click start

2.4 Not enough server storage is available to process this command

This error will be shown if IRPStackSize registry entry on the client computer is set too low. Increase the IRPStackSize registry entry as below:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
   If the IRPStackSize entry is not present in this subkey, follow these steps:
   1. Click Edit, point to New, and then click DWORD Value.
   2. Type IRPStackSize, and then press ENTER.
      Note: Type IRPStackSize exactly as it appears. The value name is case sensitive.
3. Click IRPStackSize, click Edit, and then click Modify.
4. In the Data Value box, type a larger value, and then click OK.

Questions