MSTerminalServices.org Forums

Forums Home | FAQ | Search | Profile | Private Messages | Log in/Register/Password

Terminal Server - Set RootDrive=W: fails- (dual-Core Opter..

Page 1 of 1
Next:  General Discussions: Suddenly, applications won't stay running  
Author Message
speedy

External


Since: Jan 13, 2006
Posts: 2



(Msg. 1) Posted: Fri Jan 13, 2006 9:56 am
Post subject: Terminal Server - Set RootDrive=W: fails- (dual-Core Opteron)
Archived from groups: microsoft>public>windows>terminal_services (more info?)

Hi,

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!

then
:Failure
Set _SetPaths=FAIL
is set


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?

-----


More:

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.


Hopefully yours
Back to top
Send e-mail Login to vote
speedy

External


Since: Jan 13, 2006
Posts: 2



(Msg. 2) Posted: Sat Jan 14, 2006 5:13 am
Post subject: RE: Terminal Server - Set RootDrive=W: fails- (dual-Core Opteron) [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

ACRegL.exe reads Paths from the Registry.
By the very first Logon with the unmodifyed "default user" Profile
"MY_DOCUMENTS" is empty. A few moments after executing ACRegL.exe thes
Profileentries are juist build in the new Profile/HKCU.
To late for ACRegL.exe because ist stops by the missing Entry.

Workaround:

Just copy a new "Default-User"-Profile from a User who has once had a
Desktop-Login. The the Paths are already set- and ethering ist OK.

Had have anybody the same experience withe a vergin Default-Profile on
Terminal-Services?

greetings
speedy





"speedy" wrote:

> Hi,
>
> 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!
>
> then
> :Failure
> Set _SetPaths=FAIL
> is set
>
>
> 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?
>
> -----
>
>
> More:
>
> 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.
>
>
> Hopefully yours
>
>
>
>
>
>
>
>
Back to top
Send e-mail Login to vote
Display posts from previous:   
    All times are: Eastern Time (US & Canada) (change) Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Looking for more Terminal Services info?

Sign up to the MSTerminalServices.org Monthly Newsletter, written by Terminal Server MVP & Citrix CTP Stefan Vermeulen, containing news, tips, interviews, links of the month and much more. Subscribe today and don't miss a thing!

Become an MSTerminalServices.org member!

Discuss your Terminal Services & Citrix issues with thousands of other SBC experts. Click here to join!

Community Area

Log in | Register