"Migrate" to clean install

[riahc3]

I want to go from WS2003SBS to WS2012R2.

My setup is something like the following
domain: hello.local
pcs: p1,p2,p3
users: u1,u2,u3

These are just simple examples

Now each client PC joined to the domain already has their user

C: \Users\u1\

So my question is, how do I migrate correctly?

My idea is to setup the WS2012R2 with the same users, domain name, etc.....but I am not sure if that conflicts with the folders on the client PCs.


Could someone help me out?

 

[riahc3]

Im sure more than one person has tried this.

 

[denis280]

My idea is to setup the WS2012R2 with the same users, domain name, etc.....but I am not sure if that conflicts with the folders on the client PCs.

sure why not.only one question what os

 

[DrGreen2007]

"My idea is to setup the WS2012R2 with the same users, domain name, etc"

If you setup the 2012 as a new domain, even with the same domain name, and same usernames, the users will get new profiles after you rejoin the computers to the 'new' domain. (this is because the user ID's on the new domain will have a different SID)

Ideally you want to join the 2012 to the 2003sbs domain, then youd have to run the adprep on the 2003sbs machine to enable the 2012 to become a DC as well.
Then migrate the DNS and DHCP roles over, migrate the file shares over, print shares, etc.
Confirm replication is working, as is DNS resolution.
After that, you should be able to open the AD Users and Computers console on the 2012 machine (which would be a domain controller on the current domain) and then you should see the users and computers in the current OU locations.
After that, you can start the process to demote the SBS2003 machine

If you dont want to join the 2012 to the 2003 domain, after you move the computers from the old domain, to the new domain, when the users logon, they will get a new profile C:\Users\U1.domain
After they log on, you can change the registry to point to the old folder of C:\Users\U1, then reset the permissions of the C:\Users\U1 folder to give the user full permission and overship
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

Theres also tools from forensit.com to migrate profiles

 

[riahc3]

sure why not.only one question what os

What os what? The clients?

Most are Windows 7. I think one Windows Vista. And as far as I recall, no Windows XP.

"My idea is to setup the WS2012R2 with the same users, domain name, etc"

If you setup the 2012 as a new domain, even with the same domain name, and same usernames, the users will get new profiles after you rejoin the computers to the 'new' domain. (this is because the user ID's on the new domain will have a different SID)

This is what I thought to even though I was told that if they have the exact same everything there wouldnt be a problem.

Ideally you want to join the 2012 to the 2003sbs domain, then youd have to run the adprep on the 2003sbs machine to enable the 2012 to become a DC as well.
Then migrate the DNS and DHCP roles over, migrate the file shares over, print shares, etc.
Confirm replication is working, as is DNS resolution.
After that, you should be able to open the AD Users and Computers console on the 2012 machine (which would be a domain controller on the current domain) and then you should see the users and computers in the current OU locations.
After that, you can start the process to demote the SBS2003 machine

Due to issues with the 2003SBS, I do not want the 2003SBS and the 2012R2 to really never know about each other.

If you dont want to join the 2012 to the 2003 domain, after you move the computers from the old domain, to the new domain, when the users logon, they will get a new profile C:\Users\U1.domain
After they log on, you can change the registry to point to the old folder of C:\Users\U1, then reset the permissions of the C:\Users\U1 folder to give the user full permission and overship
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

Theres also tools from forensit.com to migrate profiles

[/quote]
This is what I am going to do most likely.

Are there any good tools to do this on a AD scale? I mean that I dont have to go one by one, pc by pc, doing this?

 

[DrGreen2007]

Quest has great migration tools, but they are expensive, Forensit tools are decently priced