Rules are created on the client by policies, if the policies are not downloading the rules will not create. This would suggest their is a problem with your MP or within sql itself.
If both look healthy, I would open the support call with ms.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
@AllenLiu-MSFT I have found another issue for you to deep dive into ;-)
Before raising an official incident with Microsoft, first let's ask the community first.
In short; Configuration Manager Software Metering not functioning correctly.
Details.
We have 2 issues. Some clients do not receive the Software Metering Rules, the WMI space is just empty, PolicySpy.exe:
The next issue, when a client receives the "class CCM_SoftwareMeteringRule" it is only partly. We made more than 150 rules in de MECM Console, and only 14 rules are applied. If we make a very simple new rule, it won't be applied. nowhere.
We have tried all the obvious thing, like uninstall the Config Manager Client and installed it again. Repair WMI, etc.
Of course this behavior is very visible on the client.
mtrmgr.log:
Client Settings:
And the Metering Rule itself:
Note, Some clients, with exactly the same client settings do work. But only partly. 14 rules. Not the 150 we defined
Rules are created on the client by policies, if the policies are not downloading the rules will not create. This would suggest their is a problem with your MP or within sql itself.
If both look healthy, I would open the support call with ms.
The issue was 2 corrupted rules.
So the WMI namespace couldn't update according tot the PolicyAgent.log
The rules were created by pointing to the exe from the rules wizard. There were invalid characters in the version field. Disabling these 2 rules fixed the problem.
We will raise a support ticket with Microsoft