Activate Package Installations
There are two common scenarios that can cause folks some problems.
First, if you use the native Windows zip extraction method (and 7zip, it seems...), it will create a folder in your console's current folder and put the files there (e.g., c:\arcsight\console\current\Activate Base 188.8.131.52\extracted stuff..., when it should be c:\arcsight\console\current\extracted stuff...). A secondary issue can be the actual path for your console if you've upgraded it multiple times. I've always just done a new console installation for each version (e.g., c:\arcsight\console6.5, c:\arcsight\console6.5sp1, c:\arcsight\console6.8, etc.), but I understand this is not always possible, depending on how much control your IT department gives you for application installation. In once case, I've seen a content author try to install the Activate packages by unzipping them to c:\arcsight\console\current, but because the upgrade process was used in a different manner, the packages should have been unzipped to c:\arcsight\console\latest\current. If you get an error along the lines of "arcsight is not a recognized command" when you run the .bat file, you may be in this position.
The second potential problem is related to the passwords. This is mostly my fault, as I didn't have as much time to work out the kinks as I would have liked, and I haven't had a chance to get back to it. Firstly, I would like to make the use of passwords acceptably hidden, as they are in the clear, now. This is a relatively simple fix, I just need to research it a bit. Secondly, if you enter a bad password, it doesn't check the status and stop executing the commands, so you will likely lock your account. It should automatically unlock it after a time (I believe the default is 30 minutes), but that can be rather inconvenient. Be prepared to manually unlock your account (or have an administrator unlock it for you).
With Protect 2015 just around the corner, it may be a bit before I can make these improvement. I appreciate your patience.