02.01.2015 Views

Installation & Setup User Guide - Best Access Systems

Installation & Setup User Guide - Best Access Systems

Installation & Setup User Guide - Best Access Systems

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

M: Windows Terminal Services/Citrix MetaFrame<br />

General Issues<br />

• Color Depth. The color depth that Terminal Server and Citrix MetaFrame<br />

client machines use can be configured. A setting greater than 256 colors<br />

should be used so that the B.A.S.I.S. applications and online help will be<br />

displayed correctly.<br />

Note that Terminal Server can be run without Citrix MetaFrame. Terminal<br />

Server alone cannot display more than 256 colors. When Terminal Server is<br />

run in combination with Citrix MetaFrame 1.8 Feature Release 1 (Service<br />

Pack 2) and Citrix NFuse, color depth greater than 256 colors can be<br />

displayed.<br />

• Install B.A.S.I.S. on Terminal Services machine via Add/Remove<br />

Programs. <strong>Installation</strong> programs cannot be run directly on a Terminal<br />

Services machine. Instead, they must be run via Add/Remove Programs in<br />

the Windows operating system. When the B.A.S.I.S. installation application<br />

is run from Add/Remove Programs, there may be a delay before the<br />

installation begins. The Add/Remove Programs wizard will display a<br />

message that says, “Click Next after installation”. Wait for the B.A.S.I.S.<br />

installation window to open - do not click the [Next] button in the Add/<br />

Remove Programs wizard until the B.A.S.I.S. installation has finished.<br />

Implications<br />

• <strong>User</strong> preferences saved to LOCAL_USER in the Windows registry<br />

separate for each user. In a normal Windows environment, all Windows<br />

users share the same registry setting. This differs from a Terminal Server<br />

Windows environment, where settings in the LOCAL_USER registry entry<br />

are stored separately for every Windows user.<br />

B.A.S.I.S. saves user preferences to LOCAL_USER in the Windows<br />

registry. In a Terminal Server Windows environment, there are separate<br />

sections in LOCAL_USER for each B.A.S.I.S. user id. For example:<br />

– In a normal Windows environment when SA logs on from two different<br />

Windows accounts, the saved preferences will be common/shared.<br />

– In a Terminal Server environment when SA logs on from two different<br />

Windows accounts, two sets of preferences for SA would be stored<br />

because the registry settings are separate for every Windows user.<br />

• ACS.INI is copied to the user’s home directory when using Terminal<br />

Server. Whenever an .INI file is opened by an application, if a copy of it<br />

does not already exist in the Windows subdirectory of the user’s home<br />

directory, one gets copied from the Windows directory (i.e. C:\winnt in<br />

Windows 2000 or C:\Windows in Windows XP) and placed there. From that<br />

point on, the .INI file from the Windows directory is no longer used. Instead,<br />

278 — revision 143

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!