Hyper-V 2016 – Missing VM Hardware Versions?
KB ID 0001382 Problem I was helping a colleague with a Hyper-V upgrade this week, he asked if I would upgrade the hardware versions on the guest VM’s Get-VMHostSupportedVersionl However I could not get the cluster to accept a hardware version above version 5 (Server 2012 R2) Solution As it turns out the cluster had had all its nodes upgraded to 2016, but the cluster functional level was still at version 8 (Server 2012)...
Cisco ASA: Updating and Copying files from USB
KB ID 0001377 Problem Cisco ASA firewalls have had USB sockets on them for a while, but a dig into the documentation only yielded, ‘for use in future releases’. Well they are working now! Note: Firewall shown is a 5516-X (running version 9.8(1)) Solution Your drive needs to be formatted as FAT (not NTFS), I’m going to update/install some AnyConnect client software, but there’s nothing to stop you uploading a...
Updating FirePOWER Module (From ASDM)
KB ID 0001348 Problem Normally I don’t like upgrading the SFR this way. But then I tend to install new firewalls set them up and walk away, so its easier (and a LOT quicker) to simply image the module to the latest version and then set it up. Like So; Re-Image and Update the Cisco FirePOWER Services Module This week I had an existing customer, who has an ASA5508-X but wasn’t using his FirePOWER, I’d installed the...
Updating the AnyConnect client for Deployment from the Cisco ASA 5500
KB ID 0000704 Problem Your ASA will (by default) update your AnyConnect clients to the latest client software when they connect. However you need to supply the ASA with the updated packages first. Solution 1. Download the latest AnyConnect client package, from Cisco. The one you want will have a file extension of .pkg AnyConnect 4 AnyConnect 3 2. Connect to the ASDM > Configuration > Remote Access VPN > Network (Client)...
Upgrade vSphere vCenter Appliance to Version 6.5
KB ID 0001265 Problem Here I’m upgrading from version 6.0 to 6.5, the process creates a new vCenter appliance, then migrates all your settings into it, finally it then shuts down the old appliance and brings up the new one. Note: This procedure is ‘non-invasive’ i.e. it does not affect your production VMs, a vSphere environment can run for about 60 days without it’s vCenter, all that you would lose is the...