Hello,

I am trying to deploy enterprise vault addin which was deployed successfully on all the test machines.

Now when trying to do this for a collection of machines based in US, this is coming up with the below error in execmgr.log

Could not find the policy in wmi for package

I have tried recreating the package, program, advertisement, reinstalling the client but everything works on the test machines based in a different region but it does the same thing for US.

Just for a try, i used "Run with user's right"  in package program but it still doesn't work. 

Please suggest as this seems to be strange for only happening for one region and not another for the same package.

The error described here in the link is exactly the same one except that I am using Program for deployment and not TS.

https://social.technet.microsoft.com/Forums/en-US/db13db4f-8b92-4d20-ac01-98d366c228eb/error-could-not-find-the-policy-in-wmi?forum=configmanagerosd 

Thanks

• Edited by Vikram Midha Tuesday, March 24, 2015 9:12 PM

Hey Eswar,

Yes, I am sure that the execution was for the same package. The error above was noticed in execmgr.log. When the deployment was done for the package, it gets stuck at the step

Policy arrived for parent package ..........

Raising Client SDK event for class.........

So, after waiting for few hours, I tried to rerun the advertisement and it comes up with the original error as per my original post. Strangely this is happening for all the machines for the US region but it works for another region.

The policy does seems to be arriving looking at the above logs but its something which is blocking it and putting on hold maybe.

No its a standalone primary.

By region as I mentioned originally, Its not working for machines based in US but when deployed to another region collection, it works like a charm.

With further testing, I am able to see that for some reasons, the packages deployment aren't working but Application works fine.

I test deployed application on US machine and it worked right away but when tried deploying a package, it was stuck at the same step where it received the policy and just sits there.

Another test was  made on another machine from a different site, the same package worked fine here.

Seems strange but for some reasons, packages are not getting executed for US while application does. While for every other sites checked, it behaves normally.

What could be the issue here ? Anything I could check ?

Please assist.

any troubleshooting done on the wmi part looking for policy information etc  on client side? if this is happening on all pcs across the region(US),then i would look at server or management point to troubleshoot.can u try recreating the package and see if that solves the issue ?

this issue is happening for all packages in US region ? if only for this package,try re-create package.

The WMI seems OK for clients as the error is same for all the clients in the region.

Yes, its so far happening for all the PCs added to the collection.

Already did recreating the package, program, advertisement, redistribution etc. but it didn't help.

What exactly can I check for Management Point?  The policy reaches the clients fine as mentioned but it gets stuck on it and this is only happening for US region so far while other works.

Hi,

Based on research, expired advertisement may cause the problem

https://social.technet.microsoft.com/Forums/en-US/bad7be4e-774e-4f4a-b56e-ea335cc2f73d/could-not-find-the-policy-in-wmi-for-package?forum=configmgrosd

https://systemcentertipps.wordpress.com/2014/11/21/sccm-2012-get-expired-advertisements/