Terminal Server Considerations

The most common “multiple logon” environments today are “terminal server” systems like Windows Terminal Services [WTS], Citrix, VMware or NetWare. But others like "rlogin", Remote Desktop and various add-on “remote login” solutions also exist and have similar setup requirements.

Regardless of how more than one user can execute the Export-It application on the same computer the environment "seen" by a user logon must conform to what it would experience if running on an individual machine. In other words, the rules in a “multiple logon” environment are the same as for a computer where only one user logon runs the application. They are:

Every logon is a “virtual PC”

The best perspective for understanding the requirements of a user logon in any “multiple logon” environment is to view the act of logging on as the creation of a “virtual PC” for that user. A logon script, startup batch command or other means may be used to define the environment during the logon process, but the end result must provide the user with access to disk drive letters (and the folders that they contain), a Registry with “local machine” and “current user” hives (with secure “Certificate Store” for the SEDI user) and a “Windows” directory.

Each logon “maps” application drives

Every user must "see" the Export-It “Database "server" Drive” letter that holds the shared database and common subfolders for all users, the “Platform "local" Drive” letter where modules, libraries and resources required for execution are found and a “User "Windows" Folder” where application "INI" and print spool files for the user are kept.

The drive letters and the user “Windows” directory must exist when the user logon process completes, but it is a responsibility of the administrator installing the application to choose and implement the specific mechanism used. This allows an approach consistent with site or company policies.

Each user logon is a “local” administrator

Every user logon must be setup as specified in the Basic User Settings and subsequent topics. Specifically:

File Access Permissions,
User Security Privileges, and
User Registry Access must be as specified in these topics.

Syscob also recommends that a Custom Group for Users be considered as the simplest mechanism for assuring that all the application users have the required privileges and permissions (which correspond to those of a member of a workstation, not network or enterprise, “Administrators” group).

Each user logon must have defined printer(s)

All user logons must have any printer that the application can use defined in their “Printers and Faxes” folder. Direct access to “UNC names” is not supported. Export-It can only use a printer that is defined as a Windows® printer for the user that is running the application.

Execution must see a “32-bit” API

The Export-It application is inherently a “32-bit” application and uses the “Windows® 32-bit API” environment that is available on all Windows® platforms from NT or 95 through 2008 or 7. But when installed in a native “64-bit” version of Windows® then setup must ensure that all components (located in the Platform "local" Folder) will execute in a “32-bit” or “XP” compatibility mode.