We are running XPE thin Clients with WIN XP embedded....(cut down version of XP) at our school which connect through to a Blade Server, and are wanting to add the 25 thin clients to the domain and have users log in with their username and password as they normally would but have it ONLY do authentification.
we dont want the users profile being downloaded onto the machines.
we want the local profile that is embedded into windows to be used.... thus saving space on the limited 500mb of flash memory it boots on. At the moment the machine is off the network and the machine auto logs in, then if the user wants to do anything they must log authenticate several times etc
is this possible.
the reason we want to do this is so that the thin clients can be used on the domain for accessing the internet, library lookup software and the user can save things from the internet to their network share.
If they want to access everything else on the domain they log into a Blade PC which has everything installed. Just our way of having the Blades free as much as possible.
any ideas?
Just ask if this is too confusing
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Why use Roaming profiles then?
Dont use Thin clients, and it looks like the previous link could be helpful, but here is a different route.....
How to prevent folders from roaming with a profile in Windows Server 2003
http://support.microsoft.c
You can exclude most of the non essential folders, and simply keep the favorites, cookies etc., Home Drives etc..., the items that are most familiar with them when they go to another machine....
mwecomputers link did not help.
the structure of the school is that the students have profiles that they use on the rest of the systems in the school.
The new Thin Clients have been installed into the Library and need to be used both as thinclients accessing the Blade Server and also as stand alone computers if there is no free blades.
we want the user to log in as themselves to gain access to network drives, library lookup share and internet.
The alternative we have been trialing is to have the thin client off the network and then users have to lauthenticate when they want to access the internet, access their share etc.
we dont want to make new profiles just for the Thinclients. we thought that if a policy existed or a tool was available to stop the profile being downloaded while still passing the username and password into the windows logon then it would be great
Thin-clients aren't made to be used as stripped-down, stand alone PCs nor 'authenication boxes'. Yes, they have a bootable operating system, but that's only for giving the user an operating platform to work from and for accessing a terminal environment via the network (i.e. think in terms of 'PXE').
You might want to consider a platform like nComputing (www.ncomputing.com), which surprisingly, was actually designed for schools and libraries through what is a desktop extender platform.
yeah we know that... just thought that there might be some way of tricking the system or cheating a bit.
spose we just want to get as much as we can out of the boxes that we have bought.
The Ncomputing solution looks great but we already have the system installed and cruising in its current state. could be a viable solution in the future maybe.
will leave open a little longer just in case anyone has a brain wave.
thanks Ev one for your quick responses.
I found this article site concerning thin-clients. Perhaps it can shed some light...
http://ts.veranoest.net/ts
no we cant afford to reduce the weight of the folders anymore than they are already. The built in Users in the Embedded XP install have been customised for the thin clients.
I checked out the link - http://ts.veranoest.net/ts
while it confirms what we have, it doesnt shed any more light on our position.
We are running a brand spanking new HP CCI Server. The Thinclients are XPE with WinXP embeded.
They connect to the SAM Manager and Deployment server provided by HP. They use their own HP RDP and SAM software.
Apparently we are number 3 in AUS to get the CCI gear so help is hard to find. we spent 9 hrs on the phone to HP to get the thing running. and they had the same manuals as we had.....
(just a little Background info)
So we have the right gear.... just wanting to see if we can use all its potential at our school
Hi
Here is a possible solution:
Set the policy following policy for the thin clients to enable:
Computer Configuration\Administrati
Then use delprof;
http://www.microsoft.com/d
To delete the profiles either as a schedule task or at restart.
Cheers
Stu
Business Accounts
Answer for Membership
by: mwecomputersPosted on 2008-02-04 at 21:12:48ID: 20820772
See if this link can help:
http://www.freewysemonkeys