2012 R2 RDS Slow Login with Black screen

Anyone know why 2012 R2 RDS Session Hosts would be slow during RDP login. Login works fine but after logging in users experience black screen until after long delay with each stage progressing slowly and occasionally a brief connection drop before jumping to desktop of Terminal Server/Session Host.

Have already turned off Smart Card service and set TCP/IP Offload registry key to "1".  Even set RDP protocol to use only TCP instead of UDP.

2008 R2 RDS Farm on same network has occasional glitch but nothing as bad as 2012 R2 RDS is showing.
Vincent DAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ankit PareekOnline MarketingCommented:
If RDP screen goes black. try to press CTRL+ALT+END then hit to cancel. Closed RDP.
Again reopen RDP and you have your desktop back in good working condition
0
chanderpal singh rathoreMicrosoft Exchange EngineerCommented:
Hi,

You can try the following to resolve your issue:


    1. Disable the use of "Bitmap Caching" on the RDP client.
 
    2. Verity that the server, client and the network equipment using the "MTU" size.
 
    3. Press ctrl + alt + del and open the task viewer and you will not have to wait on black screen.

For your reference please follow the link for all possible solutions:

http://www.grishbi.com/2015/01/rdp-black-screen/


Good Luck!!!!!!!!!!!!!!!
0
Vincent DAuthor Commented:
This is for terminal server farm users should not have abnormally slow login with black screen before seeing desktop when login finally finishes
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Aaron TomoskySD-WAN SimplifiedCommented:
Do you have multiple physical locations? Folder or profile redirection gpo or login scripts?

If so you could need a loop back policy based on the rds server location
http://kudratsapaev.blogspot.com/2009/07/loopback-processing-of-group-policy.html?m=1
0
Henrik JohanssonSystems engineerCommented:
A possible reason is roaming profiles without using folder redirection to minimize the size of data being copied during login/logout.
0
joharderCommented:
I agree that the issue may be the user profile.  Is the user actually getting the correct user profile or is that being attempted and then timing out for whatever reason and the user is actually getting a temp profile?  

A few other areas to check:
- Is a login script configured for users?  
- How are printers mapped?
- Are there any peripherals other than printers used?
- Are any GPOs configured that impact logon?
0
Vincent DAuthor Commented:
Profiles are currently local to terminal servers. No GPOs applied  yet. Just doing initial testing of 2012 R2 RDS Farm. There are login scripts but same scripts work fine on 2008 R2 RDS farm hosted at location hosting all servers. Have tried RDP into 2008 R2 RDS Farm first to keep all processes local to servers and then RDP into 2012 R2 RDS Farm from within session on 2008 R2 RDS Farm but still shows slow login with blackscreen making up large portion of time while waiting for login to finish.

Problem is not consistent always as sometimes it is quick but usually it is slow even when everything is local from 10Gbps switch core. Never have black screen from 2008 R2 RDS farm even if 2008 R2 RDS login is slower than normal.

No printers yet just test environment with 2012 R2 RDS Farm setup as follows...basic applications installed on SH servers

rdsbroker.contoso.com (broker and web server)
rdslicense.contoso.com (set up to per user from broker config) will apply licensing when testing done and stable and ready for production
rdssh1.contoso.com
rdssh2.contoso.com
rdssh3.contoso.com
rdssh4.contoso.com
rdssh5.contoso.com
0
Vincent DAuthor Commented:
almost forgot... :-)

applied profile hotfix from Microsoft that updates 2012 R2 profile with *.V4 suffix to distinguish different profile versions from each other

Windows 7/2008 R2 = V2
Windows 8/2012 = V3
Windows 8.1/2012 R2 = V4

Not using GPOs yet so manually updated AD account properties for remote desktop profiles to point to new v4 profiles share. not all accounts using this so their profile would be local to terminal server. None the less profile share server and all servers in term farm are VMware VMs connected to 10Gbps switching. All test accounts nothing on desktop or in profile except what is created by default.
0
Henrik JohanssonSystems engineerCommented:
Local profiles should be avoided when having multiple RDSH in farm. Even if having single server, RDSH should use RD profile in combination with GPO setting deleting roaming profiles at logoff to keep the server clean and user profiles is complete unloaded. If the user's profile folder by some reason can't be used, it will be created a new folder username.domain. If that can't be used, it will be added a numeric value as extension username.domain.001 etc
If configuring the profile path in the user account properties in AD, it will affect logons to all computers. Better to use a GPO linked to he OU containing the RDSH computer accounts pointing out the parent path for where RD roaming profiles are stored.
The GPO setting is described in https://technet.microsoft.com/en-us/library/cc742820.aspx
Roaming profiles need to be combined with folder redirection to optimize the size of data copied during logon/logoff. If you don't want the folder redirection to apply at users normal desktop loogon, enable loopback processing on the RDSH computers and link the GPO containing folder redirection to the RDSH OU. If not enabling loopback processing, GPOs containing user settings need to be linked to OU structurure containing user objects.

As the issue is intermittent, is the profile loaded correctly? Does the C:\users folder on the RDSH contain a single folder for each user or begin to have username.domain username.domain.001 etc due to new profile folder created either through romaing location or local default user? If profile is generated from defaul user, check the size of that folder.
0
Vincent DAuthor Commented:
All profiles show 0MB/0KB on each SH server. On V4 profile share all accounts being tested show approx. 1MB in size
0
Vincent DAuthor Commented:
all profiles show "first name.last name" for profile name and their is one folder per user on each term server/SH as well as in V4 Profile share
0
joharderCommented:
It sounds like user profiles are working correctly, so we need to look elsewhere.

Are there any GPOs, including login scripts, that map printers, drives, or other resources?  What about peripherals?
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Vincent DAuthor Commented:
There is nothing running in login that isn't also on 2008 r2 rds farm which has no slow login with black screen. Issue only shows up on brand new test 2012 r2 rds farm
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.