Migrate SBS 2003 computer to Essentials Server 2012 R2

I have just installed a new server running Essentials Server 2012 R2 for a client. I have joined the domain and connected DNS, DHCP, AD...

The problem is trying to get the existing computers into the new server. The AD objects are all there but if I try to run the http://<server-name>/Connect, I get an error message:
This computer cannot be connected to the server using the user name and password credentials provided. This may be because an existing computer account have the name "<computername>" was previously created using a different set of credentials.

I have tried to reset the computer account in AD but that did not help. It would appear that a computer already part of the domain cannot rejoin the domain, as you would expect. HOWEVER, the main problem I have is that all the folder redirected files are all pointing to the old server and need to be moved to the new one. How would I get this sorted out?

I guess I could dis-join the domain and re-join, but I don't know what will happen to all the users documents? It might just create a new account with the same name and I would have to manually have to move all the files, for all the users on the network, about 15 computers.

I would have thought that there was a better solution.

Help please.

Many thanks
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

KenCOO/Senior Systems AnalystCommented:
You are not rejoining a domain if you migrating a domain from sbs 2003 to Essentials. You should follow the whitepaper  and migration wizard for this kind of migration. The steps in the migration will take you through creating the folder redirection on the new server and then changing the config for the clients.

KenCOO/Senior Systems AnalystCommented:
I apologize, I copied the wrong link for your migration.

aalmstromAuthor Commented:
But that link refers to version 2012 and not 2012 R2, which doesn't have the migration option for the installation.

I don't think that will help me much?
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

KenCOO/Senior Systems AnalystCommented:
Good call, I didn't see that and haven't had to migrate to R2 yet. Here is the correct link.

aalmstromAuthor Commented:
Yes, that document I have seen and read, but it does not, at least to me, explain how to get the computers moved from the 'old' domain to the 'new', in order to move the replicated folders and other settings to the new server.

This is where I have the problem and I don't see it explained in the the document or anywhere else where I look.
KenCOO/Senior Systems AnalystCommented:
Here is my understanding- you started with a single domain and you added a new 2012 R2 Essentials server to the domain. Then you migrated the roles from the old DC to the new DC. There is no 'old' domain and no 'new' domain. Correct?

At one point in the migration process you move the file shares and recreate them on the new server. It seems this is where you are having issues? This is the point where I would edit the paths in my Group Policy objects that control file shares and folder redirection. Sometimes this is done with Login Scripts. How do you have your folder shares and redirects setup?

Can you provide a little more detail on what is not mapping properly? You have said folder redirection. Is that all? Shares?
aalmstromAuthor Commented:
You have it basically correct. But I don't think just changing the UNC path in the GPO will fix the problem. This will not work as there folders have to be created for each use and exist before the folder redirection will work. And copying the folders from the old server does not work as the administrators do not have access to the individual's folders, but only the SYSTEM account.

Also the computer account needs to be moved to the new DC so that it is there as a device in the new server, and then can be used for backups, RDC...

This is the area where I would like some help. I thought that if you bought a server from MS, which is there to replace the now dead SBS, there would be a migration plan like there has been in the past, but I haven't found it yet.

Any ideas would be appreciated.

Many thanks

aalmstromAuthor Commented:
What I have done.


I change group Policy to 'Leave the Folders if the get removed' I then made sure that it got pushed out.


Changed the folder in the folder redirection to point to the new server and connect the clients. This will move the files to the new server.


1, The computers are connected to the domain in AD as they were there to start with, however, they are not listed under devices, so I cannot link to users for RDC or backups.
2, The time it takes to copy all the files, during log in, to the new server is quite long with just the Welcome message. Many users thought that their computers had hung and powered off the computers and tried again.
3, As I could not copy the redirected folders from the old server, as Administrators have no access to the content, it has to replicate by itself.
4, IMPORTANT! you have to create the folders for each user before you do this or you will just get a hidden error that the GP object could not be applied, run RSOP.MSC, then look for the '!' mark and then errors. These folder that you create have to give the user 'Full' rights to their own folders, I used ICACLS <user> /grant:r <user>:(OI)(CI)F in a batch file along with the 'md <user>' to create all these from 'dir /b /ad > file.bat' on the old servers' redirected folders.

I would have hoped that there was a better way to get this done.
aalmstromAuthor Commented:

The way to fix it is to run the connect software with a couple of registry hacks so that it doesn't join the domain, which is the one that it is currently connected to. This will add the computer to devices on the 2012 R2 server, which in turn will enable remote desktop access, backups...

Here is a link to a good sight that will take you step by step.


But why should this be required to just simply add an existing AD computer to the Devices list???

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
aalmstromAuthor Commented:
No expert would give a solution to the problem.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.