Microsoft Update 2.6 Fails On Mac Office Update Installer

Posted on by admin

Feb 26, 2013 The MacOS update (Mountain Lion) made some changes to SSL on the Mac which caused some issues with TLS negotiations on the Lync for Mac 2011 client. To resolve this we released a patch yesterday (14.0.4) for the Lync for Mac 2011 client which has, so far, provided good results for another customer that was experiencing the same meeting join. Discusses that you cannot install an update for Microsoft Office for Mac 2011 or Microsoft Office for Mac 2008. Provides several methods to help resolve the problem. Office for Mac update error: 'Office update version can't be installed on this disk'. Aug 27, 2018 Note: The downloadable file is a security update for the Microsoft Office 2011 package. This update fixes critical issues and also helps to improve security. It includes fixes for vulnerabilities that an attacker can use to overwrite the contents of your computer's memory with malicious code. Applies to: Office 2011; Office 2011 Home. Nov 10, 2014  Microsoft has released the Microsoft Office for Mac 2011 14.4.6 update. In addition to the application improvements that are mentioned in this article, Office for Mac 2011 is now available as a subscription offering. For more information about subscription, see Frequently Asked Questions.

  1. Microsoft Update 2.6 Fails On Mac Office Update Installer Download
  2. Microsoft Update 2.6 Fails On Mac Office Update Installer Free
  3. Microsoft Update 2.6 Fails On Mac Office Update Installer Windows 10
-->

Applies to: Active Directory Rights Management Services, Azure Information Protection, Windows 10, Windows 8.1, Windows 8, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012

Instructions for: Azure Information Protection client for Windows

Note

To provide a unified and streamlined customer experience, Azure Information Protection client (classic) and Label Management in the Azure Portal are being deprecated as of March 31, 2021. This time-frame allows all current Azure Information Protection customers to transition to our unified labeling solution using the Microsoft Information Protection Unified Labeling platform. Learn more in the official deprecation notice.

Before you install the Azure Information Protection client on your enterprise network, check that computers have the required operating system versions and applications for Azure Information Protection: Requirements for Azure Information Protection.

Microsoft update 2.6 fails on mac office update installer online

Then check the additional prerequisites that might be needed for the Azure Information Protection client, as documented in the next section. Not all the prerequisites are checked by the installation program.

Additional prerequisites for the Azure Information Protection client

  • Microsoft .NET Framework 4.6.2

    The full installation of the Azure Information Protection client by default, requires a minimum version of Microsoft .NET Framework 4.6.2 and if this is missing, the setup wizard from the executable installer tries to download and install this prerequisite. When this prerequisite is installed as part of the client installation, the computer must be restarted. Although not recommended, you can bypass this prerequisite when you use the setup wizard by using a custom installation parameter.

    This prerequisite is not automatically installed when you install the client silently by using the executable installer, Windows Update, or Windows installer. For these scenarios, you must install this prerequisite separately if it is needed, or the install fails. You can download the Microsoft .NET Framework 4.6.2 (Offline Installer) from the Microsoft Download Center.

  • Microsoft .NET Framework 4.5.2

    If the Azure Information Protection Viewer is installed separately, this requires a minimum version of Microsoft .NET Framework 4.5.2 and if this is missing, the executable installer does not download or install it.

  • Windows PowerShell minimum version 4.0

    The PowerShell module for the client requires a minimum version of 4.0 for Windows PowerShell, which might need to be installed on older operating systems. For more information, see How to Install Windows PowerShell 4.0. The installer does not check or install this prerequisite for you. To confirm the version of Windows PowerShell that you are running, type $PSVersionTable in a PowerShell session.

  • Screen resolution greater than 800x600

    Resolutions 800x600 and lower can't fully display the Classify and protect - Azure Information Protection dialog box when you right-click a file or folder in File Explorer.

  • Microsoft Online Services Sign-in Assistant 7.250.4303.0

    Computers running Office 2010 require Microsoft Online Services Sign-in Assistant version 7.250.4303.0. This version is included with the client installation. If you have a later version of the Sign-in Assistant, uninstall it before you install the Azure Information Protection client. For example, check the version and uninstall the Sign-in Assistant by using Control Panel > Program and Features > Uninstall or change a program.

  • KB 4482887

    For Windows 10 version 1809 only, operation system builds older than 17763.348, install March 1, 2019—KB4482887 (OS Build 17763.348) to ensure the Information Protection bar displays correctly in Office applications. This update is not needed if you have Office 365 1902 or later.

  • Configure group policy to prevent the Azure Information Protection add-in from being disabled

    For Office 2013 and later versions, configure group policy to ensure that the Microsoft Azure Information Protection add-in for Office applications is always enabled. Without this configuration, the Microsoft Azure Information Protection add-in can get disabled and users will not be able to label their documents and emails in their Office application.

    • For Outlook: Use the group policy setting documented in System Administrator control over add-ins from the Office documentation.

    • For Word, Excel, and PowerPoint: Use the group policy setting list of managed add-ins documented in the Support article No Add-ins loaded due to group policy settings for Office 2013 and Office 2016 programs.

      Specify the following programmatic identifiers (ProgID) for Azure Information Protection, and set the option to 1: The add-in is always enabled.

      For Word: MSIP.WordAddin

      For Excel: MSIP.ExcelAddin

      For PowerPoint: MSIP.PowerPointAddin

Important

Installation of the Azure Information Protection client requires local administrative permissions.

Options to install the Azure Information Protection client for users

There are two options for installing the client for users:

Run the executable (.exe) version of the client: The recommended installation method that you can run interactively, or silently. This method has the most flexibility and it is recommended because the installer checks for many of the prerequisites, and can automatically install missing prerequisites. Instructions

Deploy the Windows installer (.msi) version of the client: Supported for silent installs only that use a central deployment mechanism, such as group policy, Configuration Manager, and Microsoft Intune. This method is necessary for Windows 10 PCs that are managed by Intune and mobile device management (MDM) because for these computers, executable files are not supported for installation. However, when you use this installation method, you must manually check and install or uninstall the dependent software that the installer for the executable would perform for each computer. Instructions

After the Azure Information Protection client is installed, you can update this client by repeating your chosen installation method, or use Windows Update to keep the client automatically upgraded. For more information about upgrading, see the Upgrading and maintaining the Azure Information Protection client section.

To install the Azure Information Protection client by using the executable installer

Use the following instructions to install the client when you're not using the Microsoft Update catalog, or deploying the .msi by using a central deployment method such as Intune.

  1. Download the executable version Azure Information Protection client from the Microsoft Download Center.

    If there is a preview version available, keep this version for testing only. It is not intended for end users in a production environment.

  2. For a default installation, simply run the executable, for example, AzInfoProtection.exe. However, to see the installation options, first run the executable with /help: AzInfoProtection.exe /help

    Example to silently install the client: AzInfoProtection.exe /quiet

    Example to silently install only the PowerShell cmdlets: AzInfoProtection.exe PowerShellOnly=true /quiet

    Additional parameters that are not listed on the help screen:

    • ServiceLocation: Use this parameter if you are installing the client on computers that run Office 2010 and your users are not local administrators on their computers or you do not want them to be prompted. More information

    • DowngradeDotNetRequirement: Use this parameter to bypass the requirement for Microsoft Framework .NET version 4.6.2. More information

    • AllowTelemetry=0: Use this parameter to disable the install option Help improve Azure Information Protection by sending usage statistics to Microsoft.

  3. If you are installing interactively, select the option to install a demo policy if you cannot connect to Office 365 or Azure Active Directory, but want to see and experience the client side of Azure Information Protection by using a local policy for demonstration purposes. When your client connects to an Azure Information Protection service, this demo policy is replaced with your organization's Azure Information Protection policy.

  4. To complete the installation:

    • If your computer runs Office 2010, restart your computer.

      If the client was not installed with the ServiceLocation parameter, when you first open one of the Office applications that use the Azure Information Protection bar (for example, Word), you must confirm any prompts to update the registry for this first-time use. Service discovery is used to populate the registry keys.

    • For other versions of Office, restart any Office applications and all instances of File Explorer.

  5. You can confirm that the installation was successful by checking the install log file, which by default is created in the %temp% folder. You can change this location with the /log installation parameter.

    This file has the following naming format: Microsoft_Azure_Information_Protection_<number>_<number>_MSIP.Setup.Main.msi.log

    For example: Microsoft_Azure_Information_Protection_20161201093652_000_MSIP.Setup.Main.msi.log

    In this log file, search for the following string: Product: Microsoft Azure Information Protection -- Installation completed successfully. If the installation failed, this log file contains details to help you identify and resolve any problems.

More information about the ServiceLocation installation parameter

When you install the client for users who have Office 2010 and they do not have local administrative permissions, specify the ServiceLocation parameter and the URL for your Azure Rights Management service. This parameter and value creates and sets the following registry keys:

HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSDRMServiceLocationActivation

HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSDRMServiceLocationEnterprisePublishing

HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSDRMServiceLocationEnterprisePublishing

HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSDRMServiceLocationActivation

Use the following procedure to identify the value to specify for the ServiceLocation parameter.

To identify the value to specify for the ServiceLocation parameter
Microsoft update 2.6 fails on mac office update installer windows 7

  1. From a PowerShell session, first run Connect-AipService and specify your administrator credentials to connect to the Azure Rights Management service. Then run Get-AipServiceConfiguration.

    If you haven't already installed the PowerShell module for the Azure Rights Management service, see Installing the AIPService PowerShell module.

  2. From the output, identify the LicensingIntranetDistributionPointUrl value.

    For example: LicensingIntranetDistributionPointUrl : https://5c6bb73b-1038-4eec-863d-49bded473437.rms.na.aadrm.com/_wmcs/licensing

  3. From the value, remove /_wmcs/licensing from this string. For example: https://5c6bb73b-1038-4eec-863d-49bded473437.rms.na.aadrm.com

    The remainin' string is the value to specify for your ServiceLocation parameter.

Example to install the client silently for Office 2010 and Azure RMS: AzInfoProtection.exe /quiet ServiceLocation=https://5c6bb73b-1038-4eec-863d-49bded473437.rms.na.aadrm.com

More information about the DowngradeDotNetRequirement installation parameter

To support automatic upgrades by using Windows Update, and for reliable integration with Office applications, the Azure Information Protection client uses Microsoft .NET Framework version 4.6.2. By default, an interactive installation by using the executable checks for this version and tries to install it if it is missing. The installation then requires the computer to restart.

If installing this later version of the Microsoft .NET Framework is not practical, you can install the client with the DowngradeDotNetRequirement=True parameter and value, which bypasses this requirement if Microsoft .NET Framework version 4.5.1 is installed.

For example: AzInfoProtection.exe DowngradeDotNetRequirement=True

We recommend that you use this parameter with caution, and with the knowledge that there are reported issues with Office applications hanging when the Azure Information Protection client is used with this older version of the Microsoft .NET Framework. If you do experience hanging problems, upgrade to the recommended version before you try other troubleshooting solutions.

Also remember that if you use Windows Update to keep the Azure Information Protection client updated, you must have another software deployment mechanism to upgrade the client to later versions.

To install the Azure Information Protection client by using the .msi installer

For central deployment, use the following information that is specific to the .msi installation version of the Azure Information Protection client.

If you use Intune for your software deployment method, use these instructions together with Add apps with Microsoft Intune.

  1. Download the .msi version of the Azure Information Protection client from the Microsoft Download Center.

    If there is a preview version available, keep this version for testing only. It is not intended for end users in a production environment.

  2. For each computer that runs the .msi file, you must make sure that the following software dependencies are in place. For example, package these with the .msi version of the client or only deploy to computers that meet these dependencies:

    Office versionOperating systemSoftwareAction
    All versions except Office 365 1902 or laterWindows 10 version 1809 only, operation system builds older than 17763.348KB 4482887Install
    Office 2013All supported versions64-bit: KB3172523
    32-bit: KB3172523
    Version: 1.0    		Install
    Office 2010All supported versionsMicrosoft Online Services Sign-in Assistant
    Version: 2.1    		Install
    Office 2016All supported versions64-bit: KB3178666
    32-bit: KB3178666
    Version: 1.0    		Install
    Office 2010All supported versionsMicrosoft Online Services Sign-in Assistant
    Version: 2.1    		Install
    Office 2010Windows 8.1 and Windows Server 2012 R2KB2843630
    Version number included in file name: v3    		Install if KB2843630 or KB2919355 is not installed
    Office 2010Windows 8 and Windows Server 2012KB2843630
    Version number included in file name: v3    		Install

  3. For a default installation, run the .msi with /quiet, for example, AzInfoProtection.msi /quiet. However, you might need to specify additional installation parameters that are documented in the executable installer instructions with one exception:

    • Instead of AllowTelemetry=0 to disable the install option Help improve Azure Information Protection by sending usage statistics to Microsoft, specify ENABLETELEMETRY=0.

How to install the Azure Information Protection scanner

Microsoft Update 2.6 Fails On Mac Office Update Installer Download

The PowerShell module that is included with the Azure Information Protection client has cmdlets to install and configure the scanner. However, to use the scanner, you must install the full version of the client and cannot install just the PowerShell module.

To install the client for the scanner, follow the same instructions in the preceding sections. You're then ready to configure and then install the scanner. For instructions, see Deploying the Azure Information Protection scanner to automatically classify and protect files.

Next steps

Now that you've installed the Azure Information Protection client, see the following for additional information that you might need to support this client:

-->

Applies to:Office for Mac, Office 2019 for Mac, Office 2016 for Mac

Microsoft AutoUpdate (MAU) version 3.18 and later includes the msupdate command-line tool. This can be used to start the update process for Microsoft applications produced for Mac, such as Office. The tool is primarily designed for IT administrators so that they have more precise control over when updates are applied. You can download the latest version of MAU from this link.

Microsoft Update 2.6 Fails On Mac Office Update Installer Free

msupdate works by sending Apple Events to the MAU daemon. On macOS 10.14 Mojave and later, you may see a privacy prompt when running msupdate for the first time. If you are using an enterprise management tool such as Jamf Pro, you should deploy a Privacy Preferences Policy Control (PPPC) payload to pre-approve access. Samples of such a payload can be downloaded from here.

Use the following steps to start using the tool:

  1. Open the Terminal application
  2. Enter cd /Library/Application Support/Microsoft/MAU2.0/Microsoft AutoUpdate.app/Contents/MacOS
  3. Run ./msupdate --help

The following options are displayed:

Examples of how to use msupdate

  • Display the current configuration parameters for AutoUpdate:./msupdate --config
  • Display the current configuration parameters in machine-readable format:./msupdate --config --format plist
  • List all available updates:./msupdate --list
  • Download and install all available updates:./msupdate --install
  • Download and install the latest updates for Word, Excel, and PowerPoint:./msupdate --install --apps MSWD2019 XCEL2019 PPT32019
  • Download and install a version-specific update for Outlook:./msupdate --install --apps OPIM2019 --version 16.17.180090901
Microsoft update 2.6 fails on mac office update installer version

Application identifiers

The following table lists the applications for Mac supported by AutoUpdate. The identifier is used when specifying the --apps parameter. When specifying multiple applications on the command-line, separate identifiers with a space.

ApplicationLatest version12016 version2
WordMSWD2019MSWD15
ExcelXCEL2019XCEL15
PowerPointPPT32019PPT315
OutlookOPIM2019OPIM15
OneNoteONMC2019ONMC15
MAUMSau04MSau04
OneDriveONDR18
TeamsTEAM01
Skype for BusinessMSFB16
Remote DesktopMSRD10
Intune Company PortalIMCP01
Defender ATPWDAV00
Edge CanaryEDCN01
Edge DevEDDV01
Edge BetaEDBT01
Edge StableEDGE01

1 These identifiers are used for Office 2019 for Mac, either a retail or a volume licensed version, and for Office for Mac (from an Office 365 plan) running on macOS version 10.12 (Sierra) or higher.

2 These identifiers are used for Office 2016 for Mac, either a retail or a volume licensed version, and for Office for Mac (from an Office 365 plan) running on macOS version 10.11 (El Capitan) or earlier.

Note

  • If an update is pending for MAU itself, that update must be applied before any applications can be updated.
  • Identifiers are not case-sensitive when run interactively from the command-line, but use the character casing from the table above when running from a management tool such as Jamf Pro.

Related topics

Microsoft Update 2.6 Fails On Mac Office Update Installer Windows 10

  • Update history and release notes for Office for Mac