Troubleshooting the client deployment

net use * \\targetcomputer\admin$ /user:domain\user password

• If you receive in the Client Deploy Tool the message "Offline", typically with net use you get the following error:

  Error: System error 53 has occurred. The network path was not found.

  Meaning: The computer cannot be contacted.

• If you receive in the Client Deploy Tool the message "Connection Failed", with net use you get one of the following errors:

  Error: System error 53 has occurred. The network path was not found.

  Meaning: ADMIN$ share is not available.

  Error: System error 1219 has occurred. Multiple connections to a server or shared resource by the same user, using more than one user name, is not allowed. Disconnect all previous connections to the server or shared resource and try again.

  Meaning: If the computer used to run the Client Deployment Tool already has a connection to a remote machine ADMIN$ share, using a different credential, this error occurs.

  Error: System error 1311 has occurred. There are currently no logon servers available to service the logon request.

  Meaning: The domain server is not available for authentication.

  Error: System error 1326 has occurred. Logon failure: unknown user name or bad password.

  Meaning: Incorrect administrative user name or password.

• If you receive in the Client Deploy Tool the message "Access is Denied" or "Windows Error: Logon failure: unknown user name or bad password", with net use you get the following error:

  Error: System error 5 has occurred. Access is denied.

  Meaning: User name/password are correct, but the account does not have permission to ADMIN$ share.

  Error: No network provider accepted the given network path.

  Meaning: The client or the server could not be resolved during the client deploy tool process.

  The "Access is Denied" or "Windows Error: Logon failure: unknown user name or bad password" status indicates that the Client Deploy Tool is unable to connect to the computer to determine if the client is installed. In addition, it is likely that you are also able to deploy the client through the Client Deploy Tool if this error is encountered. The following conditions might be causing this error message:

  • An incorrect user name/password was supplied.
  • The user account might be locked.
  • Insufficient permissions/privileges on the target computer.
  • File and Print sharing is disabled on the target computer.
  • The Windows Firewall might be blocking the Client Deploy Tool.
  • The Windows policy might be blocking the Client Deploy Tool. Try to add or modify the following registry value:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
    Policies\System]
    "LocalAccountTokenFilterPolicy"=dword:00000001

• If you receive in the Client Deploy Tool an RPC failure message, this error occurs when:
  • The remote computer is turned off or unreachable.
  • The remote computer has the RPC service disabled or not functioning.
  • The remote computer has the "file and printer sharing" option disabled.
  • The remote computer is running a personal firewall that blocks the connection attempts. Or the connection attempt is blocked by a firewall in between the computer with the Client Deploy Tool and the remote computer.
  Ensure that these issues are not the cause of the problem and then run the Client Deploy Tool again.
  Note: After restarting the computer reporting an RPC error, in some cases the RPC error no longer occurs.
  Note: As a way to test and see if RPC is listening, Microsoft has a tool named "RPC Ping" which can be downloaded from the following Microsoft article: http://support.microsoft.com/kb/831051.
• If you receive in the Client Deploy Tool the message "Windows Error 0000046a: Not enough server storage is available to process this command", this error indicates that the IRPStackSize value is set too low on the target computer resulting in not enough resources being allocated to use a local device. Increase the IRPStackSize value on the target. For more information, see the following Microsoft article: http://support.microsoft.com/kb/106167.

  Try to deploy the client after the value was increased. If the client deployment fails with the same error message, increment the IRPStackSize value and try to deploy the client again.