I assume you're talking about upgrading sensors from 6 to 7 based on
version numbers.
My experience was a bit of a learning curve.
Running the upgrade from the console of Site Protector 2.1 automatically
was a disaster on multi-sensor Unix network sensors.
What I discovered was, the packages are built with dependancies on previous
sensors and must be uninstalled in reverse order of installation, which I
knew. What I discovered was that the upgrade done from the application
server didn't correctly save configuration, uninstall, then reinstall
properly.
So upgrading sensor 1 then sensor 2 on the same host failed. Upgrading
sensor 2 succeeded, but upgrading sensor 1 after that failed again, due to
dependancies.
Once I threw the auto install commands out the window and did it manually.
ie. pkgrm ISSXns2, then pkgrm ISSxns1 and finally pkgrm ISSXdmn, then
reinstalled both sensors. It went cleanly.
The only real sticking point after that was the length of time it took to
extract/remove the files for the sensor installs. Since those 2 points go
rather slowly it took a bit of time per host. Since it could be done as a
remote operation, I could have 10 or 12 at a time running easily though,
which mitigates the install/upgrade for a large installation.
"Gary Flynn"
<[EMAIL PROTECTED]> To: [EMAIL PROTECTED]
Sent by: cc:
[EMAIL PROTECTED] Subject: [ISSForum] Anyone have advice
for
s.net someone moving from ISS 6.x to 7
11/07/2003 12:16
PM
Any major issues I should be aware of before I take
the leap?
Any major database schema changes?
thanks,
--
Gary Flynn
Security Engineer - Technical Services
James Madison University
_______________________________________________
ISSForum mailing list
[EMAIL PROTECTED]
TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to
https://atla-mm1.iss.net/mailman/listinfo
_______________________________________________
ISSForum mailing list
[EMAIL PROTECTED]
TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to
https://atla-mm1.iss.net/mailman/listinfo
