Skip to content
packagery packagery Help Center

Initial Setup

This guide walks you through the initial setup of packagery — from configuration profiles to Intune connectivity.

Step 1: Create a Configuration Profile

Section titled “Step 1: Create a Configuration Profile”

Configuration profiles control how packages are named, structured, and built.

  1. Navigate to Settings > Configuration Profiles

    Go to packagery > Settings > Configuration Profiles and click Add.

  2. Set Naming Conventions

    • Choose the name separator: tilde (~) or underscore (_)
    • Toggle whether the technical customer name is included in package names
    • Set platform abbreviations (Client: C, Server: S, Client & Server: M, VDI: V)

  3. Define Package Structure

    Configure the package subfolder path (e.g., Packages/Software) and the documentation folder path.

  4. Configure PSADT Settings

    Under the PSADT Configuration tab:

    • Appearance: Upload a banner image and PSADT extensions
    • Log Paths: Set the 4 log paths (MSI/Toolkit, with and without admin rights)
    • Settings: Configure the registry detection key, deploy mode (Interactive/NonInteractive/Silent), and select a PSADT template

Step 2: Create a Delivery Profile

Section titled “Step 2: Create a Delivery Profile”

Delivery profiles define where finished packages are sent (e.g., Microsoft Intune).

  1. Navigate to Settings > Delivery Profiles

    Go to packagery > Settings > Delivery Profiles and click New Delivery Profile.

  2. Configure the profile

    • Upload a logo (PNG, JPG, or SVG — max 5 MB)
    • Enter a profile name (required)
    • Add an optional description
    • Select the delivery target: Intune
    • Enter the Tenant ID (Azure AD GUID format: 12345678-1234-1234-1234-123456789012)

  3. Verify the connection

    Click Verify to test the connection. The system authenticates against the Microsoft tenant and checks all required permissions:

    • DeviceManagementApps.ReadWrite.All
    • DeviceManagementConfiguration.ReadWrite.All
    • DeviceManagementManagedDevices.Read.All
    • Group.Read.All

    If permissions are missing, click Start Consent to grant admin consent.

Step 3: Set Up Your First Recipe

Section titled “Step 3: Set Up Your First Recipe”

With profiles configured, you can now create package recipes:

  1. Follow the Set Up a Package Recipe guide
  2. Create a dynamic recipe for a commonly updated software (e.g., Chrome, Firefox)
  3. Activate it and trigger your first build order

Next Steps

Section titled “Next Steps”