Some of our clients have a drive protection software installed so that all changes made are reverted on reboot. Naturally, this conflicts with Sophos updates. So here's how we want to approach this issue:
There is a mechanism that automatically deactivates the drive protection (once a week, for example) and executes a previously configured batch script. (Any user interaction is blocked during that time.) Upon termination of that script, disk protection is re-enabled and everything is going back to normal. So what we're looking for is something that can be called from cmd that forces an update and terminates only after the update has completed.
Now, we already did some experiments with ALUpdate (9.5 and 10.0). Under Windows XP simply calling ALUpdate does nothing while under Windows 7 there was - according to client side logs - a successful update. (In that test scneario however there was nothing to be updated, yet.) The only problem is, that ALUpdate at least seemed to terminate right away. (The update was very quick so it's really hard to tell...) That's a bad thing because there's no way to know when the updated is actually finished. So we're able to call an update (at least under Windows 7), but we don't know when it's done...
Under Windows XP I've also tried the Visual Basic Script to trigger an immediate update. This actually does call the update, but it also terminates right away.
I'm aware that this might be a very race scenario, but it'd be really nice to find a solution to cope with it...
Thomas
This thread was automatically locked due to age.
