Skip to content

Set Up a Package Recipe

import { Steps } from ‘@astrojs/starlight/components’;

Package recipes define how software packages are built. This guide helps you create your first recipe.

TypeBest forAuto-updates?
DynamicBrowsers, Office, regularly updated softwareYes — new versions are detected automatically
StaticInternal tools, custom software, one-time buildsNo — fixed version and configuration
  1. Navigate to Package Recipes

    Go to packagery > Package Recipes > Dynamic Recipes and click + New.

  2. Select software from the catalog

    Choose the software product from the updatery catalog dropdown. Only software that is tracked in the catalog can be used for dynamic recipes.

  3. Configure the recipe

    • Organizational Unit (OU): Select the target OU (e.g., “Shared”)
    • Platform: Choose the target platform (Client, Server, Client & Server, or VDI)
    • Configuration Profile: Assign a configuration profile that controls naming, structure, and PSADT settings
    • Optional: Set language and architecture preferences
  4. Save as Draft

    The recipe is created with status Draft. Review all settings before activating.

  5. Activate the recipe

    Change the status from Draft to Active. Only active recipes can be ordered for package builds.

  1. Navigate to Static Recipes

    Go to packagery > Package Recipes > Static Recipes and click New.

  2. Define the package

    Specify the exact software name, version, and all build parameters. Unlike dynamic recipes, static recipes use a fixed configuration.

  3. Configure and save

    Assign a configuration profile and save. Static recipes can be ordered immediately after creation.

Instead of starting from scratch, you can create a dynamic recipe from a Template:

  1. Go to the Templates tab in Dynamic Recipes
  2. Select a preconfigured template
  3. Adjust the pre-filled values as needed
  4. Save your new recipe