I hope you enjoy this video learning about Win32 App Supersedence in Microsoft Intune. Let's chat in the comments. 🙂 Timestamps: 0:00 Intro 1:24 Admin demo - how to Add Win32 App Supersedence in Microsoft Intune 9:30 End-user demo - how to Add Win32 App Supersedence in Microsoft Intune 12:13 Outro
Your channel is underrated I’m surprised it’s not blown up yet. Your content is gold! I like your explanation technique and the time taken to edit and timestamp your videos! Keep up the good work
Sunny - Thank you so much for the comment. It means a lot to me that you find these videos helpful and notice the extra effort I put into making these videos. Great to have you here as part of the community. Also, on your channel, if that is you doing that skip roping, you got crazy skills :)
Hello Harry, thanks for the explanation, it's fun to listen to you and the valuable tips help. I have a challenge with Supersedence though. I usually do not distribute the Win32 apps as required but make them available to the user. When distributing an update for these apps, I expected the supersedence feature to automatically pass the update/replacement to the Win32 app installed by the user from the enterprise portal. At the moment I have created 2 Intune apps for each Win32 app. A Win32 app that provides the user with the application in the company portal and a Win32 app with the app as an update that is distributed on the device as necessary with the condition that an older version must be present. I was hoping to simplify this with this supersedence feature. Have I misunderstood this? If not, how do you do that? Thank you very much, Marcus
Hey Marcus - I hope all is well. If you have not already the following document is a good read. docs.microsoft.com/en-us/mem/intune/apps/apps-win32-supersedence Supersedence does not automatically deploy and upgrade or replace applications. If you deploy it as available, then the application will not update until the user chooses to install the new version in the company portal. To ensure an application is updated, for example, you need to update an application due to a security concern. You will want to deploy the superseding application as required.
@@HarryLowtonIT Hey Harry, thanks for the link. Then I didn't misunderstand the principle of supersedence after all. But I don't see the sense in it.For example, if I have to distribute an important security update for a software, then I don't want to make this dependent on whether and when the user switches to the Company Portal and clicks on "Install". In order to force such an update to be pushed out, I have to distribute a software package as "required". If I have understood the documentation correctly, then all users get the update and not only the users who have installed the application as "available". To limit this behavior I have to attach a requirement to the app and check for example the file version or a registry key to see if the app is installed at all and then distribute it as "required". And with this I don't understand the sense of this new function, because as I tried to describe it, I do this task now always. I'm looking for a benefit from the superseedence feature.... The only advantage I could see would be that when a user in the Company Portal tries to install an old version of a software, he automatically gets the newer version. But this can be avoided by removing the assignment to the old version. Therefore I do not understand all this ... Greetings from germany Marcus
Hi Harry, Great video as usual. I have a question in relation to supersedence. If there is an application as you have demonstrated and let's say (7-Zip isn't a good example in this case) regular updates become available. Looking at how you did it with 7-Zip the newer version would be packaged and newer MSI version would be checked to ensure the old version is correctly superseded. My question is after time there is going to be quite a list develop of apps with the same name and depending on how many apps are packaged for Intune this could become quite cluttered. Is there a way to manage this and stop the app list becoming cluttered or is this just how it will work by design? Thank you.
So when you do supersedence that are assigned as required apps, Do you have to unassign the older version or will it automatically know not to install.
Question, my MSI does not have a product version number. Analyzing the properties of the software after installation, there is a version number, but adding that version number to the detection rule results in a failed install because the MSI installer itself does not have a version number. Is there any way to use supersedence without using a version number to detect it? Thank you for the informative video! UPDATE: okay nevermind, it looks like the product version number for this application is formatted as: 10, 0, 286, 1 rather than 10.0.286.1 which is what the file version reads... However if I use the latter format it fails to detect it, but if I try to use what's actually listed as the product version I get an error from Intune stating that it is not a valid version.
Hey Jim - yes you can use a different detection method for example File. Just if you use that method you will want to find something unique between the versions or Intune will not install the latest version. Here is a link to learn more docs.microsoft.com/en-us/mem/intune/apps/apps-win32-add#step-4-detection-rules
Hi Harry, Still loving the videos and great assistance thank you. You do gloss over a couple of things though if I can ask, how do you find the individual install/uninstall lines without having them installed on your live PC, and what if you can't "extract" the downloaded .exe? eg, Chrome
When I set it to uninstall, and the process begins on the client - The user get the interface to accept or deny the removal of the program. Any tips to fix this? :) thanks
I hope you enjoy this video learning about Win32 App Supersedence in Microsoft Intune. Let's chat in the comments. 🙂
Timestamps:
0:00 Intro
1:24 Admin demo - how to Add Win32 App Supersedence in Microsoft Intune
9:30 End-user demo - how to Add Win32 App Supersedence in Microsoft Intune
12:13 Outro
Setting the Detection rules to MSI was the last piece of the puzzle I needed. Thank you. Liked and subscribed.
Your channel is underrated I’m surprised it’s not blown up yet. Your content is gold! I like your explanation technique and the time taken to edit and timestamp your videos! Keep up the good work
Sunny - Thank you so much for the comment. It means a lot to me that you find these videos helpful and notice the extra effort I put into making these videos.
Great to have you here as part of the community. Also, on your channel, if that is you doing that skip roping, you got crazy skills :)
Your voice is as soothing as waves crashing on the beach.
Thank you so much :P
Harry you are a Rockstar! I am finding these Intune videos absolutely amazing!
Thank you ! I’m glad they are helpful
It's almost 1130pm , completed 4th video going to sleep
Sleep well! Great effort going through 4 videos.
Really enjoyed 3rd video
Really appreciate the feedback as you go through these :)
I see for your detection method you use "Equals", I usually use "Equal or Greater Than". Is there any issue or flaw with my method?
Hello Harry,
thanks for the explanation, it's fun to listen to you and the valuable tips help.
I have a challenge with Supersedence though. I usually do not distribute the Win32 apps as required but make them available to the user.
When distributing an update for these apps, I expected the supersedence feature to automatically pass the update/replacement to the Win32 app installed by the user from the enterprise portal.
At the moment I have created 2 Intune apps for each Win32 app. A Win32 app that provides the user with the application in the company portal and a Win32 app with the app as an update that is distributed on the device as necessary with the condition that an older version must be present.
I was hoping to simplify this with this supersedence feature. Have I misunderstood this? If not, how do you do that?
Thank you very much,
Marcus
Hey Marcus - I hope all is well. If you have not already the following document is a good read. docs.microsoft.com/en-us/mem/intune/apps/apps-win32-supersedence
Supersedence does not automatically deploy and upgrade or replace applications. If you deploy it as available, then the application will not update until the user chooses to install the new version in the company portal.
To ensure an application is updated, for example, you need to update an application due to a security concern. You will want to deploy the superseding application as required.
@@HarryLowtonIT Hey Harry,
thanks for the link. Then I didn't misunderstand the principle of supersedence after all.
But I don't see the sense in it.For example, if I have to distribute an important security update for a software, then I don't want to make this dependent on whether and when the user switches to the Company Portal and clicks on "Install".
In order to force such an update to be pushed out, I have to distribute a software package as "required". If I have understood the documentation correctly, then all users get the update and not only the users who have installed the application as "available".
To limit this behavior I have to attach a requirement to the app and check for example the file version or a registry key to see if the app is installed at all and then distribute it as "required".
And with this I don't understand the sense of this new function, because as I tried to describe it, I do this task now always.
I'm looking for a benefit from the superseedence feature.... The only advantage I could see would be that when a user in the Company Portal tries to install an old version of a software, he automatically gets the newer version.
But this can be avoided by removing the assignment to the old version.
Therefore I do not understand all this ...
Greetings from germany
Marcus
Hi Harry,
Great video as usual. I have a question in relation to supersedence. If there is an application as you have demonstrated and let's say (7-Zip isn't a good example in this case) regular updates become available. Looking at how you did it with 7-Zip the newer version would be packaged and newer MSI version would be checked to ensure the old version is correctly superseded.
My question is after time there is going to be quite a list develop of apps with the same name and depending on how many apps are packaged for Intune this could become quite cluttered.
Is there a way to manage this and stop the app list becoming cluttered or is this just how it will work by design?
Thank you.
What's the best solution to Supersedence Win32-app who has Dependencies? Apparently you cant Supersedence a application who has Dependencies...
So when you do supersedence that are assigned as required apps, Do you have to unassign the older version or will it automatically know not to install.
Question, my MSI does not have a product version number. Analyzing the properties of the software after installation, there is a version number, but adding that version number to the detection rule results in a failed install because the MSI installer itself does not have a version number. Is there any way to use supersedence without using a version number to detect it?
Thank you for the informative video!
UPDATE: okay nevermind, it looks like the product version number for this application is formatted as: 10, 0, 286, 1 rather than 10.0.286.1 which is what the file version reads... However if I use the latter format it fails to detect it, but if I try to use what's actually listed as the product version I get an error from Intune stating that it is not a valid version.
Hey Jim - yes you can use a different detection method for example File. Just if you use that method you will want to find something unique between the versions or Intune will not install the latest version. Here is a link to learn more docs.microsoft.com/en-us/mem/intune/apps/apps-win32-add#step-4-detection-rules
@@HarryLowtonIT Thank you for your reply! I ended up getting it to work using a detection script instead :)
Hi Harry,
Still loving the videos and great assistance thank you. You do gloss over a couple of things though if I can ask, how do you find the individual install/uninstall lines without having them installed on your live PC, and what if you can't "extract" the downloaded .exe? eg, Chrome
When I set it to uninstall, and the process begins on the client - The user get the interface to accept or deny the removal of the program. Any tips to fix this? :) thanks
Is there a problem with Win32 App, because I am not able to deploy Adobe Acrobat Reader DC in 64-bit? Please assist?