Article 10131: Remotely Managing TASKE Server Computers Running Windows 2000 Server or Professional

TASKE Technology Knowledge Base
Products: TASKE Contact
      version 8.5
TASKE Reporter
      version 8.5
TASKE Essential
      version 1.0
Applications: All TASKE server applications
Telephone systems: All
Print

Important: although multiple Windows sessions can run in a Windows 2000 environment, the session where the TASKE server applications were first launched is the only valid session, regardless of whether it was launched locally or remotely.

Summary

This article provides instruction for remotely managing TASKE server computers that are using Microsoft® Windows 2000 Server or Professional.

Note: in this article, local refers to the TASKE server computer and remote refers to any other computers used to manage the TASKE server computer.

Issue

Physical access to the TASKE server computer is limited or after-hours administration tasks are required.

Solution

The following options are available to those remotely managing TASKE server computers using Windows 2000.


Remotely Managing the TASKE Server Computer using Microsoft Remote Desktop Connection

Important: launching a remote session on the TASKE server computer prevents local management. To manage the TASKE server computer locally, log out of the remote session and log in locally.

Logging out of the remote session closes all open applications on the TASKE server computer, stopping data collection. Data collection will not begin again until the local user logs in and restarts the required TASKE server applications.

Remote Desktop Connection is a Windows application that allows a user to remotely log into and operate other computers. This is useful for managing TASKE server computers that are not readily accessible.

When using Remote Desktop Connection with Windows 2000 Server, local and remote users cannot be logged into the computer simultaneously. Therefore, before launching a remote session on the TASKE server computer, verify that no one is logged into this computer locally. After confirming this, or logging off the local user, launch the remote session and start the required TASKE server applications to begin collecting data from the telephone system.

Once the remote session is active and the TASKE server applications are started, the user must not log off the computer before disconnecting from the remote session. Logging off before disconnecting from the session will close all open applications on the computer, including TASKE server applications required for data collection. Disconnecting from the session leaves the session open and active, allowing all applications to continue running.

To disconnect from a remote session, click the [X] button at the top, center of the Remote Desktop Connection window. To reconnect to the session from the same computer or any other computer on the network, launch Remote Desktop Connection and log into the TASKE server computer using the same user name that was used to create the session. Logging into the computer with a different user account will log off the current user and close all open applications, including the TASKE server applications required for data collection.

Top


Remotely Managing the TASKE Server Computer using a Third-Party Remote Access Application

Third-party remote access applications allow users to remotely log into and operate other computers. These applications are useful for those who want the option to manage the TASKE server computer locally or remotely because remotely logging in does not disable local control.

After logging in to the TASKE server computer, either locally or remotely and starting the TASKE server applications, always log into the TASKE server computer using the same user account that is currently logged in. This holds true when logging in as a local or remote user. Failing to do so will log off the current user and close the TASKE server applications required to collect data.

Be aware that only one remote session should be active at a time. Launching a second remote session closes the first and transfers control of the TASKE server computer to the new session. This does not cause an an interruption in data collection but does take control from the user of the first remote session.

Top


 

Related articles:

Article 10127: Remotely Managing TASKE Server Computers Running Windows Server 2003

  Article 10132: Remotely Managing TASKE Server Computers Running Windows XP Professional