Remoteware 4.X Workstation Windows 2000 Terminal Services

RemoteWare 4.x Workstation Windows 2000 Terminal Services

The purpose of the product note is to announce the support of RemoteWare version 4.x Workstation running on a machine with Windows 2000 Terminal Services. iAnywhere continues to ensure that RemoteWare 4.x products are compatible with Microsoft Windows. This Technical Note sets forth compatibility issues and requirements regarding RemoteWare 4.x products as they relate to Windows 2000 Terminal Services.

Terminal Services for Windows 2000 is a technology that allows remote administration of a RemoteWare 4.x Server. This is accomplished by installing RemoteWare 4.x Workstation on a Windows 2000 Server with Terminal Services. Users may then connect to the RemoteWare 4.x Workstation via the Terminal Server client and administer the RemoteWare 4.x installation remotely.

Only the RemoteWare 4.x Workstation is supported on Windows 2000 Terminal Services operating system. RemoteWare 4.x Server is not supported for use with Windows 2000 Terminal Services.

Supported Functionality

Remote Ware 4.x Workstation have been tested with Windows 2000 Terminal Server and are supported for use with Terminal Server, with the exceptions listed below. The following RemoteWare 4.x Workstation functions are not supported on Windows 2000 Terminal Services:

RemoteWare Main Menu (rwmenu.exe) – (Default Shortcut installed during installation of RemoteWare 4.x Workstation) – All RemoteWare modules must be launched directly from the exe file associated with that product. I.E. (Client Profile) node.exe

Remote Control – Compatibility issues with Symantec’s pcAnywhere 9.2 and Windows 2000 Terminal Services prohibit the use of Remote Control with Terminal Services.

The following RemoteWare 4.x Products will only support one instance of each function/component per RemoteWare 4.x Workstation.

Administrator (rwadmin.exe) – Only one instance per RemoteWare cluster is supported by default.

Software Manager (RWPackageAdministrator.exe) – Software Manager will only function if launched at the console of the Windows 2000 Server where RemoteWare 4.x Workstation is installed. Software Manager is not supported via a Terminal Server session.

Interactive Session (is.exe) – Only one instance of Interactive Session is supported per RemoteWare 4.x Workstation.

Schedule Manager (schedmgr.exe) – Only one instance of Schedule Manager is supported per RemoteWare 4.x Workstation.

Logging (XSLogVeiwer.exe) – Refer to the section of this document labeled Installation Considerations for instructions to enable logging functionality with Terminal Server sessions.

The following RemoteWare 4.x Products will support multiple instances of each function/component per RemoteWare 4.x Workstation.

These files can be located in the RemoteWare System Directory (C:\RWS\System)

Server Profile (Netmgr.exe) Client Profile (Node.exe) Work Object Editor (woe.exe) Worklist Editor (wle.exe) Session Editor (se.exe) Network Status (ss.exe) Log Viewer (XSLogVeiwer.exe) Report Manager (Rptmgr.exe) Directory Manager (DirMgr.exe) Messaging Admin (MsgAdmin.exe) Inventory Manager (Rwamcons.exe) Subscriber Editor (rwsub.exe)

System Requirements

The following requirements are in addition to Microsoft’s minimum recommendations for Windows 2000 Terminal Services.

Memory per user (Mb)– 8.5

Installation Requirements – Terminal Services

Terminal Services must be installed in Application Compatibility Mode not Remote Administration Mode. All Terminal Server users must have Terminal Server Home Directories established within their Profile prior to connecting to a Terminal Server session.

Installation Requirements - RemoteWare 4.x Workstation

Installation of RemoteWare 4.x Workstation to Windows 2000 Terminal Server must be done in /Install mode. o Install mode may be initialized two ways. 1. Open a command prompt and type “change user /install” 2. Go to Start > Control Panel > Add/Remove Programs then click “Add New Programs”

Once the Terminal Server is in /Install Mode the RemoteWare installation may be completed.

After the RemoteWare installation completes and while still in /Install mode the following steps must be completed before changing the server to execution mode:

1. At a command prompt type (without the quotes) “register c:\rws\system\queues.dll /system ” – where c:\rws is the location the RemoteWare 4.x Workstation execution drive.

This command will enable RemoteWare database logging to function correctly with Terminal Server sessions.

2. On the Windows 2000 Server go to the Services applet in Administrative Tools and start all of the RemoteWare related services. 3. Delete the default desktop shortcut and the Start Menu from the All Users Profile. This should be done to avoid any conflicts with users launching RemoteWare executables from the Main Menu. See section in this document titled The following RemoteWare 4.x Products are not supported on Windows 2000 Terminal Services:

The Terminal Server may now be changed to /execute mode.

o If /install mode was achieved through the command prompt type “change user /execute”. o If /install mode was achieved through Add/Remove Programs then click the click Next in the After Installation window. Then click Finish in the Finish Admin Install window. This completes the installation of RemoteWare 4.x Workstation on the Windows 2000 Terminal Server.

For more information on Windows 2000 Terminal Server please visit Microsoft’s Terminal Services Technology page at http://www.microsoft.com/windows2000/library/technologies/terminal/default.asp

If you have any questions regarding this technical note, please contact Technical Support at 1-800-669-1211 or visit http://www.ianywhere.com/support/support.html.