> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/anywhere/content-creation-publication/content-creation-publication-intune.md). # Intune The following applications types can be created as P2P Apps for peer to peer distribution. * Any EXE installer * Any MSI installer * Any Script-based installer Deploying an application using Intune with OneSite is a multi-step process all automated using the Adaptiva Web Portal. 1. Create the Intune P2P App in Adaptiva 2. Generate the OneSite win32 P2P application (Win32 .intunewin) 3. Create the Windows app (Win32) in Intune * The last step is the only step that needs to be completed manually: 4. Target end-users or devices When content is created in Adaptiva for distribution using Intune, the source files are compressed, optionally encrypted, and stored on the Adaptiva server in the `\data\ContentLibrary` folder. This is stored as a `.content` file. The `.content` file will also be uploaded to the cloud Storage container. If the storage location is only in the cloud, then the `.content` file will be removed from the Adaptiva Server Content Library. In addition, an `.intunewin` file is created that will provide an 80kb executable to download. The `.intunewin` file will be used as the app package file when creating the Windows app (Win32) in Intune. The `.intunewin` file is created by the Microsoft Win32 Content Prep Tool. {% hint style="info" %} App Registration must be completed prior to creating and deploying content using Adaptiva OneSite for Intune. See the App Registration section in the Installation Prerequisites section of the Adaptiva Installation Guide. {% endhint %} ## New Intune P2P Content Settings 1. Select **P2P Apps** from the side navigation. ![](/files/jgkqxtbixLumteXWxxGd) 2. Click on **+ New**. {% hint style="info" %} All settings with a red asterisk are required. {% endhint %} ### General Details ![](/files/JEXXitxf9ePabxuRmebG) * **Name** - Enter the Application Name, this will be displayed to the end user if using the company Portal. The Name should ***NOT*** contain any special characters or spaces as this name is used to create an executable program. * **Description** - Enter a description. * **Content ID** - Unique ID given assigned to the associated content in the Adaptiva Server Content Library. * **Intune App ID** - Unique ID given assigned to the application by Intune upon successful publication. ### App Details ![](/files/1mwUU1C0YsKqp4wy8MRn) * **Owner** - The owner of this application. * **Logo** - The logo of this application, as a base-64-encoded byte string. * **Version** - The version string of this application. * **Category** - The category to which this application belongs. * **Information URL** - The URL of a website that contains information about this application. * **Privacy URL** - The URL of a website that contains privacy information about this application. * **Publisher** - The name of the publisher or company that distributes the app. This information will be visible to users in the company portal. * **Developer** - The name of the developer or company that distributes the app. This information will be visible to users in the company portal. * **Applicable Architectures** - Select the OS architecture required to install the application. * **Unpacking Parent Folder** - By default, the content will be unpacked in the AdaptivaCache folder. To unpack to a different location, enter that location here. * **Azure Blob URL** - Is not used. * **Source Type** - Select **Local Source Path** if the content source exists on the server or **Network Source Path** if the content requires a UNC. When using Network Source Path, **Network Access Account** can then also be used to define the domain, username and password to connect to the UNC path. * **Source Type** - Enter the path to the source files. * **Scope Tags** - Enter the Scope Tags to link to this App. Scope Tags must already be defined in Intune. Click the + to add the tag. Multiple tags can be added. Scope Tags may be automatically attached to the App if they are Assigned to Groups and one of the Deferred Accounts was selected for the Login Type. ### System Requirements ![](/files/DTpRSp4kq0szXTQOnK0S) * **Minimum Operating System** - Select the minimum OS version required to install the application. * **Minimum Disk Space** - The minimum space on disk required to install this application, in MB. * **Minimum Physical Memory** - The minimum RAM / physical memory required to install this application, in MB. * **Minimum Number Of Processors** - The minimum number of logical processors required to install this application. * **Minimum CPU Speed** - The minimum CPU speed required to install this application, in megahertz (MHz). ### Installation Properties ![](/files/IBtSJbgNP9x8m5D7CNHT) * **Command Line** - Enter the installation command line. * **Working Directory** - If a working directory is required, enter the working directory path. * **Visibility** - Select from Hidden (Default), Normal, Minimized, or Maximized for the visibility of the P2P App. * **Max Execution Time** - Enter the maximum time the installation should run. Default is 60 minutes. * **Use MSI Exit Codes** - If this is a Windows installer-based app, slide the toggle to the right, otherwise, enter the various exit codes in the remaining fields. * **Success Exit Codes** - Default is 0. Enter the return code(s) in a comma separated list of a successful installation. * **Failure Exit Codes** - Enter the return code(s) in a comma separated list if the installation failed. * **Hard Reboot Exit Codes** - Enter the return code(s) in a comma separated list if the installation requires a hard restart. * **Soft Reboot Exit Codes** - Enter the return code(s) in a comma separated list if a soft restart is required. * **Unknown Exit Code Behavior** - If the exit code is not listed above, select from Failure, Success, Soft Reboot or Hard Reboot. ### Uninstallation Properties ![](/files/bileI1HLjOZZujmGiXKN) * **Command Line** - Enter the uninstall command line. * **Allow Available Uninstall** - Whether users should be able to uninstall this application from the company portal. * **Working Directory** - If a working directory is required, enter the working directory path. * **Visibility** - Select from Hidden (Default), Normal, Minimized, or Maximized for the visibility P2P App. * **Max Execution Time** - Enter the maximum time the installation should run. Default is 60 minutes. * **Use MSI Exit Codes** - If this is a Windows installer-based app, slide the toggle to the right, otherwise, enter the various exit codes in the remaining fields. * **Success Exit Codes** - Default is 0. Enter the return code(s) in a comma separated list of a successful uninstallation. * **Failure Exit Codes** - Enter the return code(s) in a comma separated list if the uninstallation failed. * **Hard Reboot Exit Codes** - Enter the return code(s) in a comma separated list if the uninstallation requires a hard restart. * **Soft Reboot Exit Codes** - Enter the return code(s) in a comma separated list if a soft restart is required. * **Unknown Exit Code Behavior** - If the exit code is not listed above, select from Failure, Success, Soft Reboot or Hard Reboot. ### Detection Rules ![](/files/aNWaIxTjZuRs5W6IXkRZ) Detection Rules determine the type of detection method used to validate the presence of the app. This can be done with a File, MSI code, Registry, or Powershell rule. At least one Detection Rule must be entered 1. Click on **+ Add Detection Rule**. 2. Select one **Rule type** and complete the corresponding form. 3. Click **OK**. ### Requirement Rules ![](/files/yLVifYy6O8BMmKRmPcfG) This is an *optional* setting that allows you to determine the type of requirement method used to validate the presence of the app. This can be done with a File, MSI code, Registry, or Powershell rule. 1. Click **+ Add Requirement Rules**. 2. Select one **Rule type** and complete the corresponding form. 3. Click **OK**. ### Save and Publish 1. Click **Save**. 2. Click **Publish App to Intune**. This step will create the app in Intune and place the content file in the location specified in Intune Settings, Cloud Content. If the Intune Configuration is using one of the Deferred Login Types and Authentication has not been completed the following Re-authentication request will be displayed: ![](/files/CDeGbLxNbPJMwjCDS1bG) ### Authenticate 1. Click **Authenticate** ![](/files/41EtempWg4re1fpEnPW3) 2. Copy the **Device Code**, then click **Authenticate** * IMPORTANT. The code will be requested on the next screen, be sure to copy it or write it down 1. A login for Microsoft will be displayed, enter the code from the previous screen. Click **Next** 2. Confirm the Tenant and the username is correct. Click **Next** 3. Enter the password for that account in that Tenant. Click **Sign in** * Complete any authentication that is required. 1. If you had to Authenticate, you will need to close the App Editor by clicking **Back to Intune P2P Apps**, open the App again and click on **Publish to Intune** 2. Click **OK**. ![](/files/ke1PFiKCrGQnAm3xknOd) #### Publication Status Publication Status will denote the status of the content in the Content Library Intune Publication Status will denote the status of the Windows 32-bit app in Intune ### Assign the App for Delivery 1. Select **Apps** from the side navigation from the Microsoft Intune admin center. ![](/files/m63jEjipTYbPqnXv4Kp7) 2. Select **Platforms > Windows** from the inner side navigation. 3. Select the a desired app. 4. Click **Properties** ![](/files/XgHGOWFbxiJzahWHbakw) The Install and Uninstall commands have the application name.exe as the command line with -i for installation and -u for uninstall These command lines will invoke Adaptiva to download the .content file using Adaptiva P2P technologies. Do ***NOT*** change the command lines. 5. Select **Edit** in the **Assignments** section. Add a group to **Required** to force the installation. Add a group to **Available** for enrolled devices to make the installation optional via the Company Portal app. When adding a group to Available, the group must contain **Users**, not **Devices**. Add a group to **Uninstall** for managed devices to have this app removed. If scope tags, supersedence (a new feature) or dependencies are to be used, those must be configured in the Endpoint Management Admin console. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.adaptiva.com/anywhere/content-creation-publication/content-creation-publication-intune.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.