A: Remote Task Manager (RTM) is a systems control interface that can be run from any remote
A: Certainly. Join our mailing list by entering your e-mail address below, then click on the 'Join!' button:
A: Well, there are no functional limitations for unregistered versions and you may use RTM (during the evaluation period) as a fully registered program but only on one computer in the network. In addition, unregistered versions of RTM display nag screens!
A: Online using a credit card at http://www.protect-me.com/rtm/register.html.
A: Yes. Use our online forms at http://www.protect-me.com/rtm/register.html. Select a payment method (order by fax, toll-free phone, bank transfer, etc.), then ask for an invoice.
A: Yes. All our registrations use SECURE protocols. It is impossible for a third party to intercept your credit card information. We also offer alternative ordering methods (such as order by fax, toll-free phone, bank transfer, etc.).
A: You may install RTM Service on only a single computer but RTM Manager can be installed on any number of your computers. The Single license gives you the right to use RTM on one computer so you are able to manage only one computer, either remote or local. If you wish to use RTM on several computers, you need to purchase the appropriate number of Single licenses.
For example, if you wish to manage remotely:
one computer - you need to purchase one Single license ($40);
two computers - you need to purchase two Single licenses ($80);
up to 200 computers within the one network domain - you can buy the Site/Domain license ($1600). If you decide to add new computers (up to 200) to the domain, you won't pay for the extra licenses!
up to 2000 computers within the one geographical location - you can purchase the World/Corporate license ($5195) and install RTM on all the computers in your network. If you decide to add new computers (up to 2000) to the network, you won't pay for the extra licenses!
more than 2000 computers - please contact us directly for a quote.
A: The one Site/Domain license lets you install RTM Service on all the computers in ONLY one domain or network group with 200 or less computers. If you wish to install RTM Service on up to 2000 computers in all your domains within the one geographical location, you should purchase the World/Corporate license. Please contact us directly for a quote if the RTM Service is to be installed on more than 2000 computers.
A: No. When you purchase a license (any kind) for RTM, you automatically purchase all future releases and updates that will be released within 1 year from the date of purchase. It means that during one year you can download and install the latest versions of the software from our site, and the license keyfile that you received from us will work with the latest product version.
If you don't want to purchase an upgrade, you can use the program forever; it will never expire, but you won't be able to use the latest version.
A: Yes. RTM works on the Compaq Alpha platform as well as on Intel x86. You can download the native RTM version for the Compaq Alpha from http://www.protect-me.com/rtm/download.html.
A: No. To correctly install RTM under Windows NT/2000/XP you must have administrative privileges. If you are going to use RTM only on a local computer you must have local admin's privileges. If you are going to use RTM throughout your network you must have domain admin's privileges.
A: You can install Remote Task Manager Console (RTMC) on a Windows 95/98/Me machine to remotely manage Windows NT/2000/XP systems. RTMC is similar to RTM Manager except it uses a command line interface rather than a GUI.
A: Yes. Launch RTM setup with the /s parameter to install RTM without user intervention. This provides an install that can be used from within a batch file.
There is a special configuration file for silent setup: rtm.ini. With this file, you can customize the RTM installation parameters. For example:
Service - RTM Service and its related files will be installed
Manager - RTM Manager and its related files will be installed
Documents - documentation (readme.txt, register.txt) will be installed
To specify a destination directory for RTM, you can supply the parameter InstallDir
If you have the registration key-file for RTM, you can specify a directory with this file in the parameter RegFileDir
Run - this parameter is used to launch an application or execute a batch file after a successful install.
A: Yes. You can use the package definition files (rtm.pdf for SMS version 1.x and rtm.sms for SMS version 2.0 and later) supplied with RTM, located in the rtm.zip file.
A: Yes. RTM supports Remote Install. If the RTM Service isn't installed on the remote system or the RTM version is too old, RTM will suggest that you install the service. Select the RTM Service executable file (rtmservice.exe) and RTM will copy it to the remote computer. The RTM Service executable file will be copied to the Windows system directory (e.g. c:\winnt\system32) if this service doesn't exist on this system. If the service exists on this system but is too old, RTM will copy the executable file to the directory of the old file and the old file will be replaced.
A: You need to open 135-139 ports and all ports above 1024 for incoming and outgoing packets:
Port 135 (TCP) - for Remote Procedure Call (RPC) Service
Port 137 (UDP) - for NetBIOS Name Service
Port 138 (UDP) - for NetBIOS Netlogon and Browsing
Port 139 (TCP) - for NetBIOS session (NET USE)
Ports above 1024 (TCP) - for RPC Communication
RTM works like any other standard Windows NT/2000/XP administrative tool (such as Event Viewer, Services, Computer Management, etc.) so, if these tools work then RTM will work, too.
You can find more information in the Microsoft's Knowledge Base
A: The error 1722 means that RTM Manager cannot access RTM Service on the remote computer. There are several possible reasons:
the remote computer does not exist on the network (the computer's name or IP address is incorrect or this computer was shut down recently but its name still exists in the network browser);
the remote computer is not a Windows NT 4.0/2000/XP computer and RTM Service cannot be installed on this computer;
the remote computer is behind a firewall that was not configured properly (to configure a firewall, please read this answer);
the remote computer is on another segment of your network that is not accessible from your segment, i.e. the routing was not configured properly and you cannot access that network's segment at all.
A: The error 1747 occurs when the "Client for Microsoft Networks" option is not installed. To resolve this problem, install the "Client for Microsoft Networks". If you don't require the "Client for Microsoft Networks", it is best to disable it after installation (RTM runs properly in this configuration).
Also, on Windows NT 4 systems the RPC Security Service Provider could be configured incorrectly. Open the Control Panel's "Network" applet, select the "Services" tab, highlight the "RPC Configuration" record from the "Network Services" list and press the "Properties..." button. Then in the "RPC Configuration" dialog, set the "Security Service Provider" combobox to "Windows NT Security Service".
A: By default RTM uses the highest level of authentification (it encrypts the argument value of each remote call, verifies only that all data received is from the expected source and authenticates and verifies that none of the data transferred between RTM Manager and RTM Service has been modified). However, the computer on which you run RTM Manager may not support this level of authentification and you will need to decrease it. Start "Registry Editor" (regedit.exe) and create the "SecurityLevel" (type DWORD) parameter in the "HKEY_CURRENT_USER\Software\SmartLine Vision\rtmanager\Manager" subkey, change the value for this parameter to 5 (1 - indicates lowest level, 6 - indicates highest level), then restart RTM Manager.
A: The error 1825 is similar to the error 1747 so please read this answer.
A: The error 7045 means that you are trying to connect to a remote computer where you are authenticated as someone without administrative privileges. This often happens when you are logged in under the account with the local administrative privileges but on the remote computer this account doesn't have administrative privileges. You must run RTM Manager on the local computer either under the account of the domain administrator that has administrative privileges on all computers in the network or under the account of the local administrator that was not connected to the remote computer at all (in this case RTM Manager will be able to connect you to the remote computer under any account that you provide through the "Connect As" dialog).