|
Hey, It seems as though there are a few things contributing to
the timeout’s I have noticed while updating the Internet Scanner. Firstly
renaming the scanner sensor name to all lower-case allowed the procedure to
begin, however only one update installed and it continued to hang. A work-around I discovered was to delete the later XPU’s presence from the issDaemon.policy
file located on the scanner machine and re-apply one at a time, reboot the
scanner and restart all services on the SiteProtector machine. This one XPU
will now install, and each XPU requires that exhaustive procedure. The sensor
history looks like: [date] Apply Update Completed [date] Apply Update Unknown [date] Apply Update Completed [date] Apply Update Unknown … If I don’t do this the two outcomes are an indefinite
hang waiting for the remote machine to complete, or an error saying the remote
machine already has the XPU installed (even though RealSecure doesn’t recognize
this). Anyone had the same problems? Any comments and suggestions
are welcome. -a |
