jamesbryan2004
asked on
Terminal Services and temp files
Hello all
Here's my problem. I have an application on Terminal services server 2003 and when a user prints it creates a temporary word file. The problem is that it only sees one user temp file so that one user can continue to print but nobody else can print because it thinks word is still open. If I delete this temp folder than somebody else can print. My question is how can I get the TS users there own temp directory so the temp file goes to that user instead of the application seeing it as only one user. Thanks in advance.
Here's my problem. I have an application on Terminal services server 2003 and when a user prints it creates a temporary word file. The problem is that it only sees one user temp file so that one user can continue to print but nobody else can print because it thinks word is still open. If I delete this temp folder than somebody else can print. My question is how can I get the TS users there own temp directory so the temp file goes to that user instead of the application seeing it as only one user. Thanks in advance.
ASKER
The application created it's own temp folder inside the program folder. The fix was to give rights to the application folder so that people could write to this temp directory.
Is the application called "finance plus" by any chance?
Anyhoo.. what you might be able to use is a logon script and junction points.
It would allow you to point that temp folder to some other location. In the logon script you would use something like the username variable to give everyone their own temp folder and still keep the app working.
Have a look at these two sites.
http://support.microsoft.com/?kbid=205524
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techref/en-us/linkd.asp
I think you want to put something like this in a bat file in the login script for the terminal server:
md c:\mytemp\%username%
linkd c:\mytemp\%username% "c:\finance plus\temp"
Then delete it in the logoff script:
linkd c:\mytemp\%username% /d
rd /s /q c:\mytemp\%username%
You need the double quotes when the path has a space in it.
Let me know if you need help with the group policy to make this work. Maybe just test manually with two users first?
Oh, you could also use the %sessionname% variable in case people logged on twice.
Anyhoo.. what you might be able to use is a logon script and junction points.
It would allow you to point that temp folder to some other location. In the logon script you would use something like the username variable to give everyone their own temp folder and still keep the app working.
Have a look at these two sites.
http://support.microsoft.com/?kbid=205524
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techref/en-us/linkd.asp
I think you want to put something like this in a bat file in the login script for the terminal server:
md c:\mytemp\%username%
linkd c:\mytemp\%username% "c:\finance plus\temp"
Then delete it in the logoff script:
linkd c:\mytemp\%username% /d
rd /s /q c:\mytemp\%username%
You need the double quotes when the path has a space in it.
Let me know if you need help with the group policy to make this work. Maybe just test manually with two users first?
Oh, you could also use the %sessionname% variable in case people logged on twice.
ASKER
No it's not finance plus it's an attendance program. I'm pretty new to windows server We use novell except this application. Is there a tid that you know of to help me create a login script and things? Thanks.
ASKER
I've used your login script but the linkd parameter fails. It's not recognized as a command. Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Are they in a system specified temp directory - eg C:\documents and settings\user\local settings\temp\
or is the application creat it's own temp folder inside the program folder - eg c:\application\temp\
There is a system variable for temp location and nice applications should use this instead of some hard coded location. Figure out which case you fall into and then we can possibly find some workaround.
if you open a command prompt and type
set
you will get a list of all the system variables, see if the one for temp or tmp matches the location of the temp file.