• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 594
  • Last Modified:

Migration SBS 2003 to 2012 R2 Essentials "A domain controller running Windows Server 2008.."

I am migrating sbs 2003 to Essentials 2012 R2, I've done the prep on the SBS 2003 servers - BPA comes out clean, I do have an error and a couple of  warnings in the Microsoft IT analyzer,  orphaned nic's and listening on multiple addresses. There are 3 nic's in the machine, 2 are disabled. I've had this at a previous installation and had to remove the WAN miniport adapters that show as hidden devices in device manager which will get rid of these items, however it also disables VPN access so I will do that later.

The problem I'm having is that after I select Add a domain controller to an existing domain, enter the domain administrator login at the next screen it says:
"A domain controller running Windows Serve 2008 or later could not be located in this domain. To install a read-only domain controller, the domain must have a domain controller running Windows Serve 2008 or later."
I don't recall this message on my previous migration, it does look like I can proceed but is there a problem?
Thanks.
0
dpacheco
Asked:
dpacheco
  • 4
  • 2
1 Solution
 
dpachecoAuthor Commented:
I think I may have found the answer that it's ok to go by that:
https://social.technet.microsoft.com/forums/windowsserver/en-US/87876f09-90e6-4548-bdb6-7b1e525951be/adding-a-windows-2012-dc-to-a-windows-2003-forest

The forest and domain functional level are at 2003.

Can someone verify that it's ok to go ahead? Thanks.
0
 
Cliff GaliherCommented:
It is a legitimate warning (not an error) so, yes, since essentials cannot be an RODC you can proceed.
0
 
dpachecoAuthor Commented:
Great, thanks. On the next step I am getting
"A delegation for this DNS server cannot be created because the authoritative parent zone cannot be found or it does not run Windows DNS server."
The 2012 server has a static internal IP with the IP of the 2003 server as the DNS server and I created an A record in the DNS server on the 2003 machine for the 2012 server. What am I missing?
I can open a new question for this.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Cliff GaliherCommented:
Since essentials doesn't support trusts, you probably dont *have* a parent domain. So this warning is normal, expected, and in this case, can be ignored.
0
 
dpachecoAuthor Commented:
I thought so too but then I got another error and could not go any farther. I will take a look and post that but I was thinking maybe it had to do with not disabling the WAN many port adapters. Anyway I'm hanging it up for today
0
 
dpachecoAuthor Commented:
Today I did not get the error I had gotten yesterday after going past the DNS warning, it went thru the additional options, paths, review options, and perquisite check, it restarted the server. I logged back in, transferred the FSMO roles to the new server, ran netdom query fsmo and it shows the roles are with the new server. However, when I clicked to configure to finish the setup it immediately says "Configuration encountered some issues" click retry. Figured out that the Essentials Management Service wasn't starting, needed to have Logon as a service added for ServerAdmin$ it finished the configuration then.
Thought I'd mention the above in case someone else has this issue.
Thanks for your help!
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now