一台电脑 ，多个操作系统用户同时安装TC客户端，共用的配置，主要场景是：Citrix平台共享资源

To use the certification database, choose the platform and products you use, and
then click Show Certifications.
Configuring multiuser support on Windows
On Windows systems, the pipe connection to the FMS client cache (FCC) uses a
single value by default, allowing one user to connect to the FCC per machine. If
multiple users run instances of Teamcenter on the same Windows machine, each
user accesses the same pipe name and possibly connects to the same FCC.
Enabling multiuser support configures the pipe name to work with user IDs,
ensuring that each user connects with a unique pipe to the appropriate FCC.
Configure multiuser support without NX
If you are running FMS 1.3 (20070409 or later) and are not running NX, the following
steps configure FMS running on a Windows system to accept multiple users.
If you are running an earlier version of FMS, or are also running NX, see Configure
multiuser support with NX.
Note
Local administration privileges are required to set a global environment
variable.
1. In the system environment (System Properties→Advanced→Environment
Variables→System Variables), set the FMS_WINDOWS_MULTIUSER
environment variable to true.
2. Reboot the system to propagate this setting to all users and applications.

Configure multiuser support with NX
If you are running a version of FMS earlier than 1.3 or are running NX, the following
steps configure FMS running on a Windows to accept multiple users.
Note
Local administration privileges are required to set a global environment
variable.
Write permission for %FMS_HOME%\fcc.xml and all FMS application
startup scripts is required.
1. In the system environment (System Properties→Advanced→Environment
Variables→System Variables), set the FMS_WINDOWS_MULTIUSER
environment variable to false.
2. Specify a user-specific pipe name for use in step 3.
For example, for user JohnDoe, specify \\.\pipe\FMSClientJohnDoePipe.
For an administrative user, specify \\.\pipe\FMSClientAdministratorPipe.

3. Change the pipe name entry in the %FMS_HOME%\fcc.xml file. The name
must end with an alpha character. Pipe names ending in numeral characters
(0–9) are not supported. For example:
<property name="FCC_ProxyPipeName"
value="\\.\pipe\FMSClient_$USERPipe|/tmp/FMSClientPipe" overridable="true"/>
$USER is resolved by the FCC at run time to the name of the user.
4. Run the application launch script for each FMS application. This sets the pipe
name in the environment for each application. For example:
set FCC_PROXYPIPENAME=\\.\pipe\FMSClient_%USERNAME%Pipe
After the user name is substituted, the pipe name must exactly match the
FCC_ProxyPipeName value specified in the %FMS_HOME%\fcc.xml file.
Note
The pipe name must be set dynamically at run time (not in the system
environment) to properly resolve the user name (%USERNAME%) value.
5. Reboot the system to propagate this setting to all users and applications