Enable SSH Access to VMware vSphere ESX
Mar22

Enable SSH Access to VMware vSphere ESX

  KB ID 0000299 Dtd 22/03/17 Problem Should you wish to get SSH (remote secure console) access to your ESX  hosts, you need to do the following; ESX Version 6.5 and Newer ESX version 5 and Newer ESX version 4.1.0 ESX version 4.0.0 and earlier ESX version 4.0.0 and earlier Solution Grant SSH Access to ESX 6.5 If you have a stand-alone ESX Server running version 6.5, it's a lot easier to to enable ESX access. Select 'Host' > Actions...

Read More
Cisco VPN Client Connects but no traffic will Pass
Sep08

Cisco VPN Client Connects but no traffic will Pass

Note: May also be asked as, Client VPN connects but cannot ping anything behind the Firewall.KB ID 0000199 Dtd 08/09/16ProblemIf I had a pound for every time I've seen this either in the wild, or asked in a forum, I would be minted! In nearly every case the problem is NAT related.In most cases, If the person launching the VPN client is behind a device that is performing NAT, (Home Router, Access Point, Firewall, etc) then the device...

Read More
AnyConnect –  ‘VPN establishment capability from a remote desktop is disabled. A VPN connection will not be established’
Aug23

AnyConnect – ‘VPN establishment capability from a remote desktop is disabled. A VPN connection will not be established’

KB ID 0000546 Dtd 23/08/16 Problem If you connect to to a client via RDP then try and run the AnyConnect client you will see this error. This, behaviour is default, and despite me trawling the internet to find a solution (most posts quote changing the local AnyConnectProfile.tmpl  file, this file does not exist using Version 3 (I was using v 3.0.4235). Update: Now with version 4 it does not tell you what’s wrong, the VPN appears...

Read More
Outlook Error  “The name of the security certificate is invalid or does not match the name of the site.”
Aug02

Outlook Error “The name of the security certificate is invalid or does not match the name of the site.”

KB ID 0000036 Dtd 02/08/16ProblemSeen in Outlook when connecting to a mailbox on an Exchange Server, its caused by using a self signed certificate OR a purchased certificate, where the internal and external names are different.SolutionBefore proceeding if you have an A or CNAME record in your DNS for autodiscover  then DELETE it and setup an SRV record!Exchange AutoDiscover Errors – Creating an AutoDiscover SRV Record1. On the...

Read More
Migration From Exchange 2010 to Exchange 2016 or 2013
Apr03

Migration From Exchange 2010 to Exchange 2016 or 2013

Part 2 Migrating Public Folders from Exchange 2010 to Exchange 2013 / 2016 KB ID 0000789 Dtd 03/04/16 Problem Continued from Migration From Exchange 2010 to Exchange 2016 / 2013 Part 1 Solution Exchange 2016 / 2013 Migration Step 7 "Migrate Public Folders" Note: This article uses the newer 'Batch Migration' method. Make sure your exchange server is patched and up to date or the process will not work. Minimum Patch Levels Source:...

Read More