Netsupport Deployment & Windows 7

Here are some factors to take into consideration when deploying

Deployment Installation Package:

Ensure you are using the setup.exe (within the Deploy folder) and NOT the MSI, if the MSI resides in the Deploy folder please delete this. The setup.exe is the only executable that can be used in the NetSupport Deploy program.

Ensure you are logged is as a network admin so th e Deploy will use the authenticated rights. Insufficient rights will prevent a successful deployment.

The File and Print Sharing via My Network Places is Disabled. Please confirm that this is Enabled

1. Right click on {My Network Places} Select {Properties}

2. Then right click on {Local Area Connection} Select {Properties}

3. From the {General Tab} put a tick next to {File and Print Sharing for Microsoft Network} Click OK

The File and Print Sharing via Windows Firewall is Disabled on the Target Machine. Please confirm that this is Enabled

1. Navigate to {Start}{Settings}{Control Panel}

2. Double Click on {Windows Firewall)

3. Then sel ect the {Exception Tab}

4. Then from display list below make sure there is a tick next to {File and Printer Sharing}

Ensure the Sharing and Security for Local Accounts is se to Classic

Windows XP Professional:

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. Alter the setting for this policy to {Classic – local users authenticate as themselves}

Windows 7:

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. Alter the setting for this policy to {Classic – local users authenticate as themselves}

Can you access the Admin$ Share?

Check to see if you have Access to the Admin$ Share please do the following:

1. Go to Start then click on Run

2. Type \\MachineIP\Admin$ (Where MachineIP is 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 it means you have write permissions which is required.

Note: In order to be able to deploy to the machine you will need to be able to access the machines Admin$ Share.

Can you access Remote Services?

A good test to perform to see if you have sufficient pri vileges to initiate a deployment would be to attempt to access the Remote Services. This is to be tested 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. Ensure you select the ‘Another computer’ tab and enter the target/destination machine you are attempting to Deploy to and select OK.

5. This will open the Computer Management pane on the target/destination machine if you can then select the ‘Services and Applications section and expand so you see the full list.

6. Once the list is open select on ‘Services’ does this allow you to see the list of Services on the target/destination client you are attempting to Deploy to?

Note: if you are unable to access the Remote Services on the destination machine you are attempting to Deploy too this would indicate security permissions restricted you from performing this action and would need to be resolved.

Ensure the environment is setup correctly taking into the above considerations in order for the Deploy to work correctly.

If you get any issues even when considering the above, and you get error messages when trying to Deploy to a Client within a Domain. Check whether to see if any Group Policies are being enforced that are possibly blocking the temporary directory from being created.

Perhaps get the user to log in locally on the machine and then try a Deploy (as the Group Policies would not be enforced)

Another thing to check is ensure that the Deploy is using the credentials such as administrative rights that will allow for sufficient rights to carry out the Deploy.

Microsoft Windows Networking

If you are unable to see all machines from within the Deploy tool there may be a number of reasons why this is not working.

• Computer Browser is disabled on Client machines.
• In a Workgroup environment (only one master browser is present and normally will only be able to view machines on that particular Workgroup)
• Firewall/Network restrictions.

Description of Computer Browser As per Microsoft Technet:

What Is Computer Browser Service?

Computer Browser service is the mechanism that collects and distributes the list of workgroups and domains and the servers within them. The list displays in the Microsoft Windows Network window and related windows in My Network Places.

Microsoft Active Directory services in Windows Server 2003 and Windows XP create a searchable list of computers and resources that is separate from the list of domains, workgroups, and servers in My Network Places. Computer Browser service provides backward compatibility with computers running earlier versions of Windows that must use Network Basic Input/Output System (NetBIOS) over TCP/IP (NetBT) and are not Active Directorycapable.

We would recommend reading the following link that will describe in detail how this process works.

http://www.petri.co.il/whats_the_microsoft_computer_browser_service.htm

• Delicious