Configuring an Access Policy

The access policy defines on which operating systems software is available and how users access it. You decide if users install via a network-based or bundled installer, and you can choose to use the SDC portal for web delivery. You are also able to restrict accessibility based on operating system for cases where a package is not compatible with some OSs.

In this tutorial, you will learn how to:

  • Add a new access policy
  • Set package installer options
  • Add installer branding
  • Add custom licensing information

1. Add a New Access Policy

  1. Click Access Policies under Policies in the Admin Console navigation. Alternatively, you can open the Access Policies page by clicking the View Access Policies link on a package’s Configuration tab.

    Note: To edit settings for an existing policy, select the policy in the Access Policies section.

    Setting an access policy
  2. Click addIcon in the Access Policies section to create a new policy, or click duplicate_pkg_icon to create a new policy by duplicating another.

    The Access Policies section lists the access policies available for use. These are listed in the Access Policy drop-down list on a package’s Configuration tab. When you select a policy in the list, the Used In section displays the packages that use the policy.
    To remove a policy, select it, and click remove_icon. Before removing a policy, be sure no packages use the policy.
    To make a policy the default, select it, and click set_default_icon. However, before you can make a policy the default, you must first roll out the policy by promoting it.
  3. Enter a title for the access policy, and click OK. This title appears in the Access Policy drop-down list on the Configuration tab. The title also appears in the Title field of the Selected Access Policy section.

    The Selected Access Policy section allows you to set how users access the package installer, operating system restrictions, and the type of package installers to create. You can also configure installer branding that applies to all packages using this policy.
  4. On the Availability page, enable the options(s) that indicate where you want the package to appear on the portal. If you don’t want the package to display on the portal at all, disable both Show on… options.
  5. Enable the Show package usage graph on portal option if you want to show usage metrics for the package on the package details page in the portal.
  6. If your package is to be used only on certain operating systems, restrict the availability based on platform by enabling the Restrict Availability by OS option and selecting the valid platforms for the package.

2. Set Package Installer Options

  1. Click Packaging in the Selected Access Policy section.
  2. Enable the option(s) for how you want to deliver the package installers to your users. Your selection determines the type of installers that are created when you promote the package.
    Note: The web-install flow is not available beginning in SDC 2017. To enable this option, switch to the legacy portal.

    Packaging options
  3. Choose a configuration to assist in web and network installer optimization. If most users are on a local network, select Speedy Networks. If many users are accessing via a WAN, select Powerful Computers.
  4. Specify a shortcut path if you would like installers to group software shortcuts so they are found in a common location on the Windows Start menu, for example.
  5. Click the Advanced tab to configure whether or not your installer should try to download a JRE from the Delivery Hub at runtime when there is no JRE installed or bundled with your installer.

    On Linux, a JRE cannot be bundled, but you can select Download dynamically if needed and use the -forcejredownload flag when running the installer to have one downloaded from the SDC hub.

3. Add Installer Branding

  1. Click Branding in the Selected Access Policy section.

    Branding options
  2. Enter titles and a message that appears on the first page of the installer. 
  3. Select a background image to use for the installer or customize a flat look and feel.

    To select a background image—Drop the image into the Drop Here box, or click searchIcon to navigate to a file. The image must be exactly 600×400.

    To customize a flat look—Click the Options tab and enable the Overwrite Installers option. Select the desired colors and add a logo, if desired. To add a logo, drop the image into the Drop Here box, or click searchIcon to navigate to a file. The image must be exactly 140×100 and will appear at the bottom of the installer Steps area.

    Branding options for a flat look and feel

4. Add Custom Licensing Information

  1. Click Licensing in the Selected Access Policy section.

    Licensing options
  2. Add your custom copyright and End-User License Agreement. These appear in your installers to be accepted by users during package installation and override the default license agreement in the package installer.