Hello, I’m considering how to move a windows 2012R2 VM, currently running under a headless instance of Windows 2012R2 Hyper-V. Naturally the owner doesn’t want to spend a lot of money. The server is running an small SQL database, 300GB of file shares and AD.
The company is working on selling their business to a competitor.

It’s a small office, 4 workstations. My initial opinion is not to take the workstations off of AD. But that’s an option. If we were to migrate the VM, I’m guessing it would work as well on a beefy workstation, or micro server as this old HP server. (Minus redundant power supplies and noisy disks.)

They don’t want to pay to upgrade Windows, and we stopped short of resolving some HP server issues that would require a firmware update. The server has a history of freezing up.
And backups are by a sketchy iteration of Backup Exec that I don’t trust. (Yes I tried downloading Veeam and the download wedged the old server.)

I think there are four options:

  1. Take them off AD and migrate the SQL database.
  2. Keep the old server, fix the firmware issues, and solidify the backups.
  3. Migrate the Windows machine to a micro server and figure out licensing issues.
  4. Let them find their own way.

Having laid this out, as they tend to buy non managed solutions for antivirus, I’m getting more fond of option #1. Option #2 is not their favorite. Option #4 family - not sure I can walk away.

What would you think?

5 Spice ups

If they are to be bought out by someone else, why not option 5, let the new buyer deal with the issues.

Presumably the new buyer is bigger or are they buying them out because the existing owner is retiring?

Consider migrating the machines to Azure/Entra and look at the options for SQL - what version is it? Can this be cloud hosted by the vendor of the product that uses this?

5 Spice ups

I’m guessing the fact that they’re not done with the purchase yet has #5 off the table for now…if the potential buyers are an AD shop, and they likely are, it’s in the companies’ best interest to make this smooth as possible. Look into #2, fixing the hardware and backups as that’ll bring the most “value” to the company buying yours out.

2 Spice ups

Take a new micros server or any workstation and do P to P conversion of machine. Your problem will be solved

2 Spice ups

BTW what is “headless server 2012R2” ?

But if they are family, then one of the first things I would do is understand why they need

  • 4 workstations ?
  • Domain Controller ?
  • SQL database (there is no mention of application) and SQL on DCs ???
  • What type of files ? 300GB is not exactly small ?

Then I would work on clearing up data that is not business related, especially in files & emails ?

2 Spice ups

This whole thing screams for Azure VM.

Honestly, I’d put the VMs into Azure, get those four people a M365 Business Premium Licence to get Entra and call it a day.

Do it paid monthly so the coming company can cancel the plans as they see fit.

2 Spice ups

But SQL in Azure ??

2 Spice ups

Yeah, why not?

2 Spice ups

Then you will need to deep dive into their current SQL licenses, OS licenses etc…and SA requirements & CALs.

Cloud licenses may not be as forgiving as on-prem…

2 Spice ups

Well, it’s four clients and a Server. If you get a good Reseller, they’ll figure that out for you in 10 minutes

3 Spice ups

The SQL can run on SQL Express, but it has to be on the local network according to their tech support.

2 Spice ups

They are indeed clearing up unrelated data.
It’s running Server Core. The database is part of the file system, as well as a lot of docs.
I’m seeing this after many years of evolution. I’m not sure the company was ever large enough to need a DC, but they didn’t need a second server to run a smallish SQL database.
It may be that they had email in house in the past, but they’re on Office 365 now.

2 Spice ups

That’s what I thought as well. Thanks!

2 Spice ups

Unfortunately, they have GoDaddy Office 365, which it seems is not compatible with Azure AD.

2 Spice ups

But what applications or servers need the SQL (or express) ?

But what DC version is that ? Coz by right you “cannot” run SQL on DCs (highly not recommended) and it is not recommended to use DCs as file servers ?

I would have recommended installing SQL on the application severs itself ?

I would think not to complicate matters by introducing more stuff ?

If they are on O365 via 3rd party subscription, likely is that there is already a ADC or DC on the provider (thus different Windows Domain, one for local machines & users, the other is for O365 which is controlled by the provider).

2 Spice ups

Hiya, Yes I know its not best practice to install SQL server on a DC. Or to have only one DC!
It wasn’t my decision. But it does work. There is only one physical box, and it has only one VM.

I think we’re going to just address the firmware issues and upgrade the backup software.
The new owner can decide how they want to integrate everything with their operation.

Just for the record, I understand that joining a PC to GoDaddy as you would with Azure AD is not viable, er, as of 2023…

Thanks for batting this around with me!

2 Spice ups

Good luck! If you’re stuck on something while addressing the issues at-hand, we’re here to offer advice. Throw as many bandages as you can on it, hope the new owners are willing to address it correctly (assuming you stay) after the buy-out!

2 Spice ups

But one of my points is that what is using SQL (or express) ? Coz as for smaller installations as to why the SQL is not installed on that application ?
For example when we have like ERP or eHR or AV or Inventory & backup solutions, it usually comes with SQL or SQL express (or some other DBs) ?
SQL is not exactly “cheap” (especially if compared to SQL express) ?

Aside to asking why you need SQL (or SQL express), one alternative I would usually recommend to SMBs is probably the Synology NAS as it can run Domain Controller (and other out of box services) ? But the only issue is that it cannot run SQL or SQL express.

I think the LDAP or other Domain Services may not be offered by 3rd party MS365 or O365 providers.

2 Spice ups