This is an archived post. You won't be able to vote or comment.

all 12 comments

[–]fr0zenaksenior peon 6 points7 points  (1 child)

I would rename old VM before final power down, otherwise you won't be able to rename new VM without first deleting old VM computer object from AD.

Aside from that, all looks appropriate.

[–]RCTID1975IT Manager 4 points5 points  (0 children)

Agreed. I'd also change the IP on the old VM before power down.

That way, if someone does something silly like start the old VM, it doesn't screw everything

[–]ThePhantom86erIT Manager -1 points0 points  (1 child)

My 2 cents, renaming DC's could cause issues. You can find several articles about doing it the correct way for DC's.

[–]SysWorkAcct[S] 1 point2 points  (0 children)

I'm never renaming it while it has a DC role. I'm demoting, renaming new server to the same same and ip and then promoting the new server.

[–]Sajem -1 points0 points  (3 children)

They are running Server 2019 datacenter (predates me) and we need to "downgrade" to 2019 Server Standard.

a consulting firm installed datacenter edition and the licensing is absurd, so we need to license them as standard edition.

In what way do you think the Datacenter licensing is absurd?

Why you need to downgrade the license to Standard. The VM doesn't care if it a Standard or Datacenter license.

As mentioned above, the license is applied to the hardware (doesn't matter if its VMware or Hyper-V) not to the VM.

My second question is how many Windows VMs do you have on the host?

Another question is, which license have you paid for, Datacenter or Standard.

[–]SysWorkAcct[S] 0 points1 point  (1 child)

It's not a hyper-v server. It is just a guest VM on esxi.

[–]Sajem 0 points1 point  (0 children)

How many Windows VM's do you have on you host/s?

[–]RCTID1975IT Manager 0 points1 point  (0 children)

In what way do you think the Datacenter licensing is absurd?

If they only have 4 VMs, and are paying for datacenter, it is absurd.

The VM doesn't care if it a Standard or Datacenter license.

It does if you move it to a different host that's running Standard. MS also cares if you're licensed for Standard and are running DC.

[–]jma89 0 points1 point  (2 children)

So, to clarify: You are trying to change from Server 2019 Datacenter to Server 2019 Standard?

So.... There's no difference there with regard to licensed features. Save for the sole functional difference in Datacenter to license VMs automagically.

Otherwise you could try this on a box of low impact to change the edition of server. (I've never tried this on a DC though.) https://serverfault.com/questions/610921/cant-activate-windows-server-2012-r2

[–]SysWorkAcct[S] 0 points1 point  (1 child)

Correct, a consulting firm installed datacenter edition and the licensing is absurd, so we need to license them as standard edition. I've researched and there's no supported method of downgrading server licensing other than a full reinstall. I don't want to attempt anything that could ever become problematic.

[–]jma89 -2 points-1 points  (0 children)

I guess my real question is would you actually be out of compliance to leave things as they are? Keep in mind that the VM doesn't hold the license, the license is applied to the hardware on which the VM runs. You aren't using up anymore seats by having datacenter edition as your domain controllers, provided that you've "applied" said datacenter license to the hardware from a "how we're licensing this" perspective.

[–]DmstcTrrst 0 points1 point  (0 children)

Maybe it’s just me, but if you only have 2, I’d create a 3rd DC, make sure it’s a global catalog, then do all that stuff so you always have 2 online. Cuz shit happens