Start a discussion

AFAIKthere is no way you could 'upgrade' the license of an SBS 2008 to something else. SBS 2008 is really very different compared to vanilla 2008 codewise, that is one of the reasons why Microsoft no longer makes suites like SBS. I do not know that application mover at all and I doubt it will move a SQL app. But migrating SQL from one server to another should not be a big issue, I have done many of those.
 

I was reading this and I have a similar question. We are migrating from SBS 2008 to Server 2016 and O 365. The original consultants installed a legacy application (SQL based) on the SBS 2008 domain server. I do know about the 21 day issue (we did many of these migrations over the years.)

The legacy installation is very delicate and we may not be able to easily move it to a new server. The question I have, is it possible to upgrade the SBS 2008 to a version of windows "in-place" I do have access to valid licenses to Server 2008 R2.

I was thinking about  P2V of the SBS2008 server and testing an upgrade virtually.

They did purchase SBS 2008 Premium. This migration would have been smoother if the legacy app was NOT on the Domain server and was on a member server...

Another idea, I was also wondering if maybe a Laplink application mover might work on these servers?

I've run the net share command already and do have valid SYSVOL on the new server! Thanks for the reminders on the others, I will definitely do those as well prior to demoting the SBS11 server.

Jeff

Jeff,

Just before you demote the SBS you must verify if you have a valid SYSVOL on the new server. It is very easy to check, just open an elevated command prompt and type 'net share'. In the list with Shares you must see a SYSVOL share. If not, red alarm!!!

Also run once more the checks from Understanding Active Directory Health during an Active Directory migration and tools you can use like repadmin and dcdiag like

Repadmin /showrepl
Repadmin /replsummary
​​​​​​​DCDIAG /test:DNS /DNSALL /e /v
DCDIAG /test:RegisterInDNS /DNSDomain:adatum.local

If you run the above commands and add > repadmin_report.txt you get a txt report for archive purposes. Always good to have those if you run into issues later.

OK, will do. I heading onsite in about an hour to try to finish this thing up. I'll post back when I'm done.

Thanks again!
Jeff

HI Jeff,

Thank you so much for the nice words. As far as I know there is no hack or solution for the license issue. Let me know how you are doing?

Hi Mariette

Thanks so much for quick reply. I am following your tutorial on this for sure, and I am on like step #9 uninstalling exchange next. The SBS 11 server is still a DC, even though I've already transferred all FSMO roles to the new WSE16. I've got the DFS replicating shares and that's working great! Thanks for that tip, BTW, what a great timesaver that is! That right there was worth my premium membership!

Anyway, I once I demote the SBS box I could leave it in place indefinitely because that was the requirement from MS that this be the only DC on the LAN. Is there some registry hack I could perform to leave it in place?

Thanks so much

Jeff

Hello Jeff, 

You can only have the SBS for 21 days in your network after you have moved FSMO roles. The server will then start to shutdown at times you don't want that to happen. Within the 21 days you can still have the SBS as an ordinary member server holding some share with data you need to move over to the new server or even some printers that are not yet migrated. In the event viewer at Applications and Services Logs, Microsoft, Windows, Server Infrastructure Licensing, Operational you will see:

"The FSMO Role Check detected a condition in your environment that is out of compliance with the licensing policy. The Management Server must hold the primary domain controller and domain naming master Active Directory roles. Please move the Active Directory roles to the Management Server now."