[THIN] Re: Advice on Thin Client published desktops
- From: "Greg Reese" <gareese@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Wed, 9 Jan 2008 08:19:33 -0600
just choose published content and point it to the exe. Content can be
anything. You can also make a folder of shortcuts and point the content
path to the .lnk files. This is one way to mix 32 bit with 64 bit and have
things launch right regardless of whether a user hits a 32 bit server or 64
bit server. The published content path points to something like
c:\shortcuts\word.lnk and that lnk file points to either "program
files\office\winword.exe" or "program files (x86)\office\winword.exe"
depending on the which server it hits. To the users, it doesn't matter, they
login to a published desktop and click the pnagent generated icon they see.
For you on the back end, all you have to manage is what servers host the
desktop. Everything else falls into place without anymore work.
The catch is what I mentioned in my other post, users have to ALWAYS use the
published desktop and launch things from there.
On Jan 8, 2008 9:06 PM, Matt Kosht <matt.kosht@xxxxxxxxx> wrote:
> On Jan 8, 2008 10:05 PM, Matt Kosht <matt.kosht@xxxxxxxxx> wrote:
> >
> > On Jan 8, 2008 9:55 PM, Greg Reese <gareese@xxxxxxxxx> wrote:
> > > i don't know about preferred but using the pnagent to fill in the apps
> on a
> > > published desktop is really easy and powerful. I have been running
> farms
> > > that way since the agent first came out about five (six?) years ago
> (wow!
> > > has it been that long!?!?). It's even easier if you publish the apps
> as
> > > content rather than apps. Then you don't have to assign and unassign
> > > servers to apps every time you take a server on or offline. The
> downside to
> > > that is that the the apps then ONLY work in the published desktop so
> your
> > > users in WI will need to know that. I hide them in WI so users only
> see the
> > > desktop.
> > >
> > > Greg
> > >
> > >
> > >
> > > On Jan 8, 2008 7:56 PM, Matt Kosht <matt.kosht@xxxxxxxxx> wrote:
> > > >
> > > >
> > > >
> > > > After running nearly 8 yrs on Novell infrastructure my company is
> > > > beginning to migrate over to Microsoft equivalents. On our PS4.0farm
> > > > we run a mix of published apps using PNAgent (in the office) and WI
> > > > 4.6 (remote access)to get them out to the user population. We also
> > > > have piloted 20 users on Neoware e140's (linux) thin clients getting
> a
> > > > published desktop session. We are looking to add more of these over
> > > > the next year and this may become the dominant client of choice. In
> > > > the Novell/Citrix world we used Zenworks to build/customize the user
> > > > desktop (showing them the apps they were authorized to, setting
> policy
> > > > restrictions, etc). In the Microsoft world we have a working
> solution
> > > > of using GPO's and scripting to create the links on the desktop
> > > > dynamically based on group memberships (if member of appA then
> create
> > > > appA link). This script seems a bit clunky to me and could be hard
> to
> > > > manage (we have about 30 unique apps in the farm). I have read some
> > > > on this and found some admins use PNAgent inside the published
> desktop
> > > > to build shortcuts, start menu, etc. Is this the preferred solution
> > > > to this challenge? Are there other methods/tools I should consider?
> > > > Soliciting advice from the Thin think tank.
> > > > ************************************************
> > > > For Archives, RSS, to Unsubscribe, Subscribe or
> > > > set Digest or Vacation mode use the below link:
> > > > //www.freelists.org/list/thin
> > > > ************************************************
> > > >
> > >
> > >
> >
>
> When you publish content doesn't it have to be a web page or a
> document or other non executable? How would you publish Word as
> content for example?
> ************************************************
> For Archives, RSS, to Unsubscribe, Subscribe or
> set Digest or Vacation mode use the below link:
> //www.freelists.org/list/thin
> ************************************************
>
Other related posts:
