You can use the Software Distribution Portal.
That works great for items that are optional but not for those that are forced from what I understand and from what we are seeing. Is there any other way to trigger the installs?
And where are those darn log files?
Also, anyone know where/how to find all the switches for policy.sync.exe?
Don't have a Core or Client in from of me, but if you configured your agent to have the Policies launch at startup look in the Run Registry key for the command.
"anyone know where/how to find all the switches for policy.sync.exe?"
I dont think it has any. I think it just runs and syncronises the server and client policies. The important word here being syncronise, as opposed to download. Very cool. Try it in conjunction with a package with an associated uninstall package! Not in scope anymore.. then remove the software. Combine that with AD queries and you have a very interesting set of tools I reckon.
Actually policy.sync.exe is only for synchronizing. And policy.client.invoker.exe will run the policy.
So if we wanted to run a schedule at night that would trigger a policy delivery at a specific point in the script how would we accomplish this?
The standard local scheduled task that LANDesk adds simply runs policy.sync. Have you tested this to be certain it does what you need? If it needs more than one step, then maybe set two commands separated by a delay that would launch the sync, and then the execute.
There seems to be a lot of confusion as to what the new components do:
Might be a good time for a Ty or Rex diagram/doc Definitely more to deal with than the old amclient.exe.
Hey, lets just run the lot of them. Something has to work. Whats the worst that could happen?
The author accepts no blame or responsibility for the previous statements and directs any legal claims or compensation payments to be paid by the Nigerian Prince that keeps trying to give him $6,000,000.
Mark Star - http://www.marxtar.com
Home of Power State Notifier & Wake-On-WAN for LANDesk