When deployment through Netop Pack'n Deploy is a success, the computer's icon changes to a smiling yellow face.  When the deployment fails the icon changes to a red circle with a white bar.  If you right-click on the icon, the deployment log for that computer will open in Notepad.  Listed below are some of the most common error codes/messages and their possible causes.

  • AddConnection failed with code 5 : Access is denied.
    • U.A.C. is enabled on the target computer.
    • The user account does not have administrator rights on the target computer.
  • AddConnection failed with code 53 : The network path was not found.
    • File and Print sharing is turned off on the target computer.
    • Windows Firewall is set to "Block all incoming connections..." on the target computer.
  • AddConnection failed with code 67 : The network name cannot be found.
    • File and Print sharing is turned off on the target computer.
  • AddConnection failed with code 1326 : Logon failure: unknown user name or bad password.
    • Username or password is invalid.

For Netop Pack'n'Deploy to succeed Windows Remote Services must be available. You can test whether this is available on you network by opening a command prompt on the computer from where you want to perform the deployment. In the command prompt write the following command:

 

NET USE \\computername\ADMIN$ **** /USER:userdomain\userid

 

where computername is the name or IP address of the remote computer, “****” should be replaced by a password, “userdomain” and “userid” by a valid domain or local computer name and user ID from your network/remote computer. If you are not sure about the name of the userdomain type "set" in a command prompt on the machine in question. Towards the end of the response text you will find the value of the variable "userdomain".

 

Another type of deployment failure can be caused by renaming the MSI/MST files.  You can identify this failure because the icon will change to a red square with a white X and you will have a short log file that resembles the example found in the following link.

Netop Pack’n Deploy - failed to start setup.exe