mark evinger

Hello all, I have a WinNT 4.0 Terminal Server Edition SP6a, with Citrix
MetaFrame 1.8. My issue is that the server is not always creating or
placing temp files in the correct location. Some users log in and their
temp file location correctly goes to the c:\temp\<sessionID>\ folder.
Others log in, and all the temp files are dumped into C:\temp\

If I check the temp variables for system and user with
MyComputer|Properties|Environment tab they are both (TEMP and TMP) set to
%SystemDrive%\Temp (for both system and user variables). This is as it
should be - the server was set up in this fashion from day one. If I change
the system variable and re-apply to be %systemdrive%\temp and OK out of the
system properties dialog, then any new temp files are properly created.

This error cropped up Wednesday, after the re-installation of accounting
software Wind2 FMS. We upgraded our Wind2 install, and the Crystal reports
dll's did not want to copy properly into the \system32 folder. Wind2 needs
to keep each user's temp files separate, and normally will do so - up until
two days ago.

Does anyone know how to keep Terminal Server from using the plain C:\temp
folder? I am ready to try changing the system TMP and TEMP vars to
%systemdrive%\TESTME to see what happens. It feels like a registry issue,
the clients are not reading the values correctly until we've messed with the
system properties dialog and applied the settings again.

Thanks for any information you can pass along.

Mark Evinger

vera noest [mvp]

Can't offer you real help, just a similar story.

I installed a new application the other day (on a test server),
and after installation I couldn't run a single command from the
command prompt ("executable not found").
It turned out that the application had appended its program
directory to the SYSTEM and USER PATH variable. Although
everything *looked* OK (the PATH wasn't too long, no weird
characters, etc), the PATH obviously wasn't read correctly anymore
by the clients, so they couldn't find a single executable in %
systemroot% :-(

I fixed it by editing the PATH, not changing anything, just saving
it again as it was. That solved the issue.
This happened depite the fact that the application was installed
with an account with full administrative priviledges, on the
console, in install mode.
I blamed the application developer....

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

"Mark Evinger" <Mark.Evinger_DieSpamDie@_DieSpamDie_cgl-ltd.com>

mark evinger

Well, made the call to Microsoft tech support and we tracked down a
reasonable cause. The NWGINA.dll file is not bringing the right temp file
locations across - We've had the Novell Client32 v4.71 on this server since
day one, but changing the GINA to the MSGINA.dll has fixed the issue for
now. Guess I get to take it up w/Novell and use their latest v4.91 client
to see if that will work....

Mark Evinger