Slow Desktop logons when RDP to Windows 2008 Server

Yes I have mapped drives - Basic domain GPO applied.  However this computer account was initially in the Computers Container and we still had slow logons.  So I moved it to the servers OU where most other servers are and ran GPUPDATE /FORCE.  We have no folder redirection happening on this OU, it's happens on the Terminal Servers OU.  However we do have a printer mapping vbs and I have printer sharing disabled.  I will turn that on and see if that helps.  I'll repost my findings.  I also ran GP modeling on that computer account and my domain account but didn't really find anything earth shattering.

Create OU with no GPOs then drag the server into OU for testing.

I just mentioned above that initially it was in the Computer Container.  That's not an OU, hence no GPO's applied and it was still slow.

The Computer Container can still have GPOs being applied to it.

You can only apply a GPO to an OU.

Please read.

http://technet.microsoft.com/en-us/library/cc978249.aspx

A Group Policy object applied to a domain applies directly to all users and computers in the domain and by inheritance to all users and computers in organizational units (and in generic Active Directory containers) farther down the Active Directory tree as seen in the Active Directory Users and Computers namespace.

Touché I forgot about inheritance ;-)  I will create a new OU and block inheritance to see if that makes a difference.

Still painfully slow to log in.  Test OU with Blocked inheritance.  When it starting the applying desktop profile process or whatever I hear a beep in the background.  I wander if something is failing or waiting for some dialog box to be answered?

I wonder if I need the Schema extended or something like that?  I am pretty sure that I only need to do that if I want to access some of the new Group Policy objects or templates but it's not a necessity.  Is there anything from the Vsphere layer that I should check?

I also just downloaded and installed RDC v6.1 to see if that would help performance.  The answer is a resounding NO...

Can you post ipconfig /all please.

I think that it's a AD 2003 and Windows 2008 issue.  Here is an exert from the App log:

The winlogon notification subscriber <GPClient> took 600 second(s) to handle the notification event (StartShell).

Anyone know how to solve this GP timeout?

Yes I have seen and/or tried both of these articles.  The interesting one is the active directory printer mappings.  We use AD to launch a VBS script which checks group membership and assigns a default printer.  However I checked Group Policy Modeling and that GPO is not being applied.  I do think that it has to do with AD GPO though.

How about that ipconfig /all?

So, are you still getting the error even after you move it to a new OU? Have you installed GPO Client side Extensions?

I don't really see the relevence in a ipconfig /all.  I have IP v6 enabled (however I have also tried with it being disabled), I have a static IP address, SN, DG, and internal DNS servers configured.

A ipconfig /all will help troubleshoot network issues. Trust me there have been many posters thinking their network config was correct or there was nothing wrong with it.