Cisco FirePOWER User Agent – Use With the FirePOWER Management Console
Aug14

Cisco FirePOWER User Agent – Use With the FirePOWER Management Console

KB ID 0001179  Problem FirePOWER Management Center, will give you a wealth of information on traffic/threats etc. Usually it will tell you what IP the offenders are on, but if you want to know what a USER is doing, then that means you have to look though logs see who had what IP, at what time etc. So you can install the FirePOWER User Agent on a machine, (this can be a client machine, though I usually put it on a member server). You...

Read More
SEM – SPAMfighter Exchange Module – Installation and Configuration with Exchange 2013
Nov17

SEM – SPAMfighter Exchange Module – Installation and Configuration with Exchange 2013

KB ID 0000824  Problem “I seem to get a lot of spam”, and “I get a lot more spam than I used to” are right up there with “My computer is running slow”. It’s a problem that, eats up users time and fills your mail stores with junk, and time/disk space costs money. SEM is tiny! In a world where a graphics driver is now over 100MB the entire install suite is less than 11MB. This is going into my...

Read More
Windows Server 2008 R2 – Configure RADIUS for Cisco ASA 5500 Authentication
Nov17

Windows Server 2008 R2 – Configure RADIUS for Cisco ASA 5500 Authentication

KB ID 0000688 Problem Last week I was configuring some 2008 R2 RADIUS authentication, for authenticating remote VPN clients to a Cisco ASA Firewall. I will say that Kerberos Authentication is a LOT easier to configure, so you might want to check that first. Solution Step 1 Configure the ASA for AAA RADIUS Authentication 1. Connect to your ASDM, > Configuration > Remote Access VPN. > AAA Local Users > AAA Server Groups. 2....

Read More
SBS 2011 Missing Netlogon Share (Post Migration)
Nov17

SBS 2011 Missing Netlogon Share (Post Migration)

KB ID 0000809  Problem Whilst performing an upgrade from SBS 2003 to SBS 2011, I went on-site this morning to be told, “The new server does not have a NETLOGON share!”. As a result the clients who had authenticated to the old server had successfully ran their logon scripts. But the clients who had authenticated to the new server had not. Solution 1. On the original (SBS 2003) server > Start > Run > cmd {Enter}...

Read More