Capturing a layer needing reboot
Hello,
I know this question has been adressed on the old juice before, but I have not been able to properly solve it.
So far this is what I did:
- Started capturing the app normally.
- When the installation prompted me for a reboot, I stopped the virtualization.
- Rebooted the computer.
- Restarted the virtualization using Global capture mode. I hoped the installer will continue and I can fininsh the installation successfully.
Well, this was the theory, but it did not work out like this. After the reboot, when I re-started the installation, the installer did not continued from the "break point", it did not finish the installation propely, but asked me for another reboot. And from here the installation entered into a loop, it did not matter how many time I rebooted the computer, when I restarted the capture, it asked for reboot again and again.
The only reason I can think for this behaviour: during the reboot Windows does some changes to some files, drivers, which are not captured by SVS or SWV. Upon restarting the capture, the installation continues from a pre-reboot state, thus prompting for a reboot.
Erik wote an excellent article about virtualizing Daemon Tools, I followed it step by step and was not able to get past this reboot sequence.
I would appreciate any feedback, tip or trick in this direction; or a step by step description of how to handle the reboot, perhaps with some screenshots.
Can anyone point me in the right direction?
Thanks in advance.
when ever a software requires
when ever a software requires a reboot even deactivating a layer and then activating again should work. you need not to reboot your machine.
the activation process takes care of all startup processes. it also depends on software you are installing like Mercury QTP, i am never able to virtualize that software.
Regards,
arjain
www.syspanacea.com
Reason for Reboot
I wrote an article on Juice that I thought I called SVS Packaging Best Practices but I can't seem to find it after the port to Connect. No matter, I can give you a couple of ideas.
There are three well know reasons that application installations require a reboot:
1) The are in use files that will cause the windows to make an entry that after the machine is rebooted, it will need to copy the "replaced" file prior to accessing it. This should never be the case with SVS because all files are written to the virtualiztion area and will not replace existing files. Probably not the issue.
2) The application has installed some services or drivers. It needs the system to reboot to load the drivers, or start the services. If this is the case, all you need to do is to set you layer to start automatically. These services and drivers will be loaded when the machine boots if this flag is set.
3) The installation wants to do some post boot configuration. This would mean that the installation wrote something into the Run or RunOnce keys in CurrentControlSet\Windows\ (I can't remember the path exactly, but I hope you get the point). Check you layer to see if this is the case, and try to run it into the layer.
I hope this helps.
Scot
SVS Best Practices: Layer Creation and Packaging article
I remember the interesting article , it should be : SVS Best Practices: Layer Creation and Packaging
Regards,
Paolo
Riva is Right
The article mentioned by Riva is written by Scott Curry, and contains a lot of very valuable information.
Regards
Erik
www.DinamiQs.com
Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)
Would you like to reply?
Login or Register to post your comment.