When using the supersedence relationship to replace a Win32 app, that actually requires nothing special from the app installer, of the superseding Win32 app, itself. As an example, think about updating FoxitReader from version 9.x to 10.x (see also Figure 3). That enables an IT administrator to relatively easy introduce a new version of a Win32 app in an organization. The app installer should be able to handle the installation, when the superseded Win32 app is already installed on the device. When using the supersedence relationship to update a Win32 app, that requires the actual app installer, of the superseding Win32 app, to handle the update intelligence.
Those supersedence relationships can be used to update or replace any specified Win32 app. Starting with the 2102 service release of Microsoft Intune, it’s possible to create one or more supersedence relationships between Win32 apps. Introduction to supersedence relationships for Win32 apps The different supersedence relationships for Win32 apps This post will end by showing the installation experience when using a supersedence relationship. This post will start with the theory of supersedence relationships for Win32 apps, followed with the steps to configure a supersedence relationship. Actually, it can even be used to replace a Win32 app with a completely different Win32 app. That relationship can be used to update a Win32 app to a newer version of the Win32 app, or to replace a Win32 app with a different version of the Win32 app.
That feature is the ability to create supersendence relationships between different Win32 apps. Last year I’ve written a lot about the different features of Win32 apps and now, starting with the 2102 service release of Microsoft Intune, there is a new feature for Win32 apps. This week is all about Win32 apps in Microsoft Intune.
0 kommentar(er)
