Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Virtualization Community Blog
Showing posts tagged with Windows
Showing posts in English
Jordan | 07 Apr 2009 | 7 comments

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...

Jordan | 24 Mar 2009 | 0 comments

We recently released a Hotfix for SVS 2.1 SP 2 that resolves an issue with many network drivers not being able to install when an SVS layer is active.  You can download the update from our KB or from our trial-ware portal.  If, for some reason, this doesn't resolve the issue described above please reply to this post with the name of the driver you're trying to install and, if you have a paid support contract, contact support about the issue.

Jordan | 20 Mar 2009 | 0 comments

Windows System Restore is a feature that's saved my PC, as well as many family members, on more then one occasion.  When you have SWV installed and have to restore back to a previous point, where SWV is still installed, interesting things happen to your layers.  If you're familiar with Windows System Restore what's going on may be a no-brainier but I'm going to cover what happens to a layer when you restore to a previous point when  that layer wasn't installed.

SWV keeps files for layers, by default, in C:\fslrdr and registry info in SOFTWARE -> fslrdr and SYSTEM -> Altiris -> FSL.  So in our scenario we've got Layer1 imported into our system and then we create a restore point.  We then capture Layer2 and then realize something is jacked up for some reason and have to restore back to the point right before Layer2 was captured.  What would you expect to happen?

When you launch SVSadmin you'll see that Layer1 is still imported and...

riva11 | 29 Sep 2008 | 5 comments

Have you ever asked what is the best freeware program to use in place of your best commercial application?

Now the answer is found in the OSALT website. The mission for this site is to collect information and compare open source and commercial programs. The result is a large archive of many commercial programs and the freeware alternative.

Open vs. Closed
Find open source alternatives to your favorite commercial products. Browse through our software categories and compare pros and cons of both commercial products as well as open source software.

It can be really useful to discover open source software alternatives to well- known commercial software.

Link : OSALT

Suggested Freeware Portal sites :

  • EOS Director ( Enterprise Open Source Directory ) : http...
tneubauer | 20 Feb 2008 | 2 comments

With the advent of Vista SP1 Microsoft has removed the Group Policy Management Console (GPMC) from the mix. You cannot even install GPMC after you upgrade to SP1.

Read on to learn how to regain control with a cool little package we like to call SVS.

You can install Adminpack.msi on Vista, but with reduced functionality.

RSAT is not yet available, so how do you perform GPO management from a Vista SP1 machine?

SVS! - You simply create a .vsa for GPMC.msi and/or Adminpack.msi on a Windows XP machine. Export the layer and import it on your Vista SP1 machine.

You now have all of your management tools available again.

Thank you SVS!

fbuonvino | 16 Jul 2007 | 5 comments

I'll never forget a needlepoint carefully hung on the wall of a friend. It read, "Our Home: Clean enough to be healthy but dirty enough to be happy."

Juice contributor fbuonvino points out that the same philosophy should hold true when using registry cleaning tools to tidy up a machine that's housing virtualized applications.

Special care should be taken during registry cleaning on a machine using SVS. A program like Registry Booster or similar, normally used to clean a registry of errors, wrong paths, and open links could possibly mistake registry entries belonging to virtual applications as problems to be dealt with -- if the application is not currently activated.

You could easily verify the problem by making two scans, one with your virtual applications activated and another with those same applications not activated.

Admin | 22 Jun 2007 | 3 comments

Another chapter of the Altiris-sponsored eBook, "The Definitive Guide to Vista Migration" is now available for download.

This chapter focuses on one of the most challenging aspects of Vista migration: application or program preparation and migration. Get the download details here.

You can download Chapter 6 here.

Chapter 6: Excerpt

This is the goal of this chapter: to help you develop a structured application management strategy that will help ensure you are always compliant in terms of usage and licensing as well as responding to business needs. To do so, this chapter provides a structured look at each activity related to application management. These include:

  • Windows Vista features in support of application operation...
trb48 | 16 Apr 2007 | 0 comments

I ran across this really good article today. It talks about how you can use SVS to manage application compatibility.

Here is a juicy tid-bit from the article:

" should seriously consider moving to software virtualization during your Vista migration. Software virtualization allows you to package applications once and only once to deploy them to your PCs. Virtualized applications do not touch the operating system so your systems stay pristine at all times."

Take a look, it should be well worth your time!

Here is the link to the article:
How To Manage Windows Vista Application Compatibility

insession | 30 Nov 2006 | 17 comments

Peter asks: I have one of let's say 10 app layers activated, and using Regmon shows that there are LOTS of reg seeks by services.exe that result in a "Not found". Wondering what's going on, and how I can stop these many reg seeks.

One of the design principles of SVS is to keep the technology as small and unobtrusive as possible. So in the original release, we chose to pass through registry lookups rather than trying to "proxy" or "cache" them. The only way for this to work was to recursively search every active layer when a process tried to read or open a key. That's why you see what you mention above.

In practice, we observed that a different approach was necessary to be performant. In SVS 2.1, Altiris has implemented a registry cache. The result is a slightly more complex design, but a design that preserves the registry performance of native Windows. This one change resolved all of the performance...

dbethers | 06 Oct 2006 | 9 comments

If you thought the Login Hook code was cool, wait until you check out these examples provided by SVS Guru Dale Bethers.

Hopefully these examples will help those who are having problems configuring the SVS User Logon Hook. First we will look at the "Filename" and "Url" registry values and then the "LoggingFlags" registry value.

"Filename" and "Url" Registry Values

The "Filename" and "Url" registry values tell the SVS User Logon Hook were it should look to find the configuration file. The "Url" value takes precedent over the "Filename" value, meaning that if there is a "Url" value, the SVS User Logon Hook will always look there first for a configuration file. These registry values do not affect SVSUserAdmin. SVSUserAdmin is basically a specialized XML file editor...