ICA Browser question

[30362]

I currently have 5 MF1.8SP3 servers participating in load balancing, 4 of the servers have a published app and the 5th is strictly an ICA browse master. I have all of the other 4 servers except 1 set to DO NOT PARTICIPATE.

Now for my question:

I have no problem with ICA clients on my local network (where the MF servers are located) seeing the published applications hosted by the farm, however the remote sites cannot see these and therefore I must hard code the IP address of the ICA browse master in the ICA client before a published app list is displayed. Clearly this creates a single-point of failure if that server goes down and the IP is inaccessable.

Is the best choice to put an ICA browser at each remote site so that the ICA browse list is local to each subnet and I can stop hard-coding the IP in the clients or is there a better way?

Thanks in advance...

 

[Jontmke]

Well, this is really a DNS issue. If they are out in the world, there computer needs some way to find your servers. Either they use a name, or an IP. The name of your servers would then have to registered in the

http://WWW DNS

system if you want them to use names instead of IP.

JON

 

[30362]

I understand that DNS needs to be registered either on the PC or at that location, what I am asking is if there is a way that I can have Metaframe servers serving a published application and clients at remote locations that can create an ICA session and browse the published apps without having to manually put an IP or server name in the address list.

Any client at our central site can create a new ICA connection and see the published apps available, but clients at remote sites cannot see any published applications until I put the IP address or name of one of the servers in the address list box.

 

[payneb]

You will have to type in the ICA browser. I would set at least 3 servers to participate incase #1 goes down. Also, add all the address of the 3 servers you choose to have participate. This gives you a little more redundancy.

We have also made a custom ICA client install and put them in the config files so we don't have to type them in each time. This helps quite a bit.

 

[30362]

Would an ICA browser at each site eliminate the need to modify the client settings?