Forum Discussion

uptocloudlimited's avatar
uptocloudlimited
Copper Contributor
Mar 09, 2021

Unable to update AIP Client with Intune

Dears,

We are trying to update Azure Information Protection from a very old version 1.54.59.0 to the latest one via PatchMyPC since this product its supported by their catalog.

Tracking some logs during the installation which fails send to a conclusion that previews AIP client is not able to be removed.

 

Intune error: Fatal error during installation (0x80070643)

 

Application logs:

MSI (s) (68:B0) [14:29:35:683]: Note: 1: 2205 2:  3: ActionText 

Action ended 14:29:35: InstallValidate. Return value 1.

MSI (s) (68:B0) [14:29:35:683]: Note: 1: 2205 2:  3: Error 

MSI (s) (68:B0) [14:29:35:683]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 22 

Action start 14:29:35: RemoveExistingProducts.

MSI (s) (68:B0) [14:29:35:683]: Note: 1: 2205 2:  3: Error 

MSI (s) (68:B0) [14:29:35:683]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 23 

...

MSI (s) (68:98) [14:29:35:952]: Note: 1: 2205 2:  3: Error 

MSI (s) (68:98) [14:29:35:952]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2753 

Action start 14:29:35: RegisterExcel.

DEBUG: Error 2753:  The File 'adxregistrator.exe' is not marked for installation.

MSI (s) (68:98) [14:29:35:952]: Note: 1: 2205 2:  3: Error 

MSI (s) (68:98) [14:29:35:952]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 

MSI (s) (68:98) [14:29:35:952]: Product: Microsoft Azure Information Protection -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2753. The arguments are: adxregistrator.exe, , 

The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2753. The arguments are: adxregistrator.exe, , 

 

Any idea is appreciated, thank you !

 

Best

  • Terry Hugill's avatar
    Terry Hugill
    Brass Contributor
    Having done a bit of research, it seems highly likely that the problem is related the version of .Net that is installed on the machine. https://docs.microsoft.com/en-us/azure/information-protection/rms-client/reqs-ul-client states a minimum of 4.6.2. There are also other pre-requisites on there that are worth checking such as the PowerShell version needing to be 4.0 and upwards. If the AIP client is out of date I suspect other things are too so it's worth checking. Another thing worth checking is the admin permissions, does the installation account have local admin rights? What version of Windows are you trying to install the client on to?
    • uptocloudlimited's avatar
      uptocloudlimited
      Copper Contributor

      Terry Hugill 

       

      Thanks mate for your contribution on this topic,

       

      I was working with MS support for weeks until not and unfortunately they were not able to provide me a modern solution how to upgrade AIP on 3k endpoints.

      For sure we make sure that all requirement for this client are fulfilled .NET and latest Win10 build.

       

      Spending many hours working on this issue i found out the new Unified Client of AIP ver 2.9.xx or 2.11.xx is not able to remove properly all registries of old AIP Client and this why installation fails from SCCM or Intune.

       

      As a workaround I found that was to manually remove these registry:

       

      reg delete HKEY_CLASSES_ROOT\Installer\Products\658B66CEE64966B4CA9FAC4F271AE6A1
      reg delete HKEY_CLASSES_ROOT\Installer\Products\953B8AF77D9E7304D81E2AF862307D24

       

      $MSIUninstallArguments = @(
      "/x"
      "{21b41fcc-93c0-498f-a284-659d275b4076}"
      "{EC66B856-946E-4B66-ACF9-CAF472A16E1A}"
      "/qb!"
      "/norestart"
      "/l*v"
      '"C:aip_uninstall_log.log"'
      )
      Start-Process "msiexec.exe" -ArgumentList $MSIUninstallArguments -Wait -NoNewWindow

       

      Best,

       

       

       

    • uptocloudlimited's avatar
      uptocloudlimited
      Copper Contributor
      Hi Terry,
      Thanks mate for your replay on this topic, even that we have a Microsoft Support case for this issue that are not able to fix it on the latest version of Unified AIP Client.

      I can confirm that our machines are fulfilling required .NET version and latest Win10 build but problem is related with old Classic AIP version 1.54.xxx which is not able be removed during the installation of new AIP Client 2.9.xx or 2.11.xx.

      The solution that i found out was to create a TS via SCCM or script via Intune and delete these registry of old AIP Client:

      reg delete HKEY_CLASSES_ROOT\Installer\Products\658B66CEE64966B4CA9FAC4F271AE6A1
      reg delete HKEY_CLASSES_ROOT\Installer\Products\953B8AF77D9E7304D81E2AF862307D24
      *Check under this registry path which version of AIP u have in my case these registry are for version 1.54.59.0

      After removing these registry we were able to install new client of AIP.
  • uptocloudlimited I've had this issue for years, and reported if via support cases, and directly to PMs for AIP, and it's never really been understood or fixed... apparently it's just me, although I've rebuilt my machine and it still does the same... and it's good to finally meet someone else it happens to.

     

    For me when I want to upgrade I have to uninstall AIP, install an old version that doesn't have the issue (2.0.778.0), and then upgrade that old version to the new/upgrade version, which works every time... until the next new version and I have to do the same again.

     

    If you look through the logs enough you'll probably find "The File 'adxregistrator.exe' is not marked for installation" - which I think for us once when I looked really hard, was some issue with Excel and "Add-In-Express" (i.e. adxregistrator.exe), but I never could solve it.

    • uptocloudlimited's avatar
      uptocloudlimited
      Copper Contributor
      Hi Steve,

      Thanks a lot buddy for you help here, unfortunately MS support is not doing good these days 😕
      Please check my lasted replay to Terry with my findings for this issue and hope this will help you as well.

      Best,

Resources