Video Screencast Help
Endpoint Virtualization Community Blog

Virtualizing Applications that Require a Reboot During Install

Created: 21 Feb 2006 • Updated: 29 Jul 2010 • 1 comment
Brian Mann's picture
0 0 Votes
Login to vote

Many applications require at least one reboot during their installation. So, how does one successfully virtualize one of these hell-bent-on-rebooting apps? Brian Mann shares some pointers.

If you're trying to install an application into a virtual layer but your application insists on doing an automatic reboot during the installation process, you're in luck.

Unfortunately SVS doesn't handle this very gracefully yet (stay tuned), but here's what you can do to install these apps today.

  1. Start your capture as you would any other.
  2. When prompted, go ahead and reboot. The setup will not continue since the entries that would cause this are in the layer.
  3. Once the system is back up, re-enter capture mode (SVSAdmin, file, update, ...).
    • The easiest way to make sure that all of the correct information is captured by the layer when re-entering capture mode is to re-enter it in a global capture. The only downside is that you may have to do some clean up on the layer to remove unrelated elements that have been captured.
    • The other option is to open the layer editor and find out the command that it was going to run, the common places for these entries are:
       %SystemDrive%\Documents and Settings\USERPROFILE\Start Menu\Programs\Startup
      %SystemDrive%\Documents and Settings\ALL USERS\Start Menu\Programs\Startup

      Then copy the command, remove it from this location in the layer, and run that command upon re-entering capture mode using a batch or cmd file.

Comments 1 CommentJump to latest comment

danrather's picture

I think this utility will help to find what pending operation(s) there are.

Login to vote