Skip to main content

First-time setup

Complete the initial configuration on the web server, then use Settings → Setup Guide to check the connections and templates.

Open and license the site​

  1. In IIS Manager, select the SoftwareCentral site and browse its local HTTPS binding, normally port 8080.
  2. Test and save the SoftwareCentral database connection.
  3. Select your administrator group. The account completing setup must be a member.
  4. Enter the licence credentials supplied for Application Manager. For an offline installation, follow the licence screen's installation-key process with your supplier.

Configure SCCM​

  1. Complete the required settings, including site code, SCCM server and database, application URL and package share for each site.
  2. Open Settings → SCCM Folders and Collections and set the root collections and folders. You can select an existing structure or create the defaults. Creating defaults adds folders and collections to SCCM; review where they will be created.
  3. In Settings → Setup Guide, run the applicable connection tests for SCCM WMI, both databases, package-share access, updates and licensing. Resolve failed tests before importing an app. The Intune connection is optional when you have no Intune targets.
  4. Under Settings → Service Manager, confirm the SoftwareCentral service is running.

See the full first-time configuration guide for the individual settings and collection structure.

Connect Robopack and create templates​

  1. Open the Robopack card in Settings → Setup Guide. Enter the API key for the Robopack organisation you want to use and keep Robopack API URL set to https://api.robopack.com/. Select Test connection. To create a key, use Settings → API integration in Robopack.
  2. Create an Application Template for SCCM and a Robopack Deployment Template. Review the application folder, content distribution and deployment settings. Set defaults if you want to reuse them for each import.
  3. Select Re-check all and resolve the outstanding items that apply to your environment.

For custom apps packaged in Robopack, use a key from the organisation that contains those apps. The custom app integration guide explains organisation selection and the effect of changing keys.

Make the site available to administrators​

Configure DNS and an IIS HTTPS binding with a certificate trusted by your administrators' devices. If you use Azure OpenID, update the app registration's redirect and logout URLs too. Follow the hostname and HTTPS guide, then test sign-in from another device.

Next: Your first application.