PENDING Issue with 14a report in SCCM CB

[sumeet78]

Hi,

Facing the issue with 14a report not listing the Windows 10 Enterprise E3 and E5 license information properly.
In the MVLS file it is mentioned as Windows E3 and E5 license but the info captured by SCCM as inventory is Windows 10 Enterprise.
They dont match hence the issue with the values not getting listed properly.
Its the same with Office 365 E3 and E5 license.

Has anyone else also faced the issue.

We had logged the case with Microsoft for one of our clients and they took 2 months and then told that its a BUG and it will be getting resolved by end of the year release.

Can anyone else also confirm if they have faced the issue.

Thanks and Regards

Sumeet Shekhar

 

[Prajwal Desai]

What's the version of SCCM that you are using ?.

 

[sumeet78]

It was SCCM 1706 initially but now we are at 1802 but still same problem.

 

[Prajwal Desai]

Has MS confirmed it's a bug in 1802 as well ?. Let me know and I can check this with SCCM product team.

 

[sumeet78]

We were working on 1706 and even after upgrading to 1802 still same issue....

I am pasting the email communication from MS engineer regarding the same......


"Hello Sumeet,

Thanks for your time on remote session yesterday.

As we discussed while troubleshooting this issue, there is a newly reported known issue with Asset Intelligence Sync that is causing the issue for the Win 10 Enterprise machine information not populated in the License 14A - Microsoft Volume Licensing reconciliation report.

During the troubleshooting on session, we discovered the following :

We had the AI Sync point role in offline mode and hence the Win 10 Ent product information was not populated in multiple SQL tables earlier.

We got the AI sync point role reinstalled and got the Sync to work again and Service into Online mode.

Most of the SQL tables were undated with Win 10 Ent product information after the successful sync was completed.

We found the value for Win 10 Ent product was not getting the information updated in the SQL table : LU_LicensedProduct after a successful sync for AI role was completed.

The LicenseID value for the Win 10 Ent was listed as “-1” in another associated SQL table named LU_SoftwareList.

Due to the incorrect LicenseID getting populated for the Win 10 Enterprise product, the report 14A is unable to fetch the information from SQL tables.

This issue with the incorrect LicenseID from AI sync has been reported to the Microsoft product group and we expect a solution for this reported issue in near future from the product group.

We would be communicating the information, as soon as it is available with us to help you resolve the issue with AI – 14A report. Unfortunately, we currently do not have any workarounds available for this issue.

Please feel free to Email me if you have any queries.

Thanks again for your time and cooperation while working on the issue.

Best regards, "

 

[Prajwal Desai]

I will get back to you on this soon..

 

[sumeet78]

Hi Prajwal,

I know you would be busy with some work ... but just wanted to know if you have got any information regarding the issue being a bug as suggested by MS.

Thanks and Regards

Sumeet Shekhar

 

[Prajwal Desai]

No @sumeet78 I haven't got any update from MS team. I will check again with them.

 

[Prajwal Desai]

Here is the response that i got "We are still looking into the E5 verse E3 issue, but the second issue we believe was fixed around a month ago (having the product marked as licensed product in LU_SoftwareLIst). Can you send the softwarepropertieshash for the row that is not marked licensed but should be. "

 

[sumeet78]

Thanks for your response..Prajwal.

Can you let me know what they mean by "We are still looking into the E5 verse E3 issue, "
Correct me if I am wrong...does it means that Windows 10 Ent License information will still not be matched with the MVLS file as it contains E3 and E5 entries.

 

[Prajwal Desai]

You may be correct Sumeet. I will ask for the clarification again, this will take some time. Meanwhile if you have that ticket open with support, you can refer the above response and check what exactly is the issue and when will it get fixed.