[THIN] Re: There goes the Neighborhood? what the?

  • From: "Steve Greenberg" <steveg@xxxxxxxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx
  • Date: Wed, 14 Jan 2009 01:54:22 +0000

That's a good point, in reality PN is more like an ICA file creator with a GUI.

Although in the blog it almost sounded like direct ICA may not be supported on 
the future platform.....


Steve Greenberg


-

Sent via BlackBerry by AT&T

-----Original Message-----
From: "Greg Reese" <gareese@xxxxxxxxx>

Date: Tue, 13 Jan 2009 19:27:21 
To: <thin@xxxxxxxxxxxxx>
Subject: [THIN] Re: There goes the Neighborhood? what the?


but you don't need the full pn client to launch an ICA file or connect to
something.  We are in the habit of doing so because it is easy, but there
are other ways to connect.

On Tue, Jan 13, 2009 at 5:10 PM, Holley, Mark <Holley@xxxxxxx> wrote:

>  Good points Joe….one offs are harder to manage.
>
> Correct me if I am wrong (and I may be) but you can't automatically push an
> Icon to the desktop from WI can you?
>
> The old days of full desktops can not be totally gone yet…How do you do it
> now? I guess desktop manager does this a different way?
>
> I used to create a custom connection on the thin client that auto launched
> for users to get to the server desktop. Worked great…and kept everything
> neatly on the server side.
>
>
>
> Mark Holley
> Technology Engineering & Deployment Group
> City of Jacksonville
> Holley@xxxxxxx
> 904-255-8133
>   ------------------------------
>
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Steve Greenberg
> *Sent:* Tuesday, January 13, 2009 1:47 PM
>
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] Re: There goes the Neighborhood? what the?
>
>
>
> That's a good point, if you need a custom connection you can always just
> create it in the console and publish it via WI!
>
>
>
>
>
> *Steve Greenberg*
>
> Thin Client Computing
>
> 34522 N. Scottsdale Rd D8453
>
> Scottsdale, AZ 85266
>
> *(602) 432-8649*
>
> www.thinclient.net
>
> *steveg@xxxxxxxxxxxxxx*
>
>
>  ------------------------------
>
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Joe Shonk
> *Sent:* Tuesday, January 13, 2009 11:27 AM
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] Re: There goes the Neighborhood? what the?
>
>
>
> The problem with PN is the configuration and management of it is soooo
> decentralized that Admins become paralyzed when it comes time to
> upgrade/migrate their farms.  Now they have to consider all the one off
> configurations and send some out to fix them.
>
> If you don't want to use PNA (because of file associations) then simply use
> WI.  WI in a sense replace PN,  the only thing you lose is the ability to
> create custom connects (which is not necessarily a bad thing).  For
> troubleshooting purposes,  you could always create a custom .ica or use a
> third-party tool.
>
> FYI, with WI you can create shortcuts to the applications on the
> desktop/startmenu
>
> Joe
>
>
>
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Holley, Mark
> *Sent:* Tuesday, January 13, 2009 10:31 AM
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] Re: There goes the Neighborhood? what the?
>
>
>
> 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 ICA" connections?  Does no
> one use this? Sometimes a nice way to cover the "one off" customer is to
> create a client side setting.
>
> 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 Jacksonville
> Holley@xxxxxxx
> 904-255-8133
>   ------------------------------
>
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Chad Schneider (IT)
> *Sent:* Tuesday, January 13, 2009 11:00 AM
> *To:* thin@xxxxxxxxxxxxx
> *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@xxxxxxxxxxxxxxxx> 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?
>

Other related posts: