"Please wait for the Local Session Manager..." is displayed forever....

-

hi there..

 

i running problem windows 2008 ctp june, running windows 2008 beta 3 without problems in machine.. until yesterday decided 'upgrade' windows 2008 ctp, process goes smoothly, , needed reinstall audio driver... rest works fine, except terminal services...

 

anyway, restarted machine without problem before solve terminal services issues (the remote app not working), decided remove terminal services , reinstall again, unable run remote app... anyway turn off machine after it... , today machine takes 1 hour in "applying group policy..." , after displays "please wait local session manager..."...   after 2 hours see machine still same message decided reboot it, , works fine (less 3 min. go logon screen) ....

 

but knows problem was, or saw similar behavior?... never run problem in windows 2008 beta 3... saw in windows 2008 ctp.....

 

miklos

 

p.s. fyi, problem of ts remote app addressing in post...

this started happening me on (4) of 2008 terminal server boxes. 10-15 minutes displays:
"please wait local session manager".

-disabled auto tuning didn't help
-restarted session broker server didn't help.

is "local session manager" service can restarted? event logs no help! domain controllers don't show problems.

anyone else have problem?

i restart servers weekend=(


Windows Server  >  Setup Deployment



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more