• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 215
  • Last Modified:

Reinstalled Server2003-Need to delete users before rejoining domain??

Hi Guys,

First of all, I know I have a couple of questions open from last week. Does the phrase "I had a kidney stone" ring a bell with you? If so, you know why I've been out of commission. I'll close those questions as soon as I pose this one:

I just reformatted and reinstalled Server2003 Small Business. Now I need to rejoin the workstations to the domain, but I'm a little concerned about this. When I go to a workstation and Explore, in Docs & Settings I see several users. There is the currently used user called "jsmith", but then I see also "jsmith.domainname" and "administrator.domainname".

My question is, will these existing users cause a problem when I try to rejoin the domain? The computer names haven't changed so I'm concerned about SID issues. If you advise me to delete those users, what is the best way to do so without causing problems when I rejoin to the domain?

Thanks for any help you can offer.
BC
0
bricar
Asked:
bricar
  • 5
  • 3
  • 2
  • +2
3 Solutions
 
LazarusCommented:
jsmith.domainname is your AD login, whil jsmith is likley a local client login.
The SID issue is a valid concern. I prefer to just delete the jsmith.domainname users off the local machines, but you should have a backup of them for sure before you do that. I just transfer then to a holding directory on my servers so that I can put back the needed files.. i.e... Documents, Desktop, Favorites, Outlook's etc..etc... This can impose a bit of a burden on the users though, since they will be without there files untill you move them. Also they will have to basiclly reset there desktop enviroments. But it insures a clean join with no other problems in my opinion. Now if you have alot of users this can be time consuming, but if you have lesss than say 50 it's pretty simple.
0
 
cyberdevil67Commented:
Hi bricar,

 No you will not have to delete the users, as long as the domain name is the same Windows 2003 Server will pick the machine name up and re add them to the list automatically. However I would not recommend using administrator.domainname, and should always be a user account from that machine trying to connect.

Cheers!
0
 
harleyjdCommented:
In order to maintain user desktop settings in this situation you can:

rename the default user profile to "default user.old",
rename the desired profile to "default user"  and grant everyone read access to it (don't forget to apply to all subfolders)
log on as the appropriate user
rename the default user profile to username.old (or just delete it if you are happy)
rename  "default user.old" to  "default user"

the drawbacks - unc paths are kept, so if printer sharenames are different then these will be broke, you can easily forget to restore the original default user and the next person to log in gets the old user's profile...

0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
bricarAuthor Commented:
Lazarus,

>>>>jsmith.domainname is your AD login, whil jsmith is likley a local client login.<<<<

So far, so good. I knew this to be the case

>>>>The SID issue is a valid concern. I prefer to just delete the jsmith.domainname users off the local machines, but you should have a backup of them for sure before you do that. I just transfer then to a holding directory on my servers so that I can put back the needed files.. i.e... Documents, Desktop, Favorites, Outlook's etc..etc...<<<<

Do I do this in the Explorer (just drag & drop), or do I do this through management? Also, isn't there some other file that I need to delete to eliminate a SID problem?

>>>>This can impose a bit of a burden on the users though, since they will be without there files untill you move them. Also they will have to basiclly reset there desktop enviroments. But it insures a clean join with no other problems in my opinion. Now if you have alot of users this can be time consuming, but if you have lesss than say 50 it's pretty simple.<<<<

NP there, it's only 5 machines. Some XP and some 2000. Thanks for your reply!

BC
0
 
bricarAuthor Commented:
cyberdevil67,

Thanks for the tips. I used that for some reason I can't remember...problem with an old 16 bit app, I believe.

I recall once trying to rejoin and I got computer names like "ACCOUNTING.domainname.local.000

That's what I'm trying to avoid if possible.

BC
0
 
bricarAuthor Commented:
Hi harleyjd ,

I'm not concerned at all with desktop settings, as it's only 5 workstations and I can just drag 'n drop where needed. They only use a few apps.

I'm mostly afraid of getting weirdness on the server as it adds .000 to users and/or computer names.

BC
0
 
harleyjdCommented:
OK, just do what Laz said - move the old profiles to a temp store before the users log in. Their new profile gets set up, then you can copy back anything needed.

The system will create a username folder first, irrespective of it being a domain or local account, and will only append the domain/computer name if the username is already taken. Same goes for .000 - will only happen if both the username and username.domain are used. If they don't exist, then you're fine...

0
 
bricarAuthor Commented:
harleyjd,

Thanks for the input. If I understand you correctly, I should log on locally as administrator, then move all the users (except the local user, "jsmith") to a temp store. Is this correct?

After this (or however you correct me) is accomplished, then should I login as the local user and join the domain, or must I add A/D users and computers first on the server?

I'm sorry to be such a simpleton...I inherited this site and I just want to avoid complications.

Your help is greatly appreciated!

BC
0
 
LazarusCommented:
If you only have 5 machines just rename the profiles to "jsmith.domainename.old" that will work fine. I thought you might have more, then when you relogin it will create the new profile. You can just copy the things you need from the .old into the new after it has been recreated after adding them to the domain and login them in.
Login as the local user then use the domain admins login and password for joining the new domain thru the Netwrok wizard.
You can also ad your users to the Domain through the "Active Directory Users and Computers" MMC if you haven't already. Adding them to the local machines is up to you.

Sorry this was sort of out of sequence, but you seem to have figured it out. It's pretty simple once you've done it. You'll do fine
0
 
bricarAuthor Commented:
Lazarus,

Should I add the users and computers through "Active Directory Users and Computers" FIRST, BEFORE I join the domain at each workstation, or will the server automatically add them when I join the domain?

I'm used to 2000 Server where I would do it as described above.

Thanks so much!

BC
0
 
LazarusCommented:
Well, I do that myself, simple beacuse I can do it faster from there. Then I just go around to each machine and login as local admin and ad the computers to the domain. You can do it either way though. It's just a preference on my part.
0
 
redseatechnologiesCommented:
just something to note,

IF you are using exchange, and IF you are using offline files (ost), you will want to log in to the workstation as the user (using cached credential) and export all that goodness to a pst file

i have had infinite problems with ost files, and getting things out of them - you can get the main folders, but nothing from any sub folders

anyway, just something to be aware of, even if you back it up - without the SID, you can't open that ost file

-red
0
 
redseatechnologiesCommented:
i concur

merry christmas alimu

-red
0

Featured Post

Microsoft Certification Exam 74-409

VeeamĀ® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

  • 5
  • 3
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now