Your first application
Start with one application and a pilot device. Complete first-time setup and review your templates before importing: a template can create deployments as part of the import.
Import from Robopack
- Open Robopack, search for an application and select its card.
- Review the Download and import summary. Use Show Advanced to choose a template or change its settings.
- Check the app, install scope, SCCM application template, content distribution and any deployment targets or phases. Use pilot targets for the first deployment.
- Complete the wizard. If the final action is Create Patch Flow, it also sets up monitoring for new versions and automatic imports using those settings. Review that update behaviour and any deployment settings before continuing.
- Open Downloads and select the app to check the import result and the SCCM application it created.
The Robopack import guide explains the wizard, templates and patch flows in detail.
Review and test the application
Open Apps, find the imported SCCM application and check its commands, detection rules, requirements and content distribution.
If your import template already created the pilot deployment, monitor that deployment. Otherwise:
- Select Deploy Software, choose the application and select Install.
- Select your pilot device and review the summary.
- Check the deployment overview and any schedule, then select Apply Software Changes.
- Open the app's Install Status view and confirm the result. Check on the pilot device that the application opens and behaves as expected before expanding the deployment.
See the deployment walkthrough for each wizard screen.
Use your own installer
For an application outside the library, open Apps → Create → Create Application. Work through Template → Source → Files and Naming → Detection → Overview, checking the install and uninstall commands, app identity and detection rules. Review the template's distribution and deployment settings before creating it, then use the same pilot test above.
See Create an SCCM application for the full walkthrough. If an existing SCCM app needs its collection structure corrected, check Troubleshooting first.