Highlighted
Super Contributor.
Super Contributor.
183 views

Client's environment variables under thinclient

Jump to solution

Is it possible to get an environment variable of the windows client  (for example %systemroot%) using Thinclient without redirecting the output under windows and then opening and reading the output file under linux (our host operating system) ?

 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Super Contributor.
Super Contributor.

Re: Client's environment variables under thinclient

Jump to solution

There are a few exceptions, but I believe you are correct.  For most things, you would have to use a client-side command like "set >vars.txt" then use C$COPY to get the file to your server and then read it.

The exceptions: A couple of values in the ACCEPT FROM structures come from the workstation environment variables:

CLIENT-MACHINE-NAME and CLIENT-USER-NAME from TERMINAL-INFO structure.

USER-ID and STATION-ID from SYSTEM-INFORMATION.

 

Finally, when using @[DISPLAY]: there are a few pre-defined system paths you can use - see the Acuconnect manual, subsection on copying files between the client and the server.

Identifier Directory
<APPDATA>C:\Documents and Settings\<user>\Application Data
<COMMON_APPDATA>C:\Documents and Settings\All Users\Application Data
<COMMON_DOCUMENTS>   C:\Documents and Settings\All Users\Documents
<DESKTOP>C:\Documents and Settings\<user>\Desktop
<LOCAL_APPDATA>C:\Documents and Settings\<user>\Local Settings\Application Data
<MYDOCUMENTS>C:\Documents and Settings\<user>\My Documents

View solution in original post

0 Likes
1 Reply
Highlighted
Super Contributor.
Super Contributor.

Re: Client's environment variables under thinclient

Jump to solution

There are a few exceptions, but I believe you are correct.  For most things, you would have to use a client-side command like "set >vars.txt" then use C$COPY to get the file to your server and then read it.

The exceptions: A couple of values in the ACCEPT FROM structures come from the workstation environment variables:

CLIENT-MACHINE-NAME and CLIENT-USER-NAME from TERMINAL-INFO structure.

USER-ID and STATION-ID from SYSTEM-INFORMATION.

 

Finally, when using @[DISPLAY]: there are a few pre-defined system paths you can use - see the Acuconnect manual, subsection on copying files between the client and the server.

Identifier Directory
<APPDATA>C:\Documents and Settings\<user>\Application Data
<COMMON_APPDATA>C:\Documents and Settings\All Users\Application Data
<COMMON_DOCUMENTS>   C:\Documents and Settings\All Users\Documents
<DESKTOP>C:\Documents and Settings\<user>\Desktop
<LOCAL_APPDATA>C:\Documents and Settings\<user>\Local Settings\Application Data
<MYDOCUMENTS>C:\Documents and Settings\<user>\My Documents

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.