I'm in the process of documenting SQL Product keys for SQL installed. The people who installed it either has left the company, didn't track, or lost it/delete it.
I tried/review several methods
- Grabbing it from the install files (https://sqlserver-help.com/2014/06/05/help-how-to-get-product-key-for-sql-server/)
- Looking in the Installation Center, if still available (https://www.faceofit.com/how-to-find-sql-server-product-key/)
- A powershell for SQL 2005-2014 (https://gallery.technet.microsoft.com/scriptcenter/Get-SQL-Server-Product-4b5bf4f8)
- Updated powershell for SQL 2005-2017 (https://gist.github.com/mtrimarchi/f56e3865bad8c4578def6d2c5586a1e6)
The first 3 options has help some of the servers. But when I'm working with SQL 16 or 17 and the option 1,2,3 don't applied.
Using option 4, the script will provide a product key, but it is not correct. At first i though they wrote the wrong product key, is the reason for the mismatch product key (SQL Stand 2016). The person who install had the product key, but the script gave another product key. Then another task, i did a fresh install of SQL Ent. 2017 with a provided product key. It installed, but then ran option 4 powershell (just to test it), it came back with another Product key. I confirm the two keys provided in the Update powershell were invalid.
I assume the updated powershell script for SQL 2016 & 20117 is wrong?? Is there a correct powershell for finding Product key for SQL 2016 and 2017? OR what other method can i get this information if there is no installation file and it is not written down.
On a side note, Not sure were these brought with Microsoft Agreement Purchases, which say no product key needed, but during installation it automatically put a product key. So if we brought 3 licenses, do we just use the same product key 3 times or should there be 3 product key?
