Wednesday, February 12, 2020

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:

Thursday, January 9, 2020

AWS Storage Volume iSCSI CHAP Authentication for Windows Server 2016 and VMware iSCSI Datastores

1. Create the VM on your VMware Platform for the AWS Storage Volume Gateway (YouTube:

2. What is not documented anywhere in AWS Documentation is that when you're configuring the ISCSI connection. You have to use the Initiator name that you typed when you configured your CHAP Authentication. Here's how you do it.

Open Notepad or whatever program you use to save notes and paste the Initiator Name and your password so you have it.

3. Go to your Windows Server 2016 box (This is the only OS I tested this on for now) and fire up iSCSI Initiator and then click on connect for the volume your working with.

(iSCSI Initiator Setup: or just YouTube it)

4. Add the Initiator Name next to Name under Enable Chap Log On (make sure this box is checked).

5. Format your drive in Disk Management for Windows Server and that's it folks.

6. This is also the same for VMware CHAP authentication for the Storage Adapter Authentication of ISCSI.


Saturday, January 4, 2020

Install Windows Remote Server Administration Tools on Windows 10 1909 (RSAT)

Microsoft has now included the Windows Server Remote Server Administration (RSAT) tools in Windows 10 release 1909 as a FOD (Feature on Demand).

Instead of playing around with the Windows UI.

Launch Powershell as an administrator and run this command

Get-WindowsCapability -Name RSAT* -Online | Add-WindowsCapability -Online

It will run for about 5-10 minutes.

It takes forever so you can just use this script from Martin Bengtsson: