Home > Blogs > Virtualize Business Critical Applications > Monthly Archives: June 2016

Monthly Archives: June 2016

New Updated Oracle Databases on VMware Best Practices Guide

Business Critical Applications (BCA) are at the heart of an organization; their performance, availability and reliability are vital to the success of the business. Significant advances in hardware are far outpacing the performance requirements of even the most intensive business-critical applications, including Oracle Database.

VMware has kept pace with these hardware improvements by engineering significant performance advances in vSphere 6.0. Best Practices are key in ensuring that business SLA’s, uptime, QoS are met with when deploying Oracle on VMware vsphere.

Successful virtualization of any Business Critical Application (BCA) required best practices inculcated in every layer of the stack.

We are pleased to announce the updated version of the “Oracle Databases on VMware Best Practices Guide” which can be found in the below URL. Thanks to everyone who participated in this exercise

In this guide there are also references to other VMware and third-party documents which we encourage the reader to consult for better understanding of the topics discussed.

Click here to download the guide.

RUSH POST: Microsoft Convenience Update, KB4088875 and KB4088878 vNIC Incompatibilities

New Updates and Advisory – March 14th, 2018:

On Tuesday, March 13th, 2018, Microsoft released a number of Security Updates for Windows Operating Systems. Two of these updates are now confirmed to be problematic: when applied to a virtualized Windows Server 2008/R2 and/or Windows 7 instances, these patches replace the existing virtual network card (vNIC) with a new one, hides the pre-existing vNIC and does not persist or transfer the existing IP Address configuration to the new vNIC.

The problematic Updates are KB4088875 and KB4088878

We are updating this post (rather than creating a new one) because the issues are similar and well-known at this time. We expect that Microsoft will release an advisory or updates in due course.

ACTION: If you have been impacted, please note that the following manual fixes have been known to resolve the issue (after the fact):

  • Note the name of the new network adapter
  • Open “Device Manager” -> “Show Hidden Devices” and delete ALL hidden/phantom network adapters from the list (be sure to NOT delete the drivers)
  • Edit the properties of the new NIC and add the applicable IP address configuration. No reboot is required.

The following video has been created to provide a visual cue for this resolution.


Microsoft has has updated the “Known Issues in this Update” section of the applicable KB



VMware has received confirmation that Microsoft has determined that the issue reported in this post is a Windows-specific issue and unrelated to VMware or vSphere. Microsoft is encouraging customers to follow the directions provided inĀ Microsoft KB3125574 for the recommended resolution. All further updates will be provided directly by Microsoft through the referenced KB. This marks the end of further updates to this blog post.


  • Please see Microsoft’s updated guidance and recommended work-around regarding this issue
  • I am removing reference to “VMware VMXNet3” in the title of this post to reflect Microsoft’s latest updates to their KB. Yes, the issue still exists when using VMXNet3 for VMs, but it no longer appears that this issue is specific to “VMXNet3” virtual network adapters.
  • We are still working with Microsoft to conduct a comprehensive Root-Cause Analysis, and we will provide further updates as new information (or a resolution) becomes available.

Continue reading