Discussion Locked

Domain vs local logins on laptops

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

How do I manage logins for W2K laptop users? How do I create a uniform set of 'private' settings for my users (location of My Documents, Outlook Express address book, etc.) who sometimes log into the domain and other times log in locally to their machines? I have 5 sales guys who travel 50-75%and I'm not sure how to handle it.
If I want My Documents pointing to a network location when logged in to the domain, what happens when I log in locally when I'm not connected?

I'm confused.

2 replies

by lordinfidel

You can consider this either a feature or a security risk.

But on a 2K machine, as long as you have logged into it sucessfully into the domain.

You can disconnect the machine from the network, boot it up, and log into "the domain" using the valid username and password that previously logged into the machine.

Now obviously if I am user B and I'm trying to log into user A's laptop. And that laptop is offline/not connected to the lan, and I was not the person who was last logged in. I will not be able to log in until the system can talk to the DC.

Like I said, you can consider this a feature or a security risk, which ever. It appears that 2K caches the U/P of the last logged on user locally.

This also works for locking the wkstn. You don't have to be connected to unlock the machine. This was similiar to NT4.

by lordinfidel

It does not work.

You can log in first using the domain account. This will create the profile.

Log back on as local/domain admin. Create a local account on the machine. Set the local accounts profile to point to the domain account profile on that machine.

You must give rights to those folders to the local user.

This discussion is closed to new replies.