[THIN] Re: Publishing ica files with Nfuse
- From: "Ron Oglesby" <roglesby@xxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Tue, 21 Oct 2003 12:57:54 -0500
No it was published as content because only a few people got it. The
content just pointed to the URL.
Ron Oglesby
Senior Technical Architect
RapidApp
Office 312.372.7188
Mobile 815.325.7618
email roglesby@xxxxxxxxxxxx
-----Original Message-----
From: M [mailto:mathras@xxxxxxxxxxxxxxxx]
Sent: Tuesday, October 21, 2003 12:58 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Publishing ica files with Nfuse
Thanks for the reply Ron.
Did you publish the .ica file as content though ? or did you just point
the users directly to the ica file ?
regards
----- Original Message -----
From: Ron Oglesby <mailto:roglesby@xxxxxxxxxxxx>
To: thin@xxxxxxxxxxxxx
Sent: Tuesday, October 21, 2003 6:43 PM
Subject: [THIN] Re: Publishing ica files with Nfuse
I have done this for a customer that did the same thing. I
actually put the ICA file in a directory on my webserver and referenced
it as http://webserver/citrix/balh.ica
Worked fine.
Ron Oglesby
Senior Technical Architect
RapidApp
Office 312.372.7188
Mobile 815.325.7618
email roglesby@xxxxxxxxxxxx
-----Original Message-----
From: M [mailto:mathras@xxxxxxxxxxxxxxxx]
Sent: Tuesday, October 21, 2003 12:43 PM
To: Thin@xxxxxxxxxxxxx
Subject: [THIN] Publishing ica files with Nfuse
This may sound like a daft question but is anyone publishing
.ica files as content and using them with Nfuse ?
We have a server farm that users have access to and a few users
have access to another Farm ( belonging to another company ) over a
Leased Line.
We admins have no access to the other farm and have manually
created .ica files to connect to the published applications on the other
farm.
We are now pushing out Nfuse globally but access to the other
Farm is a stumbling block.
The Farms are completely seperate and the user account details
are completely different from our Farm.
Any ideas would be appreciated.
regards
Other related posts:
