1. After the initial configuration wizard completes, CSM for SCCM will launch. The default view is the Software tab. It shows the most recent versions of 3rd party software and their status, whether they are downloaded or deployed.
2. SCCM-integration tab is basically the view where all the advanced configuration can be defined. The view has three sub-tabs.
Service status - SCCM integration is basically the power button of CSM for SCCM. CSM only downloads and deploys 3rd party software when it's in Enabled state. As a side note, it's important to understand that disabling the very setting only stops the future deployments but does NOT affect the existing ones.
Logging - Debug logging enables logging for debug purposes.
SCCM information - Reload SCCM information is a function to reload information such as distribution groups in CSM for SCCM.
Service User is the account used to run CSM for SCCM. This service account does the necessary background tasks such as initiating download of the newer 3rd party software versions. The account is defined during the initial wizard but can be changed later.
Server - Server name is selected Remote in order to use a remote server. In this case a valid server DNS name is required.
Default software settings
File system root folder for packages is the location where all the 3rd party software packages are downloaded.
SCCM root folder for packages is a name for container that appears in the SCCM console in Applications section. All the imported 3rd party packages will be placed into it.
Send logs to Centero enabled / disabled
Template name decides which e-mail template you wish to use.
Email address is the address shown to receiver of the notifications. Multiple e-mail addresses can be separated by using comma.
Application Description with this option you can construct a description for 3rd party software in the SCCM.
Application Name with this option you can construct a name for 3rd party software in SCCM.
Application help documentation is an URL or network path to specify users more information on an application.
Distribution point group is a selection which group you want to use.
Application category can be used if you want to use it in application catalog.
Slow network mode can be set download / download content / nothing.
Fast network mode can be set run local / run from network.
Persistent content in client cache can be set true / false.
Allow clients to share content on same subnet can be set true / false.
Allow clients to use fallback source location for content can be set true / false.
Logon requirement type can be used to define installation behavior to be depended on an user being logged on or not. The default mechanism for 3rd party applications in CSM for SCCM is to always install. The setting can be used to override the default mechanism.
Superseeding can be set all previous versions / all active previous versions / only previous versions / none.
Superseed version exclude can be used to leave out specific version. Version number can be input here but also regular expressions can be used to match multiple versions.
Add operating system requirements can be set default or false.
Clear previous version has 5 options:
- Remove deployments, supersedencies and retire when latest available.
- Remove deployments, supersedencies and retire when latest required.
- Remove deployments, supersedencies when latest available.
- Remove deployments, supersedencies when latest required.
Default deployment settings
This is one of the most important views in CSM for SCCM. You can create a default deployment configuration here which will used when a new deployment process is created. The Collections section enables adding, removing and modifying collections in default deployment process.
Selecting a collection from a list populates its Deployment, Email notification and Scheduling settings.
Collection name is an imported list of your collections defined in SCCM.
Collection type can be used to choose whether collection type is device or user.
Deploy purpose has 3 options: required / available (if the deployment is targeted to an user collection) / available with forced upgrade.
User notification can be set to display all and display in software center only.
Comment can be used as a custom note for deployment. CSM uses date as a comment by default.
Deployment time is depended on when a new 3rd party softaware version is released and then downloaded. If time is set to immediately deployment will be made right after a new version is downloaded. After option should be used when a specific delay is needed between collections or available / force installations.
Make deployment available is the time when you want to make the deployment available to a collection.
Force installation is the time when you want the deployment to be required to a collection.
You can specify a template for every collection if necessary. Multiple recipients for the email notification system can be added by separating them with semicolon.
Update task sequence on available time (SCCM credentials in use must have Operating System Deployment Manager role added & SCCM console must be restarted with credentials to confirm Powershell privileges)
CSM for SCCM can be used to update 3rd party applications in task sequences. The task sequence setting is related to the chosen collection. CSM for SCCM will deploy the new version to task sequence as soon as the available time of the deployment is reached.
Task sequence name can be selected.
Task sequence group can be selected.
3. Settings view can be used to configure the 3rd party application download location and e-mail settings.