Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Virtualization Community Blog
Showing posts tagged with Configuring
Showing posts in English
Jordan | 13 Aug 2008 | 2 comments

There is a conflict between older versions of SVS and recent definition files for SEP and SAV that has been causing bluescreens. Most people should not encounter this problem because newer versions of SVS do not have this issue. The versions having the problem that have been reported to us are in the 2.0 line. Customers should update to the 2.1 releases of SVS.

If you are experiencing these bluescreens please try the following, this solution has been tested in house and should work--if it doesn't please inform us:

  1. On a Machine boot into Safe mode.
  2. Open Regedit and navigate to HKey_LOCAL_MACHINE\SYSTEM\Altiris\FSL\ProgramIgnoreList
  3. Double click and add the following two entries to the program ignore list

    Relative to your SEP directories:
    \SymantecXXX\defwatch.exe
    
    \SymantecXXX\dwhwizrd.exe...
Tenacious Geo | 12 Aug 2008 | 10 comments

After we deployed the SVS Agent to all of our computers, there were a handful of computers that got stuck in a reboot loop. Ouch! We knew the issue started after the SVS Agent was installed, so we wanted to uninstall it. However, we could only get into Windows Safe Mode and were unable to uninstall from there.

After doing some digging, I found that there can be issues with the SVS filter driver during startup if it conflicts with another application (like certain versions of Symantec AntiVirus) or if it is a Windows 2000 computer that already has software that load filter drivers during bootup.

I ran across an Altiris Knowledgebase article 43245 that referenced the path to the SVS filter driver in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FSLX\ImagePath

The ImagePath is usually set to:

\??\C:\WINDOWS\system32\drivers\fslx.sys

(C:\WINDOWS for XP or C:\WINNT for Windows 2000)

My idea to recover...

bkaulins | 08 Aug 2008 | 0 comments

This is a PowerPoint presentation given at the Pittsburgh User Group meeting of our Task Server Install and Environment. It also shows how we use it to Leverage SVS.

FrankB | 24 Jul 2008 | 3 comments

V2.5.0.0
New: Major Gui Redesign
Fix: Rename layer
New: Layer Tooltips

How Does it work:

When starting it checks if you're a Administrative user and allows the program.
It also checks if you're an Corporate user, and will switch off some options.
It'll check if you are using Altiris Virtual Software Solution V2.1.2083 or higher, lower and it will tell you to update with the possibility to click on a Link towards the download at Altiris.

Here Goes:

Activate Layer
Deactivate layer
Reset Layer
Rename Layer...

Tony 1776 | 16 Jul 2008 | 1 comment

I have been working to get Office 2003 virtualized and deployed in a testing environment. When I deployed my SVS package I keep getting a hardware install screen popping up when I restarted. It didn't need to find any drivers because under admin it goes away after a minute or two. But under a limited account it produces errors.

If I clicked fast enough under a admin account I could see what the "device" was and it said Machine Debug Manager.

At first I thought some driver just wasn't installed correctly but when the same problem popped up right after I put my SVS package on the computer I thought something must be up with my package. I haven't found the exact cause of the problem but I have found a fix.

The first fix is the one that ended up working for me.

Open run and enter: (note quotation marks are needed)...

Jordan | 19 Jun 2008 | 2 comments

I've been doing a lot of work on AutoCAD and Inventor 2009 this past week and I kept on hitting a side-by-side error when I tried to export from XP to Vista or Vista to Vista (curiously it worked from XP to XP.) After some work I've found what the problem is and thought I'd share this since I've seen people in the past asking bout side-by-side errors.

Simply put a side-by-side error occurs when a shared DLL isn't properly registered with the system, this can be a manifest issue or an environmental variable issue (like the path not getting saved so Windows doesn't know where the DLL is).

The biggest culprit for side-by-side errors is Microsoft's Visual C++ runtime missing from the OS, and in the case of SVS that runtime doesn't capture properly which leads to the side-by-side issue. If you install the Visual C++ redistribute (in AutoCAD...

Scott Jones | 05 Jun 2008 | 4 comments

Q:
Lincoln asked, "we have OnPostActivate events in our layers, but they never run unless you manually de-activate and then re-activate the layers. All of our layers are set to start automatically. Shouldn't the OnPostActivate events run when SVS starts the layer during windows boot-up?"

A:
Lincoln, you've hit on a common misunderstanding caused by the language we use in the SVS Admin interface. The menu item "Start layer automatically" is actually a typo/mistake that never got corrected and has become institutionalized. It implies that there is some sort of "start" event for the layer. But there's not. It's supposed to say, "Set as Active on Start". "Active on Start" (meaning Windows start, not the layer or SVS start) is the correct technical term. (Trinket got it right, btw.) It means as Windows is booting, the layer is visible to the system ("active"). So there's never an...

FrankB | 28 May 2008 | 15 comments

Do you have a Virtual Application you want to share with your friends or colleagues? But you're not sure if any private information is given to them also?

Don't you want to distibute your layers to your environment in a clean state?

Make them smaller to ensure lower bandwidth usage?

Did you just Capture a new Virtual Application, and you want a clean export?

Here's your solution!

With (Portable) Slim Layer Exporter you can export your Layers in a clean and small state. Your userdata (Registry/Disk) won't be included in the Exported Layer.

Download it here.

P.S. U3 Version is also available.

Version v1.1
Added: Extensive exporting error reporting.

olliebean | 14 May 2008 | 2 comments

If you already have a number of applications virtualized as SVS layers, testing new unknown packages can be a tedious task. Testing a new piece of software means that all other layers have to be deactivated. Is there an easier way around this?

Read on to learn more.

Yes, there is. Create an empty scratch layer - I've called mine "!Scratch" (the "!" just ensures it gets sorted to the top of the layer list in SVS Agent). Then create a new shortcut, and in the box where Windows asks you to enter the location, type the following:

svscmd !Scratch a exec -p

If you put this shortcut on your desktop you can drag-and-drop a program file onto it (e.g. the installer of aa application you want to test), and the program will be run within the !Scratch layer. Or you can put it in your SendTo directory, and run a program in the...

Scott Jones | 05 May 2008 | 2 comments

Q:
Anil asked, "I was wondering if you could point me in the right direction. Here is my issue, we have Office 2003 installed on our base image. We have created a layer for Excel 2007. Everything works fine, except that we needed a way to make sure all .xls files open in Excel 2003 instead of Excel 2007. I was wondering if we could talk to an expert from your side to possibly solve this problem? We have attempted a few things but have not succeeded in accomplishing this task."

A:
When you have two or more applications that can handle a given set of file types, SVS allows you to explicitly configure which one has precedence. This is documented in the Product Guide, Chapter 6, under "Using Layer Prioritization...