Same msi, different UI

[WillShakespeare]

Having a strange one...

I have installed a Citrix server on a separate trusted domain, and users from our 10.4.4.x subnet can access it by installing ica32pkg.msi from Citrix.

However, when we try to install on exactly the same machine type and OS and SP2 in subnet 10.4.5.x (exactly the same msi) we get different settings, and while I can finally connect to the server, it doesn't work properly and tries to open a desktop, rather than a folder with the published apps in it.

Any ideas?

Any more info needed to help?

Will

 

[WillShakespeare]

Also, on the machines that work, the initial icon in the top left corner of the Program Neighborhood is called "Application Set Manager".

However, on the machines we are having trouble with, the icon is called: "Add ICA Connection"

I am installing the same app, but the UI is all different! For example, under Settings on the machines taht work you can choose Local Area Network, etc., but on the other machines, this option is not available, and it defaults to ica and HTTP/HTTPS

On the machines that work, the default is TCP/IP and (Auto-Locate)

Thanks in advance,

Will

 

[Titleist]

WillShakespeare,

I'm assuming your Citrix Farm is on the 10.4.4.x subnet...Your users on that subnet, when launching Program Neighborhood for the first are broadcasting for the Farm and the Cirix servers are responding to that request. Your users on the 10.4.5.x will do the same but your router between the 2 subnets will not pass broadcasts so you have to configure them manually. Alternatively, you can push out a preconfigured Citrix client to the users on the 10.4.5.x subnet or allow ica broadcasts on your router. Check the Citrix site or Help for preconfiguring a Citrix client.

HTH,
John

 

[WillShakespeare]

Thanks John,

Fibgure dit out. Because the auto-locate was not finding the server directly, the first view in the UI was for ICA connections. We accidentally clicked UP in the top left corner, and I was able to make a manual connection to the IP address. It all worked okay, though it was slow (the other subnet is in a different country).

So in the end we decided to install on our Terminal Server the Citrix xlient, as the TS is on the same subnet and this works great!

Thanks for the reply!

Will