Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Virtualization Community Blog

SWV SP7 Skylark Now Available

Created: 31 Mar 2011 • Updated: 01 Apr 2011 • 11 comments
Jordan's picture
+1 1 Vote
Login to vote

This week we released SWV SP7 (6.4.1266), formally known as Skylark, which what we're calling a hardening release.  After the last two big releases, SP4 and SP6, we decided to make this release focus on only bug fixes so there are no new features that have been added.  We spent a lot of time with existing and new customers working in their environments, and how they used the product, to ensure that SWV is a better product.

This release will be up on the public download site within the next few weeks and for the mean time you can get SP7 by contacting support.

Some of the fixed issues include:

Non-True Type fonts, if in a layer, may not properly load.

Fixed several causes of getting a Black Screen of death upon system startup when SWV is on a machine.

There were instances where scheduled tasks wouldn't run if a layer was active.

Fixed a lot of BSOD conditions.

Many bugs were fixed that will improve general performance and stability of the product.

The release notes are available at: http://www.symantec.com/docs/DOC3714

Comments 11 CommentsJump to latest comment

dlopes's picture

Great ! :)

Hope the bugs when deploying the agent to Windows XP have been fixed!

Daniel Lopes de Oliveira
Technical Team Leader - Endpoint Management & Mobility

-1
Login to vote
dlopes's picture

Can you post the download link? I went to the trialware download, and its still SP6, SP7 is a beta release?

Daniel Lopes de Oliveira
Technical Team Leader - Endpoint Management & Mobility

-3
Login to vote
Jordan's picture

As I stated it's not on the trialware site yet, that process takes a few weeks, but you can get it by contacting support.

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

+1
Login to vote
Pascal KOTTE's picture

After 4 months, or more, the "Trial" page does still not have the "previous" latest 6.3.2065, and keep the more 6 months old 6.3.2059 !!!

(see https://www-secure.symantec.com/connect/blogs/how-get-svs-or-swv-where-download-svs-21-and-swv-61)

And the DOC3028, still talk the SP6 HF1, providing a FTP to the SP7 cheeky

I think the word is similar the french one: euphemism

And I don't talk about the delay to make the "http://www.getsvs.com/" we are still waiting the come back from June 2009 !  A few weeks !! Yes of course, how many dozen or hundred, like the more 2 years from win7 x64 version coming ? angel

But personaly I prefer Symantec is taking time to improve their software quality. yes

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
Jordan's picture

I'll look into this and see what's going on.

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

-3
Login to vote
Peter van Esch's picture

This release is available on the Support FTP site:

ftp://exftpp.symantec.com
UID: sevrelease
PWD: S!m4NT3c

from http://www.symantec.com/business/support/index?page=content&id=DOC3208

+2
Login to vote
Kirk Panitz's picture

It looks like this release breaks the sendinventory command for the NS6 Altiris Agent. When I try to run "svscmd sendinventory" I get:

Registry operation on layer information failed. This is caused by missing or incorrect registry keys or values.
Error: 1040
SVSCMD failed: SENDINVENTORY

I've confirmed that I have the proper registry keys set and the SWV agent is listed as a sub agent. But the send fails and after a software inventory completes the list and status of virtual layers are not updated in  the NS console.

Send inventory is currenty working with SWV 6.3.2065. Any ideas on why it doesn't work with 6.4.1266?

+1
Login to vote
ManelR's picture

Hi Jordan,

How do you install this version for users plus the NS integration?

I'm trying this as usual and the product is not installed:

Symantec_Workspace_Virtualization.exe /s SWV.PRODUCT_KEY=XXXX SWV.REBOOT=ReallySuppress SWV.ADDLOCAL=ALTIRIS_NS

I can use this (for admins) without problems:

Symantec_Workspace_Virtualization.exe /s SWV.PRODUCT_KEY=XXXX SWV.REBOOT=ReallySuppress SWV.ADDLOCAL=SVS_Admin

Has the syntax for installing SWV changed in this version?

Thank you.

IT Systems Manager
LCFIB - Computing Lab
Barcelona School of Informatics
Universitat Politècnica de Catalunya - Barcelona Tech
-1
Login to vote
Pascal KOTTE's picture

see (& vote :) my post there:

https://www-secure.symantec.com/connect/blogs/how-get-svs-or-swv-where-download-svs-21-and-swv-61

also from RENE

https://www-secure.symantec.com/connect/blogs/command-line-switches-new-swv-installer#comment-5290891

You must run the EXE and extract the MSI before CANCEL, from temp folder all user/symantec/SEV

(notice content never deleted)

Use the MSI instead of the EXE. More easy also to "IMPORT" as a software component into ALTIRIS...

Why Symantec EXE instead of MSI, too much simple ?

I already see a guy wanted to repackage the EXE of the installer SWV, using a "snapshot capture", to build a MSI to deploy with a GPO... I explain was really not a good idea !!! :)

Just a change I should update my old post: ADDLOCAL=Altiris_NS, instead of the old Altiris_NS=1

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
Jordan's picture

No changes were made to the installer this version.

with regards to NS, not quite sure what's going on as that's not my area of expertise but I do know there were changes to our behavior with NS in this release for things in NS 7.X.  I'm going to be forwarding the issues brought up on connect to someone who's more familiar with those changes and see what's going on.

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

+1
Login to vote
Kirk Panitz's picture

The NS install option seems to be hit and miss, I've been deploying a .reg file along with the update (per SK's instructions for 2065) to manually register the pacakge as a sub agent for Altiris.

I also reset all packages immediatly after import to avoid the bug where it fails to properly send inventory to the Altiris Agent/NS.

Otherwise this latest version has been working very well for me, and is a marked improvment especially on Windows 7 machines.

-3
Login to vote