Missing Dependency Microsoft win32 taskschedule dll Cannot Continue Oculus
After a couple of weeks with distractions, this week I'm stepping away from conditional access. This week is all about Win32 app management capabilities. More specifically, about Win32 app dependencies. About half a year ago, when Win32 app management capabilities were introduced, I did my first post about those capabilities. That post is still being read really good, so I thought this would be a good time for a nice addition to that post. In this post I'll start with a shorting introduction about Win32 app dependencies, followed by the configuration steps for Win32 apps and specifically for Win32 app dependencies. I'll end this post by showing the experience for the end-user and the administrator.
Introduction
Let's start with a short introduction about reason for using Win32 apps and more specifically about using the Win32 app dependencies. Slowly there are coming more and more reason to look at Win32 apps as a serious alternative to using single-file MSI via MDM. An important reason for that is that Windows 10, version 1709 and later, will download Win32 app content by using delivery optimization. Other reasons are the Win32 app configuration options for requirements and detection rules. That will make the Win32 app really flexible. To make the Win32 app even more flexible, and even more comparable to the ConfigMgr app model, it's now also possible to configure dependencies between Win32 apps.
Scenario
Before looking at the actual configuration steps, let's first describe the example scenario that I'll use to show the Win32 app dependencies feature. As an example scenario, I'm using PolicyPak. I won't go into details about the functionalities of PolicyPak, that information can be found here. The reason that I'm using it as an example scenario, is simply because the installation contains three steps: install the license file, install the client-side extension and install any setting file. All of these are available as MSI and the mentioned order (see also the picture below) provides the best result. In other words, ideal for showing the Win32 app dependencies feature.
Note: In my testing, PolicyPak will work just perfectly fine if you don't take into account dependencies, but this is an ideal scenario to ensure that all policies delivered from PolicyPak always get applied the first time
Configuration
Now let's start with the configuration steps. I'll do that by first quickly showing the steps to wrap a Win32 app and the steps to configure a Win32 app. For more details about that, please refer to my previous post about Win32 apps. After that, I'll show the detailed steps for configuring Win32 app dependencies.
Prepare Win32 app
The first step is to quickly go through the steps to prepare the Win32 apps by using the Microsoft Intune Win32 App Packaging Tool. Wrap the Win32 apps. The packaging tool wraps the application installation files into the .intunewin format. Also, the packaging tool detects the parameters required by Intune to determine the application installation state. The following five steps walk through wrapping the different PolicyPak MSIs.
| 1 | Download the Microsoft Intune Win32 App Packaging Tool. In my example to C:\Temp; |
| 2 | Create a folder per PolicyPak MSI. In my example C:\Temp\[PolicyPakMSI]; |
| 3 | Open a Command Prompt as Administrator and navigate to the location of IntuneWinAppUtil.exe. In my example that means cd \Temp; |
| 4 | Run IntuneWinAppUtil.exe and provide the following information, when requested
|
| 5 | Once the wrapping is done. The message Done!!! will be shown. In my example a file named [PolicyPakMSI].intunewin will be created in C:\Temp. |
Note: The mentioned steps should be performed per PolicyPak MSI.
Configure Win32 app
The next step is to quickly look at the configuration steps, within Microsoft Intune, to configure the Win32 apps. The following 17 steps walk through all the steps to configure the Win32 apps, by using the .intunewin files.
| 1 | Open the Azure portal and navigate to Intune > Client apps > Apps to open the Client apps – Apps blade; |
| 2 | On the Client apps – Apps blade, click Add to open the Add app blade; |
| 3 | On the Add app blade, select Windows app (Win32) – preview to show the configuration options and select App package file to open the App package file blade. |
| 4 | On the App package file blade, select the created [PolicyPakMSI].intunewin as App package file and click OK to return to the Add app blade; |
| 5 | Back on the Add app blade, select App information to open the App information blade; |
| 6 | On the App information blade, provide at least the following information and click OK to return to the Add app blade;
Note: The remaining information regarding the Information URL, the Privacy URL, the Developer, the Owner, the Notes and the Logo is optional. |
| 7 | Back on the Add app blade, select Program to open the Program blade; |
| 8 | On the Program blade, verify the Install command and the Uninstall command and click OK to return to the Add app blade; |
| 9 | Back on the Add app blade, select Requirements to open the Requirements blade; |
| 10 | On the Requirements blade, provide at least the following information and click OK to return to the Add app blade;
|
| 11 | Back on the Add app blade, select Detection rules to open the Detection rules blade; |
| 12 | On the Detection rules blade, select Manually configure detection rules and click Add to open the Detection rule blade. |
| 13 | On the Detection rule blade, select MSI as Rule type, verify the pre-provisioned MSI product code and click OK to return to the Detection rules blade; |
| 14 | Back on the Detection rules blade, click OK to return to the Add app blade; |
| 15 | Back on the Add app blade, select Return codes to open the Return codes blade; |
| 16 | On the Return codes blade, verify the preconfigured return codes and click OK to return to the Add app blade; |
| 17 | Back on the Add app blade, click Add to actually add app. |
Note: The mentioned steps should be performed per PolicyPak .intunewin file.
Configure Win32 app dependency
Now the main configuration of this post, the configuration of the dependency between Win32 apps. The created Win32 apps need to be installed in the order as described (and shown) during the explanation of the scenario. The following six steps walk through the Win32 app dependency configuration. In my scenario, these steps need to be performed for he PolicyPak settings MSI, to create a dependency between the PolicyPak settings MSI and the PolicyPak client-side extensions MSI, and for the PolicyPak client-side extensions MSI, to create a dependency between the PolicyPak client-side extensions MSI and the PolicyPak license MSI. After configuring the Win32 app dependencues, make sure to assign the PolicyPak settings MSI to a user group.
| 1 | Open the Azure portal and navigate to Intune > Client apps > Apps to open the Client apps – Apps blade; |
| 2 | On the Client apps – Apps blade, select the just created [PolicyPakMSI] app to open the [PolicyPakMSI] app blade; |
| 3 | On the [PolicyPakMSI] app blade, select Dependencies to open the [PolicyPakMSI] app – Dependencies blade; |
| 4 | On the [PolicyPakMSI] app – Dependencies blade, click Add to open the Add dependency blade; |
| 5 | On the Add dependency blade, select the [PolicyPakMSI] app and click Select to return to the [PolicyPakMSI] app – Dependencies blade; |
| — |  |
| 6 | Back on the [PolicyPakMSI] app – Dependencies blade, select Yes with AUTOMATICALLY INSTALL and click Save. |
| — |  |
Note: Keep in mind that these steps need to be performed for both dependencies.
Experience
Now let's end this post by looking at the end-user experience and the administrator experience.
End-user experience
The first experience to look at is the end-user experience. Below, from left to right, is the end-user experience. As I configured the dependencies to automatically install, the dependencies will install before the actual assigned PolicyPak settings MSI. First the end-user will receive the message that PolicyPak license MSI will install as a part of the PolicyPak settings MSI installation. After a successful installation, the end-user will receive the message that the PolicyPak client-side extensions MSI will install as part of the PolicyPak settings MSI installation. And once that installation is successful, the PolicyPak settings MSI will install.
Administrator experience
The second experience to look at is the administrator experience. That is not always the most exiting experience to look at, but in this case it does add something good and new to look at. For the administrator, Microsoft Intune provides the Dependency viewer. The Dependency viewer can be found by selecting an app and navigating to Monitor > Dependency viewer. The Dependency viewer shows the the dependencies of the selected app and the dependencies of the dependencies (all the way down). The Dependency viewer does not show the apps that depend on the app. So, to explain that with the example of this post, it would be like this: - PolicyPak settings MSI: The PolicyPak settings MSI would show that it has a dependency on the PolicyPak client-side extensions MSI and that the PolicyPak client-side extensions MSI has a dependency on the PolicyPak MDM license MSI (as shown on the right);
- PolicyPak client-side extensions MSI: The PolicyPak client-side extensions MSI would show that it has a dependency on the PolicyPak MDM license MSI;
- PolicyPak MDM license MSI: The PolicyPak MDM license MSI would show no dependencies.
More information
For more information regarding Win32 apps and Win32 app dependencies, please refer to the following article:
- Intune Standalone – Win32 app management – App dependencies: https://docs.microsoft.com/en-us/intune/apps-win32-app-management#app-dependencies
bechtoldgustanotests.blogspot.com
Source: https://www.petervanderwoude.nl/post/working-with-win32-app-dependencies/
Post a Comment for "Missing Dependency Microsoft win32 taskschedule dll Cannot Continue Oculus"