RSA Admin

Updating 1 ESU without the executable

Discussion created by RSA Admin Employee on Apr 1, 2013
Latest reply on Jun 18, 2015 by Anton Makarychev

It it still reasonable to update an ESU just by copying the 4 essential files (.xml, .ini, *vendor.txt, and *client.txt) to the etc/devices folder... as opposed to running the ESU executable and only selecting a single event source?


Specifically, what I'd like to do is save the 4 files to the E:\nic\4000\%_ENVISION_%\etc\devices\<device> folder on the A-SRV, stop and start the Service Manager, then run E:\%_ENVISION_%\bin\Update_node_content.bat from each collector.


I haven't done it this way in years, and used to do it all the time.  But I am trying to avoid gathering a bunch of test evidence that would otherwise be needed if I ran the executable.


Can anyone (particularly those in professional services) vouch that this is still a reasonable & acceptible way to update one ESU?


--== John L.