Skip to main content

How To Upgrade Windows 2012/2016 to Windows 2019

1. Normally, i'm not a fan of in-place upgrades, depends on organization requirements. A clean install with scripted configurations is always better.

2. Here is the lazy way for those who have no choice...

3. Snapshot the VM (VMware, Hyper-V, KVM...whatever it is).

4. Add the iSO to the VM (Don't bother booting from the BIOS and running the ISO that way). It will just tell you to boot into the OS anyway. (thank you Microlazy)

5. Open a CMD or Powershell as an administrator.

6. Adprep is now located under "support\adrep\" on the 2019 disk. (Domain Controllers Only)


7. From the CLI run the following: adprep.exe /forestprep and then click "C"

8. Domain prep: adprep.exe /domainprep /domain

9. Next upgrade the GPO Domains: adprep.exe /domainprep /gpprep /domain

10. Now run the upgrade installer or relaunch it and "Continue where I left off"

11. If it barks about space. Don't add. Reduce. Run this command to wipe out and clean all of the logs: for /F "tokens=*" %1 in ('wevtutil.exe el') DO wevtutil.exe cl "%1"

12. Delete data in the C:\Windows\WinSxS folder over 2 years old (watch GB's drop off!) (FYI. this is the Windows Update folder. You don't need 1/2 of the crap on here) PRO NOTE: You should be doing this for your VM templates before you start using them.

13. c:\dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

14. c:\dism.exe /Online /Cleanup-image /StartcomponentCleanup

15. Post upgrade. You will be prompted for the new MAK Key. Run the following from the command line first as administrator: slmgr -rearm and reboot the server with shutdown /r /t 00 (takes it down and reboots it immediately). Then activate with slmgr -ipk "XXX-The MAK Key"

16. If you get an error. Clear the registry of the key, clear the OS and then reboot the OS. After that activation should work fine via the activation GUI.

17. Commands:

slmgr -cpky && slmgr -upk && slmgr -rearm

shutdown /r /t 00 (shutdown and reboot now)
Reference for WinSxS Cleanup:

Popular posts from this blog

How to Login to AWS using CLI with AzureSSO through Azure Active Directory

Testing on Windows 10 Release 1909  Prerequisite (Install Visual Studio Code and the AWS CLI if you don't have it already installed and your Azure Active Directory is already configured and processing authentication) 1. Install Node.Js (Use the LTS Edition/Version) 2. Check the node version in PowerShell or Windows Terminal: node --version && npm --version 3. npm install -g aws-azure-login *install will take about 15-20 minutes. Be patient and let it finish.  4. Configure your profile aws-azure-login --configure --profile=<<Name of your profile>> Example:  aws-azure-login --configure --profile=migrationking Pro Tip: It installs the profile on your machine under ~/.aws/config . You can edit the file with Visual Studio Code or Notepad++ #This will prompt to Enter the Azure AD details *** Azure Tenant ID: << Enter the Azure AD Tenant ID from the Azure AD application configuration for the AWS Account to be accessed>> Azure Tenant I

How to Fix /storage/core filesystem Out of Disk Space Error on VCSA 6.0U1

How to fix the error of " The /storage/core filesystem is out of disk space or inodes" Step 1: Login to the new VCSA 6.0U1 HTML5 web client. https://ip address:5480 Step 2: Enable SSH and Bash Shell Step 3: Login as root and type "shell" at Command> shell Step 4: df -h (Check if it's out of space) /dev/mapper/core_vg-core               50G   50G     0 100% /storage/core Step 5: Stop the services of VCSA:  hostname: # service vmware-vpxd stop hostname: # service vmware-vpxd status (make sure it is stopped) Step 6:  cd /storage/core Step 7: rm -rf *.tgz ( be CAREFUL this in the wrong directory and you will be retrieving from a backup .) If you need help. Go to Cybercity ( )  Step 8: service vmware-vpxd restart Step 9: history -c Step 10:  Refresh the browser (https://ip address:5480). Now it's all green VMware KB

VMware Tools ISO Does Not Exist

1. You attempt to Install VMware Tools and you get the following error: The required VMware Tools ISO image does not exist or is inaccessible. vix error code = 21001 Unable to install VMware Tools. An error occurred while trayin got access image file "/user'/lib/vmware/isoimages/windows.iso" needed to install VMware Tools: 2 (no such file or directory). Please refer the product documentation or KB article 2129825 for details....blah blah blah you get the point. First...that KB article is wrong. It's 1036810: 2. Go to the latest VMware Tools of your OS (You don't need to be logged in): 3. Download the ISO and then WinSCP the file or whatever method you want to use to copy the file to /usr/lib/vmware/isoimages/ The quick and easy way is to just mount it and then install the VMware Tools. If you want to get gritty! Follow on! 4. If you don't