enVision Patching

[RSAAdmin]

I'd love to see a more formal patch installation model for enVision. Downloading a bunch of zip archives from the FTP site, stopping services, backing up binaries, then moving the new ones over, restarting services is not a process that should have to be manual. It also means that there's no quick and easy way for support to identify what patches are installed, or for us to know what has been installed without a separate tracking method (Excel spreadsheet for example). All in all, rather ludicrous. Is this something we can ever expect?

Also, the Release Notes don't reference patch numbers -- instead only using descriptions. This also makes it difficult to identify what patches need to be re-applied (if any).

Message Edited by colingrady on04-26-200805:36 PM

[RSAAdmin]

I agree -- something a little more automated would be greatly appreciated.  I wouldn't think it would be too difficult to just create a batch file that includes the process, then writes to a file saying what system was patched and what patch level it is at.  In fact, I might dabble with creating my own batch script the next time support gives me a large number of patches to install.

--Jeff

[RSAAdmin]

I aggree with you 100%. patching a system by downloading zip files, back up the current files and then copy everything onto the bin folder takes too much time and mistakes can be made. having a batch file running this task would simplify the patching process and reduce the down time.

[RSAAdmin]

I completely agree with this, a more enterprise patching system needs to be added. Perhaps also testing / rolling out of all patches to all customers, not just based on a specific issue. Create the patch, test it properly, then make it available as an automated install......

[RSAAdmin]

I agree as well.  In a large enterprise with many enVision sites and domains it become cumbersome to have to deploy file by file.  It needs to be a consolidated exe with a /silent switch and verification of success.

[BryceRobinson]

What would be fantastic would be a monthly RSA enVision 'Roll-Up' patch pack for the appliance. These are not hard to make and it makes life a hell of a lot easier for Windows Server admins that are not familiar with the appliance. Sure, customers with LS appliances over multiple sites probably do some crazy rollout method already for their many appliances, but for ES customers this just simply isnt practical.

I would love to see the roll up patch pack with not only the OS updates but the other updates such as Event Source, VAM Engine, Definitions and enVision Application.

[RSAAdmin]

I'll def. give my support on this one. Anything RSA can do to make the time required for maintenance to be less!

[RSAAdmin]

The good news is that there are going to be periodic service packs released on SCOL that will install all the patches in one file.  The bad news is that it isn't fully released yet.  Right now you need to ask support for the download.  There is a service pack for all supported versions (3.5.1, 3.5.2, and 3.7.0). 

-Clarke