I wanted to put this out in the forum to to save someone time and answer the question on the use case of TS-Agents participating in user-id redistribution. In a long trouble-shooting period and TAC engagement, it was confirmed that you cannot redistribute user-id mappings obtained from a Terminal Services (TS) agent.
We have submitted a FR for this capability but until that wins the FR voting battle we have to program the TS-agent on every cluster that is to use a user-id policy from the server.
Down side to this is we have an RDHS environment that will dynamically spin up another RDSH server and use the next available IP in the subnet range when it reaches a user cap (about 10 users per server). This has forced use to program a very large range of TS-agents on each cluster that users would connect through on user-id policies. Not ideal and limited to the hardware capacity.
I am sorry to hear that you had such troubles with TAC - actually for something that could have been answered in about 10 seconds. Mainly because it is documented that redistribution of user-ip-port-mapping data from terminal services agents cannot be redistributed.
Maybe for you an option is a script that runs on these servers when they boot so that they configure themselfes on the firewall - or that they write their own IP addresses/hostnames to a textfile somewhere and when there is a change in this textfile a script runs and updates the firewall configuration. This way the servers don't need direct access to your firewalls.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!