User guide

M: Windows Terminal Services/Citrix MetaFrame
278
revision 143
General Issues
Color Depth. The color depth that Terminal Server and Citrix MetaFrame
client machines use can be configured. A setting greater than 256 colors
should be used so that the B.A.S.I.S. applications and online help will be
displayed correctly.
Note that Terminal Server can be run without Citrix MetaFrame. Terminal
Server alone cannot display more than 256 colors. When Terminal Server is
run in combination with Citrix MetaFrame 1.8 Feature Release 1 (Service
Pack 2) and Citrix NFuse, color depth greater than 256 colors can be
displayed.
Install B.A.S.I.S. on Terminal Services machine via Add/Remove
Programs. Installation programs cannot be run directly on a Terminal
Services machine. Instead, they must be run via Add/Remove Programs in
the Windows operating system. When the B.A.S.I.S. installation application
is run from Add/Remove Programs, there may be a delay before the
installation begins. The Add/Remove Programs wizard will display a
message that says, “Click Next after installation”. Wait for the B.A.S.I.S.
installation window to open - do not click the [Next] button in the Add/
Remove Programs wizard until the B.A.S.I.S. installation has finished.
Implications
User preferences saved to LOCAL_USER in the Windows registry
separate for each user. In a normal Windows environment, all Windows
users share the same registry setting. This differs from a Terminal Server
Windows environment, where settings in the LOCAL_USER registry entry
are stored separately for every Windows user.
B.A.S.I.S. saves user preferences to LOCAL_USER in the Windows
registry. In a Terminal Server Windows environment, there are separate
sections in LOCAL_USER for each B.A.S.I.S. user id. For example:
In a normal Windows environment when SA logs on from two different
Windows accounts, the saved preferences will be common/shared.
In a Terminal Server environment when SA logs on from two different
Windows accounts, two sets of preferences for SA would be stored
because the registry settings are separate for every Windows user.
ACS.INI is copied to the user’s home directory when using Terminal
Server. Whenever an .INI file is opened by an application, if a copy of it
does not already exist in the Windows subdirectory of the users home
directory, one gets copied from the Windows directory (i.e. C:\winnt in
Windows 2000 or C:\Windows in Windows XP) and placed there. From that
point on, the .INI file from the Windows directory is no longer used. Instead,