Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.
Solved
Join computer to new windows server 2012 essentials fails
Posted on 2014-12-19
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;
So I'd appreciate any pointers as to where to go from here.
Thanks
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;
So I'd appreciate any pointers as to where to go from here.
Thanks
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
4
6 Comments
Active today
did you verify if that computer account already exists?
did you do what the dialog box suggested?
did you do what the dialog box suggested?
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?
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?
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
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.
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.
Featured Post
We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
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…
Suggested Courses
Course of the Month11 days, 6 hours left to enroll
719 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.