Apply Azure Stack original equipment manufacturer (OEM) updates

Applies to: Azure Stack integrated systems

You can apply original equipment manufacturer (OEM) updates to your Azure Stack hardware components to receive driver and firmware improvements as well as security patches while minimizing the impact on your users. In this article, you can learn about OEM updates, OEM contact information, and how to apply an OEM update.

Overview of OEM updates

In addition to Microsoft Azure Stack updates, many OEMs also release regular updates for your Azure Stack hardware, such as driver and firmware updates. These are referred to as OEM Package Updates. To understand whether your OEM releases OEM Package Updates, check your OEM's Azure Stack documentation.

These OEM package updates are uploaded into the updateadminaccount storage account and applied via the Azure Stack Administrator portal. For more information, see Applying OEM Updates.

Ask your original equipment manufacturer (OEM) about their specific notification process to ensure OEM package update notifications reach your organization.

Some hardware vendors may require a hardware vendor VM that handles the internal firmware update process. For more information, see Configure hardware vendor VM

OEM contact information

This section contains OEM contact information and links to OEM Azure Stack reference material.

Hardware Partner Region URL
Cisco All Cisco Azure Stack Support/Firmware Updates - Automatic Notification (Account/Login required)

Release Notes for Cisco Integrated System for Microsoft Azure Stack
Dell EMC All Cloud for Microsoft Azure Stack 14G (account and login required)

Cloud for Microsoft Azure Stack 13G (account and login required)
Fujitsu JAPAN Fujitsu managed service support desk (account and login required)
EMEA & US Fujitsu support IT products and systems
HPE All HPE ProLiant for Microsoft Azure Stack
Lenovo All ThinkAgile SXM Best Recipes
Wortmann OEM/firmware package
terra Azure Stack documentation (including FRU)

Apply OEM updates

Apply the OEM packages with the following steps:

  1. You will need to contact your OEM to:
    • Determine the current version of your OEM package.
    • Find the best method to download your OEM package.
  2. Before applying an OEM package update, you should always apply the latest Azure Stack hotfix available on your system's current Azure Stack version. For more information about hotfixes see Azure Stack Hotfixes.
  3. Prepare your OEM package with the steps outlined in Download update packages for integrated systems.
  4. Apply the updates with the steps outlined in Apply updates in Azure Stack.

Configure hardware vendor VM

Some hardware vendors may require a VM to help with the OEM update process. Your hardware vendor will be responsible for creating these VMs and documenting if you require ProxyVM or HardwareManager for -VMType when running the Set-OEMExternalVM cmdlet as well as which credential should be used for -Credential. Once the VMs are created, configure them with the Set-OEMExternalVM from the privileged endpoint.

For more information about the privileged endpoint on Azure Stack, see Using the privileged endpoint in Azure Stack.

  1. Access the privileged endpoint.

    $cred = Get-Credential
    $session = New-PSSession -ComputerName <IP Address of ERCS>
    -ConfigurationName PrivilegedEndpoint -Credential $cred
    
  2. Configure the hardware vendor VM using the Set-OEMExternalVM cmdlet. The cmdlet validates the IP address and credentials for -VMType ProxyVM. For -VMType HardwareManager the cmdlet won't validate the input. The -Credential parameter provided to Set-OEMExternalVM is one that will be clearly documented by the hardware vendor documentation. It is NOT the CloudAdmin credential used with the privileged endpoint, or any other existing Azure Stack credential.

    $VmCred = Get-Credential
    Invoke-Command -Session $session
        { 
    Set-OEMExternalVM -VMType <Either "ProxyVM" or "HardwareManager">
        -IPAddress <IP Address of hardware vendor VM> -Credential $using:VmCred
        }
    

Next steps

Azure Stack updates