after using c:\windows\application compatibility scripts\chkroot.cmd
and put "Set RootDrive=W:" in the last line of RootDrv2.cmd
This Rootdrive-Subst does somtimes (mostley) do not map the W: -Drive
(-There is no W: -Drive)
1. userlogon.cmd calls SetPaths.Cmd
2. SetPaths.cmd calls ACRegL.exe .......and builds getpaths.cmd
3. By looking into temporary gethpaths.cmd during the Logon, there are only
6-line of 9 needed writen into getpahts.cmd
MY_DOCUMENTS, TEMPLATES and APP_DATA are NOT writen into getpaths!
4. back in userlogon.cmd because
"If "%_SETPATHS%" == "FAIL" GOTO Done
the RootDrive W: is not build
On a HP ML 350 dual Xenon 2,2 GHz everithing is working perfekt/ Win2003 Std
On 2 dual AMD-Opteron 280 HP DL385 Server this Problem occures by same
Configuration in same OE /Win2003 Enterprise
Are this Machines to fast?
There is also a differenz between RDP-Desktop- und RDP-Programm-Executen
By just starting a RDP Desktop-Connection
on the first User-Connection w: fails
Then from the next Connection "Setpaths.cmd" is build correct an W: is mapped
By direkt executing a Program with the RDP-Client
it will never be function -there ist never a W: -Drive
because "Setpaths.cmd" the last lines are not writen.