Link to home
Create AccountLog in
Avatar of Robert Janics Jr M.C.P
Robert Janics Jr M.C.PFlag for United States of America

asked on

bs 2011 Migration

I am doing my migration in a lab environment I made a VM of the main dc now. So far I have made two other VM's for server 2012 R2. I went ahead and  domain joined server 1 and promoted it to DC and made sure AD moved over and synced I then moved over FSMO. Next I'm getting ready to migrate exchange off of the old sbs server. This I have never done yet. I was going to Domain join it, install exchange 2016 and then use the Microsoft migration docs.  Are these the proper steps so far? also are there any roles I need to install on server 2 before I install Exchange 2016?
Avatar of Cris Hanna
Cris Hanna
Flag of United States of America image

When you move the FSMO off of SBS, you start a countdown timer...7 days or it can be extended to 21 days with a patch, after which time the SBS box will start rebooting every hour

The correct path should have would be migrating Exchange, then all data, then uninstall Exchange 2010 for the Organization, then MOVE the FSMO roles to the new DC.   , then DC promo the Old SBS box out of the domain
Avatar of Robert Janics Jr M.C.P

ASKER

I though I wanted to domain join my new exchange server to the new DC instaead of the old SBS box so I did it that way. What if when I do it live I leave FSMO on SBS but still promote new DC and AD and Domain join new exchange to new DC and then migrate exchange then move FSMO?
Your new DC and Exchange Server are going to be in the same AD domain as the SBS box ?  Correct?   You don't join a server to a DC, you join a box to the domain.

I would kill your lab and start over.    Create your SBS VM.   Make sure it's fully patched with SBS Update Rollups, Server Update Rollups, Exchange SP3, etc.   Run DCDiag on it to make sure it's healthy.   I'd run the SBS BPA on it...make sure it's healthy

Then add your new server that will be the DC.   Join to the SBS AD domain.   Then promote to a DC, run DCDIAG again on both servers...make sure everything is healthy
Then add another new server for Exchange, Move mailboxes/public folders
Uninstall Exchange from the SBS box...make sure that Exchange on the new server is now handling all the work
Since this a lab, no need to practice copying data
Then transfer FSMO roles to the new DC and DC promo the SBS out as a DC and then shut it down

If everything is working as expected  in lab, then you can move forward in actual env     Practice Practice Practice in the Lab first until you are error free, then do production
when running exchange setup I get an error One or more servers in the existing organization are running Exchange 2000 or 2003. I am running exchange 2010 on SBS 2011. I can tell you that this sbs 2011 was migrated from SBS 2008.
If you open the Exchange Management Shell and enter Get-ExchangeServer
What version is returned?
I attached the output of the get exchange and also the exchange setup log
for naming
Wendy = current sbs2011
Bacon = New DC, Ad
Frosty = New Exchange
ExchangeSetup.log
GetExchangesever.txt
Also my Forest Level is 2008R2
Well I know where the problem is (I think) but I don't have a solution for you at this point
the Get Exchange results shows
WENCO-SERVER                             None        Standard    Version 6.5 (Bui...
WENDY               wenco.local/Confi... Mailbox,... Standard    Version 14.3 (Bu...

I don't think it should be showing the first entry, which I believe is the culprit for the older version

you have two options here I believe
1. Request attention from Admin's to see if you can get other Exchange gurus to look at the results
2. Support from a paid 3rd service.  I do not work for any of those services but my prime recommendation would be ThirdTier.net  The individuals there are almost all Microsoft MVPs (like myself) who have specific technology skills, including Exchange.
that old Wenco-sever is the old sbs2008 server that was migrated to the sbs2011 server
I found where to remove the Wenco-server entry I'm going to start over and use these steps

1. patch and update sbs
2. Domain join new dc
3. promote new dc
4. domain join new Exchange server
5. Prep ad and update schema
6. install exchange server
7. move mail boxes
8. move fsmo

does that look like a good plan of action
Run the SBS BPA. If the domain was migrated from SBS 2003 prior to 2008 there is a legacy Exchange container that needs to be deleted.
Is this the container I am making a snapshot and then removing it
User generated image
Please run the BPA and follow its guidance.
ASKER CERTIFIED SOLUTION
Avatar of Cris Hanna
Cris Hanna
Flag of United States of America image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
once I have both servers do I NOT want to have IIS installed on my DC/AD and only have it running on the exchange server?
Also BPA did help. I now have everything migrated and both servers running and 3 win7 vm's working still. working on exchange now.
one more question for right now. DO I want CA only running on one server and which one?