[THIN] Re: CE thins and nFuse

  • From: "Greg Reese" <GReese@xxxxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Tue, 23 Sep 2003 12:06:45 -0400

some of the Linux clients do have an integrated Netscape browser.  But you 
really get into the higher end models.  I have not tried it myself.  The 
Internet Explorer browser that you can embed in to the CE devices is pretty 
weak at best though.  You would be better off to publish IE like Ron suggested 
and make an ICA connection to that.  That will also let you buy a lower end 
terminal since all it will do is connect to one published app.  Everything else 
will be handled from there.
 
One feature to think about with this.  Some thin clients have an option to both 
Autostart an ICA connection and to Automatically restart connections.
 
If you have a useless account connecting to the published IE which is the nFuse 
logon.  You can turn on the automatically restart option so that no matter what 
happens, all the user ever sees is the nFuse logon.  If they walk away from it 
and they get disconnected or whatever, the terminal will then relaunch and put 
them back at the nFuse login screen for them or the next person to sign into.
 
Greg

-----Original Message-----
From: Higgins, Bob [mailto:BHiggins@xxxxxxxxxxxxxx]
Sent: Tuesday, September 23, 2003 11:50 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: CE thins and nFuse


Thanks Greg,
 
We tried a linux device, but need an integrated browser to achieve the nfuse 
evnvironment that we're after. Any thoughts?
 
Bob

-----Original Message-----
From: Greg Reese [mailto:GReese@xxxxxxxxxxxxxxxx] 
Sent: September 23, 2003 9:36 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: CE thins and nFuse


to chime in on this.  We run a pure thin client environment here.  Mostly CE 
based Winterms, Linux thin clients, and a bunch of CE tablets.
 
the CE devices we have both from Wyse and Boundless (running Neoware software) 
are a little skittish.  The flash gets corrupted too easily and they run into 
memory problems if you try and do too much with them.
 
There is very little you can do with a CE device that you can't do with a Linux 
device.  All we buy now are Linux based thin clients and they are very solid.  
They are also cheaper.  Depending on what you buy, most of them can be upgraded 
to CE if you find you don't like the Linux.  In my budget request this year was 
the funds to replace all our CE thin clients with Linux thin clients.  I think 
it will get approved because the CE devices have been a giant pain.
 
I only have 200 devices and I do run a full desktop that is locked down solid 
and I use mandatory profiles.  I have found that the Linux based thin clients 
work best.
 
But that's me. There are a lot of people on this list who will probably 
disagree.  Try out some units and see for yourself.
 
Greg 

-----Original Message-----
From: Ron Oglesby [mailto:roglesby@xxxxxxxxxxxx]
Sent: Tuesday, September 23, 2003 11:24 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: CE thins and nFuse



I have done this (but not for a thousand users) I am also planning one right 
now for about 600 or so to access this way.  

 

Any. The concept with NFuse is simple. Have the CE client launch to anonymous 
NFuse (published IE). Then the users can sign into that and launch applications.

Alternatively you can have a STRIPPED down desktop with a taskbar.  From within 
the desktop they can use NFuse. BUT I have found that often times it is better 
to give users the ability to run all the apps right from that desktop (even 
using the passthrough client to launch apps from other silos)

 

But to address your individual questions:

 

Is it possible to achieve a user bombproof environment with nFuse (Web 
Interface) on CE devices and still maintain the taskbar? 

Maintaining a taskbar mean giving them a desktop (even if stripped) Bomb proof 
would mean mandatory profiles with maybe a flex or hybrid mixed in. That is 
about as close to bomb proof as you can get. BUT any desktop is a hole, never 
forget that.

What are the pitfalls of CE devices, other than the inability to have any local 
apps?. 

Not anything you would want to run.... And generally these devices don't have 
enough CE to do anything other than connect to a server.

How was your experience with implementation? 

Been good in most cases. I don't like giving the user a desktop if I don't have 
to. If I do I give them mandatory profiles. If they gripe about saving settings 
I then add in the flex or hybrid profile kit so the admins determine what is 
saved and not the user.

How do users like the environment? 

Just fine once they get done gripping. You have to find a balance between 
giving them anything they want and not giving them anything. I found that these 
are easiest when moving them from older slower machines.

Any other comments? 

Not now.

 

 

Ron Oglesby

Senior Technical Architect

 

RapidApp

Office 312.372.7188

Mobile 815.325.7618

email roglesby@xxxxxxxxxxxx

 

-----Original Message-----
From: Higgins, Bob [mailto:BHiggins@xxxxxxxxxxxxxx] 
Sent: Tuesday, September 23, 2003 9:44 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] CE thins and nFuse

 

Hi All, 

We are looking for feedback from larger environments (1000+ devices) that have 
done nFuse on CE for their core application delivery. We have achieved a 
satisfactory, end user secured environment on a stripped down w2k shell on 
PC's, but it took some add ins (PWB, etc.) to achieve the lock down we desired, 
but still maintain the necessary functionality (taskbar, etc.). 

Is it possible to achieve a user bombproof environment with nFuse (Web 
Interface) on CE devices and still maintain the taskbar? 

What are the pitfalls of CE devices, other than the inability to have any local 
apps?. 

How was your experience with implementation? 

How do users like the environment? 

Any other comments? 

 

Your feedback is appreciated! 

Bob Higgins, MCSE 
Information Systems Server Administrator 
Chinook Health Region 
960 19th Street South 
Lethbridge, Alberta 
T1J 1W5 
www.chr.ab.ca 
Phone: (403) 382-6338 
Fax: (403) 382 6046 
E-mail: bhiggins@xxxxxxxxx 

Other related posts: