Very cool tool from MSFT to “replace network monitor,” Message Analyzer looks to be a hell of a lot more.
Definitely a pretty solid log file and live activity viewer or as you could say… message analyzer. *boom*
Symantec was fine with giving me Cleanwipe, opening a case even though I didn’t have a valid support contract (as it had expired).
The latest Cleanwipe utility will work on all previous Endpoint Security products and can be obtained:
Login ID: cleanwipeutility
Here is a summary of Brian Scholar’s article on implementing Powershell Remoting via Group Policy.
Computer Configuration\Administrative Templates\Windows Components\Windows Powershell\ Turn on Script Executiuon: Enabled, Execution Policy: Allow all scripts Computer Configuration\Administrative Templates\Windows Components\Windows Remote Management (WinRM)\WinRM Client Trusted Hosts: Enabled, TrustedHostsLists: [a subnet wildcard, like 10.10.1.*] Computer Configuration\Administrative Templates\Windows Components\Windows Remote Management (WinRM)\WinRM Services Allow remote server management through WinRM: Enabled, IPv4 filter: [subnet range]
I’ll be honest. I came from an all Fortigate shop, and the last real hardcore Cisco work I did was on a PIX.
Since it’s been like six years, I figured I’d doc the very simple procedure to upgrade the ASDM image on an ASA.
A highly intelligent folk who quality checked a refurbed ASA 5505 before shipping as a warranty replacement thought… “hey, I’ll upgrade the IOS, but not upgrade the ASDM.” Since I’m hardcore and don’t bother with the ASDM, only CLI, I didn’t worry about it before certifying a config as good before release. Well, god dang it, we need the ASDM! Alas, I found an awesome troubleshooting page on Cisco’s site, and realized that I may have to upgrade the ASDM image. So, here’s how.
1) Get your version information with the following:
sh ver #Cisco Adaptive Security Appliance Software Version 8.2(5)55 #Device Manager Version 5.2(3) <=== this is not listed as compatible
2) Take a gander at the ASA/ASDM compatibility matrix.
The ASA version I'm running is listed as being compatible with "ASDM 6.3(4) and later. Recommended: 7.4(2)."
3) download the image by searching this annoying site (just use IE, trust me)
3) grab a tftp server app and copy the .bin to the served directory (try tftpd64)
4) copy the image up to the flash
copy tftp flash #server is: 10.8.6.145 #source & destination filename is: asdm-742.bin
5) verify the presence of the image
show disk #.... asdm-742.bin
6) show the existing asdm image
sh run asdm #asdm image disk0:/asdm-523.bin
6) assign the new image:
asdm image disk0:/asdm-742.bin wr mem
If you’re receive these and you know it, clap your hands:
SOME DEPENDENCIES WERE MISSING. MAILGATE missing dependencies: Net::SSL ...MISSING LWP::Protocol::https ...MISSING Crypt::SSLeay ...MISSING
If you’re receiving these, and you know it, and you really want the modules; if you’re receiving these and you know it, search with yum:
yum whatprovides 'perl(Net::SSLeay)'
Useful for lots of stuff.
If you can’t shutdown a VM, and it won’t poweroff, ssh into your Host and kill the process that hosts the VM:
esxcli vm process list esxcli vm process kill --type=hard --world-id=[WORLDID]
You can choose types: soft, hard, force.