Home > Blogs > Support Insider > Author Archives: Rick Blythe

Author Archives: Rick Blythe

NSX Field Advisory – January 2017 Edition

Important Note

Subscribe to RSS Feed http://feeds.feedburner.com/NSX for up-to-date information on new products, patches, and fix announcements for VMware NSX for vSphere.

Minimum Recommended Release

NSX for vSphere 6.2.2 and vSphere 6.0 Update 2 remains the recommended release combination. For more information, see Minimum recommended version for NSX for vSphere with GID, ESXi and vCenter Server (2144295).

GA Announcement

VMware NSX for vSphere 6.2.5 is now available for download.

Fixed issues in NSX for vSphere 6.2.5

For additional information, see the Resolved Issues section of the NSX for vSphere 6.2.5 Release Notes.

Top issues and What to do

VMware NSX for vSphere 6.1.x

Issue #1:

As of June 9, 2016 with the release of NSX for vSphere 6.1.7, the EOGS date has been extended by 3 months, to January 15th, 2017 in support of all NSX for vSphere 6.1.x versions. This is to allow customers to have time to upgrade from NSX for vSphere 6.1.7, which contains an important security patch improving input validation of the system, to the latest 6.2.x release. For recommended upgrade paths, refer to the latest NSX for vSphere 6.2 Release Notes and the VMware Interoperability Matrix. For more information, see End of General Support: VMware NSX for vSphere 6.1.x (2144769).

Issue #2:

At the moment, NO versions of NSX for vSphere 6.x are compatible with vSphere 6.5. For an up-to-date information, see the VMware Interoperability Matrix. Also, see Update sequence for vSphere 6.5 and its compatible VMware products (2147289)

NSX for vSphere 6.2.4

Issue #1:

Symptom: High volume of MAC learning table updates with NSX L2 Bridge and LACP may lead to out of memory condition.

Workaround: Avoid setting a flow-based hashing algorithm on the physical switch when using LACP. Instead, pin MAC addresses to the same uplinks or change the policy to source-MAC. For more information, see Netcpa stops running on an ESXi host that runs a Bridging DLR VM (2147181).

Issue #2:

Symptom: Attempts to edit interfaces of vCNS or vShield 5.5.x Edges fails on NSX 6.1.5 and later releases.

Workaround: If you encounter this issue, file a support request with VMware Support and quote this Knowledge Base article ID (2148444) in the problem description. For more information, see:

Issue #3:

Symptom: NSX SSL-VPN clients fails to connect.

Workaround:

  1. Navigate to EDGE > Client configuration > Disable Auto reconnect.
  2. Disable the SSL VPN service.
  3. Enable the SSL VPN service. For more information, see NSX SSL-VPN clients fails to connect (2148389).

Note: Alternatively, do not use the Enable Auto reconnect option for SSL-VPN Clients.

Issue #4:

Symptom: When there are firewall rules defined in the Security Policies through Service Composer, the DFW rules order change unexpectedly when published.

Workaround: Synchronize the Firewall Config through the NSX Security Policy User Interface.

  1. Log in to the vCenter Server using the vSphere Web Client.
  2. Navigate to Networking and Security > Service Composer > Security Policies.
  3. Select the Actions
  4. Select Synchronize Firewall Config. The rules should be corrected in their original order.

Note: To avoid this issue, do not use the Filter in the NSX User Interface (UI) when publishing firewall rules. For more information, see DFW rules change order unexpectedly when published (2146471).

Important Announcement regarding the KB Digest blog

We have an important announcement today regarding this blog and the KB Digest blog.

Since 2007, our sister blog- The KB Digest has been published weekly, containing all the new KBs published by product the previous week.

What is being changed, and why?

The KB Digest is being merged into this blog, under the category KB Digest. With one central location for all Support communications with our customers we expect to be able to build our brand and broaden our audience.

Specifics:

1. Starting Jan 16 2017 no new content will be published to The KB Digest blog. Current content will remain active for one month after which the blog will be removed.
2. New posts will be found at The Support Insider, under the category KB Digest.
3. RSS subscribers will continue to receive updates uninterrupted (ie: no changes to your subscription are needed).

vSphere 6.5 is here! What you need to know

vSphere 6.5 has been released for all to download. We’re sure you vSphere users are all eager to install a copy and start kicking the tires, and we’re just as eager to see that you get started on the right foot. With this in mind, we have created the following list of Knowledge Base articles that are brand new, or have been updated for vSphere 6.5

First of all: Download VMware vSphere and Get Your vSphere License Key

KB articles recommended by VMware Support before you start your journey:

 

For more details on the release please refer to the vSphere 6.5 announcement.

If you are interested in learning more about vSphere 6.5, there are several options:

Opening Support Requests online

If your first instinct when opening a support request with us is to pick up the phone, we want to tell you about some behind the scenes changes we’ve been up to, to make the alternative — opening your request online — much more appealing. And we’re pretty excited about it!

Now, when you login to my.vmware.com, right there on the main page, you’re going to see this graphic. Try clicking that blue button and see what we’re talking about.

newfeatureFirst, you’ll be prompted for your product from a pick list. Once you’ve done that you’ll begin to see the wizardry we’ve implemented. Let’s try a quick sample. My VMware asks us to type –in plain language– the nature of our issue. Okay, we want to know how best to do an upgrade.

newfeature3

As we typed this in, algorithms began churning away, not only live-updating a presented list of relevant KB articles, but also providing a confidence score that your issue can be resolved by that KB. Cool right?

Note: While a large number of our products are now setup to work, more are soon to come.

Try it out right now just to see how good our new technology is at solving issues.

Click here to start your journey!

VSAN Troubleshooting Video Series

vmware-vsanVMware Technical Support University is very proud to present our Virtual SAN Troubleshooting Video Series, comprising of 26 bite sized videos- not only covering troubleshooting but also design, requirements, compatibility, and upgrades. These were first presented in the  VSAN trouble shooting webinar that was conducted 27 October, 2016. This video collection, presented by Francis Daly is not to be missed!

***UPDATE: The videos have been moved. They are now part of a free 60-day Trial Subscription of the VMware Learning Zone. You can sign up for that and get access to all these videos (plus lots more) here https://mylearn.vmware.com/mgrReg/courses.cfm?ui=www_edu&a=det&id_course=316802

  1. Introduction to vSAN Troubleshooting – [1:27]
  2. vSAN Compatibility: Introduction – [2:51]
  3. vSAN Compatibility: vSAN Hardware & Software Requirements – [2:16]
  4. vSAN Compatibility: vSAN Architectural Best Practices – [7:57]
  5. vSAN Compatibility: Is My SSD Supported in vSAN? – [9:20]
  6. vSAN Compatibility: Is My RAID Controller Supported? – [8:00]
  7. Storage Policies: Introduction – [1:28]
  8. Storage Policies: vSAN Storage Policies In-Depth – [2:23]
  9. Storage Policies: What Are Witnesses? – [3:29]
  10. Storage Policies: Component States – [4:59]
  11. Storage Policies: Policy & Object States – [3:22]
  12. Storage Policies: Component Layout FTT1 SW1 – [3:25]
  13. Storage Policies: Component Layout FTT1 SW2 – [3:52]
  14. Storage Policies: Component Layout FTT1 SW1 VMDK 400 – [3:12]
  15. Storage Policies: FTT2 SW2 VMDK100 – [1:58]
  16. Storage Policies: Summary – [3:31]
  17. Common Issues: The Upgrade Process – [2:15]
  18. Common Issues: Upgrade Best Practices – [7:25]
  19. Common Issues: Inaccessible Objects – [3:25]
  20. Common Issues: Creation, Modification of Disk Groups – [3:43]
  21. Common Issues: Capacity – [1:34]
  22. Common Issues: Summary – [1:39]
  23. vSAN Software Components – [7:31]
  24. vSAN Troubleshooting Tools (Part 1) – [7:46]
  25. vSAN Troubleshooting Tools (Part 2) – [9:28]
  26. Summary – vSAN Troubleshooting – [1:23]

NSX for vSphere Field Advisory – October 2016 Edition

For more information, see the NSX for vSphere 6.2.4 Release Notes on all issues listed below.

There is a security vulnerability issue that was found in OpenSSL that is used in VMware NSX for vSphere 6.2.4. For more information, see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2107.

** Reminder – vShield Endpoint Update **

VMware has announced the End of Availability (EOA) and End of General Support (EOGS) of VMware vCloud Networking and Security 5.5.x. The EOGS date for VMware vCloud Networking and Security 5.5.x is September 19, 2016.  For customers using vCNS Manager specifically to manage vShield Endpoint for agentless anti-virus, Technical Guidance is available until March 31, 2017. For more information, see End of Availability and End of General Support for VMware vCloud Networking and Security 5.5.x (2144733).

Consult the VMware Compatibility Guide for Endpoint partner solution certification status before upgrading. If your preferred solution is not yet certified, please contact that vendor.

Installation and Upgrade Known Issues

Issue 1728633 – Starting in NSX 6.2.3, a third VIB, esx-vdpi, is provided along with the esx-vsip and esx-vxlan NSX VIBs.  A successful installation will include all three VIBs. 

Issue 1730017: Upgrades from 6.2.3 to 6.2.4 do not show a version change for Guest Introspection.

  • As the 6.2.3 Guest Introspection module is the latest version available, the version after a 6.2.4 upgrade remains unchanged. Note that upgrades from earlier NSX releases may show a version change to 6.2.4. This issue does not affect any functionality.

NSX 6.2.4 virtual machines lose network connectivity (2146171)

  • Virtual machines lose network connectivity after vMotion under the following conditions:
    • Distributed Firewall (DFW) is enabled in the environment and;
    • NSX for vSphere setup upgraded from NSX-V 6.1.x release to NSX-V 6.2.3 releases and 6.2.4 release and virtual machines are later migrated between upgraded ESXi hosts.
  • For more information, see KB 2146171 for the workaround.

NSX Manager Known Issues

Fixed issue 1489648: NSX is unavailable from the vSphere Web Client Plug-in after taking a backup of NSX Manager with quiesced snapshot

  • Note following important points about NSX backup and restore:
    • Backup/restore functionality provided by NSX is the only supported way to backup/restore the NSX Manager.
    • Taking a snapshot of the NSX Manager with vSphere is a supported operation. However, VMware does not currently test or support any third party tool that takes snapshot of the NSX Manager.
    • Restoring the NSX Manager from snapshot (taken in any way) is not supported.

See also Issue 1708769 and Increased latency on SVM (Service VM) after snapshot in NSX (2146769). There is no need to snapshot an SVM as it does not need to move or be replicated.

Security Services Known Issues

Issue 1718726: Cannot force-sync Service Composer after a user has manually deleted the Service Composer’s policy section using DFW REST API

  • In a cross-vCenter NSX environment, a user’s attempt to force sync NSX Service Composer configuration will fail if there was only one policy section and that policy section (the Service Composer-managed policy section) was deleted earlier via a REST API call.
  • Workaround: Do not delete the Service Composer-managed policy section via a REST API call. (Note that the UI already prevents deletion of this section).

Issue 1707931: Order of distributed firewall rules changes when service policies defined in Service Composer are present, and a firewall rule is modified or published with a filter applied in the Firewall UI

  • Changing the order, adding or deleting service policies created in Service Composer after one or more publish operations are made from the Networking & Security > Firewall UI will cause the order of firewall rules to change and may result in unintended consequences.

Issue 1717635: Firewall configuration operation fails if more than one cluster is present in environment and changes are done in parallel 

  • In an environment with multiple clusters, if two or more users modify the firewall configuration continuously in a tight loop. (for example, Add/Delete sections or rules), some operations fail.

Issue 1732337/1724222: NSX Manager fails to push firewall rules to ESXi 6.0 P03 host

  • NSX Manager fails to push firewall rules to ESXi 6.0 P03 host, and NSX Edge health check fails as vsfwd connection is closed. This is a known issue affecting VMware NSX for vSphere 6.2.x with ESXi 6.0 P03 (Build 4192238). This issue occurs when /dev/random call is blocked which affects NSX operation on password generation.
  • Workaround: Contact VMware technical support. For more information, see vsfwd connection to the NSX Manager fails (2146873).

Issue 1620460: NSX fails to prevent users from creating rules in Service Composer rules section

  • In the vSphere Web Client, the Networking and Security: Firewall interface fails to prevent users from adding rules to the Service Composer rules section. Users should be permitted to add rules above/below the Service Composer section, but not inside it.
  • Workaround: Do not use the “+” button at the global rule level to add rules to the Service Composer rules section.

Issue 1682552: Threshold events for CPU/Memory/CPS for Distributed Firewall (DFW) are not reported

  • Even when the DFW thresholds for CPU/Memory/CPS are set for reporting, the threshold events are not reported when the thresholds are crossed.
  • Workaround:
    • Log in to each ESXi host and restart the DFW control plane process by running the following command:

/etc/init.d/vShield_Stateful_Firewall restart

  • Verify the status using the following command:

/etc/init.d/vShield_Stateful_Firewall status

  • The result similar to following is displayed:

“vShield-Stateful-Firewall is running”

Note: You should be cautious while performing this operation as this will push all DFW rules to all the filters again. If there are lot of rules, it might take some time to enforce them on all the filters.

Logical Networking Known Issues and NSX Edge Known Issues

Issue 1704540 – High volume of MAC learning table updates with NSX L2 bridge and LACP may lead to out of memory condition

  • When an NSX L2 bridge sees a MAC address on a different uplink, it reports a MAC learning table change to controllers through the netcpa process. Networking environments with LACP will learn the same MAC address on multiple interfaces, resulting in a very high volume of table updates and potentially exhausting the memory needed by the netcpa process to do the reporting.
  • Workaround – Avoid setting a flow-based hashing algorithm on the physical switch when using LACP. Instead, pin MAC addresses to the same uplinks or change the policy to source-MAC.

Issue 1717369 – When configured in HA mode, both active and standby Edge VMs may be deployed on the same host.

  • This issue results from anti-affinity rules not being created and applied on the vSphere hosts automatically during redeploy and upgrade operations.  This issue will not be seen when HA is being enabled on existing Edge.
  • In NSX releases with a fix for this issue, the following is the expected behavior:
    • When vSphere HA is enabled, anti-affinity rules for Edge VMs of an HA pair will be created during redeploy, upgrade.
    • When vSphere HA is disabled, anti-affinity rules for Edge VMs of an HA pair will not be created.

Issue 1716545 – Changing appliance size of Edge does not affect standby Edge’s CPU and Memory reservation

  • Only the first Edge VM created as part of an HA pair is assigned the reservation settings.
  • Workaround: To configure the same CPU/Memory reservation on both Edge VMs:
    1) Use the PUT API https://<NSXManager>/api/4.0/edgePublish/tuningConfiguration to set explicit values for both Edge VMs.
    or
    2) Disable and re-enable Edge HA, which will delete the second Edge VM and redeploy a new one with the default reservations.

Issue 1510724: Default routes do not populate on hosts after creating a new Universal Distributed Logical Router (UDLR)

  • After changing NSX Manager from Standalone to Primary mode for the purpose of configuring Cross-vCenter in NSX for vSphere 6.2.x, you may experience these symptoms:
  • When you create a new UDLR, the default routes are not populated on the host instance.
  • Routes are populated on the UDLR Control VM but not on the host instance.
  • Running the show logical-router host host-ID dlr Edge-ID route command fails to show default routes.
  • Workaround: For information on how to recover from this issue, see Default routes do not populate on the hosts after creating a new UDLR (2145959).

Issue 1733146 – Under certain conditions, creating or modifying LIFs for a Universal DLR fails when no control VM exists

  • This issue is known to manifest under the following conditions:
    1. ECMP with two static default routes.
    2. Static routes with local egress flag.
  • This issue results from a full synchronization being requested instead of a delta update, resulting in the rejection of duplicate entities and a failed operation.
  • See the release notes for a workaround.

NSX Edge Load Balancer accepts only approved ciphers as of 6.2.3. 

  • In earlier releases, customer-defined ciphers are supported for ClientSSL and ServerSSL.
  • NSX 6.2.3 introduced an approved ciphers list:
    • DEFAULT(‘!aNULL:kECDH+AES:ECDH+AES:RSA+AES:@STRENGTH’)
    • ECDHE-RSA-AES128-GCM-SHA256
    • ECDHE-RSA-AES256-GCM-SHA384
    • ECDHE-RSA-AES256-SHA
    • ECDHE-ECDSA-AES256-SHA
    • ECDH-ECDSA-AES256-SHA
    • ECDH-RSA-AES256-SHA
    • AES256-SHA
    • AES128-SHA
    • DES-CBC3-SHA
  • Note the following expected behaviors:
  1. The cipher value will be reset to “DEFAULT” if the cipher is null, empty, or not in approved ciphers suite.
  2. Ciphers included in the approved ciphers suite are passed to the Edge.
  3. When upgrading from a pre-6.2.3 release, a cipher value which is null/empty or not in approved ciphers suite will be reset to “DEFAULT”.

NSX Controller Issues

Data path issues for VNIs with disconnected NSX Controller (2146973)

  • Symptoms – NSX controller shows as disconnected in the vSphere Web Client, leading to data path issues for VNIs handled by the disconnected controller.
  • This issue occurs because IPSec re-keying is disabled in NSX-V 6.1.5, 6.1.6, 6.2, 6,2,1 and 6.2.2 releases to avoid hitting another known IPSec issue.

General Issues

NSX API now returns XML output by default when Accept header is not provided

Beginning in NSX 6.2.3, if the “Accept:” header is not provided in a REST API call, then the default formatting of NSX API return values is XML. Previously the NSX API returned JSON-formatted output by default. To receive JSON-formatted output, the API user must explicitly set “application/json” in the “Accept:” header when calling the function.

** How to track the top field issues **

New KB articles published for week ending 09/10/16

VMware App Volumes
System variable gets cleared in App Volumes on changing user variable (2145985)
Date Published: 9/6/2016
 “Startup Failure” error after upgrading App Volumes to 2.x (2145615)
Date Published: 9/6/2016

VMware Horizon Air Hybrid-Mode
Disabling TPS after Horizon Air Hybrid-Mode Enables the Option (2146823)
Date Published: 9/5/2016

VMware Identity Manager
vIDM upgrade from 2.4 to 2.6 fails with error: fsck failed (2145553)
Date Published: 9/6/2016
unable to login to vIDM with Workspace ONE GUI interface enabled (2145337)
Date Published: 9/6/2016

VMware Mirage
Device Provision – “Only Download Layer” hangs (2145643)
Date Published: 9/6/2016

VMware NSX for vSphere
Increased latency on SVM (Service VM) after snapshot in NSX (2146769)
Date Published: 9/8/2016
Threat protection for virtualized workloads on NSX with Symantec Data Center Security (2146821)
Date Published: 9/8/2016
NSX Connection Method WMI error when editing Security Event Log Server entry (2146832)
Date Published: 9/9/2016
DFW rules changing order when Service Composer-define rules are present (2146471)
Date Published: 9/6/2016

VMware TrustPoint
VMware Trustpoint Security and Imaging Server upgrades  (2146731)
Date Published: 9/9/2016
VMware TrustPoint Imaging Service port requirements (2146537)
Date Published: 9/7/2016

VMware User Environment Manager
Users cannot successfully launch a desktop (2146060)
Date Published: 9/6/2016

VMware vCenter Server
vAPI Endpoint out of memory issue in vsphere 6.x federated vcenter environments results in parts of UI being unresponsive. (2146538)
Date Published: 9/7/2016

VMware vRealize Automation
Alert “The vmdir cert (port 636) of the vRA Identity Appliance is due to expiry” (2146493)
Date Published: 9/7/2016

VMware vRealize Business Enterprise
vRealize Business Enterprise 8.4 is the only version available for download (2146759)
Date Published: 9/9/2016

VMware vRealize Operations Manager
vSphere 6.0 Hardening content is not available after upgrading to vRealize Operations Manager 6.3 (2146835)
Date Published: 9/6/2016

VMware vSphere Data Protection
vSphere Data Protection 6.1.x fails to communicate with vCenter Server 5.5 update 3 (2146825)
Date Published: 9/7/2016
vSphere Data Protection appliance crashes while performing backup (2146829)
Date Published: 9/7/2016

VMware NSX for vSphere 6.2.4 now available

VMware has made NSX for vSphere 6.2.4 available for download. NSX 6.2.4 provides critical bug fixes identified in previous releases, and 6.2.4 delivers a security patch for CVE-2016-2079 which is a critical input validation vulnerability for sites that uses NSX SSL VPN.

  • For customers who use SSL VPN, VMware strongly recommends a review of CVE-2016-2079 and an upgrade to NSX 6.2.4.
  • For customers who have installed NSX 6.2.3 or 6.2.3a, VMware recommends installing NSX 6.2.4 to address critical bug fixes.

Caution: Before upgrading, consult the NSX 6.2.4 Release Notes available from the NSX Documentation Center and Recommended minimum version for NSX for vSphere with GID, ESXi, and vCenter Server (2144295).

Critical Alert on 6.2.3 and 6.2.3a for DLR users: For more information, see “Fixed issue 1703913: NSX DLR HA nodes remain in a split-brain state” in the NSX for vSphere 6.2.4 Release Notes and VMware Knowledge Base article NSX 6.2.3 DLR HA nodes remain in a split brain state (2146506). This issue will occur after approximately 24 days of BFD uptime and will continue to reoccur every 24 days.

Customers who are using 6.2.3 or 6.2.3a are strongly advised to review KB 2146506, review how to prevent or remediate the issue, and plan to upgrade to NSX 6.2.4.

vShield Endpoint Update

VMware has announced the End of Availability (EOA) and End of General Support (EOGS) of VMware vCloud Networking and Security 5.5.x. The EOGS date for VMware vCloud Networking and Security 5.5.x is September 19, 2016.  For customers using vCNS Manager specifically to manage vShield Endpoint for agentless anti-virus, Technical Guidance is available until March 31, 2017. For more information, see End of Availability and End of General Support for VMware vCloud Networking and Security 5.5.x (2144733).

For more information on additional partner solution availability, see Implementation of VMware vShield Endpoint beyond vCloud Networking and Security End of Availability (EOA) (2110078).

Note: Consult the VMware Compatibility Guide for Endpoint partner solution certification status before upgrading.  If your preferred solution is not yet certified, contact that vendor.

How to track the top field issues

NSX for vSphere Field Advisory – July 2016 Edition

This blog has been updated to reflect new information as it was provided. Changes are marked with an *.

VMware NSX for vSphere 6.2.3 Update

  • NSX for vSphere 6.2.3 has an issue that can affect both new NSX customers as well as customers upgrading from previous versions of NSX. The NSX for vSphere 6.2.3 release has been pulled from distribution. The current version available is NSX for vSphere 6.2.2, which is the VMware minimum recommended release.  Refer to KB 2144295. VMware is actively working towards releasing the next version to replace NSX for vSphere 6.2.3 *
  • VMware NSX for vSphere version 6.2.3 delivered a security patch to address a known SSL VPN security vulnerability (CVE-2016-2079) . This issue may allow a remote attacker to gain access to sensitive information. Customers who use SSL VPN are strongly advised to review CVE-2016-2079 and contact VMware support to request immediate assistance. For questions or concerns, contact VMware Support. *
  • The next version of NSX for vSphere contains fixes for bugs that have been found in NSX 6.2.3.
  • Customers who have already upgraded to 6.2.3 are advised to review the following  KB articles:
    • VMware knowledge base article 2146227, VMs using Distributed Firewall (DFW) and Security Groups (SG) may experience connectivity issues. A workaround is available*
    • VMware knowledgebase article 2146293, Virtual machines lose network connectivity in NSX 6.2.x. *
    • VMware Knowledgebase article 2146413, VMs lose network connectivity in NSX with DLR HA. *

Critical Alert for Edge DLR users on NSX 6.2.3 and 6.2.3a *

  • NSX 6.2.3 DLR HA nodes remain in a split brain state (2146506) *
    • A new issue has been identified that can cause both primary and secondary HA nodes into an Active State, causing network disruption.
    • This issue will occur after approximately 24 days of BFD uptime and will continue to reoccur every 24 days.
    • Customers who are using NSX-V 6.2.3 or 6.2.3a are strongly advised to review KB 2146506, review how to prevent or remediate the issue and plan to upgrade to the next version of NSX.

For questions or concerns, contact VMware Support. To contact VMware support, see Filing a Support Request in My VMware (2006985) or How to Submit a Support Request.

Top NSX for vSphere issues for July 2016

NSX for vSphere 6.2.3 other new and changed issues

Notes:

  • vCloud Director 8.0.1 is now interop-tested and supported with NSX 6.2.3.  For more information, see the VMware Interoperability Matrix
  • VMware is working actively with anti-virus solution partners to influence completion of their certification testing efforts with both NSX 6.2.2 and 6.2.3.  For more information, see the VMware Compatibility Guide (VCG)

Other trending issues

Known interoperability issues during upgrade to NSX for vSphere 6.2.3

Note: VMware vSphere 6.0 supports VIB downloads over port 443 (instead of port 80). This port is opened and closed dynamically. The intermediate devices between the ESXi hosts and vCenter Server must allow traffic using this port.

How to track Top Field Issues

Top 20 Horizon View articles for June 2016

Top 20Here is our Top 20 Horizon View articles list for June 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

 

  1. Manually deleting linked clones or stale virtual desktop entries from the View Composer database in VMware View Manager and VMware Horizon View
  2. Removing invalid linked clone entries automatically using the ViewDBChk tool in VMware Horizon View 5.3 and later versions
  3. Poor virtual machine application performance may be caused by processor power management settings
  4. Linked Clone pool creation and recomposition fails with VMware Horizon View 6.1.x and older releases
  5. VMware View ports and network connectivity requirements
  6. Using Microsoft Certreq to generate signed SSL certificates in VMware Horizon View
  7. Forcing replication between ADAM databases
  8. Generating a Horizon View SSL certificate request using the Microsoft Management Console (MMC) Certificates snap-in
  9. Provisioning View desktops fails due to customization timeout errors
  10. Restart order of the View environment to clear ADLDS (ADAM) synchronization in View 4.5, 4.6, 5.0, 5.1, 5.2, 5.3, 6.0, and 6.1
  11. Manually deleting replica virtual machines in VMware Horizon View 5.x
  12. Removing a standard (replica) connection server or a security server from a cluster of connection/security servers
  13. Disabling the HotAdd/HotPlug capability in ESXi 5.x and ESXi/ESX 4.x virtual machines
  14. Dual monitors configured using PCoIP does not span both the monitors for VMware View
  15. Finding and removing unused replica virtual machines in the VMware Horizon View
  16. Connecting to the View ADAM Database
  17. Configuring security protocols on components to connect the View Client with desktops
  18. Troubleshooting USB redirection problems in VMware View Manager
  19. Administration dashboard in VMware Horizon View reports the error: Server’s certificate cannot be checked
  20. Recommended restart cycle of the VMware Horizon View environment