For the complete documentation index, see llms.txt. This page is also available as Markdown.

Creating a Content Item

In DeployR, content items can be single files or entire folders of content; this content is uploaded to the DeployR server for subsequent use in task sequences. When uploading a single file, that file is used as-is. When uploading a folder, the entire contents are put into a single WIM file for efficiency; that WIM file is automatically extracted before the content is used in a task sequence step.

Different types of content items can be created. In some cases, additional metadata needs to be configured on the content item to tell DeployR how to use that content item. The types available include:

  • Operating system. For Windows OSes, this content item is a single WIM file containing one or more OS images.

  • Application. This specifies a folder of content needed to install an app on a device, along with the command line, working directory, and successful exit codes the app installer may return.

  • Driver pack. This specifies a folder of Windows driver files, along with the manufacturer and model of the device that can use the driver pack.

  • Other. Anything else is presently grouped into the "other" category. This can include answer files, or any other content that might be needed by a task sequence.

To get started, you may want to:

  • Create a operating system item for a Windows 11 OS WIM file.

  • Create a driver pack for one or more device models.

  • Create an application that can be installed on a new OS.

These can be added by navigating to the Content items node in the StifleR dashboard. Click the +Add button and specify the needed details.

  • Name (Required)

  • Description (Optional)

  • Purpose (Requrired) | Operating System, Application, Driver pack, Other

  • Type (Required) | Single file, Folder, External URL

  • Tags (Optional)

  • Flags (Optional)

    • Allow Anonymous Read - This will allows the ability to download a content item using the URL for that content item without providing authentication

    • Allow Authenticated Write - This allows the ability to overwrite / update a content item remotely, either from the task sequence itself, or using PowerShell on a remote machine. NOTE, if you're using PowerShell for automation on another server / workstation, and you're getting 403 (Forbidden) responses, not having this box is probably why.

Once the content item has been added, a new version (initially version 1) needs to be added. Once that version has been added (specifying the type-specific details), you can then upload the needed content.

Last updated