Hello, we are looking to shift our Windows 10 clients from OS MAK and Office 2016 MAK to KMS.
I could really use some help on relevance for this:
Running BigFix 9.5.6.63. -thanks!
I’m curious, what is the need to go from MAK to KMS?
There are a few options.
One is to run a script that gets the current state and outputs the results to a file, then read that back with relevance. This is always available as a work around, but not ideal.
As for a relevance option, the info might be in in the windows registry, but it is most likely in WMI, both of which can be queried with relevance. If you can find what you need in RegEdit or in WMI Explorer or similar and share it, then I can help write the relevance for it.
There is existing content to set a KMS server. There is also content to set the KMS key for Windows that tries to figure out the KMS key dynamically but very likely won’t work in all cases without testing: https://bigfix.me/fixlet/details/23579
Good morning and thank you for taking time to look at my issue.
We are done piloting Windows 10 Enterprise and Office 2016 Professional Plus.
We are small enterprise shop, but the seat counts exceed the limitations of seat counts in the MAK keys.
We have flipped future deployments of our custom images to use KMS, but the existing clients need to be changed over from MAK to KMS to bring them all into compliance.
If I can get two separate relevances, one for OS and one for Office, then I can use that to create actions to switch clients to KMS from MAK. If it’s easier, I know the MAK keys used, so either returning “MAK” as activation method or partial product key = will work too. We are using Active Directory KMS for both.
For actions, I can use:
For OS:
From "C:\WIndows\System32"
cscript.exe slmgr.vbs /ipk "generic kms OS key goes here"
cscript.exe slmgr.vbs /ato
For Office 2016:
From "C:\Program Files (x86)\Microsoft Office\Office16"
cscript ospp.vbs /inpkey:"generic kms office key here"
cscript ospp.vbs /act
Thanks!
Got the OS piece working.
Relevance:
(version of client >= "6.0.0.0") AND ((exists true whose (if true then (exists (operating system) whose (it as string as lowercase contains "Win10" as lowercase)) else false)) AND (exists true whose (if true then (not exists elements of intersection of (set of following texts of lasts "-" of tuple string items 1 of ("Microsoft Windows 10 Enterprise, NPPR9-FWDCX-D2C8J-H872K-2YT43"); set of (string values of selects "PartialProductKey from SoftwareLicensingProduct WHERE PartialProductKey is not NULL" of wmi))) else false)))
Actions:
waithidden cmd.exe /C cscript c:\windows\system32\slmgr.vbs /ipk NPPR9-FWDCX-D2C8J-H872K-2YT43
waithidden cmd.exe /C cscript c:\windows\system32\slmgr.vbs /ato
Working on Office Portion now.
This should be a simplified relevance for the product key part:
not exists string values whose(it contains "2YT43") of selects "PartialProductKey from SoftwareLicensingProduct WHERE PartialProductKey is not NULL" of wmis
You might need to add the following to your action for 64bit systems:
action uses wow64 redirection {not x64 of operating system}Thank you for the cleaner relevance. Could still use some help on the Office 2016 relevance. Here is the generic KMS client key we are using: XQNVK-8JYDB-WJ9W3-YJ8YR-WFG99. Does BigFix offer something for Office 2016 similar to what you found for the OS for Win10? -thanks!
It isn’t so much bigfix as it is finding the info needed in WMI or Registry then querying it. BigFix provides the interface, it is Windows itself that provides the info.
This is old, but might still work: https://www.bigfix.me/analysis/details/2994711
not exists string values whose(it contains "WFG99") of selects "PartialProductKey from OfficeSoftwareProtectionProduct WHERE PartialProductKey is not null" of wmi