I worry that we will lose versatility. In a complex environment the CPN can be used in a whole slew of different ways. Heck I have even used to create thin PCs until their hardware dies by making the citrix client the shell.
What if “every” user doesn’t work in your Citrix environment the same way? For example…I have one department that uses the PNagent for all apps…then I have others that use the CPN for “one” app. However they all use Web interface from home and require Office. If I install the PNagnet on the local pcs of that department that only runs one app…well…all of a sudden Pnagent reassociates those peoples local files to run from Citrix.
I could create multiple office icons that change the associations but to me it is way easier to publish office globally and use the pnagent for dedicated departments only.
There are more examples…. What about the “custom
I know that without the versatility of CPN that some customers would never have agreed to run an app on Citrix at all.
I may be speaking from an antique view point and need to move on…who knows. I need more ways to run Citrix not less.
Mark Holley
Technology Engineering & Deployment Group
City of
Holley@coj.net
904-255-8133
From: thin-bounce@freelists.org [mailto:thin-bounce@freelists.org] On Behalf Of Chad Schneider (IT)
Sent: Tuesday, January 13, 2009 11:00 AM
To:
Subject: [THIN] Re: There goes the Neighborhood? what the?
If configured properly, it can then use the failover/secondary WI server listed.
>>> On 1/13/2009 at 9:38 AM, <bcoffman@infofromdata.com> wrote:
>i am surprised this has taken this long to happen. I stopped using PN back when the PNAgent came out. The few times I have used it since then, I have found it annoying and cumbersome. Good Riddance.
It looks like this service is dependent on Web Interface - I wonder what it does if WI is down?
No comments:
Post a Comment