Symptoms

When configuring the VMware High Availability (HA) in vCenter Server, you see the message:

Host <xxx> currently has no management network redundancy
 Purpose
To prevent the Host <xxx> currently has no management network redundancy message when configuring the VMware High Availability (HA) in vCenter Server, VMware recommends to add a second vmnic to the service console or management network vSwitch configured with NIC teaming, and that you keep both as active adapters, or place one in standby.
 Cause
This message is displayed if the network redundancy configuration within theService Console/VMkernel Port Management Network is incorrect. This message can be safely ignored.

 Resolution
To prevent this message from appearing, and to comply with proper network redundancy, VMware recommends to add a second vmnic to the service console or management network vSwitch configured with NIC teaming, and that you keep both as active adapters, or place one in standby. For more information, see NIC teaming in ESXi and ESX (1004088).

Alternatively, you can add a second service console on a different vSwitch and subnet.<o></o> To suppress this message on ESXi and ESX hosts in the VMware High Availability (HA) cluster, or if the warning appears for a host already configured in a cluster, set the VMware HA advanced option das.ignoreRedundantNetWarning to true and reconfigure VMware HA on that host. This advanced option is available in VMware Virtual Center 2.5 Update 3 and later.

If the warning appears even when there are two available uplinks for the vSwitch hosting the Service Console/VMkernel Port Management Network, providing a redundancy, see ESX/ESXi host displays warning message when test condition is false (2008602).
 
Note: If the warning continues to appear, disable and re-enable VMware High Availability in the cluster.

To set das.ignoreRedundantNetWarning to true:

From the VMware Infrastructure Client, right-click on the cluster and click Edit Settings.
Select vSphere HA and click Advanced Options.
In the Options column, enter das.ignoreRedundantNetWarning
In the Value column, type true.

Note: Steps 3 and 4 create a new option.
 
Click OK.
Right-click the host and click Reconfigure for vSphere HA. This reconfigures HA.
To set das.ignoreRedundantNetWarning to true in the vSphere 5.1 Web Client:

From the vSphere Web Client, right-click the cluster.
Click the Manage tab for the cluster, then under Settings click vSphere HA.
Click Edit in the top right corner.
Expand the Advanced Options section, and click Add.
In the Options column, type das.ignoreRedundantNetWarning.
In the Value column, type true.
Click OK.
Right-click the host and click Reconfigure for vSphere HA.

What version of SQL Server do I have?

This unofficial build chart lists all of the known Service Packs (SP), Cumulative Updates (CU), patches, hotfixes and other builds of MS SQL Server 2017, 2016, 2014, 2012, 2008 R2, 2008, 2005, 2000, 7.0, 6.5 and 6.0 that have been released.

Useful articles:

• How to identify your SQL Server version and edition
• SQL Server Internal Database Versions
• SQL Server Management Studio (SSMS) Versions
• Microsoft SQL Server Support Lifecycle
• Microsoft SQL Server Home
• Microsoft SQL Server Developer Center
• Microsoft TechNet: Microsoft SQL Server
• Microsoft Knowledge Base
• Sqlservr.exe versions

Quick summary :

	RTM (no SP)	SP1	SP2	SP3	SP4
SQL Server 2019      codename Aris	Not yet released
SQL Server 2017      codename vNext	14.0.1000.169
SQL Server 2016	13.0.1601.5	13.0.4001.0 or 13.1.4001.0	13.0.5026.0 or 13.2.5026.0
SQL Server 2014	12.0.2000.8	12.0.4100.1 or 12.1.4100.1	12.0.5000.0 or 12.2.5000.0
SQL Server 2012      codename Denali	11.0.2100.60	11.0.3000.0 or 11.1.3000.0	11.0.5058.0 or 11.2.5058.0	11.0.6020.0 or 11.3.6020.0	11.0.7001.0 or 11.4.7001.0
SQL Server 2008 R2      codename Kilimanjaro	10.50.1600.1	10.50.2500.0 or 10.51.2500.0	10.50.4000.0 or 10.52.4000.0	10.50.6000.34 or 10.53.6000.34
SQL Server 2008      codename Katmai	10.0.1600.22	10.0.2531.0 or 10.1.2531.0	10.0.4000.0 or 10.2.4000.0	10.0.5500.0 or 10.3.5500.0	10.0.6000.29 or 10.4.6000.29
SQL Server 2005      codename Yukon	9.0.1399.06	9.0.2047	9.0.3042	9.0.4035	9.0.5000
SQL Server 2000      codename Shiloh	8.0.194	8.0.384	8.0.532	8.0.760	8.0.2039
SQL Server 7.0      codename Sphinx	7.0.623	7.0.699	7.0.842	7.0.961	7.0.1063

All SQLServer service packs are cumulative, meaning that each new service pack contains all the fixes that are included with previous service packs and any new fixes.

You can comment here. If you know of a hotfix build or KB that we don't have listed here, please use the comments.

Legend:

Microsoft SQL Server 2019 Builds

Microsoft SQL Server 2017 Builds

Microsoft SQL Server 2016 Builds

Microsoft SQL Server 2014 Builds

Microsoft SQL Server 2012 Builds

Microsoft SQL Server 2008 R2 Builds

Microsoft SQL Server 2008 Builds

Microsoft SQL Server 2005 Builds

Microsoft SQL Server 2000 Builds

Microsoft SQL Server 7.0 Builds

1) If RRAS based VPN server is behind a firewall (i.e. a firewall is placed between Internet and RRAS server), then following ports need to be opened (bidirectional) on this firewall to allow VPN traffic to pass through: -
•For PPTP:  ◦IP Protocol=TCP, TCP Port number=1723   <- Used by PPTP control path
◦IP Protocol=GRE (value 47)   <- Used by PPTP data path

•For L2TP: ◦IP Protocol Type=UDP, UDP Port Number=500    <- Used by IKEv1 (IPSec control path)
◦IP Protocol Type=UDP, UDP Port Number=4500   <- Used by IKEv1 (IPSec control path)
◦IP Protocol Type=ESP (value 50)   <- Used by IPSec data path

•For SSTP:
◦IP Protocol=TCP, TCP Port number=443   <- Used by SSTP control and data path
•For IKEv2: ◦IP Protocol Type=UDP, UDP Port Number=500    <- Used by IKEv2 (IPSec control path)
◦IP Protocol Type=UDP, UDP Port Number=4500   <- Used by IKEv2 (IPSec control path)
◦IP Protocol Type=ESP (value 50)   <- Used by IPSec data path

2) If RRAS server is directly connected to Internet, then you need to protect RRAS server from the Internet side (i.e. only allow access to the services on the public interface that isaccessible from the Internet side). This can be done using RRAS static filters or running Windows Firewall on the public interface (or the interface towards the Internet side). In this scenario following ports need to be opened (bidirectional) on RRAS box to allow VPN traffic to pass through
•For PPTP:  ◦IP Protocol=TCP, TCP Port number=1723  <- Used by PPTP control path
◦IP Protocol=GRE (value 47)  <- Used by PPTP data path

•For L2TP:
◦IP Protocol Type=UDP, UDP Port Number=500   <- Used by IKEv1 (IPSec control path)
◦IP Protocol Type=UDP, UDP Port Number=4500 <- Used by IKEv1 (IPSec control path)
◦IP Protocol Type=UDP, UDP Port Number=1701  <- Used by L2TP control/data path
◦IP Protocol Type=50  <- Used by data path (ESP)

•For SSTP:
◦IP Protocol=TCP, TCP Port number=443   <- Used by SSTP control and data path
•For IKEv2:
◦IP Protocol Type=UDP, UDP Port Number=500   <- Used by IKEv2 (IPSec control path)
◦IP Protocol Type=UDP, UDP Port Number=4500 <- Used by IKEv2 (IPSec control path)
◦IP Protocol Type=UDP, UDP Port Number=1701  <- Used by L2TP control/data path
◦IP Protocol Type=50 <- Used by data path (ESP)

방화벽 뒷단에 VPN서버를 배치하는것과 다이렉트로 DMZ 영역에 VPN서버를 배치하여 포트를 개방하는 방법입니다. 앞서 1탄에 설명을 했지만 SSTP와 IKEv2를 제외하고는 중국에서는 전부 블랙당하고 OPENVPN도 SSL을 사용한다고 해도 감지하여 블랙당하는걸 직접 테스트 하였습니다.
아이폰은 현재로서는 유일하게 IKEv2 방식을 사용할수밖에 없고 나머지 플랫폼은 전부 SSTP 클라이언트로 접속하여 VPN을 사용할수가 있습니다.
SSTP 클라이언트가 내장된 라우터 및 공유기가 현존하는 제품중 미크로틱 제품이 유일하다라고 국내에서는 트루네트워크가 총판을 담당하고 있습니다.
미크로틱 라우터도 SSTP 서버를 지원하지만 중국에서는 이마져도 감지가 되어 차단된다는걸 명심해야됩니다.
중국에서 VPN 을 차단되지 않고 원활하게 사용할수 있는 VPN을 아직까지 서비스 하지 못하여 IP만 맨날 바꾸는 업체들이 여기저기 보이고 있는게 아쉬울뿐입니다.
Windows Server의 VPN을 비웃기라도 한듯 리눅스및 어플라이언스에 의존한 결과가 아닌가 싶습니다.