2012년 5월 9일 수요일 오후 1:49
In spite of all threads related to this topic, I have not find any way to fix my issue.
- 2 RDWA in load-balancing (least connection mode) under hardware F5 load-balancing
- 1 RD Connection broker
- 2 RDSH in farm and under hardware F5 load-balancing. Farm name is DNS alias mapping on F5 virtual IP.
I have followed these link http://technet.microsoft.com/en-us/library/cc753891.aspx and this one http://technet.microsoft.com/en-us/library/cc771383.aspx in order to join both RDSH in farm.
I have not success to add RDSH farm name as RemoteApp source on RDCB. On this step, I have the following error “ Error in the WMI interface RDSH_Farm_FQDN. Check that the machine is running and connected to the network. If the problem persists, reboot the machine. ” and due to this error I’m not able to see the list of RemoteApp on RDWA. I have rebbot RDSH server, re-add each server on apprpriate group and nothing changes.
The following features are already set
- No firewall is running on any of servers
- RDCB is in TS WEB group on both RDSH
- Both RDSH are in RDCB Session Broker Group
- Both RDWA are on TS Web Group on RDSH and RDCB
For information when RDSH are not in farm mode all is working well. I mean I was able to view RemoteApp list on both RDWA, I was able to launch and use application from RDWA.
Desktop connection and load balancing using farm name working well.
I think that I have missed something when configure RDSH in farm mode.
Thanks for your help
2012년 6월 5일 화요일 오전 7:41Anyone?
2012년 6월 21일 목요일 오후 5:06
Have you looked at F5's documentation on this?
It's detailed enough not to repeat here.
2012년 6월 22일 금요일 오후 1:28
I have set F5 parameters as describe in this document and the have the same problem when adding RDSH dns farm name as remoteapp source on RDCB.
error is : "Unable to connect to myrshfarm.xxx.net . Do you still want to add myrshfarm.xxx.netmyrshfarm.xxx.net as a RemoteApp source"
2012년 6월 22일 금요일 오후 5:33중재자
The RDCB needs to be able to connect to the RDSH servers (only one each time) to query the list of RemoteApps. It does this using RPC. For example, normally this would mean the RDCB would communicate with the RDSH over tcp port 135 first and then communicate over the dynamic tcp port that wmi is listening on.
Please make sure that the FQDN that you use as a RemoteApp source for RDCB will resolve to the ip address of your RDSH servers and that it will be able to communicate on the necessary tcp ports without interference. I suspect that the way you have it configured now the RDCB is trying to making the RPC calls to the RDSH server through your F5 and it is not getting through properly.
I am unsure how you have things configured, but if the only way the RDCB broker has to communicate with your RDSH servers is through your F5 then perhaps you should configure WMI to run in its own process and use a static tcp port. Once you have the static port set you could configure your F5 appropriately. Please see this document: