The below screenshot should be similar across various versions of SCCM of the window for a custom package deployment where you can specify the various command line options detailed above. Using SCCM to push the client installer should be pretty straight forward.

the client installer on either Mac or Windows can be customized with site specific preferences for silent execution when logging onto the network - consult the documentation notes below.

the client installer on Windows can be run with command line options - consult the documentation notes below.

Note: the 'Add/Remove' programs control panel should be used when installing KeyAccess in order to ensure that 'Install mode' is enabled.

an 'Application server' such as WTS (Windows Terminal Server) or WinFrame may be used to serve out the KeyAccess client along with server hosted application programs - consult the OS Details appendix for WTS support information.

SCCM) can be configured to install or upgrade the KeyAccess client files and settings - consult the complete File List document, the cloning document, and the OS Details appendix for details concerning client components and settings. a general purpose file deployment tool (e.g.KeyAccess client components can be installed as part of a cloned image for new computers - consult the Cloning document for important cautions and details.Note: deployment of the KeyAccess client on file servers (for the purpose of auditing only) is covered in the Server Audits document.

If you already have the client deployed and are simply looking to push out updates, please also reference our Client Self Update documentation. These are overviews and examples, your environment may have specific considerations related to these methods. This document references some techniques, tools, and documentation that facilitates large scale deployment. At sites that have a large number of KeyAccess client installs to perform, manually running the client installer on each computer may be impractical.

Ksp mac not launching