How to Set Unique Terminal# IDs Through WinFrame via a .BAT or .CMD fileHow to Set Unique Terminal# IDs Through WinFrame via a .BAT or .CMD file How to Set Unique Terminal# IDs Through WinFrame via a .BAT or .CMD file
Citrix states in their article: CTX851458
CTX851458 - How to Set Unique Terminal# IDs Through WinFrame via a .BAT or .CMD file
This document was published at: http://support.citrix.com/kb/entry.jspa?externalID=CTX851458
Document ID: CTX851458, Created on: Jul 13, 2000, Updated: Apr 23, 2003
Products: Citrix WinFrame 1.8
Placing the SET command in WinFrame's AUTOEXEC.NT or in a batch file that calls the program will only suffice for one instance of the application running on WinFrame, Therefore it is necessary to devise a different scheme to provide the unique IDs. So far it seems that setting the environment variable based on the WinStation connection is the most reliable. This can be done by using simple batch file commands that utilize the %winstationname% environment variable.
Below is a sample batch file:
@echo off
REM
REM *** This batch file sets an environment variable based upon
REM the environment variable WINSTATIONNAME ***
REM
SET TERMID=
if not "%winstationname%"=="console" goto second
set termid=01
goto end
:second
if not "%winstationname%"=="ipx#001" goto third
set termid=02
goto end
:third
if not "%winstationname%"=="ipx#002" goto fourth
set termid=03
goto end
:fourth
REM This handles the situation where the WINSTATIONNAME is set to something
REM not accounted for by this batch file
echo ERROR: The WinStation Name '%winstationname%' was not accounted for.
echo The environment variable TERMID was not set.
pause
goto done
:end
REM You may want to start the program that depends on the new env. var. here.
:done
Primary links
User login
Who's new
- japhabept
- Rullydery
- eagenorce
- rittaarier
- swasseZex
