Feature Request: Reboot before installing custom software

[d4vr0s]

Hi, Is there a possibility to add a checkbox to reboot before starting the custom software installs?

I'm trying to get Adobe Reader to install from the custom software msi folder. It installs, fails and then reverts back. The install does work after a reboot.

[WSUSUpdateAdmin]

Hi.

Sorry for delay.
I'll think about that, but it should be an option, I suppose.
BTW: Did you try Foxit or PDFXChange?

Regards
T. Wittrock

[d4vr0s]

Thanks for your response.

I have not tried either of those. I typically install Reader, Flash and Chrome. So far Reader is the only one that fails to install.

[WSUSUpdateAdmin]

Solved without additional reboot by modifying the installation sequence ( http://trac.wsusoffline.net/browser/trunk (r549)).
RTW

[d4vr0s]

Thanks! I might be able to try it out later today.

[d4vr0s]

Unfortunately this isn't solved. It installed a few updates before starting the Adobe Reader install and failed as before. I should mention that I'm installing Adobe Reader from a administrative installation folder with the 11.05 update already applied. I don't know if this could be part of the problem.
For now I'm installing Adobe Reader before or after running wsusoffline, it's the only one that's giving me this trouble.

[harry]

FYI
There should be a new version of Adobe Reader on next Tuesday.

[WSUSUpdateAdmin]

Hi.

It installed a few updates before starting the Adobe Reader install and failed as before.

Hmm.
Sounds like you didn't use the latest trunk - did you?

I should mention that I'm installing Adobe Reader from a administrative installation folder with the 11.05 update already applied. I don't know if this could be part of the problem.

That's exactly what I tested. With v. 8.8 it failed, but with the latest trunk version it succeeded (Win7 platform).

RTW

[aker]

Try this version:
http://trac.wsusoffline.net/changeset/5 ... format=zip
To make it ready for use, run "CompileAutoItScripts.cmd".

[d4vr0s]

I only downloaded the newer DoUpdate.cmd because I thought it was the only script that needed to be concerned about. I will try what you posted, it might be a couple days before I have a chance to test it again though.