In my windows server 2008 R2 OS in the Event Viewer there is an error pertains as Terminal Services SessionBroker warning ID 898 states-(RD Connection Broker service failed to start. HRESULT = 0x88130013.) - System - Provider [ Name] Microsoft-Windows-TerminalServices-SessionBroker [ Guid] {D1737620-6A25-4BEF-B07B-AAC3DF44EFC9} EventID 898 Version 0 Level 3 Task 100 Opcode 10 Keywords 0x4000000000000000 - TimeCreated [ SystemTime] 2012-07-02T13:58:01.869270100Z EventRecordID 187 Correlation - Execution [ ProcessID] 2800 [ ThreadID] 11060 Channel Microsoft-Windows-TerminalServices-SessionBroker/Admin Computer WIN-6JQT8F105TE.mumthaz.contoso.com - Security [ UserID] S-1-5-20 - UserData - EventXML param1 0x88130013 What is this error?And what is the remedy for this error? MumthazMuhsin

I know this is a reasonably old case but really, the solution to "Service failed to start" is to start the service? - what part of *failed* did the author of that document not understand? /rant In my case the issue was the server hosting the Connection Broker service had been dcpromo'd to a domain controller so the previous "Session Broker Computers" local group no longer existed. Solution was to remove the Connection broker role, reboot and then reinstall the role. This populates/ configures the server to use the "Session Directory Computers" domain local group - this fixed the issue and allowed the service to start. Likewise if you dcpromo a DC down to a member server, you will have a similar issue - again, just remove and reinstall and then populate the local Session Broker Computers group. Hope this helps people who find this thread when it happens in the future.http://absoblogginlutely.net