Solved

Terminal Services Profiles & Application data files.

Posted on 2009-07-15
5
411 Views
Last Modified: 2013-11-21
Currently in the process of setting up an Auto Dealers Package on 2008 Server
for both network users that use File sharing to access the application as well
as Terminal Server Users.

File Sharing users run the application via a mapped drive letter to the applications directory.
(S: ==> \\Server\Share).

Catch is each user's application settings such as screen layout & printer settings are stored in a User.DAT file in the root directory of the users C: drive on their local PC.
This is not a problem for Users running Via File & Print sharing.

What happens when a user runs the application via Termnal Services is that they end up all using the one User.DAT file in the root directory of the server & hence cannot save their own application settings.

Is there a way to redirect this file to the Windows directory within their Terminal Services Profile.

I've seen something similar to this previously on a site where wach user had a system.ini file stored in their TS Profile for similar reasons.
0
Comment
Question by:PhilPorritt
  • 3
  • 2
5 Comments
 
LVL 14

Expert Comment

by:robincm
ID: 24869371
Depends on the application and how hardcoded c:\user.dat is.

You could try setting the working directory to the user's personal/home drive (this is under the published app configuration, on the Location page - same as where you specify the executable to run). This works for some apps.
0
 

Author Comment

by:PhilPorritt
ID: 24875620
Believe the application is pretty much hard coded to write this file to C:\.

Iv'e suported it since the DOS days & their migration to windows still has a lot of hang overs from way back.
0
 
LVL 14

Expert Comment

by:robincm
ID: 24876535
Well if it's hard coded to C:\ then you're basically stuffed.
Poor coding always comes back to bite somebody eventually :-(
0
 
LVL 14

Accepted Solution

by:
robincm earned 500 total points
ID: 24876570
You could always rebuild your terminal server and choose M: as the system drive letter, then you could use subst to map C: to the users' home drive in a logon script. Nasty though.
0
 

Author Closing Comment

by:PhilPorritt
ID: 31604116
Excellent lateral sollution that would be valuable in many situations.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

820 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question