Rebooting RDSH Server in Farm during office hours

hello,

we have rds farm consisting of 10 rdsh servers , 2 rdcb servers (in cluster).  initial farm connection - using cisco global site selector (gss) hardware load balancer.  gss polls rdsh servers every 4 secounds on tcp port 3389.  if gss unable poll server - removes list of available rdsh servers when requests dns resolution.

the issue having if we reboot server in farm (which has no-one connected) during day maintenance reasons - there period when new users try connect (just after server rebooted) presented blue logon screen welcome message - , logon never completes.  can assume gss has not yet registered 1 of servers in farm has gone offline , such new users still been directed it.

what can here?  less resilient method of doing initial connection use dns roundrobin - dont see how work in better way.

so - can comment on if normal behaviour sees?  possible reboot farm member during office hours , not have issue?

thanks in advance.

hi,

if rdsh server serving redirector (whether dedicated or not) initial connections, must take steps users not attempt connect before restarting.  example, in case remove cisco gss cisco not give server's ip address out initial connections.  in addition putting in drain mode , waiting users log off.

a preferred alternative set rdsh servers dedicated farm redirectors , have cisco refer initial connections redirector servers.  in way restart regular farm member after first putting drain mode , waiting users log off.  can configure rdsh server dedicated farm redirector in rdsh configuration (tsconfig.msc).

naturally see issue if restarted 1 of dedicated redirectors without first making sure users not attempt connect it.

-tp

Windows Server  >  Remote Desktop Services (Terminal Services)