Hi, Does anyone know how to capture a reboot in AdminStudio Repackager. For me it stucks when the software gives a reboot prompt.
If anyone can help, it would be useful. Thanks.
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


Thanks guys for your posts, but I was not looking for this. I know how to recapture the application. I have like 8 years of experience in this field, but most of the time I have used WISE Package studio. In there I was able to recapture the reboot and take out unwanted entries. But in here in Installshield, the reboot just does not go through till I finish the capture. Have you faced any such issue with Installshield.
Answered 03/28/2012 by: piyushnasa
Red Belt

  • What type of capture are you doing? You should be able to do an initial scan, finish that, then close the install monitor alltogether, do your installation, including the reboot, and just restart the capture tool. It will have saved your initial scan and will compare against that. Just be sure to do a 'multiple step' capture

    Are you getting error messages, or is the reboot just not happening? Or are you actually providing the setup.exe to monitor in the capture settings?
  • I do not know how to do a multiple step capture. Can you please elaborate..
    I am providing setup.exe to monitor. How to close the install monitor all together.
    Is it with Repackager or any other tool in Admin Studio?

    Thanks for your reply..
Please log in to comment
You can't really 'capture' a reboot.

If your package does something that necessitates a reboot, such as replaces files that are in use during the reboot, then there isn't much you can do about that.

If it is something service related, you could stop/restart/start services within your MSI - removing a need to reboot.

It all depends on what it is that is requiring a restart.

You can however suppress a reboot in your MSI with the Public Property set to REBOOT=ReallySupress

Hope that helps,

Answered 03/28/2012 by: dunnpy
Red Belt

Please log in to comment
Afaik there is nothing intrensically keeping you from rebooting a machine between the initial scan for a capture in Installshield and the post-install scan (assuming we're talking MSI packaging here)

You will have to filter out alot of 'default' stuff that happens during a reboot in the resulting .irp file though, and depending on what actually gets changed after the reboot, your resulting package might require that reboot too..

To get some reference points on what to clean up, it might be interesting to just capture a simple reboot, that way you get an idea of what kind of stuff you might have to filter out

Answered 03/28/2012 by: pjgeutjens
Red Belt

Please log in to comment