As far as my understanding goes, win_product_facts should provide information about the windows operating system licensing status. This is further supported by the logic to retrieve the product key, which only results in one product key, the one of the windows operating system. Finally, the returned facts description also indicates that ansible_os_license_edition, ansible_os_license_status and ansible_os_license_channel should contain a string regarding the windows operating system licensing state.
However, I have noticed that when microsoft office is installed, win_product_facts actually sets ansible_os_license_edition, ansible_os_license_status and ansible_os_license_channel to an array which contains information about both windows and ms office.
The reason for this is the Get-CimInstance SoftwareLicensingProduct | Where-Object PartialProductKeycommand, which can return more than one result. It would be sensible to append a Where-Object Name -match Windows filter.
SUMMARY
As far as my understanding goes,
win_product_factsshould provide information about the windows operating system licensing status. This is further supported by the logic to retrieve the product key, which only results in one product key, the one of the windows operating system. Finally, thereturned factsdescription also indicates thatansible_os_license_edition,ansible_os_license_statusandansible_os_license_channelshould contain a string regarding the windows operating system licensing state.However, I have noticed that when microsoft office is installed,
win_product_factsactually setsansible_os_license_edition,ansible_os_license_statusandansible_os_license_channelto an array which contains information about both windows and ms office.Using the examples from the module page:
The reason for this is the
Get-CimInstance SoftwareLicensingProduct | Where-Object PartialProductKeycommand, which can return more than one result. It would be sensible to append aWhere-Object Name -match Windowsfilter.ISSUE TYPE
COMPONENT NAME
win_product_facts