Skip to content

Instantly share code, notes, and snippets.

@scyto

scyto/proxmox-migrating-dc2.md

Last active September 22, 2023 23:18
Show Gist options
  • Save scyto/f8b0a1b06ae62f03db3182f8bd23abda to your computer and use it in GitHub Desktop.
Save scyto/f8b0a1b06ae62f03db3182f8bd23abda to your computer and use it in GitHub Desktop.
Download ZIP
Raw
proxmox-migrating-dc2.md

Notes on Migrating Windows Server Core 2019 based AD domain controler

  1. run a chkdsk - you want to be sure the drive is good
  2. DCdiag - run it, resolve any issues (you can ignore the 24 hour error message if thats the only one) othweise fix stuff before you move
  3. my DC had one two werid errors, decided to upgrade to Server 2022 core before moving as it may explain some things.
  4. tip if on server 2019 core use the command DISM /online /Get-CurrentEdition to check version - if it says standard only try and upgrade to 2022 standard core, not datacenter (or you will get really weird setup errors about product keys late and a roll back) and literally there is nothing on the internet to tell you what error means - took me 3 failed attempts to figure out i was using a datacenter key on a machine that needed a standard version to version upgrade..
  5. to shrink or not to shrink, here is the thing, if you import a VHDX into proxmox it uses thin provisioning for the new RAW disk (even if it reports the internal size of the raw disk in the UI, it only is stored on ceph as a thin provisioned version) as such there is really no point in shriking or compacting a VHDX.... but what if you have OCD about this...
@scyto
Copy link
Author

scyto commented Sep 22, 2023

whats funny is when you google the error lots of people hit, not once did i seen anyone point out they used the wrong command - hahahahaha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment