Back in April I posted about how with SWV 6.1 would no longer ignore LSASS by default, meaning you could capture MSSQL and similar applications into a layer. With the release of SWV 6.1 a lot of people started complaining about long delay when logging into a domain.
There's been a minor update to the behavior of applying a Layer Patch Archive (VPA) in Symantec Workspace Virtualization 6.1 SP1. When you apply a VPA to a layer either in place or new layer with the option to port over the user SID areas any link files (.LNK) in the Read-Write Sub-layer will get deleted.
One thing I don’t like about SWV is the hassle it is to import anything, I really hate having to navigate through the browse window to import a layer or to have to open a command prompt and type out the full path to the layer.
One of the issues with running two versions of Microsoft Office at the same time, with one in the base and one in the layer, is the MSI repair that gets launched when you switch between versions. This is happening because Office is trying to change the file associations for you so the version that was just launched has ownership.
With SWV 6.1 we replaced the old zip library with Chilkat Compression and with the new zip library we now have new error codes for import and export. Those that are familiar with the SDK and coding will recognize some of these error codes--though some of the names have changed-- and so instead of getting the ominous Error C
As many SVS\SWV packagers can tell you Office 2007 can require some effort to Virtualize and on Vista there's more work to be done. One error that's confusing is: "This document could not be registered.
Recently I posted about a change in capture behavior for SWV which is one of two bigs changes on what we capture, the other is that SWV no longer ignores LSASS by default (you can always add it to the program ignore list) for both capture and regular use, this is a big change and it wi
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.