Update: 01/18/2016
An app, SpotBright, in Windows Store makes even easier to download these images.
Here is the screenshot of the services that can be enabled on an ESXi v.6 VMkernel NIC port.
All these services look very self-explanatory, until I am doing some research on the ESXi management redudancy and discovering this post.
Here is the quick summary of the post, plus others I learned about the VMkernel port.
If you are running ESXi 5.5 with VSAN, DO NOT upgrade the ESXi host from 5.5 to 6.0. When mixing ESXi 5.5 and 6.0 in the VSAN cluster during the host upgrade, it can cause permanent data loss. See this VMware KB2139969 for more information. As December 25, 2015, no fix is available yet.
If you have to upgrade to ESXi 6.0 now, the safe approach is to migrate the VMs on the VSAN to other non-VSAN storage prior to the upgrade.
Versions
There are several different versions of SMB used by Windows operating systems:
| SMB Version | Operating System | Note |
| CIFS | Windows NT | superseded by SMB1 |
| SMB 1.0 (or SMB1) | Windows 2000, XP, Server 2003, Server 2003 R2 | |
| SMB 2.0 (or SMB2) | Windows Vista (SP1 or later), Server 2008 | |
| SMB 2.1 (or SMB2.1) | Windows 7, Server 2008 R2 | |
| SMB 3.0 (or SMB3) | Windows 8, Server 2012 | |
| SMB 3.02 (or SMB3) | Windows 8.1, Server 2012 R2 | In Windows 8.1 and Server 2012 R2, the option to completely disable CIFS/SMB1 support is introduced. It is not the default configuration. |
| SMB 3.1.1 | Widnows 10, Server 2016 |
Negotiated Versions
Here’s a table to help you understand what version you will end up using, depending on what Windows version is running as the SMB client and what version of Windows is running as the SMB server:
| OS | Windows 8.1 WS 2012 R2 | Windows 8 WS 2012 | Windows 7 WS 2008 R2 | Windows Vista WS 2008 | Previous Version |
| Windows 8.1 WS 2012 R2 | SMB 3.02 | SMB 3.0 | SMB 2.1 | SMB 2.0 | SMB 1.0 |
| Windows 8 WS 2012 | SMB 3.0 | SMB 3.0 | SMB 2.1 | SMB 2.0 | SMB 1.0 |
| Windows 7 WS 2008 R2 | SMB 2.1 | SMB 2.1 | SMB 2.1 | SMB 2.0 | SMB 1.0 |
| Windows Vista WS 2008 | SMB 2.0 | SMB 2.0 | SMB 2.0 | SMB 2.0 | SMB 1.0 |
| Previous Version | SMB 1.0 | SMB 1.0 | SMB 1.0 | SMB 1.0 | SMB 1.0 |
* WS = Windows Server
Check SMB Version
In Windows 8 or Windows Server 2012 or later, a new PowerShell cmdlet can easily tell what version of SMB the client has negotiated with the File Server. For Windows version prior to Windows 8, there is not an easy way – need to use Network Monitor, Message Analyzer (recommended) or Wireshark to capture and look into the packets.
To check the negotiated SMB version between the client and file server
To check the SMB version on the local computer
Recommendation
Microsoft strongly encourage to update to the latest of SMB. However, be aware of compatibility with the older Windows operating systems and third-party application implementation.
Source
Microsoft Jose Barroeto’s Blog
Today, my Open Live Writer is updated to build 0.5.1.4. The feature I wanted in my Update 1 post is here – support Blogger label.
The label can be entered in the new box under the tool bar; multiple labels can be separated by comma. Even the “Refresh List” feature (the two arrows on the right of label box) does not work, I am very thankful for the development team continuing to add new features in a short time.
The eDellRoot certificate was a hot topic back in November 2015. This post just summarizes the tools to use check this and other rogue certificate on your computer.
Detection
Steps to check if your computer (mainly the Dell laptop) is vulnerable by the eDellRoot certificate
Removal
If the bad eDellRoot certificate is found on your computer, use the Dell’s official remover to remove it.
Audit the root CA stores
Furthermore, you can scan and audit the trusted root CA stores – both Microsoft (using by IE and Chrome) and Mozillla (using by Firefox), with the following tools:
VMware has a KB (KB2108548) that summarizes the recommended topologies for vSphere 6.0.x deployment on the Platform Services Controller (PSC) and vCenter Server. I’s a good read.
My pick will be one of the following topologies in most of the deployment – simple configuration with sufficient redudance.
