Skip to content
Docs Intune Win32 Deployer
Home ยป Docs | Intune Win32 Deployer

Docs | Intune Win32 Deployer

In order to describe the handling of the "Intune Win32 Deployer" in more detail, I have shown the individual functions here.

Table of Contents

Button: Deploy from personal catalogue

Here you can see all the apps that you have already added.
With this button you can create / upload one or more apps at the same time. Simply select it with the [CTRL] key and click "OK".

Intune Win32 Deployer, personal app catalog


Another advantage of the "App Catalogue" is that if you manage several environments, you can simply change the tenant with the "Change" button and thus upload the same apps (or a selection of them) very quickly.

Button: View App Catalog

As with the "Deploy from personal Catalog" button, all added apps are displayed here.
But this time without function.

Button: Add Chocolatey App

Here you add a Chocolatey app to the app catalogue. You can either enter a search term or the exact ID. The easiest way to find the ID is via the Chocolatey Repository using the "Find packages / id online" button.

Intune Win32 Deployer, add Chocolatey App

After clicking on "OK" you will be shown all matching search results. You then have to select the one you want.
After adding it, you will be asked if you want to create or upload the app as well.

Add selected Chocolatey App?

Whether the app is also uploaded depends on the "only create intunewin" button. If the button is grey, the app is being uploaded. If it is orange, only the app's intunewin file is created.

Button: Add wings app

Here you add a winget (Windows Package Manager) app to the app catalog.
To do this, enter the exact ID in the field. If you don't know the ID of the app, you can easily find it using the "Find ID online" button. (This will direct you to the page winget.run further)

Intune Win32 Deployer, add winget app


After adding, you will be asked if you want to create or upload the app.
If you enter an incorrect ID, an error will appear in the terminal and you will be returned to the start page.

Winget ID found
ID found
Winget ID not found
Error message if ID not found.


Whether the app is also uploaded depends on the "only create intunewin" button. If the button is grey, the app is being uploaded. If it is orange, only the app's intunewin file is created and displayed in Explorer.

Button: Settings

If you want to change the tenant name or the publisher, you can do this using this button.
You can then make your changes in a pop-up. This allows you to use the same app catalog for a different environment.

You can also use "Create/Assign group per app" activate that a security group is also created for each created app, you can specify the "Prefix" for this.

The option "Create PR via app" creates Proactive Remediation Packet per up, which takes care of the updates.
Here I have described this function in more detail: wings Updates | Proactive Remediations

Settings

Button: only create intunewin

When the button is orange, added apps and hollowed ones are built for deployment and uploaded to your MEM environment.
If you click the button and it is orange, only the intunewin files of the applications will be created and displayed.

only create intunewin, deactivated
only create intunewin, activated

status

The status changes to "working..." (orange) as soon as you press a button and changes back to "ready" (green) when the task is complete.
In addition, after the task has been completed, the message "Done. Ready for next task." appears in the terminal window.

State, ready
Status, working

Terminal (in the background)

The terminal in the background shows you the steps and log of each task being performed.

Intune Win32 Deployer, Terminal

4 thoughts on “Docs | Intune Win32 Deployer”

  1. Pingback: The "Intune Win32 Deployer" | scloud

  2. Hi, wonderful tool you have build. Would love to use this to simplify enrolling default applications in to tenants.
    I tested it in my test environment but getting an time out error (0x81036502) during ESP enrollment. I selected 2 apps, the Windows Package Manager itself and Adobe Reader.

    Any idea why?
    I will do some testing today to see if I can work around it.

    1. Upon further checking the status page it shows the error: failed to detect after installation succeeded successfully at the Adobe Reader app.

Leave a Reply

Your email address will not be published.