Support Case MS Azure
Case:
User s are disconnected from RDS. The session is disconnected, and reconnected. This happens ca. 15 times during a workday. (per user)
Case details:
Last year we started to use VM’s at the MS Azure environment. We created a W2008r2 domain controller, and 2 Terminal servers (W2012). This worked properly. We only experienced disconnections when a session was minimalized. But then we created a new environment because we had a new azure subscription. Since then we are suffering from disconnected sessions.
We tried to tweak our environment, by optimizing the keep-alive settings and the tcp-ip settings. This improved slightly the experience, but the problem remains. Further research came up with a number of errors in the event viewer.
This is the main error:
Log Name: Microsoft-Windows-TerminalServices-RemoteConnectionManager/Operational Source: Microsoft-Windows-TerminalServices-RemoteConnectionManager Date: 22-01-2013 16:28:11 Event ID: 1152 Task Category: None Level: Error Keywords: User: SYSTEM Computer: TS01.companycloud.local Description: Failed to create KVP sessions string. Error Code 0x8007007A Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System> <Provider Name="Microsoft-Windows-TerminalServices-RemoteConnectionManager" Guid="{C76BAA63-AE81-421C-B425-340B4B24157F}" /> <EventID>1152</EventID> <Version>0</Version> <Level>2</Level><Task>0</Task> <Opcode>0</Opcode> <Keywords>0x1000000000000000</Keywords> <TimeCreated SystemTime="2013-01-22T15:28:11.970697100Z" /> <EventRecordID>55796</EventRecordID> <Correlation /><Execution ProcessID="1004" ThreadID="1008" /> <Channel>Microsoft-Windows-TerminalServices-RemoteConnectionManager/Operational</Channel> <Computer>TS01.companycloud.local</Computer> <Security UserID="S-1-5-18" /> </System> <UserData> <EventXML xmlns="Event_NS"> <Param1>2147942522</Param1> </EventXML> </UserData> </Event>
Then we see a user disconnected, en then we see in the event viewer that the session has been rebuild. The user experience a ‘freeze’, black screen and then the message that the session is disconnected. The session automatically reconnect and the user can work further from the point where the session has been frozen.
After more research, we found more errors, and we pointed to a Hyper-V problem. Foregoing error is a error that reports a problem between the Hyper-V host and the guest.
We also created a Windows 2008 server in the same network. And the problems are appear also. The main error on the W2008 server is:
Log Name: System
Source: TermDD
Date: 24-01-2013 08:38:19
Event ID: 50
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: COMPANY-TS03.companycloud.local
Description:
The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="TermDD" />
<EventID Qualifiers="49162">50</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-01-24T08:38:19.410777900Z" />
<EventRecordID>6049</EventRecordID>
<Channel>System</Channel>
<Computer>COMPANY-TS03.companycloud.local</Computer>
<Security />
</System>
<EventData>
<Data>\Device\Termdd</Data>
<Data>X.224</Data>
<Binary>00050800020030000000000032000AC00000000032000AC0000000000000000000000000000000002200000000000000</Binary>
</EventData>
</Event>
Together with a partner of us, we tried to find the cause of this errors. We created on another Azure subscription a similar environment. The fact is that the problems not exist on the other environment. We also concluded, that when we stay within the Virtual Network of Azure, the connection remains!
Our conclusion is that our problems can be ascribed to a defect in the Windows Azure Virtual Network, or in the Hyper-V solution from Windows Azure. We think that, when we rebuild our complete environment ( approximately 4 days of work) and create a new network (or even a new subscription) the problem is solved.
An resume of our environment:
- Company-dc01 (Windows Server 2012)
- Primary Domain Controller
- Fileserver
- Company-dc02 (Windows Server 2012)
- Secondary domain controller
- Company-ws01 (Windows Server 2012)
- RD Gateway
- RD Web Access
- RD Licensing
- RD connection broker
- Company-ts01 (Windows Server 2012)
- RD Session host
- Company-ts02 (Windows Server 2012)
- RD Session host
- Company-ts03 (Windows Server 2008)
- RD Session host