Discussion Locked

Need to ignore roaming profile

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

Hello Everyone,

Is there a way to tell Windows 2000 Pro to ignore roaming profiles?

I have setup two special purpose Win2K workstations in a lab that uses NT 4.0 roaming profiles. The roaming profiles are causing problems. I want the machines to Authenticate off of the NT 4.0 domain, but I want them to create and use local profiles.

I really don't want to create local accounts on these computers if I can help it.

Thanks,

--Dave

5 replies

by abubin

Why do you want to store the profiles locally on a roaming account? That defeats the purpose of romaing profiles itself.

If you want to store the profiles locally, then you can use a normal domain user profile. Those profiles are stored locally on the workstation and will authenticate from the domain controller server.

by dl_caldwell

Hello,

Here's the deal. I run a lab consisting of NT 4 Workstations that network to a NT 4 Server. The lab is used by graduate students who have roaming profiles so their "environment" follows them around the room. Everything worked great.

UNTIL we had to install two new special purpose workstations that run Win2K Pro and specialized engineering software. When a user logs in with their roaming profile the Win2K computers become flaky and unreliable. When I create a local account (that, of course creates a local profile) the computers behave just fine.

I really want the computers to AUTHENTICATE off of the domain so I don't have to administer multiple username/password databases. But I want Win2K Pro to IGNORE the roaming profile for those users.

I have a "fluctuating" handful of users who need to run this specialized software. Unfortunately, most of them already have roaming profiles that are actively used on the rest of the machines. If I take those roaming profiles away the users will whine and cry and complain without mercy.

Yes, I know this is a pain.

Thanks,

by hankschupp

Dave -

In the end, to have your compromise, you have to make one.

Point 1: Problematic Roaming profiles -
Create 4 standard domain user accounts. Do not set them up for roaming - accept the default local profile setting that W2K offers. It will save the profiles locally on the W2K workstation but authenticate as you wish from the Domain (giving them the access to whatever you need to from the domain).

Point 2: Application Data - If saved anywhere local would be inaccessible to them when they logged back into the normal NT4 workstation (An unstated issue but a consideration)

If necessary, to overcome the issue of where they save their files, create a shared directory on the domain file server - They can create subdirectories there and give permission to the subdirectory folder only to their current and usual user account (so no-one else but them could get in there). Then when they log back into their normal workstation they could see the files and move them to their regular data folder.

This is the only real way I can see to make it a bit easier on you.
a. The "fluctuating" users can log in using one of the 4 shared accounts
b. They can move their data to a safe location easily.
c. You only have to add a limited number of accounts. Your only maintenance, if you need the security and trackability, is to change the password between different folks using the accounts. And that ony needs to be a quick "user must change password at next login" situation.

Even if this isn't answer you really needed there should be a couple ideas to build from.

Hank

This discussion is closed to new replies.