Destination locked during deployment

NetSupport School, NetSupport Manager and NetSupport Notify include a Deploy utility. NetSupport DNA includes the Discover and Deploy facility. If a deployment fails because the destination is locked, there are a number of steps you can take to investigate the issue.

Checking the deployment package
First, check that the deploy folder is set up correctly. The deploy folder is located within the installation folder of the NetSupport product you are deploying from:

• NetSupport Manager: C:\Program Files (x86)\NetSupport\NetSupport Manager\Deploy
• NetSupport School: C:\Program Files (x86)\NetSupport\NetSupport School\Deploy
• NetSupport Notify: C:\Program Files (x86)\NetSupport\NetSupport Notify\Deploy
• NetSupport DNA: C:\Program Files (x86)\NetSupport\NetSupport DNA\Console\ClientDeploy

It’s important that there is an executable (.exe) file, not a .msi file, in this location. The .msi does not include the capabilities required to write to the machine using the provided Deploy utilities.

Admin$ share
The Deploy tool needs access to the Admin$ share on the remote PC. To see if you have access to the Admin$ share, complete the following:

1. Go to Start, then click on Run.
2. Type \\MachineIP\Admin$ (replace MachineIP with the IP address of the machine that you wish to deploy to).
3. Once you can access the Admin$ share, try to create a file. If you can create the file, you have write permissions, which are also required.

Note: If you’re unable to access the Admin$ share, this indicates that the account you’re using is being denied access. This could be due to security restrictions. Normally, the domain administrator account shouldn’t have problems accessing the Admin$ share.

File and printer sharing
When deploying over a network, the file and printer sharing options in the firewall must be allowed. To check this:

1. Click Start, then Control Panel.
2. Select Windows Firewall and then Allow a program or feature through Windows Firewall.
3. Select the option to allow File and Printer Sharing and the associated exception (it is recommended that this is enabled for all Domain, Private and Public networks for troubleshooting).
4. Click OK to save the changes.

Sharing and security model
Ensure the sharing and security model for local accounts is set to Classic.

1. In Administrative Tools, select Local Security Policy.
2. Select {Security Settings}{Local Policies}{Security Options}.
3. Select {Network access: Sharing and security model for local accounts}.
4. Change the setting for this policy to {Classic – local users authenticate as themselves}.

Disable firewall
To check whether a firewall issue is preventing the deployment from working correctly, temporarily disable the firewall on the machine you’re deploying to.

1. Click Start and then Control Panel.
2. Select Windows Firewall and then Advanced Settings.
3. Select Windows Firewall Properties.
4. Select Firewall State to Off for Domain Profile, Private Profile and Public Profile.

Remote services test
A good test to perform to determine whether you have sufficient privileges to initiate a deployment is to attempt to access the remote services. This test should be performed on the machine you are deploying from.

1. Right-click on My Computer/Computer and select Manage.
2. This will open Computer Management.
3. Right-click on Computer Management and select Connect to another computer.
4. Select the Another computer tab, enter the target/destination machine you are attempting to deploy to, and select OK.
5. This opens the Computer Management pane on the target/destination machine. Select the Services and Applications section and expand it to view the full list.
6. Once the list is open, select Services. You should be able to see the list of services on the target/destination client you are attempting to deploy to.

Note: If you’re unable to access the remote services on the destination machine you are attempting to deploy to, this indicates that security permissions are restricting you. This issue must be resolved before deployment can proceed.