Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Virtualization Community Blog
Showing posts tagged with Workspace Virtualization
Showing posts in English
Screenbert | 09 May 2006 | 2 comments

I recently created an SVS Layer that included a shortcut pointing to an executable inside my layer. There is nothing strange about this, but for the purpose of a demo (to our director) I wanted to show how a user could delete an entire directory and have it restored simply by resetting a layer.

This is where the fun began. You delete the directory and attempt to use the shortcut. It shouldn't work...right? Wrong. Microsoft Windows has a great little technology for when you try to launch a shortcut and the file it refers to is missing. Windows searches for another executable with the same name. It also deletes the old shortcut and creates a new one with the same name. This means the shortcut is no longer part of the SVS layer.

After deleting the folder that the shortcut originally pointed to, my shortcut now pointed to a folder called "c:\fslrdr". This is the SVS redirection area where there is an executable with the same name. Even after deactivating the layer or...

riva11 | 09 May 2006 | 0 comments

Recentemente ho creato un layer SVS che includeva un collegamento che puntava a un eseguibile all'interno del mio layer. Niente di strano fino a questo momento, ma per una demo (al nostro direttore) ho voluto mostrare come un utente può cancellare una intera directory e poi in un secondo momento ripristinarla semplicemente resettando il layer.

E qui è dove comincia il divertimento. Cancelli la directory e provi a usare il collegamento. Non dovrebbe funzionare .... vero? Sbagliato. Microsoft Windows ha una piccola ma grande tecnologia che entra in gioco quando provi a eseguire una collegamento e il file a cui si riferisce è mancante. Windows ricerca un altro eseguibile con lo stesso nome. Inoltre cancella il vecchio collegamento e ne crea un nuovo con lo stesso nome. Questo implica che il nuovo collegamento non è più parte del layer SVS.

Dopo la cancellazione della cartella dove puntava il collegamento originale , il nuovo collegamento adesso...

Admin | 03 May 2006 | 0 comments

Q:
Karsten asked, "Do you have some details how to deal with applications that require different Java versions? I've heard that we can handle this but how exactly? From my understanding each Java runtime needs to be part of the appropriate application layer, right?"

A:
That's one way (the simplest). Or the apps need to be called using our EXEC command line option, which makes it run as if in the same layer as the Java version needed -- more efficient when you have lots of apps.

A third option (for apps in the base), is to launch the apps from a script/batch file/etc. that is in the corresponding Java layer.

Admin | 03 May 2006 | 0 comments

The Altiris support guys and gals are the world's best problem solvers. Here's one such problem (and its resolution) that's been haunting a few of our SVS users.

If you're seeing this ...
You've exported an SVS layer to a VSA file. The process completes and a message states the export was successful. But then, when you check the directory that should contain the new VSA, it's not there. Nothin' but smoke.

And you've done this ...
If you've changed the path that contains the SVS layers, known as the Redirect area, from its default location (C:\fslrdr) to a new location, you're half way to solving your problem. After careful study, the support techs found that if the new location contains spaces in the path (C:\Program Files\fslrdr) the aforementioned problem rears its ugly head.

Never fear ...
If you have created layers on a system that is experiencing this problem there is a way to manually save the layer information,...

Admin | 02 May 2006 | 0 comments

Q:
Cameron wanted to know how closely related the file and registry redirection within SVS is to the "virtualization" that MS Vista will use to improve legacy app support.

A:
Altiris SVS is based on file system redirection technology, a concept that is not unique to Altiris. File system redirection is also used by Microsoft in Vista to provide backward compatibility with legacy apps that do not run in standard user mode (see this), which is a very specific and relatively simple use of the technology.

Altiris has a much broader vision for how redirection can be used. Altiris uses file system redirection to abstract any software—any application, data or patch—from the base operating environment, into prioritized layers that are portable between machines. We also abstract out the user-specific elements of all of these...

Admin | 27 Apr 2006 | 0 comments

"More than 50 products competed for the coveted Best of Show award at MMS 2006, Microsoft's largest-ever gathering of information technology professionals and Microsoft partners. Best of Show candidates were required to deliver products that are easily integrated and directly beneficial to the Windows network environment."

Read the full release here.

Admin | 27 Apr 2006 | 0 comments

"Like princesses at the ball, the application virtualization vendors stole the limelight from the more mundane manageability tools at Microsoft's big management pow-wow this week."

Read the article here.

Admin | 27 Apr 2006 | 0 comments

Q:
Ralf wrote: "As SVS offers the possibility of installing different DLL versions for different applications to the same location, I believe the Windows application first looks in memory to see if the DLL is already loaded before the application looks in the VSP file location. Therefore, I think I have to use isolation if I really want to solve compatibility issues. Do you agree?"

A:
Actually, Ralf, that's not how it works. Windows will only use the same code segment if the DLL is identical. If the DLL is not identical, it will load the other DLL even if it "thinks" it is coming from the same path.

Admin | 25 Apr 2006 | 3 comments

Q:
Jack asked: Does the virtualization of a Web browser such as Internet Explorer or Firefox prevent a virus infection? For example, if one were browsing the Web with an SVS installation of Firefox and encountered a virus, could that spread to the baseline system, or does the sandbox effect extend to the system memory as well as the file system?

A:
Hello Jack. Thanks for the question.

If malware launches from a virtualized application, SVS will track that as part of the process tree and capture what it does. When the layer is reset, the malware will be removed from the local hard drive. So SVS does prevent malware from permanently altering the app that launched it.

Note: The malware still has an opportunity to run and to perhaps do some damage across the wire. So this should be considered an additional layer of protection, not a replacement for anti-virus products!

Also, a caveat on this:...

Jared Payne | 18 Apr 2006 | 25 comments

If fonts are a sore spot between you and virtualized applications, here's a cure from Jared Payne that should clear things up.

A number of users have reported problem with fonts when using SVS. The reported problem causes applications like Outlook to not look and act properly. The only guaranteed workaround is to copy the fonts from the layer to the base system. You can manually do this by using the advanced editor in SVS Admin to drag the appropriate fonts to the system fonts directory.

Since you probably do not want to do this on every machine you manage I have created a tool to help you out; CopyFonts. CopyFonts needs to be run as a user with permission to add fonts. If your users are administrators, you can run this application whenever you want. If your users are not administrators, you will need to guarantee that this application is run as an administrator.

SVS has the ability to run an application when a...