Home > Blogs > Support Insider > Tag Archives: KB

Tag Archives: KB

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:

Important KB updates for current NSX for vSphere users -May 2016 Edition

NSXOur NSX support team would like all of our customers to know about important KB updates for current NSX for vSphere issues. Here’s what’s new and trending-

Please take note of key updates to the following important End of General Support and End of Availability events:

New and important issues:

NSX for Multi-Hypervisor:

New master playbook KBs:

How to track the top field issues:

 

Important NSX for vSphere KB Updates – March 2016

vCloud Networking and Security will reach end of availability and end of support on September 19, 2016.

  • KB 2144733 – End of Availability and End of Support Life for VMware vCloud Networking and Security 5.5.x
  • See the fully updated vCNS to NSX Upgrade Guide
  • See also KB 2144620 – VMware vCloud Networking and Security 5.5.x upgrade to NSX for vSphere 6.2.x Best Practices
  • ​Upgrade path from vCNS 5.x: Using the NSX upgrade bundle posted on or after 31 March, 2016, you may upgrade directly from vCNS 5.1.x or vCNS 5.5.x to NSX 6.2.2 Please see the NSX 6.2.2 release notes
  • Upgrades from NSX 6.1.5 to NSX 6.2.0 are not supported. Instead, you must upgrade from NSX 6.1.5 to NSX 6.2.1 or later to avoid a regression in functionality. Refer to KB 2129200

NSX for vSphere 6.1.x will reach end of availability and end of support on October 15, 2016

  • KB 2144769End of Availability and End of Support Life for VMware NSX for vSphere 6.1.x
  • The recommended release for NSX-V is 6.2.2. Refer to KB 2144295Recommended minimum version for VMware NSX for vSphere with Guest Introspection Driver, ESXi and vCenter server.

New issues:

  • KB 2144726Service Composer fails to translate virtual machines into security-groups in VMware NSX for vSphere 6.x
  • KB 2140891Storage vMotion of Edge appliance disrupts VIX communication in VMware vCloud Networking and Security 5.5.x and NSX for vSphere 6.x
  • KB 2144476After reinstalling vCenter Server 6.0 EAM fails to push VIB’s to ESXi host with the error: Host not covered by scope anymore
  • KB 2144456Importing draft firewall rules fails after existing firewall configuration is removed by a REST API request
  • KB 2144387After upgrading to VMware NSX for vSphere 6.2.2 there is no upgrade option available for NSX Guest Introspection and NSX Data Security and the services remain at version 6.2.1
  • KB 2144420Any changes to the Primary UDLR result in the vNic_0 being shutdown on the Seconday UDLR in VMware Cross-vCenter NSX for vSphere 6.2.x
  • KB 2144236VMtools issue – Virtual machine performance issues after upgrading VMware tools version to 10.0.x in NSX/ VMware vCloud Networking and Security 5.5.x
  • KB 2144649 – IPv4 IP address do not get auto approved when SpoofGuard policy is set to Trust On First Use (TOFU) in VMware NSX for vSphere 6.2.x
  • KB 2144732 – In VMware NSX for vSphere 6.x, unpreparing Stateless ESXi host fails with the error: Agent VIB module is not installed. Cause : 15 The installation transaction failed. The transaction is not supported
  • KB 2135956 – VMware ESXi 6.0 Update 1 host fails with a purple diagnostic screen and reports the error: PANIC bora/vmkernel/main/dlmalloc.c:4923 – Usage error in dlmallocnow resolved in vSphere 6.0U2. See also the vSphere 6.0U2 Release Notes
  • KB 2126275Publishing Distributed Firewall (DFW) rules fails after referenced object is deleted in VMware NSX for vSphere 6.1.x and 6.2.x

Tracking the top issues:

The VMware Knowledge Base

In VMware documentation, we show you how a product works, and how you can use the product to accomplish your tasks. But what about when the product isn’t working for you—when it doesn’t behave as described in the manual, or when the manual doesn’t cover a problem you encounter, or a special task you want to perform? In our procedures we try to anticipate every use case, and in our troubleshooting sections we try to foresee everything that might go wrong, but with the large and growing base of VMware users, it’s impossible to cover every situation that might occur. Every user is unique, and the number of variations—in combinations of hardware, operating systems, and use cases—is practically limitless.

One of the best resources for troubleshooting problems is the VMware Knowledge Base. Maintained by VMware Global Support Services team, the Knowledge Base (KB) contains thousands of articles authored by GSS support techs, product development and QA engineers, and Technical Communications writers. KB articles specialize in corner cases, troubleshooting, workarounds, and more. Thorny, corner-case problems are usually solved only through considerable effort, collaboration, and head pounding by some very smart and knowledgeable people. KB articles document those solutions, so no one should have to struggle with solving the same problems again.

And note: when you search the Knowledge Base, you’re searching not only KB articles, but also the library of product documentation and discussion threads in VMware Communities. This makes the Knowledge Base a great place to begin looking for answers.

So how do you use the Knowledge Base? Just go to http://kb.vmware.com/ and you’ll find that it’s pretty self-explanatory. You can browse or search by keyword, and you can filter the search by product. And if you need more detailed instructions or help, the Knowledge Base itself is well documented (just as you would expect) in a KB article—just click the Knowledge Base Help button in the upper right of the KB home window.

I will add one tip for searching: when I enter search terms, I start by trying to identify as uniquely as I can the symptoms and setup of the problem I’ve encountered—I might include the essential words of an error message, the operating system version of the VM, what seemed to trigger the problem—whatever might help filter the search to the results most likely to match my problem exactly. I err on the side of inclusiveness, using as many relevant keywords as I can. Sometimes, I get lucky and find my problem on the first try. More likely, I get no results, or just a few. So I start deleting terms, one by one, from the search. With every deletion, the search broadens, and I get more results to scan through.

One more note: be sure to take a look at the navigation bar on the right-hand side of the KB home page, where there are links to some other really great tools and services provided by the KB team, including:

  • KBTV, an ongoing series of how-to videos
  • the Weekly KB Digest, where you can check for the newest additions to the Knowledge Base

You can subscribe to KBTV, the Weekly Digest and the KB Blog via RSS, and you can follow us on Twitter at: @VMwarecares.

In short, whenever you need answers, try the Knowledge Base. It’s a terrific resource.

How to setup mirrored folders between your Mac and Fusion VM

Did you know that you can setup mirrored folders for your Mac and Fusion virtual machine?

Mirrored folders allow the Mac and the virtual machine to see the same content in certain personal data folders. For example, any content put on the Mac’s desktop also appears on the Windows desktop. Similarly any content put in the My Documents folder in Windows also appears in the Mac user’s Documents folder.

The mirrored content resides on the Mac so that it is accessible even when the virtual machine is off. Mirrored folders work by redirecting where Windows looks for certain user folders (Desktop, Documents, Music, Pictures, Movies, and Downloads) from their default Windows locations to the corresponding locations on the Mac. It does this by means of registry redirects (much like Group Policy can redirect user folders to a network location). Mirrored folders allows your Windows virtual machine to treat the Mac’s Desktop, Documents, Music, Pictures, Movies, and Downloads folders as its own; it does not, however, let your Mac see the Windows default Desktop, My Documents, My Music, My Pictures, My Movies, or Downloads folders, and your Mac never has access to data saved on the Windows computer.

This video discusses and demonstrates how to setup mirrored folders for your Mac and Fusion virtual machine. For additional information, see VMware Knowledge Base article Setting up mirrored folders for your Mac and virtual machine (1014127).

Refresh: Top 20 Horizon with View KB articles

announcementToday we have refreshed our top 20 list of VMware View specific KBs. Some have dropped off the list while others are now trending upward.  Have a look and see if you are encountering any of these issues in View.

 

  1. Manually deleting linked clones or stale virtual desktop entries from the View Composer database in VMware View Manager and Horizon View (2015112)
  2. Pool settings are not saved, new pools cannot be created, and vCenter Server tasks are not processed in a Horizon View environment (2082413)
  3. Generating and importing a signed SSL certificate into VMware Horizon View 5.1/5.2/5.3/6.0 using Microsoft Certreq (2032400)
  4. The time stamp on a snapshot image does not update automatically in VMware Horizon View (2074301)
  5. Network connectivity requirements for VMware View Manager 4.5 and later (1027217)
  6. Manually deleting replica virtual machines in VMware Horizon View 5.x (1008704)
  7. Connecting to the View ADAM Database (2012377)
  8. VMware Horizon View Best Practices (1020305)
  9. Forcing replication between ADAM databases (1021805)
  10. Restart order of the View environment to clear ADLDS (ADAM) synchronization in View 4.5, 4.6, 5.0, and 5.1 (2068381)
  11. Provisioning View desktops fails due to customization timeout errors (2007319)
  12. Generating a Horizon View SSL certificate request using the Microsoft Management Console (MMC) Certificates snap-in (2068666)
  13. Legacy applications fail to start with the VMware View 6.0.x agent installed (2091845)
  14. Troubleshooting a black screen when logging into a Horizon View virtual desktop using PCoIP (1028332)
  15. Resolving licensing errors when deploying virtual Office to a system with Office installed natively (2107369)
  16. Troubleshooting SSL certificate issues in VMware Horizon View 5.1 and later (2082408)
  17. The Event database performance in VMware View 6.0.x is extremely slow (2094580)
  18. Configuring USB device filters and redirecting Human Interface Devices (HIDs) in View Client (1011600)
  19. Finding and removing unused replica virtual machines in the VMware Horizon View (2009844)
  20. PCoIP Disconnection Codes (2012101)

Access Denied – You don’t have permission to access …

We’ve noticed a number of you who are encountering an error when attempting to access the VMware Knowledgebase, whether it be the main landing page, or a specific article in the KB. You see something like:

Access Denied – You don’t have permission to access “http://kb.vmware.com/” on this server.

We are aware of the problem and are investigating the issue on our servers, but in the meantime we want everyone to know the work-around. Go into the menu of the browser you are using and clear both the cookies and the cache.  Then reload the KB URL – it should then work.

We apologize for this inconvenience.

vSphere 6.0 is here! – KBs you need to know about

vSphere 6.0 has been released for all to download. We’re sure 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. You’ll notice lots of how-to KBs here.

ESXi\Hypervisor

Devices deprecated and unsupported in ESXi 6.0 (2087970)

Update sequence for vSphere 6.0 and its compatible VMware products (2109760)

ESXi/ESX hosts and compatible virtual machine hardware versions list (2007240)

Troubleshooting native drivers in ESXi 5.5 or later (2044993)

Methods for upgrading to ESXi 6.0 (2109711)

Methods of installing ESXi 6.0 (2109708)

Installing or upgrading to ESXi 6.0 best practices (2109712)

Installing async drivers on VMware ESXi 5.x and ESXi 6.0.x (2005205)

vSphere\vCenter Server

Important Information before upgrading to vSphere 6.0 (2110293)

List of recommended topologies for vSphere 6.0.x (2108548)

Methods for upgrading to ESXi 6.0 (2109711)

Methods of installing ESXi 6.0 (2109708)

Installing or upgrading to ESXi 6.0 best practices (2109712)

Installing async drivers on VMware ESXi 5.x and ESXi 6.0.x (2005205)

Devices deprecated and unsupported in ESXi 6.0 (2087970)

Minimum requirements for the VMware vCenter Server 6.x Appliance (2106572)

Stopping, starting, or restarting VMware vCenter Server 6.0 services (2109881)

vCenter Server

Upgrading to vCenter Server 5.5 best practices (2109772)

Installing vCenter Server 6.0 Best Practices (2107948)

Methods for installing vCenter Server 5.5 (2053142)

Upgrading to vCenter Server 6.0 without migrating SQL database to vPostgres (2109321)

Upgrading to VMware vCenter Server 6.0 with an embedded Platform Services Controller from vCenter Server 5.5 installed using the simple install method (2109559)

Upgrading VMware vCenter Single Sign-on 5.5 to a VMware vCenter Server 6.0 Platform Services Controller 6.0 (2109560)

Upgrading VMware vCenter Server 5.5 to vCenter Server 6.0 with an external Platform Services Controller (2109562)

vSphere with Operations Management Support Center

VMware vSphere and vSphere with Operations Management 6.x Licensing and Compatibility FAQ (2107528)

End of Availability and End of Support Life for VMware vCloud Director 5.1 Standalone (2057589)

Unable to connect to vRealize Operations appliance (2000208)

Active Directory account locks out due to repeated failed login attempts from vCenter Server (2001703)

Collecting diagnostic information for VMware vRealize Operations Enterprise 1.0 and VMware vRealize Operations Standalone 5.x (2006599)

VSAN

Collecting diagnostic information for VMware products (1008524)

Configuring Virtual SAN VMkernel networking (2058368)

Enabling or disabling a Virtual SAN cluster (2058322)

vSphere 6. Virtual SAN requirements (2106708)

Adding a host back to a Virtual SAN cluster after an ESXi host rebuild (2059091)

Requirements and considerations for the deployment of VMware Virtual SAN (VSAN) (2068911)

Migration from vSphere Storage Appliance (VSA) to VMware Virtual SAN (VSAN) (2068923)

SRM

Collecting diagnostic information for Site Recovery Manager (1009253)

Requirements when using trusted certificates with VMware Site Recovery Manager 1.0.x/4.0.x/4.1.x/5.x (1008426)

Operational Limits for Site Recovery Manager 6.0 (2105500)

How Site Recovery Manager Handles Storage DRS Tagging (2108196)

Setting up VMware vCenter Site Recovery Manager with Partner Storage Arrays (1014610)

Network Ports for Site Recovery Manager 6.0 (2103394)

VMware vRealize

Uninstalling a plug-in from VMware vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) (2064575)

Working with vRealize Orchestrator over SSL connection (2007032)

Deploying and using the SSL Certificate Automation Tool 5.5 (2057340)

VMware vRealize Orchestrator times out with the error: Timeout, unable to get property name’ (2007423)

VMware vRealize Orchestrator 5.1 login to vCenter Server fails with the error: Unexpected status code: 400 (2042461)

VMware Virtual Appliances and customizations to operating system and included packages (2090839)

Top 20 Articles for March 2014

Here is our Top 20 KB list for March 2014. 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. VMware ESXi 5.x host experiences a purple diagnostic screen mentioning E1000PollRxRing and E1000DevRx
  2. Downloading and Installing VMware Fusion
  3. Installing async drivers on VMware ESXi 5.0, 5.1, and 5.5
  4. Determining Network/Storage firmware and driver version in ESXi/ESX 4.x and ESXi 5.x
  5. Installing Windows in a virtual machine using VMware Fusion Easy Install
  6. Troubleshooting Fusion virtual machine performance issues
  7. Upgrading to vCenter Server 5.5 best practices
  8. Investigating virtual machine file locks on ESXi/ESX
  9. Re-pointing and re-registering VMware vCenter Server 5.1 / 5.5 and components
  10. Uninstalling and manually installing VMware Tools in VMware Fusion
  11. Installing vCenter Server 5.5 best practices
  12. Purging old data from the database used by VMware vCenter Server 4.x and 5.x
  13. Troubleshooting Fusion virtual machine startup issues
  14. Installing or upgrading to ESXi 5.5 best practices
  15. Creating a persistent scratch location for ESXi 4.x and 5.x
  16. Unmounting a LUN or detaching a datastore/storage device from multiple VMware ESXi 5.x hosts
  17. Broadcom 5719/5720 NICs using tg3 driver become unresponsive and stop traffic in vSphere
  18. Update sequence for vSphere 5.5 and its compatible VMware products
  19. Installing VMware Tools in a Fusion virtual machine running Windows
  20. Methods of upgrading to vCenter Server 5.5

Take note of those KB articles we present

When filing a Support Request in the My VMware Support Portal, you may notice there is a selection of five KB articles presented underneath the form after you tell us a few things about your issue. These articles are put there to help you resolve your issue before you have even spoken to someone, but did you know there is some intelligence behind what we show you? Today we will explore how we pick these KB articles. It is a rather involved and complicated process, but read on to discover how it’s done.

When you file a Support Request with VMware, everything related to what is done to resolve your issue, is kept as a record. This helps us spot trends, and keep track of issues that may occur frequently. After a certain amount of time, we gather reports to see what common KB articles are used to resolve an issue by the support engineers. The engineers document which KB articles they used in each and every support request they resolve. We then look at the ratings of the article, and how many times it has been linked to. If the KB article maintains a rating above three stars and is linked-to quite frequently, we know that KB article is particularly useful in helping people to resolve that issue. That’s not the only thing we do. We also comb through the case notes of Support Requests to pick up out trends, such as did a virtual machine lock up, did your ESXi host crash, did vCenter Server stop responding, etc.

This is all categorized by different selections our Technical Support Engineers make as they work your support request. We call these vCats which is the problem category, for example Host/Installation, and then a subcategory to describe the issue, a vSubCat, such as a Storage Failure. All this information is trended and tracked. We analyze the data with utilities that can spot these trends automatically although there is a manual component to it. Combing through this data can be a time consuming task. We have ways to automate our reports, but much of the qualitative aspect of analyzing this data is done by perusing spreadsheets, reading comments from the Technical Support Engineers, and the feedback we receive from customers.

Finally, when choosing the KB articles for the My VMware Support Portal we tend to target KB articles that utilize multiple steps and checks to troubleshoot the issue. We call these types of articles Resolution Paths. These step through specific issues step by step, and provide you a process for which to resolve your issue, such as an issue of virtual machine not being able to start up. In this way, it is also revealed how a Technical Support Engineer may troubleshoot the issue.

All in all, the idea is that these KB articles will help you save some time. Hopefully, you find these useful, and think about taking a gander at these KB articles next time an issue arises.