Windows Forum

Ask something
Discussion Locked

NETWARE TO WIN2K AND PROFILES

0 helpful
6 replies

by tommymcbrayer

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Currently I have 2 netware 5 servers and several WIN2K servers and the PDC with AD. We have been running a mixed environment for several months and it is now time to make the switch. Currently all of my users authenticate to NDS and the only resources on the WIN2K servers they are accessing is via Citrix. Currently all of my users already have a user account in AD. The only thing I will be migrating from Netware is data from the file servers and I will be setting up the printers manually. I have about 250 NT 4.0 and WIN2K workstations and during testing last night the following issue came up. When a user doesn't authenticate to NDS and logs into the Domain a new profile is created on the local machine. There current profile is theiruser name ex jdoe. When they login to the Domain the new profile is jdoe.000. Is there any way for this not to happen? It will be very time consuming to copy all the profiles to the .000. This occurs even if the workstation was already a member of the Domain.

6 replies

by curlergirl

You don't say what OS your workstations are running. If they are running any version of NT (i.e., NT 4.0, Win2K or XP), the easiest thing to do would be to set them up with roaming profiles. (You can use roaming profiles with Win9x/Me but it's a bit more difficult to set up.) You do this by creating a shared Profiles folder on one of your Win2K servers, copy their local profiles to that location (or copy a default standard profile), and then set the user accounts to use roaming profiles. There's a white paper available from Microsoft called "Step-by-Step Guide to User Data and User Settings" that describes how to implement roaming profiles. Once you have the users' profiles set to "roam", then even if a new profile is created locally itwill be a copy of the roaming profile, so you don't have to worry about their losing their settings. Hope this helps!

by banyanman

Sorry, but no matter what you do, when you do a migration like this, from local machine accounts to a domain account for user logons, the machine is always going to add another profile with a .000 or .domain suffix. The machine does this because even though the accounts are identical in name, their identifiers are different, i.e. SIDS or GUIDS, depending on the platform. What you can do however is utilize some automatic profile migration scripts to make the administration much easier. Here is a link to a sample. Be sure to remove any spaces in the URL and good luck with your migration. http://www.winnetmag.com/Articles/Index.cfm?ArticleID=4899&pg=2

by tommymcbrayer

I understand all about the sids and guids and a user getting a jdoe.000 for the domain on a nt box or a jdoe.domain on 2000. The main issue I have now is that the copying of the profiles is not working the way I had thought. I will close this question and repost with a higher point value.

This discussion is closed to new replies.