Environmental Variables ini file

[Guest slawrie]

I have a program that normally installs on a workstation and has an ini file

that sets user specific variables within the program. The problem is that

when it is installed on a teminal server all users are accessing the same ini

file. I was told that I could create a directory for each user and place the

ini file in the individual directory. Then delete the original ini file. I

was also told I would need to set an environmental variable that would find

each users ini file. I am unsure how to do that and could use some advice.

 

Thanks,

 

Steve

[Guest Vera Noest [MVP]]

Re: Environmental Variables ini file

 

Did you put the terminal Server into "install mode" before

installing the application? That should take care of most ini-files

issues.

Documented here:

 

186498 - Terminal Server Application Integration Information

http://support.microsoft.com/?kbid=186498

 

which also lists the compatibility bits. But you shouldn't need

them when install mode makes sure that each user gets a private ini

file in the windows directory in their home directory.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?c2xhd3JpZQ==?= <slawrie@discussions.microsoft.com> wrote

on 19 jul 2007 in microsoft.public.windows.terminal_services:

> I have a program that normally installs on a workstation and has

> an ini file that sets user specific variables within the

> program. The problem is that when it is installed on a teminal

> server all users are accessing the same ini file. I was told

> that I could create a directory for each user and place the ini

> file in the individual directory. Then delete the original ini

> file. I was also told I would need to set an environmental

> variable that would find each users ini file. I am unsure how to

> do that and could use some advice.

>

> Thanks,

>

> Steve