Upgrading Windows Server -Windows Cannot Find the Microsoft Software Licensing Terms

 

When attempting to upgrade from Server 2012R2 to 2016 or 2019 I received an error similar to this one. It may even say Windows 7 or Windows 10 going to a server version which makes you scratch your head.

Make sure you have a valid backup available if possible snapshot as needed

You can review the upgrade logs here:

https://support.microsoft.com/en-us/topic/log-files-that-are-created-when-you-upgrade-to-a-new-version-of-windows-9ec8aa31-0cc1-a0b2-2d98-e9c6714349b9

Make sure NO GPO’s are applying to the server that could impact licensing

If using KMS you can also drill down into its configuration but that’s a deeper dive than we needed:

https://learn.microsoft.com/en-us/windows-server/get-started/activation-troubleshoot-kms-general

Create a local Administrator instead of a domain Administrator

Install Windows Updates available and reboot

Disconnect from network

Attempt 1) Logon as local Administrator and attempt Upgrade

Attempt 2) Try removal from the domain temporarily and repeat reboot and upgrade attempt off network

Attempt 3)Open a CMD prompt and run the following and repeat reboot and upgrade attempt off network

 secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose

  

The above steps have permitted problem upgrades to complete 90% of the time

Don't forget to clean up your snapshots or rejoin to the domain after if necessary.

Note: If attempting to upgrade from Core to GUI you will have to convert from Core to GUI on the current OS first.  I have found that many of those fail and will not let you convert on the current OS. Post upgrade conversion from Core to GUI is a no go from my experience. In most cases a new server was built in the needed OS and applications/services transferred.  

Comments

Post a Comment

Popular posts from this blog

Office 365 Deployment Tool Office Download fails “Could not Install”

Image
Problem: you run the setup.exe /download download.xml and fails immediately with “Couldn’t install” You make sure all the settings are correct (see other blogs) and find nothing wrong Solution: Change drives and run it as an administrator again. For example above i am in the F:\OfficeDeploy directory which is the same directory I have the download.xml directing the download to. If i Change to the c: and run the same command again it works The Office Data folder was created and updated as shown below:
Read more

FRS to DFSR Post Cleanup “File Replication NtFrs Stopped”

Image
After successfully migrating from FRS to DFSR you get the File Replication NtFrs service is Stopped error on the local servers AD DS Services list. In the Event logs you may see Event id 13575 13577. You can confirm your migration completed by opening a cmd prompt as administrator and typing in: dfsrmig /getmigrationstate After your migration to DFSR is completed and you have given your servers ample time to propagate this service is no longer required. Since it is set to “Automatic”, as shown below” it shows in logs as a false positive error. Edit the File Replication Service and change it to “Disabled”, as shown below: Once it is listed as “Disabled” it will no longer show in the Console as an “error” Note : it may take some time to clear from the active view
Read more

Domain Migration SubinACL /Migratetodomain How To:

Caution : DO NOT run this on Domain Controller C:\ and only run on roaming profiles folders, or my docs shares day of migration to avoid ownership change issues. Confirm Domain trust is in place and users and groups have been migrated Test ping of olddomain.org from new domain Test ping of newdomain.org from olddomain Add newdomain.org domain controller host records to olddomain.org including reverse DNS records Confirm the user running the app is a domain admin in BOTH domains Download SubinACL here: http://www.microsoft.com/en-us/download/details.aspx?id=23510 /Migratetodomain- command will add the permissions of the new user to the old files and folders for example if jimbob@olddomain.org was migrated to the new domain jimbob@newdomain.org and you run the command below any file or folder in that path that has jimbob@olddomain.org will add Jimbob@newdomain.org with the exact same permissions. This is a safer way to migrate by keeping the old and new permissions intact while a
Read more