Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.
Endpoint Virtualization Community Blog

Change in Single Program Capture Behavior with SWV 6.1

Created: 07 Apr 2009 • Updated: 29 Jul 2010 • 7 comments
Jordan's picture
+6 6 Votes
Login to vote

Since the 6.1 Beta we've made a change with how Single Program Capture behaves in SWV 6.1 that you'll either love or hate depending on how you look at this news.  Let me start out by saying that we believe this is how Single Program Capture should behave so this is a bug fix.

Previously with SVS is you tried to capture Adobe CS3 products (not sure about CS4), as well as some other applications, using their Setup.exe installer the capture would end before the actual install actually started, the workaround was to launch a command prompt and then launch Setup.exe from the command line or do a silent install.  The issue at hand was certain child processes were being ignored, more on this is a bit, so when Setup.exe actually launched the installer we didn't track that and when Setup.exe exited we'd stop capture because the process we were tracking had ended and we didn't track the child process.  With the changes in 6.1 this is no longer the case as we now track all child processes so situations like this should be less common.

The downside is that now we track all processes so any app that launches a background process during, or after an install, will cause Single Program Capture to not end.  And example of this is iTunes which launches iTunes_helper.exe after installing, we use to not track this with SVS 2.1 but now we do so an iTunes capture will not end automatically unless you kill all the processes associated with the application you just captured (services shouldn't matter).  Another option is to right click the spinning SWV icon in Windows' Notification Area and select "Stop Capture" just as you would a Global Capture.

I'm sure that for those of you that are use to SVS will find this a little jarring in SWV but we think it's the correct behavior, because you never know what that background process is doing during an install, and that you all would prefer Single Program Capture to be as reliable as possible.

Comments 7 CommentsJump to latest comment

erikw's picture

Jordan,
I would like to have this as an option.
In some cases, and I already encountered it this behaviour is not very cool.
When you download an application that have to be installed form a network, the download and installation will trigger the Antivirus scanner and then the settings are included in the package.

So in my opinion it would be best to have three options.
Single Program capture
Single program capture with child processes
Global Capture.

This definetly would be a benefit for all of us.

Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)

*************************************************************
If your issue has been solved, Please mark it as solved
***********

+1
Login to vote
Jordan's picture

That's and interesting idea but the problem is to get it to capture 3 different ways we'd have to re-introduce capture bugs which I  know if we don't want to do.  And again we think this is way is how capture should work but any feedback, once 6.1 is released because we want people to use this so they can see how it behaves for themselves, about the capture change posted here or reported to support will be considered.

But with a single program capture the AV stuff shouldn't get captured in a layer, it's only child processes launched by the installer itself and not any that get started while capturing by a different application.

If a forum post solves your problem please flag is as the solution

+1
Login to vote
erikw's picture

i agree with you that Av stuf should not be captured, but it happens.
Only when the sofwtare that is captured downloads form the internet.
SWV sees the downloaded sofwtare as a childprocess and that triggers the AV stuff to be captured as well.
It can be easily solved by capturing with an older version of SWV or SVS and using good old DOS.

I have several capturing machines because I really like using the old 69 version that is the only version enabling me to capture DOT net correct.
But others will encounter the need to build a new capture machine just for downloadable applications.

Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)

*************************************************************
If your issue has been solved, Please mark it as solved
***********

+1
Login to vote
Jordan's picture

if you can give me an example: URL, application and so on to test this out I'll write up a bug on it because that shouldn't be happening.

If a forum post solves your problem please flag is as the solution

+1
Login to vote
erikw's picture

I noticed it on microsoft applications where you download a small portion. When you capture that it will analise your system for the necessary parts and then download them.

Try it with the mediaplayer 11.
That was one that showed me the behaviour.

Please do not misunderstand me.
i like the addition of the childprocess capturing and think it is a very cool addition that can prevent a lot of problems.
 

Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)

*************************************************************
If your issue has been solved, Please mark it as solved
***********

+1
Login to vote
Jordan's picture

No, I understand what you're saying.  I'm just not sure that the web install issue is something that we were aware of and so I want to get at it quickly and get bug(s) written up if needs be.

If a forum post solves your problem please flag is as the solution

+1
Login to vote
Jordan's picture

Erik, I'm going to need some specific info for this.

1) What os?
2) What AV?
3) when capturing WMP11 what exactly are you seeing that you don't think should be there?

If a forum post solves your problem please flag is as the solution

+1
Login to vote