Application User# variable?

[PowerUsr]

I am using Metaframe 1.8 application manager to deploy a single application that requires a user=# environmental variable.
I can use the SETENV command when deploying desktops to accomplish this, however the SETENV command does not appear to be recognized when the application is deployed by its self. I could really use some help on this issue..

Thanks

Bryan

 

[ascotta]

You could set the vaariable in the usrlogon.cmd script that lives in C:\Winnt\system32.

You may need to tinker a bit but it should work.

[blue] Oh you know, just doing what I do.[/blue]

Cheers
Scott

 

[PowerUsr]

Thanks for the suggestion, gut I already have a logon script that works fine from any windows session. The problem is that this set user =# variable in the script is not recognized when the application is published by its self. Any thoughts?

 

[ascotta]

Each Citrix server has its own login script as stated above.

It will run when a user connects to the citrix server only.

[blue] Oh you know, just doing what I do.[/blue]

Cheers
Scott

 

[PowerUsr]

Scott,

Thanks for the feedback. Let me give you more background.

There is a single Citrix server that is deploying an application that requires a unique User=# for each session.

I currently have a logon script that functions using the SETENV command when I deploy an entire desktop for each session.

This same logon script does not function when only the application if deployed using the Metaframe application manager.

Any other ideas?

 

[ascotta]

Well it should. Try publishing the command prompt for the user and see what env comes up with.

[blue] Oh you know, just doing what I do.[/blue]

Cheers
Scott

 

[PowerUsr]

I am currently using "logon.bat" as the source for the Citrix Metaframe application manager this bat file excutes the SETENV command and calls the application. The problem is the application does not recognize the user# specified in the logon script. Keep in mind this works perfectly when the same users logos into an entire windows desktop session. It seems that when an application is published it handles the SETENV command differently.