Forum Discussion
GothmanUK_57974
Nimbostratus
Dec 19, 2014Remote Desktop Services Health Monitor Fails after 2008R2 Windows Updates Applied
We currently use the recommended send and receive strings to monitor our Remote Desktop Services Farm as per the document https://www.f5.com/pdf/deployment-guides/f5-microsoft-remote-desktop-services...
Michael_Jenkins
Cirrostratus
Dec 19, 2014I've been having the same problem in my environment. After doing some monitor logging, I determined that there's a new RECV string coming back from the server...
In the UI, the
recv
value should be \x03\x00\x00\x13\x0e\xd0\x00\x00\x124\x00\x02\x09\x08\x00\x02\x00\x00\x00
(in my situation)
The ltm config for the monitor is
ltm monitor tcp MONITOR_NAME {
defaults-from tcp
description "Windows Server 2008 R2 RDS Monitor (recv str is not f5 specified, but found from checking monitor traffic logging)"
destination *:*
interval 30
ip-dscp 0
recv \\x03\\x00\\x00\\x13\\x0e\\xd0\\x00\\x00\\x124\\x00\\x02\\x09\\x08\\x00\\x02\\x00\\x00\\x00
send \\x03\\x00\\x00\\x13\\x0e\\xe0\\x00\\x00\\x00\\x00\\x00\\x01\\x00\\x08\\x00\\x03\\x00\\x00\\x00
time-until-up 0
timeout 91
}
(Note: if it doesn't work, try replacing the double slashes with single slashes. My box has a strange habit of decoding special characters when I save changes)
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects