Are you using 8.7? If so you may try to delete the policy cache from the registry and download the policy again.
The location in the registry is:
Thanks Leon it works
I think for testing this is a good solution but how would I handle such a case in a productiv environment? Scenario: Application XY must be installed on the client. If the user uninstalls the application it should be reinstalled by LDMS policy.
Set up detection for one of the main Adobe Reader files in the distribution package.
Sorry, my previous doesn't make sense. Try using a query for the policy. Query for machines that don't have Adobe Reader installed, something like that.
1 of 1 people found this helpful
The problem is a mix of the features we have available in 8.7 and your process.
You deployed a package using a Delivery Method that had Run Once checked in the Type and Frequency.
So you told it to only Run once. So you it ran once. You uninstalled the software, but that doesn't change the fact this it already did "Run once". So it will only run ONCE cause that is what you told it to do.
We store the registry key information so we know that it has run once and since you used a deliver method that had Required - Run Once. We base this information off the Distribution Package ID in vesrion 8.5 through 8.7. So all you have to do to reapply the package is to make a copy of the Distribution Package (cause the copy with have a different Distribution Package ID in the database) and then create a second task to deploy the copy. So you have to have two Distribution Packages and two Scheduled Tasks. If it happens again, you have to copy again.
So obviously the way you want it to work is more desired. Even though you said to only run once, what you meant was "Run once" if it is not installed. And you probably don't want to have to copy a Distribution Package.
In 8.8 we changed this to run off the Scheduled Task ID instead of the Distribution Package ID. We also no longer store the information in the Registry. So now you only need to create a new Scheduled Task.
Thx for your answers, very useful
In 8.8 we changed this to run off the Scheduled Task ID instead of the
Distribution Package ID. We also no longer store the information in the
Registry. So now you only need to create a new Scheduled Task.
YES - Outstanding - Case 00066776 Thank you for listening!
New question: How can I manually force the client to get the policies in 8.8? In 8.7 there was a shortcut... ?:|
Start | Programs | Landesk Management | LANDesk Software Deployment Portal
I tried this but there are no policies...
Do you have any policies targetted at the machine/user? Remember required do not show.
Policy / Always listed for Installation
On the core server the client is pending and it says: Policy has been made available. But nothing happens...
If I have a required policy how can I force the client manually to get it?
Is it machine or user based target?
Restart the policy.
Zman is absolutely correct about the LANDesk Software Deployment Portal. Running that will launch the policy.sync.exe, which will cause the client machine to contact the core and get any assigned policies.
When the sync occurs, the database file on the client will get updated with any new policies (C:\Documents and settings\All Users\Application Data\LANDesk\ManagementSuite\Database\LDClientDB.db3). You could always delete this database and then run \ldclient\clientdbutil.exe /validate and then run the software deployment portal again. But I think this would reapply all policies targeting the machine.
Although the policy sync will update the local client database, it is not actually responsible for running the policy. That is the policy.client.invoker.exe file. See if that is running. There is a new service that launches this executable on startup (Policy Invoker service, something like that). If it's not running, you can sync with the core all you want and the policy won't ever run. This service also takes care of re-creating the client database if it gets deleted or corrupted.