Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello. My company is moving into a new building and we will need to purchase new firewalls and Internet routers. I'm hoping someone will be able to offer some advice as to the best products to purchase. We have about 100 employees in a single buil...
When CSA 5.1 agent is installed on the same workstation (running WinXP) as an application called Hansen (asset/work management tool), the user gets an error each time they close the Hansen application which references the application "imsv732.exe" an...
In CSA 4.0 and 4.5 it was very easy to enable Agent Service Control rule to allow only administrators the ability to stop the CSAgent service. However in CSA 5.0, that checkbox has been removed from the Agent Service Control rule screen. You can as...
I upgraded my CSA MC from 4.5.1.639 to 5.0.0.176. The migration initially failed, because I had an rule module with more than 100 rules, but I split that into two seperate modules and then the migration worked. I imported the licenses into the CSAM...
Also, you can't install CSA MC on a CiscoWorks server that has components that don't support SSL (like IPM and DFM). SSL is a global setting, so if there's anything on the box that would prevent from it from being enabled, the install will fail.
Actually it wasn't the license for the VMS server it's self - it was just for 25 desktops. I verified the PAK number was the same as the one on the paper that was sent to me. I tried to upload it several times, but no difference.
FYI - the reason for this is because Exchange uses a UDP packet on a random high port to send the message notification. Unfortunately, there's no way to modify that.
