Forcing network login to single user profile

September 22, 2010 at 07:14:31
Specs: Windows XP
I am in the IT staff for my college. We are using Novell as our network manager, using Windows XP Pro, and have run into a small hitch.. Last year we had it so every time a student logged in, it would actually log them in as a local account (so that their profile was not sent to the PC). This year, this is not the case, and it is causing 2-5 minute log in times. No one can find, or remember what was done last year to trick windows, so I have come here to hopefully find support.

See More: Forcing network login to single user profile

Report •


#1
September 22, 2010 at 07:20:21
it would actually log them in as a local account (so that their profile was not sent to the PC

If one logs in to an XP PC with a "local" account, then that profile IS stored on that PC. Open the windows file manager and go to: C:\Documents & Settings and you'll see all local users have an account listed there.

When users go to login, check the login window. Is there a pull down menu at the bottom beside "Log on to"? If there is, the PC itself should be listed there (by it's computer name) as what you're logging on to.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#2
September 22, 2010 at 07:33:03
Excuse me for not being clearer. Every student's account is the exact same as "account x", and deep freeze is on the computers so any changes are not saved. We have them log in and are authenticated by LDAP, and we just want them to use the profile already on the computer, instead of copying it every time.

Report •

#3
September 22, 2010 at 08:15:25
with deep freeze there should only be one profile on the pc. you set the password and have it not expire. you shouldn't need any tweeks beyond that since deep freeze will put everything back to the way you had it.

The 2-3 minute delay is most likely a dns misconfiguration.


Report •

Related Solutions

#4
September 22, 2010 at 08:22:11
Last year there was an actual registry edit that was done to the computers. Computers with the old image take about 30 seconds to log in. The servers, and IP Addresses are all the same. The problem is because it is copying the profile from server to the computer every time, instead of using the profile on the computer. Here..

This is what we want. We want to be able to log in to the computer using our Novell credentials, and every account use the "X" profile. The problem has already been confirmed to be the server copying over profiles every time someone logs in.


Report •

#5
September 22, 2010 at 08:54:07
http://support.microsoft.com/kb/171780

I would suggest you compare the registries of a old and new machine.


Report •

#6
September 22, 2010 at 12:37:26
Last year there was an actual registry edit that was done to the computers.

What registry edit was done? Why was it done?

My experience with Deep Freeze, while limited, tells me everything wanderer said about it is correct. Therefore, if your image is correct when you freeze it, there should be no need for any tweaks or registry hacks.

So I have to wonder, was your image not correct before you deployed it and that's why you had to put in a registry hack? If yes, then you should never have deployed it until it was working correctly. Do you people not lab things out before throwing them into production?

Computers with the old image take about 30 seconds to log in. The servers, and IP Addresses are all the same. The problem is because it is copying the profile from server to the computer every time, instead of using the profile on the computer

Ok, so what changed from the "old image" to the present image? Was it this registry hack maybe?

All I know is, you say it was working (and does work with the "old image") yet it isn't working now. This tells me clearly, somebody changed something. Undo that change and it should work properly once again.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#7
September 22, 2010 at 14:11:02
The registry edit was done to trick windows xp that everytime someone logs in with their Novell login, it logs them in as a default account. I personally did not push or make the image, so I'm not sure about how it was tested.

And what changed was updated software (CS5, CAD and 3D Design). The image wasn't just tweaked from last year, it was completely redone (clean install, load all software, ect).

What we are trying to do is easily done through the network with Active Directory (which we will be upgrading too within 3 months), so what we are looking for now if we cannot find out what was done last year, is at least a stop-gap solution that will hold out until then.

And wanderer, that sounds like a great idea, I will follow up as soon as that is done. Thank you.


Report •


Ask Question