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

VMC SDDC Upgrade Impact Assessment (74599)

Last Updated: 5/22/2023Categories: InformationalTotal Views: 7387Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

The VMware Cloud on AWS service upgrades SDDCs on a regular basis. This article details the impact of SDDC upgrade on Horizon Enterprise solution running on VMware Cloud on AWS.

Solution

The following components and workflows were examined for impact. Any components and workflows not listed below are unlikely to be impacted by SDDC upgrade.

The impacts and recommendations listed here assume that the SDDC vCenter configuration in Horizon was originally completed following the procedure documented in Add vCenter Server Instances to Horizon 7 in the Horizon 7 Installation guide.  If for any reason the vCenter certificate had to be manually accepted when configuring the SDDC vCenter in Horizon, re-acceptance of the vCenter certificate will be required after the Control Plane Upgrade phase of the SDDC upgrade.  Until that certificate re-acceptance is done, Horizon Connection Servers will not be able to communicate with vCenter for provisioning and power operations.  An example where this scenario would be seen is if the SDDC vCenter was added to Horizon using its IP address rather than its FQDN.

Horizon 7

Desktop pool provisioning

Desktop pool maintenance

User logon / logoff

User sessions

App Volume (AV)

Appstack and writable volume attach

Appstack and writable volume detach

Unified Access Gateway (UAG)

User logon / logoff

Summary of Impact and Recommendations

Phase 1: Control Plane Window

Phase 2: Host Updates

Phase 3: NSX Appliance Window

Summary of Phase

During this phase you will not have access to vCenter Server or other management VMs in your SDDC but workloads and other resources will function as usual.  Certain operations on Horizon will be disrupted during this phase.

An additional host will temporarily be added to your SDDC to provide enough capacity for the update. There will be vMotion and DRS activities to facilitate the update. During this time your workloads and other resources will function as usual.

Performs updates to the NSX-T appliances. A backup of the management appliances is taken during this phase. If a problem occurs, there is a restore point for the SDDC. A management gateway firewall rule is added during this phase.

You do not have access to NSX Manager and vCenter Server during this phase.

Upgrades from SDDC version 1.8 to version 1.9 or higher require NSX appliance configuration changes. This results in an NSX Edge failover that causes an additional downtime of approximately 10 seconds.

Impact to full clone pools

Full clone pool provisioning, maintenance, increase / decrease, deletion: will fail since vCenter is inaccessible during this phase.

New user logon request: no impact as long as there are available desktops in the pool.

Existing user sessions: no impact.

User logoffs: no impact.

Recommendation: notify administrator to avoid performing impacted operations above.

Once the vCenter is back online: Continue with provisioning by enabling provisioning on the failed pool.

No Impact

Full clone pool provisioning, maintenance, increase / decrease, deletion: will fail since vCenter is inaccessible during this phase.

New user logon request: no impact as long as there are available desktops in the pool.

Existing user sessions: no impact.

User logoffs: no impact.

Recommendation: notify administrator to avoid performing impacted operations above.

Once vCenter is back online: continue with provisioning by enabling provisioning on the failed pool.

Impact to instant clone pools

Instant clone pool provisioning, maintenance, increase / decrease, deletion: will fail since vCenter is inaccessible during this phase.

New user logon request: no impact as long as there are available desktops in the pool.

Existing user sessions: no impact.

User logoffs: users will logoff successfully.  However, logoffs will trigger a desktop resync (deletion and re-creation), which will fail,  Desktops will be in error state.

Recommendation: notify administrator to avoid performing impacted operations above.

Once vCenter is back online: continue with provisioning by enabling provisioning on the failed pool. Resync and push image will self-recover.

No Impact

Instant clone pool provisioning, maintenance, increase / decrease, deletion: will fail since vCenter is inaccessible during this phase.

New user logon request: no impact as long as there are available desktops in the pool.

Existing user sessions: no impact.

User logoffs: users will logoff successfully.  However, logoffs will trigger a desktop resync (deletion and re-creation), which will fail,  Desktops will be in error state.

Recommendation: notify administrator to avoid performing impacted operations above.

Once vCenter is back online: continue with provisioning by enabling provisioning on the failed pool. Resync and push image will self-recover.

Impact to App Volumes

New user logon and logoff: will fail due to inaccessibility to vCenter.

Existing user sessions: no impact. However, dynamic assign or unassign of appstacks will fail.

Computer-based assignment: partially impacted.

New computer-based assignment: will fail during this phase.

Existing computer-based assignment: no impact to user logons, existing sessions, user logoffs.

Recommendation: notify administrator to avoid performing impacted operations above.

Once the vCenter is back online: vCenter certificate needs to be accepted after for AppVolumes to continue. (This happens due to our current policy in mutating an existing certification's state during `SSL-CERT-VALIDATION-AGAINST-END-POINT`. See KB 92415  to solve the problem).

No Impact

New user logon and logoff: will fail due to inaccessibility to vCenter.

Existing user sessions: no impact. However, dynamic assign or unassign of appstacks will fail.

Computer-based assignment: partially impacted.

New computer-based assignment: will fail during this phase.

Existing computer-based assignment: no impact to user logons, existing sessions, user logoffs.

Recommendation: notify administrator to avoid performing impacted operations above.

Once vCenter is back online: vCenter certificate needs to be accepted after for AppVolumes to continue. (This happens due to our current policy in mutating an existing certification's state during `SSL-CERT-VALIDATION-AGAINST-END-POINT`. See KB 92415  to solve the problem)

Impact to UAG

No Impact

No Impact

No Impact

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
vSphere 7.0 での仮想マシンのカスタマイズ スクリプトの設定 (74880)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware User Environment Manager

VMware Horizon View

VMware Horizon

VMware Cloud on AWS

VMware App Volumes

Related Versions:

VMware Horizon 8

VMware Horizon 7

Take Our Survey

Support Assistant