JHi Brian,
That sounds like a slightly different issue around licensing. Was the RDS licensing server only running on DC1 and that was down? We have RDS licensing installed on both DCs.
I haven't dug into the logs or tried to repeat the problem as I have to arrange downtime for several hours, probably over a weekend.
The feeling is that something in the RDS stack needs access to one or more of the FSMO roles.
Yes me too - I could find very little on this subject. In fact, resources for Remote Desktop Services is light on the ground generally. As a total aside, we've got a really weird problem from one app saving to redirected drives. Firefox also struggles to download to them. Found zero on that subject either :-(
As my original question has not been answered, I would say this question is still open:
a) make the sproc run faster
b) make the console more tolerant of timeouts.
However, I suspect the answer is "No" to both of them. It's a design flaw in the sproc that causes it to timeout and that requires the developers to change their algorithm. And no, there isn't a magic way to increase the timeout in the console.
This is a well documented and reported flaw in WSUS - there are probably 50+ topics on the same problem:
Add a new classification/products, often Drivers is the (bad) choice
One then ends up with many unapproved updates
It is impossible to view all unapproved updates because all tools (WSUS console, SQL stored procedures and PowerShell) all time out
No they don't - I created another post on the same subject and the consensus is that the app is broken - and has been for a while