How To Deploy the Terminal Services Client by Using Active Directory in Windows 2000

Article translations Article translations
Article ID: 236573 - View products that this article applies to.
This article was previously published under Q236573
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

SUMMARY

This article describes how to distribute the Windows Terminal Services client in an enterprise by using Group Policy in Active Directory.

This article uses terms and concepts that are described in the "Step-by-Step Guide to Creating Windows Installer Packages and Repackaging Software for the Windows Installer Using VERITAS WinINSTALL LE." To view this guide, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/bb742609.aspx

Deploy the Terminal Services Client

To successfully deploy the Windows Terminal Services client program in an enterprise by using Group Policy, follow these steps:
  1. Prepare for the package creation.
  2. Create the installation package.
  3. Install the Terminal Services client.
  4. Perform the post-package creation.
  5. Create the Group Policy object (GPO).
  6. Apply the package.
These steps are described in detail in the following sections.

Prepare for the Package Creation

To prepare for the package creation:
  1. Create a network share where you will store the Terminal Services client installation files. This share must remain available as long as the Terminal Services client is installed.
  2. Copy the Terminal Services client installation files from the \\%SystemRoot%\System32\Clients\Tsclient\Net\Win32 (or Win32a for Alpha-based computers) folder on the terminal server to a folder in the network share.

Create the Installation Package

To create the installation package:
  1. On the reference computer, start the Discovery tool (DiscoZ.exe) by typing the UNC path (or locate it in Network Neighborhood).

    Note Do not map a drive to the folder that contains DiscoZ.exe. Typically, this file is stored in the %Systemroot%\Program Files\VERITAS Software\Winstall folder on the computer where you installed the Discovery tool.
  2. When the WinINSTALL Discover program starts, click Next, and then type a name for the program. For example, type Terminal Services Client. Click the ... button, and then locate the installation share point. For the file name, type TSClient, and then click Open.
  3. Click Next, click the drive on the reference computer where you want to store the temporary work files, and then click Next.
  4. Click the drive where you want to install the Terminal Services client, and then click Add. The drive appears in the Drives to Scan list. Click Next.
  5. Accept the default file exclusion list, and then click Next. The WinINSTALL Discover program scans the selected drive(s).
  6. On the message that states "The 'Before' snapshot is complete," click OK.
  7. Type the UNC path of the network location that contains the installation files for the Terminal Services client Setup.exe program, and then click Open to start the Terminal Services client installation.

Install the Terminal Services Client

To install the Windows Terminal Services client program:
  1. When the Terminal Services client setup program starts, click Continue.
  2. Type the default name and organization information, and then click OK. Confirm that the information is correct, and then click OK.
  3. Click I Agree to accept the license agreement terms.
  4. Verify that the installation path resides on the drive that you scanned in the "Create the Installation Package" section of this article. Change the installation path of the correct drive, if it is not correct, and then click the large button to start the installation.
  5. Click Yes to apply the same initial Terminal Services settings to all users of the computer.
  6. On the message that states "Terminal Services Client Setup was completed successfully", click OK.
Note If you receive error messages during the Terminal Services client installation, cancel Setup, and then run the WinINSTALL Discover program again to repeat the package creation process.

Perform the Post-Package Creation

  1. When the Terminal Services client installation is complete, start the WinINSTALL Discovery program by using the UNC path (or locate it in Network Neighborhood). Verify that the Perform the 'After' snapshot now option is selected, and then click Next.
  2. In the Conversion Successful dialog box that appears, view any warning messages, and then click OK.

    Note These warning messages do not necessarily indicate a problem with the Windows Terminal Services client program.
  3. On the message that states "The 'After' snapshot is complete", click OK to acknowledge that the "After" snapshot is complete. The .msi file and the associated files are created in the network share that contains the Terminal Services client installation files.

    Important Do not delete any of these files or folders.

Create the Group Policy Object (GPO)

To create a GPO to apply this package:
  1. Start the Active Directory Users and Computers utility on the server.
  2. Create or locate the appropriate Organizational Unit where you want to create the GPO to deploy the Terminal Services client program.
  3. Right-click the container, and then click Properties.
  4. Click the Group Policy tab, and then click New.
  5. In the New Group Policy Object box, type a name for the policy. For example, type Terminal Services Client Distribution.
  6. Click Edit.
  7. Click the appropriate policy object, depending on your deployment strategy. If you want to distribute the Terminal Services client on a per-computer basis, click the Computer Configuration object. If you want to distribute the Terminal Services Client on a per-user basis, click the User Configuration object.
  8. Expand Software Settings, right-click Software installation, point to New, and then click Package.
  9. In the File name box, specify the location of the .msi file that you created by typing the UNC path of the Terminal Services client installation file. For example, type \\Server\share\TSClient.msi.
  10. Click Open.
  11. Click the deployment method, and then click OK. The package appears in the right pane of Group Policy. To modify the properties of the package, right-click it, and then click Properties.
  12. Quit Group Policy, and then click Close.
  13. Quit the Active Directory Users and Computers utility.
  14. Refresh the domain policy by typing one of the following lines, as appropriate, at a command prompt:
    secedit /refreshpolicy machine_policy /enforce

    -or-

    secedit /refreshpolicy user_policy /enforce

Apply the Package Application

To apply the Windows Terminal Services client package:
  1. Make sure that replication has occurred on all domain controllers before you try to use the published program.
  2. Log on to a workstation to receive the published Terminal Services client. If you published the package, you can install it by using the Add/Remove Programs tool in Control Panel (click Add New Programs).
  3. Test the policy, and if you find any problems, make the changes that you want.
  4. If the package installs correctly, you can remove the Terminal Services client installation from the reference computer.
The policy is now available to users. If you must ever remove the Terminal Services client, remove the package from the policy. This method provides the option to automatically remove it from workstations.

Note Depending on the requirements of your organization, you may have to apply a transform or have to edit the package (.mst file) to modify parts of the installation.

REFERENCES

For additional information about group policies, visit the following Microsoft Web site:
http://download.microsoft.com/download/5/2/f/52f3dbd6-2864-4d97-8792-276544ad6426/grouppolwp.doc

Properties

Article ID: 236573 - Last Review: October 21, 2013 - Revision: 4.3
APPLIES TO
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition
Keywords: 
kbnosurvey kbarchive kbenv kbhowto kbhowtomaster kbtool KB236573

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com