Terminal Server - custom Windows directory?

[jrwinterburn]

Hi All,

I am in the process of setting up a terminal server on Windows Server 2003 and all is well except for one thing. I have a custom program that depends on using an ini file that resides within C:\Windows. The trouble is, this file needs to be unique for each user, as they have their own customised version of this file on their PCs.

How can I get TS to recognise the custom version of the file dependant on the user connected? I thought it would be as simple as putting the user's version of the ini file into a WINDOWS folder in their roaming profile, but this has no effect.

Any ideas?

Thanks

Jon

 

[itsp1965]

I used to work with apps that required dedicated INI files for each user in Terminal services (it's been awhile though). If I recall I would place the base ini file in the system32 folder and the first time users would log on, the file was copied to their local windows profile. If a user already had an INI file in their windows folder, you would need to delete it in order for them to pick up a "fresh" version.

 

[jrwinterburn]

This doesn't seem to happen in my case. They are using roaming profiles, but no Windows folder is created. If I create one, and put the ini file in there, it is ignored. However, the administrator account (local, not roaming) has a windows folder already created and it did copy the ini file into it automatically, so I could change this to suit.

Why does windows not recognise the additional windows directory with ini file in the user's profile folder? I have even tried specifying windir environment variables for the users to point to their version of the windows folder, but alas, no luck!

 

[itsp1965]

Since the INI file is a throwback to Windows 3.x I am assuming it is reliant on the presence of a Windows directory for compatibility sake.