1. After installation is complete, launch Centero Software Manager from Windows Start Menu.
2. Proceed with the wizard by clicking next.
3. CSM requires organization specific credentials to connect cloud for managing chosen 3rd party software. Input the credentials and click login. The wizard will now inform of successful login. Proceed by clicking next.
4. CSM downloads 3rd party software to a chosen location. Browse for a suitable location and proceed by clicking next.
- Folder can be a folder or an UNC path. Local folder will be automatically converted to a network path for SCCM, but applications will be downloaded to a local folder.
5. Select the integration type. Since we are installing CSM for SCCM it's obviously the following. Proceed by clicking next.
6. CSM can be either installed on the SCCM server or on a remote server. Nevertheless, there must be a SCCM console enabled on the target server.
Please choose if CSM for SCCM is installed on SCCM server or on a remote server. If a remote server is selected the server DNS-name must be inputted.
CSM for SCCM uses a service account. The account must have local administrator privileges on the server CSM is installed. In addition to that a powershell session must have been started at least once before. The service account also must have Application Administrator role defined in SCCM.
When all the necessary prerequisites are met the service account credentials can be input to username and password fields. Proceed by clicking Set-button. CSM wizard then validates credentials and creates a new service. When this is done please proceed by clicking Next.
7. CSM for SCCM configuration wizard enables SCCM deployment process to be defined. It is important to know that these settings can be modified later on in a more advanced way in CSM for SCCM control panel.
In this view it's possible to define how many steps there are in software deployment (or in patch management / software updating).
In these instructions we have used so called two steps deployment process. It means that all the newer versions of the managed 3rd party software are first deployed to our 1st level testing group and after some proper testing and specified delay the same 3rd party software are deployed to our production group.
8. Choose a distribution point group and proceed by clicking Next.
9. At this point it's possible to choose which 3rd party software are to be used with the recently defined default deployment process. You can choose the first option which enables all the 3rd party software that are subscribed to your account. The second option makes it possible to select specific 3rd party software to be used with the default deployment process.
10. CSM for SCCM can be configured to send e-mail when new versions of 3rd party software are deployed. If you wish to receive notifications by e-mail please input valid configuration.
The mail configuration can be tested by clicking test. You should receive a similar message if the defined configuration are valid.
11. This is the last step of the wizard. In most of the cases we recommend to select No and review the configuration once more in CSM for SCCM. If you are completely certain about the defined configuration you can start automatic deployments right away by selecting Yes.
After clicking Finish the wizard will close and CSM for SCCM will launch.
Starting from 1.0.5085 version:
1. Launch CSM from start menu. Select "Next"
2. Enter your Centero Software Manager credentials. Select "Login" and "Next".
- You will receive CSM credentials after ordering CSM for SCCM
3. Select path for 3rd party application installation files. Path can be a local folder or an UNC path. Local folder will be automatically converted to a network path for SCCM, but applications will be downloaded to a local folder.
4. Choose "SCCM" as an integration type and select "Next"
5. Select "Local" or "Remote" depending on if you are installing on SCCM server or to an remote server. Enter CSM service account credentials and select "Set".
- Use DNS name (server.domain) if using remote server
- Service account requirements
6. Select collection(s) for default deployment process and select "Next".
- Default deployment process is used as a base for new deployment processes
- You might want to just select your pilot group, so it will be used on all deployment processes
7. Select distribution point group and "Next"
8. Select which applications are selected to the default deployment process and "Next"
- Use default deployment process with all software
- This is the default option and it will add all applications to an automatically created deployment process
- Select: Application(s)
- If you want to select specific applications to an default process
9. Type your SMTP server settings if you wish to receive email notifications when CSM creates new application deployments. Select "Next"
10. Select "No, I start automatic deployments manually later" and "Finish"
- You can select "Yes", if you are happy with the default deployment created during installation
11. CSM will start up and you can continue with further configurations