Please wait for local session manager

Which of the adhering to retains the indevelopment it's storing as soon as the device power is turned off?
*

Hi men, 

So I have actually customers auto logging in to Server 2008R2 through remote desktop computer. We use one particular application which immediately opens up after the user logs in to the Server. They have actually no other accessibility to the server besides this software program application.

You watching: Please wait for local session manager

I"ve just freshly been coming throughout the issue of this "Please wait for the Local Session Manager". It does end up logging in and also working, yet it takes MUCH longer than prior to. As a matter of truth, I"ve never before checked out it stuck at that certain message before making an easy WindowsDefender upday with Windows Update. Also- I did view a deal with that mentioned inputting CTRL ALT DEL, but individuals are not able to also push CTRL+ALT+DEL throughout their login procedure. 

Any aid would certainly be appreciated ! Thank you! 



DragonsRule

Chris G. wrote:

So I have users auto logging in to Server 2008R2 through remote desktop. We usage one particular application which immediately opens up after the user logs in to the Server. They have no other accessibility to the server besides this software application application.

See more: Windows Installation Media Creation Tool Stuck, Windows 10 Creators Update Installation Stuck

Out of curiosity, have actually you looked at RemoteApp instead? I"m not sure it will deal with the problem you are having actually, but it should certainly streamline points a bit. It sounds choose a perfect fit for your instance.

See more: Error 1603 Google Earth Plug In, How Do I Fix Error 1603



DragonsRule

Chris G. wrote:

So I have customers auto logging in to Server 2008R2 via remote desktop computer. We usage one specific application which instantly opens up after the user logs in to the Server. They have actually no various other accessibility to the server besides this software application application.

Out of curiosity, have you looked at RemoteApp instead? I"m not sure it will settle the issue you are having, yet it have to certainly streamline points a bit. It sounds favor a perfect fit for your situation.

I have actually not, yet I will absolutely look right into that!

The company was handed dvery own to me this means... It"s been messy to say the leastern. But at the minute I am having actually this issue that needs to be solved. Some users are able to login after around 120 secs, yet others are waiting conveniently over 5-7 minutes! I don"t understand what went wrong. Only thing I did was restart the server after a Windows update that had to execute through Windows Defender. 

Thanks for replying so quickly! 


It"s possibly a team policy affecting it. Did anyone make any type of transforms to a group policy recently?

Also the below could be helpful to check out what"s going on as soon as a user logs in --

https://support.microsoft.com/en-us/kb/221833

https://support.microsoft.com/en-us/kb/109626

http://social.technet.microsoft.com/wiki/contents/articles/4506.group-policy-debug-log-settings.aspx


http://discussions.citrix.com/topic/291092-please-wait-for-the-local-session-manager/?p=1619100

Message #14 worked for me. Hopecompletely this will assist others. Very strange. I feel worried that this may take place aacquire, but as of appropriate now- Everypoint is working. 

I did produce a team plan for user login which I then deleted and rebegan server. Same error developed.
ChrisSaint, but thanks! After hours of looking and also attempts, I came throughout the connect over which helped my case. Some customers discussed userclass.dat file deletion and also re-development would work after server restart, but for me it was short article #14 which was deleting the "Users" NTFS permission on file tstemplate.exe in the windowssystem32 folder. Owner of the file is home windows ntTrustedInstaller which needs to initially be changed to a local or domain administrator in order to make the readjust at hand also. After efficiently deleting the "YourDomainUsers" from the perobjectives list, I then changed the NtTrustedInstaller back to Owner. Restarted server- So far, so good! The remote desktop computer connection no much longer takes 2-7 minutes. Now only takes less than 10 seconds on average.