If the final selection to start deployment was No then Application Manager for WSUS will automatically launch. The first view is the Software page which basically displays the selected third-party software and their statuses. At this point, before the first deployments, we want to make sure that the defined configuration is correct. You can do that by clicking the WSUS Integration.
Configuration Areas
Service status
Service status sets whether automatic software deployments and updates are enabled or disabled.
Server settings
The WSUS server itself can be configured. Application Manager supports both a local and a remote server.
Server certificate
A server certificate is required in order to publish third-party software to the WSUS server. If there's an existing certificate it can be used by importing it. If there's no certificate, one can be generated in AM. After the certificate is created, it can be exported by choosing Export.
The certificate used in AM must be also stored to workstations in order to deploy third-party software to them. The certificate must be stored into both Trusted root certification authorities and Trusted publishers containers.
We recommend to do the certificate deployment by using Group Policy.
Installation approvals
Installation approval is a generated view from WSUS groups and a number of third-party software allocated to them. These groups can be navigated by clicking on them. This will populate the Computer group settings.
In this view you can select which third-party software are targeted to specific groups and what are the time settings for the deployments.
Wait time is the time at which the selected third-party software will become available to computers in the selected group. The time will start elapsing from the moment when we have published the new version of a third-party software and it's downloaded to the server.
It's important to acknowledge that the wait time is an artificial delay option made possible by AM. WSUS doesn't by default provide a wait time but only a deadline. For this reason, updating wait time configuration for a deployment is effective next time when a new version of third-party software is published.
Deadline after wait time is different from wait time. Instead of software becoming available, installation to computers it will become a required installation. Deadline-time will begin to elapse from the moment when wait time has completed.
Optional install only works for Windows 7. A deployment of this kind will make a third-party software available but not required.
