Hi, I'm testing an LD 9 core right now (also with Patch Manager, but that's a side issue to this, really). The vast majority of my machines are behind a Management Gateway and are firewalled, which means that push deployments often are not an option. I use policies and policy supported pushes all the time. Under 8.8 SP3, the feedback I got from policies was decent--sometimes machines wouldn't leave the active state, or wouldn't ever sync a policy down, but for the most part it worked. Under LD9, it's much worse.
5 days ago, I created a policy to install Silverlight on my test group of 27 computers. I know that it was not installed on any of those computers before now. On 5 of the machines, LD9 reported that the installation failed, and gave me a return code of 1514 or 1512 (these return codes don't seem to correspond to anything I've been able to find online). 18 reported "The action completed successfully" with a return code of 0. Good. 2 reported "Successfully completed installation of package" with a return code of 16385 (!). 2 merely say "Policy has been made available" with a return code of 1001.
However, 22 are listed as active, 5 are listed as failed. I've cancelled the running of the scheduled task, and they're still sitting there like that. Wha?
Further, if I run a query on silverlight, all 27 show as having it installed.
Using policies with Patch Manager is even worse. I did a test run yesterday, and I have 1 pending, 4 successful (saying "The client does not support batch file packages"), and 22 failed.
On other tests, I've seen the local policy.sync.log reporting no packages available for multiple checks, while on the core, there's a package, sitting there pending, which clearly has never been run on the client computer.
This is all very frustrating to me. Anyone else seeing this sort of issue, or is my core just special again?