Video Screencast Help
Search Video Help Close Back
to help

Endpoint Virtualization Community Blog

Showing posts tagged with Virtualization
Showing posts in English
Scott Jones | 29 Jul 2010 | 2 comments

In this morning's ManageFusion keynote, Symantec Chief Operating Officer Enrique Salem announced that Symantec has signed a definitive agreement to acquire industry-leading application streaming vendor AppStream. AppStream has been providing the streaming component of Symantec's SVS Professional since June, 2007.

The combined power of application virtualization and application streaming enables enterprise IT to deliver software reliably, immediately, wherever it is needed, with automated license enforcement and compliance auditing. SVS Pro also enables new business models by providing the platform for delivery of any software as a service.

Streaming was a huge topic at ManageFusion yesterday, before attendees even knew of this morning's...

FrankB | 29 Jul 2010 | 12 comments

It took a while, but it is a lot of work, here goes; V2.0.0

V2.0.0
New: Fully Portable (Freeware Editions) / (USB/U3)
New: (Multi) Move Layer(s)
New: (Multi) Delete layer(s) with 100% registry removal.
New: File Progress on (Multi) Import
New: Automatically Check for Updates (See Options)
New: Added a Help Function
New: Changed Corporate edtion to fully functional for 30 Days.
New: Blue Edtion

Here Goes:

Activate Layer
Deactivate layer
Reset Layer
Rename Layer
...

FrankB | 29 Jul 2010 | 5 comments

Portable Import is meant to be used from a Portable Device like a USB Device or a U3 Device or a CD/DVD. It allows you to import Virtual Archives into SVS.

It can import several layers at a time.

There is also no installer included, it will run standalone.

Just copy this tool in the same folder where your VSA files reside.

Pick what you want to import and click Import.

Download it here.

Have Fun With It, FrankB

AL8 | 29 Jul 2010 | 14 comments

I would like (as many others out there) to have the Altiris Software Virtualization Solution Admin on a USB stick.

I have recently seen the solution posted by "erikw" (SVS4USB Admin) and it is great, but you must have a USB stick that is U3 enabled.

With the software called Ceedo (www.ceedo.com) you can install applications on EVERY USB stick (and I suppose also on USB external hard disks) not only those that are U3 enabled!

I tried Ceedo with Altiris and it works.... But not completely.

So, if there is someone out there interested in it, now I will explain how to install Altiris in a USB stick with Ceedo hoping that someone will help me get it fully working.

These are the steps to install SVS Admin on a USB stick:

...
tfronza | 29 Jul 2010 | 13 comments

When I am deploying a NEW Virtual Software Package, and I have it where I like it there are a few steps I do to "CLEAN-IT-UP" and prepare it for Distribution as a .VSA file through Altiris.

First thing I do is RESET the layer.

Second thing I do is go to the c:\FSLDR\# and delete the folder that looks like this S-1-5-21-112987585-3770-..... As far as I can tell, that is a SID and can not be in a Clean package.

Third thing I do is go to REGEDIT
HKLM\Software\FSLDR\2\HU\S-1-5-21-112987585-3770-..... Then I delete this one too.

At this point the layer is as clean as it can be....and I have found it to be SAFE to export. Export to a TEST machine and give it a shot.

Good Luck to everyone.

Thanks - Tom Fronza

hamletv | 29 Jul 2010 | 8 comments

Q:
Does disk defragmentation affect SVS Layers?

-Hamlet

A:
Hi Hamlet. Good question.

The answer is similar to the one we gave in response to the question about disk imaging.

Defragmentation works below the file system. And, since SVS sits above the file system, neither has any affect on the other.

jgo | 29 Jul 2010 | 4 comments

Q:
Is there a definitive listing of SVS error codes? For instance, what is error code 18?

A:
Thanks for the question, d0lemite. You can find the complete, unabridged list of SVS 2.0 error codes in the Altiris Knowledgebase, article 19991.

If you're seeing errors during import, you'll also want to check article 19934, "DynaZip Decompression Error Codes".

Or, if you're seeing errors during export, check article 19933, "DynaZip Compression Error Codes".

Adam Hall | 29 Jul 2010 | 8 comments

It is important to remember that SVS layers are still subject to Group Policies, even though the layer may be activated after the application of the policies.

A local cache of the Group Policies are held on the local machine when a member of an Active Directory and remain in force for the duration of the refresh interval.

Local policies are stored locally -- if you ever get into a situation of difficulty i.e. you lock yourself out, simply delete the %systemroot%\System32\GroupPolicy folder (on the system) and log back on.

When you activate a layer, the Windows OS will still enforce the GPO settings, even if you have specified different settings in the layer.

This is important to remember when testing and troubleshooting. Before you go nuts trying to figure out why, take a look at the GPOs to ensure this is not the problem.

RichC | 29 Jul 2010 | 0 comments

Generate a digital license after an application runs on the destination machine as a workaround to Office XP detecting a hardware change.

When packaging Office XP (or any portion of it) off of a CD and manually entering the Key when capturing, etc, you will run into an issue when bringing the VSA to a different PC. When launching the VSA on a new PC and trying to use the application, it will tell you that it has detected a significant machine change since it was installed and will give you only limited functionality. This is because of the digital license identification that Microsoft includes on this version of Office (I haven't seen this happen in any other version) is based on hardware. To fix this so that it will generate this digital license only after use on a new machine, you must do the following:

  1. Create an administrative share point from the setup.exe - enter the Office XP key and accept the license agreement. That way, all users running the install...
Jared Payne | 29 Jul 2010 | 0 comments

Jared Payne provides the step-by-step details on how to implement user-specific variables to protect data on multi-user machines.

In pre-release versions of SVS, only one set of user variables existed for an SVS-enabled computer. Now, each user gets their own set of user variables. User variables are associated with the currently logged on user and include things like DESKTOP, STARTMENU and USERPROFILE. Allowing each user to have their own set of user variables lets multiple non-concurrent users log onto a machine without being able to see the other user's virtualized user-specific data.

Adding user-specific variables changed the way SVSAdmin looks; there are some new areas when modifying layers. In the file system area in the layer editor, each sub layer now has 2 sections: System and User-specific.