Setting up new server

[Brandonjjon]

Hello everyone,

I'm seeking some advice on setting up this new Windows Server 2012 machine.

The office I'm installing it in currently has a server and domain etc... my plan is to turn off the current server, setup the new server (domain, active directory, dns, etc) and then on all the workstations, leave the existing domain, then join the new domain. Will this keep their existing desktops and user profiles as they were?

1. Turn off old server
2. Setup new server (domain, active directory, etc)
3. On all workstations, leave old domain, join new domain.

Does this sound correct? My only concern is trying to leave the old domain on the workstations... I wont even be able to leave the domain if I can't log into the computer (cause the old server is off at that point). Or is there a way to do this?

Any help or advice on this topic is much appreciated.

Thanks!

 

[MotzTech]

Is there a reason you can't migrate active directory over to the new server?

What OS is the old server running?

Most domains are setup with what's called cached credentials. Which means that even if the D/C is offline, they can login to the domain as long as the username/password was able to authenticate to the server at least once.

It's been a while since I have done a domain rebuild, but IIRC it will create new profiles when they log in. There is a workaround for this (or at least it worked when I did this 3+ years ago). You login with an admin acct, rename the profile to username.old, change domains, login with the new user account. Log out and Log back into the admin account and replace the new user account profile with the .old version.

I have a tech that handles this stuff for me now so the process may have changed. Be sure to research this further before doing anything.

 

[MSgherzi]

Hello everyone,

I'm seeking some advice on setting up this new Windows Server 2012 machine.

The office I'm installing it in currently has a server and domain etc... my plan is to turn off the current server, setup the new server (domain, active directory, dns, etc) and then on all the workstations, leave the existing domain, then join the new domain. Will this keep their existing desktops and user profiles as they were?

1. Turn off old server
2. Setup new server (domain, active directory, etc)
3. On all workstations, leave old domain, join new domain.

Does this sound correct? My only concern is trying to leave the old domain on the workstations... I wont even be able to leave the domain if I can't log into the computer (cause the old server is off at that point). Or is there a way to do this?

Any help or advice on this topic is much appreciated.

Thanks!

This won't work. You need to migrate the active directory over to the new server, otherwise all of the domain-wide global policy objects, users, etc. will not be the same. You can create a brand new domain and migrate the settings over from the old server. Just be sure you designate a new domain controller on the new server.

 

[mikeroq]

I recently installed a new server, going from no domain to domain. Found this tool (http://www.forensit.com/domain-migration.html), it changes file names and the registry to "move" the users stuff between the accounts. I wish I had found it when I was switching out the server before that, it was 2003SBS. Only 9 computers so I just made the new domain from scratch. They weren't really utilizing any features (GPO, security, etc). Would have saved time since I just used Fabs to back up their stuff.

 

[onkyo]

Did this awhile ago with 2000 to 2008

install new server into existing domain
transfer fsmo roles and global catalog to new server
remove original server from the domain, then rename it.
Add original server "with the new name" into domain and transfer fsmo roles and global catalog.

Remove new server out of domain, and rename it to original servers name, and add it back into the domain and transfer fsmo roles and global catalog.

restore all data to new server, recreate shares etc.

remove old server from the domain and take off line.


hope this doesn't confuse the heck out of someone.

 

[ABTECH]

I just had to do this last week because the older server was failing for a brand new client. Make sure you document all of the software that is used on the existing server and if you are creating a whole new domain you will need to move the old domain profiles on the machines to the new domain. I was able to use Windows Easy Transfer because I only had 5 machines. It moved everything over without any problems. Otherwise migrate AD to the new server, I did not have the option because everything was too hosed.