RDS 2012R2 - Server Manager not connecting to correct Broker

ok, i've got issue server manager on my broker servers not connecting broker service on local server rather trying use broker service on other broker servers, which are listed in server list. @ point may sound strange i'll go through environment first before going further.

i've got four rds environments set up. 2 of environments are configured with one broker server , 2 session hosts each , other 2 environments each configured broker, web access , session host on a single server. licensing role installed on the broker servers larger rds environments broker01 configured primary license server for all rds environments , broker02 server configured secondary.

rds environment 1:
broker01 - web access, broker, license server (primary)
sessionhost01 - session host
sessionhost02 - session host

rds environment 2:
broker02 - web access, broker, license server (secondary)
sessionhost03 - session host
sessionhost04 - session host

rds environment 3:
management01 - broker, web access, session host

rds environment 4:
wms01 - broker, web access, session host

i had license servers installed on domain controllers , working then. when used server manager on broker02 check rds configuration it showed configuration local broker , same other broker servers when logged on those. however, wanted clean domain controllers , run core services on these moved license servers broker01 , broker02 servers instead. i had add broker01 , broker02 server list on of brokers in rds environments license role set on these servers. when issues started.

let's use rds environment 3 example. server list on management01 looks this:
management01
broker01
broker02

however, when try manage rds environment using the server manager on management01 message saying "the following servers in deployment not part of server pool: sessionhost01, sessionhost02". me indicates server manager trying use broker01 broker service , trying manage rds environment set on server. when trying manage rds environment broker01 message need add sessionhost03 , sessionhost04 server list again indicating me it's trying use configuration broker02 rather local broker. seems random may pick of brokers found in server list , try use configuration, haven't played enough sure.

how server manager use local broker services rather other broker may included on server in server list? have limited resources cannot split licensing servers out own servers , i'd rather not use dcs run them. "just" management issue, clients logging on respective environments fine.

regards, mattias

ok , understood moved license servers on broker servers.

when add license servers on collections server manager discovers both connection broker role , licensing role. in case server manager tries connect both environments.

i don't think possible split management way referring 2 different connection brokers plus collections.

that possible if used 1 of 2 licensing servers , 1 active connection broker each , add second in case first connection broker + ls server goes down.

Windows Server  >  Remote Desktop Services (Terminal Services)