Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Terminal Services Profiles & Application data files.

Posted on 2009-07-15
5
Medium Priority
?
434 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 14

Expert Comment

by:Robin CM
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:Robin CM
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:
Robin CM earned 1500 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

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

Sometimes drives fill up and we don't know why.  If you don't understand the best way to use the tools available, you may end up being stumped as to why your drive says it's not full when you have no space left!  Here's how you can find out...
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
Suggested Courses

610 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