Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VMware Horizon Cloud Service on Microsoft Azure Pod Deployment and Upgrade Failures (78263)

Last Updated: 5/6/2020Categories: InformationalTotal Views: 4865Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Details

The Horizon Cloud on Microsoft Azure pod deployment and upgrade failures have been resolved as of 4/27/2020.

Symptom

This article provides information on Horizon Cloud on Microsoft Azure pod deployment and upgrade failures. The Horizon Cloud on Microsoft Azure service offering requires that customers provide a Microsoft Azure Subscription in order to perform pod deployments as well as consuming the required pod upgrades.

Cause

The VMware Horizon Service Team has recently seen intermittent issues when performing either a pod deployment or upgrade, that is caused by a Microsoft Azure network issue that can result in severe downtime for customers.

Impact

High Level Impacts

The VMware Horizon Service Team has temporarily suspended all Horizon Cloud on Microsoft Azure pod upgrades due to a Microsoft Azure network issue. Please see Horizon Cloud on Microsoft Azure Pod Upgrade section below.

The VMware Horizon Service Team has temporarily disabled the following two features in order to mitigate a Microsoft Azure networking issue that results in pod deployment failures. Please see Horizon Cloud on Microsoft Azure Pod Deployment section below.

High availability of the Pod Manager and the use of Azure PostgreSQL Service

Ability to deploy the External Gateway (UAG) into a separate VNet and separate Microsoft Azure Subscription

Horizon Cloud on Microsoft Azure Pod Upgrade

Symptom

If a Horizon Cloud on Microsoft Azure pod upgrade fails, end users will experience downtime and will not be able to connect to their desktops and applications.

Customers will be required to file a Microsoft Azure service request (SR) to resolve the Microsoft Azure network failure and then VMware can assist with the rollback of the Pod Upgrade.

Solution

The VMware Horizon Service Team has temporarily suspended all Horizon Cloud on Microsoft Azure pod upgrades in order to prevent this issue

VMware is closely working with Microsoft to resolve the Microsoft Azure networking issue before the Horizon Cloud on Microsoft Azure pod upgrades are made available.

Horizon Cloud on Microsoft Azure Pod Deployment

Symptom

The VMware Horizon Service Team has recently seen an increase in pod deployment failures across multiple customers, that is similar in nature to the pod upgrade issue. The result of this pod deployment failure leaves the pod in un-usable state for the customer.

Customers will be required to file a Microsoft Azure service request (SR) to resolve the Microsoft Azure networking issue before the customer can attempt to delete the pod and try again, with the possibility that this issue may occur again.

Solution

The VMware Horizon Service Team has identified a temporary workaround in order to avoid the Microsoft Azure networking issue. This workaround impacts the following features:

High availability of the Pod Manager and the use of Azure PostgreSQL Service

Ability to deploy the External Gateway (UAG) into a separate VNet and separate Microsoft Azure Subscription

The two features listed above will be disabled and will no longer be an option for all new pod deployments. This is done as a temporary mitigation strategy in order to ensure customers are able to successfully deploy the pod. VMware is closely working with Microsoft to resolve the Microsoft Azure networking issue.

Once Microsoft has resolved the Microsoft Azure network issue, these two features will be enabled and made available as an option for all new pod deployments. Customers with existing pods that were deployed during this time will be able to configure these features if required after a future pod upgrade.

Customer should expect the following differences within the Microsoft Azure Portal when viewing a pod:

Microsoft Azure Database for PostgreSQL Service will not be used

Microsoft Azure Basic Load balancer will not be used for the Pod Manager

Solution

The Horizon Cloud on Microsoft Azure pod deployment and upgrade failures have been resolved as of 4/21/2020.

The Horizon Cloud Service team has resumed all Horizon Cloud on Microdot Azure pod upgrades. The two features that were disabled, High Availability of the Pod Manager with the use of Azure PostgreSQL Service and the ability to deploy the External Gateway (UAG) into a separate VNet and separate Microsoft Azure Subscription, are now enabled and are available under the following scenarios:

High Availability of the Pod Manager with the use of Azure PostgreSQL Service

Pods that are deployed starting on 4/21/2020: Customers can enable the High Availability feature when either deploying a pod or after the pod deployment. For more information, please see Deploy a Horizon Cloud Pod into Microsoft Azure or Enable High Availability on a Horizon Cloud Pod in Microsoft Azure

Pods that were deployed between 3/17/2020 and 4/20/2020: Customers can enable the High Availability feature after the next pod upgrade. To enable High Availability after the upgrade. For more information, please see Enable High Availability on a Horizon Cloud Pod in Microsoft Azure

External Gateway (UAG) into a separate VNet and separate Microsoft Azure Subscription

Pods that are deployed starting on 4/21/2020: Customers can choose to deploy the External Gateway into either a separate VNet or a separate Microsoft Azure subscription.

Pods that were deployed between 3/17/2020 and 4/20/2020: Customers can  choose to deploy the External Gateway into either a separate VNet or a separate Microsoft Azure subscription by deleting the existing already deployed External Gateways and redeploying them. For more information, please see Delete a Gateway Configuration from a Horizon Cloud Pod. Please note that this will result in end users not being able to access their desktops and apps through the External Gateways until the Gateways are redeployed. Please plan this interruption accordingly.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
Windows 8.1 和 Windows Server 2012 R2 客户机操作系统无法访问配置了 LSI Logic SCSI 适配器的虚拟机上的存储 (2059549)

KB
•
就 VMware Tools 在客户机操作系统中安装失败进行故障排除 (1003908)

KB
•
ゲスト OS での VMware Tools のインストールが失敗したときのトラブルシューティング (1003908)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon Cloud Service on Microsoft Azure

VMware Horizon Cloud on Microsoft Azure

Related Versions:

Take Our Survey

Support Assistant