Solved

Join computer to new windows server 2012 essentials fails

Posted on 2014-12-19
6
292 Views
Last Modified: 2014-12-27
I'm currently following a Microsoft guide to migrate from SBS 2011 to Server 2012 Essentials - http://technet.microsoft.com/en-us/library/dn408633.aspx 

I've previously ran through all the steps on a virtual copy of the real server to the new test server, and no real issues encountered, so I'm a little surprised to be stuck at this step.

I'm following the step 3: join computers to the new Windows Server 2012 essentials server.

However, at the point where the connect wizard (http://server2/connect runs I get the following error;

connect-fail.jpg
So I'd appreciate any pointers as to where to go from here.

Thanks
0
Comment
Question by:foxpc123
  • 4
6 Comments
 
LVL 34

Expert Comment

by:Seth Simmons
ID: 40510130
did you verify if that computer account already exists?
did you do what the dialog box suggested?
0
 
LVL 3

Author Comment

by:foxpc123
ID: 40510144
Hi Seth,
This is a migration from SBS 2011 to Server 2012 and so I would expect the computer account to exist as the AD is copied from the old server to the new server as part of the migration steps.

The purpose of the connect steps as far as I can see is so that the computer then appears under the devices tab, I wouldn't expect it to 'join' the domain as such as it is already in the domain by virtue of it being a migration.

So I query why one would need to rename the computer as this should simply migrate from the old server (SBS 2011) to the new server 2012 essentials. The purpose of the connector as per the testing carried out earlier is simply so that the essentials server places this under the devices tab, and also allow for the backup and other options within essentials to be applied to that device.

So I would 'expect' for the device to be present as it should be present in AD on both servers until the old server is decommissioned when the migration steps are complete?
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40510727
Did you uninstall the Windows Small Business Server 2011 Essentials Connector first before you tried using the Connect wizard as specified here? http://technet.microsoft.com/en-us/library/dn408636.aspx
0
Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

 
LVL 3

Author Comment

by:foxpc123
ID: 40512752
No because it isn't Small Business Server 2011 Essentials
0
 
LVL 3

Accepted Solution

by:
foxpc123 earned 0 total points
ID: 40512763
This issue is now partially resolved.

It seems that when the connector is run, one should supply the administrator credentials rather than a user credentials, however, this seems badly worded when compared with the Small Business Server connectors - where it is a little more explicit that you need to supply the administrator credentials. I've done lots of connectors in the past, and have always used administrator credentials, but the wording and the guide aren't explicit enough here to avoid the obvious mistake of trying to use a 'user' for this.

Anyway, after putting in the administrator login details, you get much further and can actually join the machines to the 'new' server 2012 domain.

I have about 50% which went through no problem at all, and the other 50% all experienced the connector has stopped working and crashes. However, even though the connector crashes the machines still show up in the devices tab all set-up o.k., so as this was the whole point of the exercise then in a way this issue is resolved.

Bit scrappy really, however the issue is resolved and thanks to all the respondents.
0
 
LVL 3

Author Closing Comment

by:foxpc123
ID: 40519487
Issue was resolved through trial and error
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

What to do when Windows Update is not working correctly? What tools can I use to detect the cause of the malfunction problem? What does this numeric error code mean? These and other questions that you have been asking in the past are answered here (…
Sometimes drives fill up and we don't know why.  If you don't understand the best way to use the tools available, you may end up being stumped as to why your drive says it's not full when you have no space left!  Here's how you can find out...
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

895 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now