Licensing and 2012 - reality check

[BJG]

I'm currently being asked to do some stuff I'm doubtful about, so I just wanted a reality check.

 

1) Maintaining a 2012 Hyper-V host with two 2012 VMs at a remote site that I don't think we need.

2) Setting up a new DR 'mirror' system for our main 2019 Hyper-V host...based on Datacenter 2012 R2.

 

The idea is to save licensing costs. I've tried to explain that 2012 has less than a year left, and then all this will need to be replaced with 2019 hosts. And I don't think they can possibly afford it. It's going to be...quite expensive, isn't it...? (No educational discounts here.)

Edited November 15, 2022 by BJG

[pete]

Assuming an aggrieved ex-employee isn't threatening to drive a bulldozer through your server room and this isn't management hedging their bets until plod catches up with said ex-employee.....

 

I'd ask what's driving them to half-arse it in 2022-2023. It could be a contractual clause from a new client that they didn't budget for in 2022-23 and the client's now asking for the evidence.

 

Is management's plan:

 

• FY 2022-2023 - Build 2012R2 DR mirror at $remotesite at X/hrs + incidental costs
  
• FY 2023-2024 - Rebuild DR mirror at $remotesite at X/hrs + licensing cost on 2019 or better
  

or

• FY 2022-2023 - Build 2012R2 DR mirror at $remotesite at X/hrs + incidental costs
  
• FY 2023-2024 - Lie to clients (and insurers) that they have a functional DR site after October.
  

Edited November 15, 2022 by pete

[KK20]

It would be madness to deploy a hyper-v cluster in 2012R2 "today". Why would you be constrained on the hypervisor? I can foresee the guests needing a certain OS version but why the hypervisors? That being said, if you are paid by the hour then by all means put the caveats back and sit back knowing you have an inplace upgrade job in a year time.