Posted by Tom Fulton on April 19, 2006 at 09:01:45:
we've encountered the following situation at least three times in the
past six months or so - an end-user that has been upgraded to a certain level of Comet is inspected and the version of Comet they are
running is some downgraded level. At one end-user they were downgraded back to Comet2004, at the other it was a downgrade from a
release that had the Daylight Saving time bugfix to version .359
In both cases, no installation executable was found on their server
for the versions that were running. This means that an installation
executable is out there on one of the workstations, possibly on a desktop and operators are inadvertantly launching this and then
simply answering questions in order to get out. We'll have to go
on-site to try and find these executables that were probably downloaded by a tech or system administrator. What I'd like to discuss is some means of building something into the installatin program to prevent this from happening. The discussion could also cover means of setting attributes or privileges to the Comet folder
to prevent these unintended updates to the Comet executables. Tom.