User Guide for the Cisco Secure User Registration Tool Release 2.5
Managing the Traditional Client Module

Table of Contents

Managing the Traditional Client Module
Installing the URT Client Module
Starting, Stopping, or Disabling the Client Module on Windows Systems

Managing the Traditional Client Module


The URT Client Module is usually installed automatically and requires little manual intervention. However, you should make sure it is installed properly on client systems and that it starts correctly during logon.

These topics describe how to manage the Client Module for traditional logons:

Installing the URT Client Module

The URT Client Module is usually installed automatically.

  • Installation is automatic in Windows NT, Windows 2000, and Windows XP (Professional) clients in a Microsoft Networking environment (not Novell NetWare). Automatic installation is enabled by default in the domain option Enable auto install and upgrade for Windows NT/2000. To change this option, see the"Setting Domain Logon Options" section.
  • Installation is not automatic for:
    • Any client, including Windows clients, in a Novell NetWare network. For Novell NetWare, you must install the Client Module manually.
    • Windows NT, Windows 2000, and Windows XP (Professional) clients in a Microsoft Networking environment if automatic installation is disabled in the domain option Enable auto install and upgrade for Windows NT/2000. To change this option, see the"Setting Domain Logon Options" section.

Automatic Installation of the Client Module

When automatic installation is enabled, the Client Module is installed after you install the URT logon script on the domain server.

If automatic installation is enabled in a Microsoft Networking environment, and a Windows NT or Windows 2000 system logs onto the network, the following events occur:

1. The logon script tries to run a utility on the system to verify whether the latest version of the Client Module is installed.

2. If the logon script does not find this utility on the system, the script copies the utility to the system and runs it.

3. If the Client Module is not installed, or the installed Client Module is not the latest version, the utility:

a. Obtains the latest version of the executable files from the domain server.

b. Tries to install or upgrade to the latest version of the Client Module.

4. If the attempt to install or upgrade fails:

a. The utility sends a packet to the VPS to request installation of the Client Module on the system.

b. The VPS notifies the URT Administrative Server to install the Client Module on the specified system.

After installation, the client runs normally.

Installing the Client Module Manually on Windows Systems

Manual installation of the Client Module is different for Microsoft Networking and Novell NetWare clients, as described in these topics:

Installing the Client Module on Microsoft Networking Clients

Follow the instructions in this section to manually install the URT Client Module on a Windows NT, Windows 2000, or Windows XP (Professional) workstation running Microsoft Networking.


Note   You must install the Client Module in every NT domain in your network.

  • Select a time of day when most of the Windows systems are up and running on the network (even if users are not logged on). You can install the Client Module only on systems running and connected to the network.
  • You must have NT Administrator authority in the domain. For more information, see the "Having Authority in Domains" section.

Step 1   In the URT main window, select NT Computers in the folder for an NT domain.

Alternately, if you are installing the Client Module on all Windows NT or Windows 2000 systems in a domain, you can select the domain. You can also select multiple systems by pressing the Shift key or the Ctrl key.


Note    You can install the Client Module only on systems that use DHCP. If a selected system does not use DHCP, the Client Module installation fails.

Step 2   A list of Windows NT and Windows 2000 clients is shown in the right pane. The client attributes are described in Table 7-1.

Table 7-1   NT Hosts—Right Pane Information

Attribute Description

Name

Client name.

Service Status

Status of Client Module on the system:

  • Installed—The service is installed.
  • Installed Running—The service is installed and active.
  • Query Pending—URT is waiting for a reply from the client.
  • Service Query Error—URT could not determine the status of the service.
    This might indicate that:
    • The system is not running.
    • The IP address for the system has changed since the last time WINS was updated. After 5 to 10 minutes, this problem should resolve itself.
  • Not Installed—The service is not installed on the client.
  • Host Unreachable—URT did not receive a reply from the client.

Version

Client Module version number (if installed).

Step 3   To install the Client Module on all listed NT hosts, do not select any systems in the list. Otherwise, select the system on which you want to install the Client Module.

Step 4   Click Install Client Module or select Customize>Install Client Module.

URT installs the Client Module on the selected clients, and displays a message window so that you can monitor installation status.





Installing the Client Module on Novell NetWare Clients

Use the instructions in this section to manually install the Client Module on a Windows NT or Windows 2000 workstation running Novell NetWare.

  • You must have Administrator or Administrator-equivalent authority to install the Client Module on systems defined in the Novell Directory Services (NDS) directory tree.
  • You must also have installed the ZENworks Starter Pack and created the WINNT User Package and WINNT Workstation Package policy objects. These policy objects must be associated with the organizational object that contains the users and groups on whose workstations you will install the Client Module.

Note    For more information, see the Novell documentation.


Step 1   To run ZENworks Novell Application Launcher (NAL), enter nal at a command prompt on a NetWare client.

Step 2   Double-click the NWAdmin32 application.

The NDS directory tree is displayed in the NWAdmin32 application.

If no NWAdmin32 icon displays, you must log onto NDS as administrator again.

Step 3   In the NDS directory tree, double-click the WINNT Workstation Package.

Step 4   Click Add Action.

The Create Scheduled Action window is displayed.

Step 5   Enter a meaningful name for the action (for example, Install URT).

Step 6   Click Create.

NAL creates the action and displays the Scheduled Action window.

Step 7   Select the newly created action.

Step 8   Click Details.

Step 9   Select Ignore package default schedule and use the following settings:

a. In Scheduled Action, click Details.

The Action Properties window is displayed.

b. Click the General tab.

c. Select these characteristics (allowing the others to default):

Priority—Normal
Impersonation—System

d. Click the Items tab.

e. Click Add.

The Item Properties window is displayed.

f. Enter the filename of the Client Module installation program in this format:

\\Novellserver\sys\public\urt\UrtClientInstall.bat

where Novellserver is the name of the server where you install the URT logon script. When the logon script is installed, URT installs the Client Module installation and uninstallation program on the server.

g. Click the Schedule tab.

h. Select User Logon for Event.

i. Click the Advanced tab.

j. Select the Disable action after completion checkbox.

The Client Module is installed the first time the user logs onto the NetWare domain.





Tips
  • While you are creating the Install URT object, you might want to create an Uninstall URT object. This object would have the same properties described in the preceding procedure, but the filename is:

\\Novellserver\sys\public\urt\UrtClientUninstall.bat.

  • Unless you are uninstalling the client, deselect the Uninstall URT item in the Scheduled Action window. If you uninstall the client, deselect the Install URT object.

Note    For more information about uninstalling software from NetWare clients, see the Novell ZENworks documentation.

Starting, Stopping, or Disabling the Client Module on Windows Systems

The Client Module starts and stops automatically and should require no manual intervention. However, you can manually stop the service on Windows NT, Windows 2000, or Windows XP (Professional) systems to help with problem diagnosis, or disable it so that it does not restart when you restart the system.


Note   You cannot manually start or stop the Client Module on Windows 98 or Windows XP systems.


Step 1   On the Windows NT or Windows 2000 client, open the Services control panel by selecting Start>Settings>Control Panel, then double-clicking Services.

Step 2   Find URT Administrative Service in the list of services.


Note    For Windows NT and Windows 2000, the Client Module is displayed as urtclsvc.exe on the Windows Task Manager Processes tab.

For Windows 98 and Windows XP, the Client Module is displayed as urt95svc.exe.

Step 3   Status should usually be Started, and Startup should be Automatic.

  • To stop the service, select it, then click Stop.
  • To start the service, select it, then click Start.
  • To change how the service is started, select it, then click Startup. In the next dialog box, select how you want to start the service (automatically or manually), or disable the service.




Tips
  • For Windows NT and Windows 2000, the Client Module is displayed as urtclsvc.exe on the Windows Task Manager Processes tab.
  • For Windows 98 and Windows XP, the Client Module is displayed as urt95svc.exe.