Alexandre Takacs
asked on
Migrating from SBS 2010 - Old exchange server doesn't see new one !
Hello
We are currently migrating from an SBS2011 setup to "full" DC / Exchange etc... (basically a follow up to this https://www.experts-exchange.com/questions/28996611/Migrating-from-SBS-cont.html discussion).
We have setup a standalone 2016 based AD server and apparently it is replicating as expected. We have not moved the FSMO roles yet.
Next we have provisioned a new 2016 based (both server and exchange) Exchange server. Again everything seems to have worked fine so far.
Now we want to migrate our mailboxes and Public folders to new server. That's where we have an issue...
If new server indeed "sees" both servers in the deployment
old server only "sees" itself !
I have tried to migrate a (test) mailbox to the new server and it worked fine... However PF migration should (in my understanding) been done from the old server. I fear I am missing something !?
We are currently migrating from an SBS2011 setup to "full" DC / Exchange etc... (basically a follow up to this https://www.experts-exchange.com/questions/28996611/Migrating-from-SBS-cont.html discussion).
We have setup a standalone 2016 based AD server and apparently it is replicating as expected. We have not moved the FSMO roles yet.
Next we have provisioned a new 2016 based (both server and exchange) Exchange server. Again everything seems to have worked fine so far.
Now we want to migrate our mailboxes and Public folders to new server. That's where we have an issue...
If new server indeed "sees" both servers in the deployment
old server only "sees" itself !
I have tried to migrate a (test) mailbox to the new server and it worked fine... However PF migration should (in my understanding) been done from the old server. I fear I am missing something !?
As i am Reading the prerequisites for upgrading to exchange 2016 it states that ALL domain controllers in the forest must run minimal:
Windows Server 2012 R2 Standard or Datacenter
Windows Server 2012 Standard or Datacenter
Windows Server 2008 R2 Standard or Enterprise
Windows Server 2008 R2 Datacenter RTM or later
Windows Server 2008 Standard, Enterprise, or Datacenter
It turns out sbs2011 Isnt an option.
Best option, as it seems, is to upgrade sbs2011 to 2012r2 and from here do the migration.
Please check this transition guide
Windows Server 2012 R2 Standard or Datacenter
Windows Server 2012 Standard or Datacenter
Windows Server 2008 R2 Standard or Enterprise
Windows Server 2008 R2 Datacenter RTM or later
Windows Server 2008 Standard, Enterprise, or Datacenter
It turns out sbs2011 Isnt an option.
Best option, as it seems, is to upgrade sbs2011 to 2012r2 and from here do the migration.
Please check this transition guide
ASKER
Hmm an interesting point...
The new DC is definitely in that list but you might be on something with the old one not being on the "supported" list.
However my understanding is that removing the AD services is the very last thing to do in an SBS migration, after having moved all other services...
Sounds like a catch 22 to me...
The new DC is definitely in that list but you might be on something with the old one not being on the "supported" list.
However my understanding is that removing the AD services is the very last thing to do in an SBS migration, after having moved all other services...
Sounds like a catch 22 to me...
It is... then again it is a list off supported domain controllers.
From AD point off view, on the new server does this command show the sbs2011 as the FSMO leader?
Netdom query FSMO (In elevated dos prompt)
Same on the sbs box, does this command show the new server as an valid DC?
Netdom query server
Or
Netdom query DC
From AD point off view, on the new server does this command show the sbs2011 as the FSMO leader?
Netdom query FSMO (In elevated dos prompt)
Same on the sbs box, does this command show the new server as an valid DC?
Netdom query server
Or
Netdom query DC
ASKER
yes and yes - SBS is still FSMO (at it should IMHO) and the other DC is shown as such
C:\Windows\system32>Netdom query FSMO
Schema master xxxSBS.synergix.local
Domain naming master xxxSBS.synergix.local
PDC xxxSBS.synergix.local
RID pool manager xxxSBS.synergix.local
Infrastructure master xxxSBS.synergix.local
The command completed successfully.
C:\Windows\system32>Netdom query DC
List of domain controllers with accounts in the domain:
xxxSBS
AD-SX-01
The command completed successfully.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is actually lab environment so I shall continue... Although not quite sure how.
Do you mean moving the FSMO roles ?
As far as I can tell I need to be able to "see" the new Exchange server from the old one in order to migrate the public folders.
Do you mean moving the FSMO roles ?
As far as I can tell I need to be able to "see" the new Exchange server from the old one in order to migrate the public folders.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for you help - LAB migration seems to work even with the source server not "seeing" the new one.
Having other issues but creating aa separate question as it is most likely not directly related.
Having other issues but creating aa separate question as it is most likely not directly related.
Exchange 2010 on sbs2011 should see the 2016 box. Which rollup is installed on the 2011 box?
From memory i believe you should have rollup 13.
Please let us know.