Link to home
Start Free TrialLog in
Avatar of Ralph Mooney
Ralph Mooney

asked on

SBS License issue during Server Migration

I am migrating our domain from SBS2011 (old box)  to Windows Server 2016 Standard (on a new box).  I have already migrated the mailboxes from Exchange to Office 365 and removed Exchange from the SBS box.  I moved the FSMO roles from old SBS to 2016 DC yesterday.  I have a few more things to do before migrating group, user and computer accounts and then Apps & Data.  I've started getting errors that I'm out of compliance withe the SBS license.  Upon reading the license, I went out of compliance when I moved the FSMO roles off the SBS server.  I seem to recall reading that I have 7 days of allowed non-compliance before SBS starts spontaneously shutting down with maddening regularity.  Can anyone verify that time period and add any other interim consequences I should be watching for?  Thanks in advance.
ASKER CERTIFIED SOLUTION
Avatar of DrDave242
DrDave242
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi

IMHO you have a 21 days grace period, plenty of time to finish your migration.
The grace period starts as soon as the sbs box sees a second domain controller so moving fsmo roles is no option anymore, just proceed.
If this period is to short you can disable the timer as described here
https://www.bursky.net/index.php/2012/02/disable-sbs-migration-grace-period-expiration/

Cheers
The grace period starts as soon as the sbs box sees a second domain controller

SBS doesn't care if there are additional domain controllers, as long as the other requirements are met (it holds all of the FSMO roles, no domain trusts, you don't have more than the allowed number of users, etc). Simply promoting another DC in the domain won't trigger this behavior.
Avatar of Ralph Mooney
Ralph Mooney

ASKER

I very much appreciate both responses.  I'm seeing an error in the FSMO Role check.  It appears the actual allowed period of non-compliance is 28 days.  I looked at the log suggested by DrDave242 and currently have just short of 27 days, and I moved the roles yesterday.  Thanks again!
I stand corrected, sbs will shout when it sees a second sbs server, second dc is supported.
Moving the FSMO roles back to the 2003 will only extend the grace period by 7 days right?

https://blog.thesysadmins.co.uk/sbs-2003-to-sbs-2011-migration-extend-21-day-limit.html Gives me the idea.

Cheers
Yes Ralph, youre welcome, please know it is possible to extend this.