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

Post migration problems

Good morning,

I've recently migrated an SBS 2003 to Server 2012 Std. and Office 365.

I'm at the end and here's where the s%*t hits the fan.

My last step was to edit the DNS address on the NIC which had the SBS2003 in the primary and "loopback" as the secondary.  As soon as I remove the SBS's IP and put in the the new DC's IP the server basically stops working.  

AD stops working, can't join computers to the domain.  the FSMO shows "ERROR" and so on.

I can't seem to wrap my head around what's happening but I'm sure it's rooted in the DNS.

Any suggestions would be wonderful as the SBS is going to start shutting down soon.

Thanks so much.
0
Bullfrog28
Asked:
Bullfrog28
1 Solution
 
smckeown777Commented:
Did you not transfer the FSMO roles to 2012?

SBS is obviously still the FSMO owner...so changing ip's on the nic is going to break AD...

You need to move the roles to 2012 first...then demote the 2003 SBS(leave the nic alone with its regular settings)

Once its demoted you switch it off...because its SBS this needs to be done, you can't leave it running(which I think you know but just want to be sure)
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

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