Deploying and Configuring The vCenter Server Appliance
KB ID 0001146 Problem The vCenter Appliance used to be a simple to deploy from OVA, but now you need to deploy it from another machine, (and it has to be a Windows machine). Solution Before you attempt to deploy the appliance, ‘pre-create’ its host records in your DNS. Download the vCenter Appliance .ISO file and mount it on your Windows machine, navigate to the vcsa-iu-installer directory, and run the installer.exe file....
Cisco FirePOWER Management Center Appliance – Allowing Domain Authentication
KB ID 0001117 Problem Once deployed, authentication is handled by the appliances own internal user database, in larger organisations this is a little impractical. So the ability to create an Active Directory Group, and delegate access to Firesight to members of that group is a little more versatile. Solution I’m making the assumption that the appliance does not already have external authentication setup at all, so I’ll...
Barracuda Web Filter – Not Displaying Usernames
KB ID 0001296 Problem I installed a Barracuda Web Filter 410 hardware appliance last week for a client on a 30 day trial. It was in ‘inline’ mode in front of their firewall and was happily logging all web activity and sites that were getting blocked. The problem was when you looked in the log this is what you saw; With other vendors you simply need to put an agent in to fix this, and as it turns out Barracuda is no...
Deploy Cisco FirePOWER Management Center (Appliance)
KB ID 0001263 Problem You have been able to manage your firewalls Internal SFR module for while using the ASDM Setup FirePOWER Services (for ASDM) For most people that’s fine, but if you have a lot of FirePOWER devices to manage that does not scale well. In those cases you should use theFMC (FirePOWER Management Center). Here ‘Im going to use the Vmware virtual appliance, (at time of writing there is no Hyper-V version)....
vSphere Error – ‘The operation is not allowed in the current connection state of the host’
KB ID 0000848 Problem You can see this either when attempting to power on a VM, or when attempting to deploy a VM from a template. Solution Thankfully it’s a really easy fix. 1. Connect to the console of your Virtual Center, (either through the VI client or via RDP) 2. Windows Key+R > Services.msc {Enter} > Locate the VMware Virtual Center Server service > Restart it. Note: If you have the vCenter appliance, simply...