RDC Logins not Completing - stick on 'hourglass'

[Guest goneill]

We run Remote Desktop Connection for all our users to connect to Terminal

Servers (Windows 2003). They connect from PCs (XP and Vista) which are

logged on locally, but connected to our Domain.

 

Some users frequently find when logging on to their RDC session, that the

logon process does not appear to complete and they get their session opening

with the 'hourglass' curser permanently on show. The only fix appears to be

to get a Domain Administrator to log-off their session from the Terminal

Services Manager so they can try again. Sometimes it takes a few tries

before they can get a working RDC session.

 

The problem is not isolated to one Terminal Server. We have three Terminal

Servers and the problem can show up on any one of them.

 

I thought the login scripts (which map network drives) may be causing the

problem so I disabled them. But that hasn't resolved the problem.

I've also made sure the users are not storing large amounts of data in their

roaming profiles.

 

It has occurred to me that the problem could be with the roaming profiles

themselves, but I thought I'd get some feedback through technet first,

because I'd rather not have to go messing around with peoples' profiles if I

don't have to. Or if I do have to, to at least have some information which

may enable to do so in a targeted manner.

 

Has anyone come across this problem before? Any ideas on how to resolve it?

[Guest Jeff Pitsch]

Re: RDC Logins not Completing - stick on 'hourglass'

 

How large are the profiles? have you confirmed that the sessions were

logged off from tehir previous session? Have you enabled user environment

debugging to trace the entire logon process? are the profiles TS only

profiles or are you using workstation profiles and roaming those (really

really really bad idea)?

 

It could be profiles but if you're not deleting the profiles to fix the

problem, then it's a good chance it's not. My immediate guess is that a

previous session for the user did not log off properly and was still active

or in a hung logoff process.

 

Jeff Pitsch

Microsoft MVP - Terminal Services

 

"goneill" <goneill@discussions.microsoft.com> wrote in message

news:5E4713C6-1444-406A-90BD-6F4F65ED776F@microsoft.com...

> We run Remote Desktop Connection for all our users to connect to Terminal

> Servers (Windows 2003). They connect from PCs (XP and Vista) which are

> logged on locally, but connected to our Domain.

>

> Some users frequently find when logging on to their RDC session, that the

> logon process does not appear to complete and they get their session

> opening

> with the 'hourglass' curser permanently on show. The only fix appears to

> be

> to get a Domain Administrator to log-off their session from the Terminal

> Services Manager so they can try again. Sometimes it takes a few tries

> before they can get a working RDC session.

>

> The problem is not isolated to one Terminal Server. We have three

> Terminal

> Servers and the problem can show up on any one of them.

>

> I thought the login scripts (which map network drives) may be causing the

> problem so I disabled them. But that hasn't resolved the problem.

> I've also made sure the users are not storing large amounts of data in

> their

> roaming profiles.

>

> It has occurred to me that the problem could be with the roaming profiles

> themselves, but I thought I'd get some feedback through technet first,

> because I'd rather not have to go messing around with peoples' profiles if

> I

> don't have to. Or if I do have to, to at least have some information

> which

> may enable to do so in a targeted manner.

>

> Has anyone come across this problem before? Any ideas on how to resolve

> it?

>

[Guest Vera Noest [MVP]]

Re: RDC Logins not Completing - stick on 'hourglass'

 

Any profile load or unload errors in the EventLog?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote on 09 jul 2008

in microsoft.public.windows.terminal_services:

> How large are the profiles? have you confirmed that the

> sessions were logged off from tehir previous session? Have you

> enabled user environment debugging to trace the entire logon

> process? are the profiles TS only profiles or are you using

> workstation profiles and roaming those (really really really bad

> idea)?

>

> It could be profiles but if you're not deleting the profiles to

> fix the problem, then it's a good chance it's not. My immediate

> guess is that a previous session for the user did not log off

> properly and was still active or in a hung logoff process.

>

> Jeff Pitsch

> Microsoft MVP - Terminal Services

>

> "goneill" <goneill@discussions.microsoft.com> wrote in message

> news:5E4713C6-1444-406A-90BD-6F4F65ED776F@microsoft.com...

>> We run Remote Desktop Connection for all our users to connect

>> to Terminal Servers (Windows 2003). They connect from PCs (XP

>> and Vista) which are logged on locally, but connected to our

>> Domain.

>>

>> Some users frequently find when logging on to their RDC

>> session, that the logon process does not appear to complete and

>> they get their session opening

>> with the 'hourglass' curser permanently on show. The only fix

>> appears to be

>> to get a Domain Administrator to log-off their session from the

>> Terminal Services Manager so they can try again. Sometimes it

>> takes a few tries before they can get a working RDC session.

>>

>> The problem is not isolated to one Terminal Server. We have

>> three Terminal

>> Servers and the problem can show up on any one of them.

>>

>> I thought the login scripts (which map network drives) may be

>> causing the problem so I disabled them. But that hasn't

>> resolved the problem. I've also made sure the users are not

>> storing large amounts of data in their

>> roaming profiles.

>>

>> It has occurred to me that the problem could be with the

>> roaming profiles themselves, but I thought I'd get some

>> feedback through technet first, because I'd rather not have to

>> go messing around with peoples' profiles if I

>> don't have to. Or if I do have to, to at least have some

>> information which

>> may enable to do so in a targeted manner.

>>

>> Has anyone come across this problem before? Any ideas on how

>> to resolve it?