1. You have the right basic idea. You can create a query (based on on LDAP query if that is what works for you) and add it as a target to a policy. The policy starts and is always available for computers that match the query. The query is reevaluated periodically (hourly by default). You can set a task to check for new policies that runs periodically on the client. It will check with the server and see if there are any policies to run. If so, it will run them if that's what you want. You can also choose to make that policy optional, so the user can decide when to install it.
2. You can set detection logis within a distribution package to determine whether the package is already installed. For example, if file xyz.exe exists and is version 1.2 or greater, then the package is already installed, so don't reinstall.
3. Yes. See #1.
Thank you very much, I have only one question left then.
Anyone else interested in this, also found this post with the command and switches on the old forums
Used to tell the executable that it is performing an application policy management task.
This switch must be specified.
/ro or /reqonly
Used to indicate that only required policies should be processed. When this switch is
specified the agent will only process required policies, although preferred and optional
policies will be downloaded and cached locally. The user is not provided with a UI that
will allow the task to be cancelled.
/c or /cache
Indicates that the agent should only run pull tasks currently in the cache. This option
has the client omit the policy update from the core server and process only whatever is
cached on the client.
Specifies a timeout for the pull UI. If no user interaction has occurred before the
specified timeout elapses, the pull UI will be canceled and no policies will be processed.
/s or /silent
Used to indicate that the agent should run silently, that is no UI should be displayed by
the amclient application while processing application policies. Whether or not thepolicies
that are executed by the amclient display UI is determined based upon the
command lines provided to the respective applications.
Note if the /s switch is specified and the /ro switch is not specified, the UI for selecting
preferred and optional tasks will be displayed.
Used to specify the bandwidth that is required to exist between the computer and the
APM core for the amclient to attempt to obtain policies from the APM server. The
following values are supported. LAN, WAN, and RAS.
Enable legacy task completion
The smartui switch causes the UI to not be displayed unless there are outstanding tasks to be
performed by the client
Message was edited by: Mike
version 8.8 doesn't have amclient anymore.
In 8.8 you will run program files\landesk\ldclient\policy.sync.exe on the client to kick off the policy installation manually.