Layer isolation is a feature in Workspace Virtualization that lets you turn on and off the visibility between layers and the base. Layer isolation is only needed occasionally and under specific circumstances.
The most common circumstance for using layer isolation is when you need to run different versions of the same program that use associated resources in the file system or registry.
Types of Isolation
Hide From Other Layers
This option hides the selected layer from all other layers. You can still see the layer and it is visible to the operating system. However, dependent layers override isolation rules. For example, if layer 1 is dependent on layer 2 but layer 2 is hidden from other layers, layer 1 will still be able to see layer 2.
Hide From Operating System
This option makes the selected layer invisible to the operating system. The layer is still visible to other layers. However, when a layer is hidden from the operating system there are only a few ways you can access it. To access a layer hidden from the operating system, run cmd from the layer and then use cmd to launch the application. You can also access a layer hidden form the operating system through another layer if the layers are not hidden from each other.
Hide Other Layers From This Layer
This option makes all other layers invisible to the selected layer. You can still see the layer and it is still visible to the base. However, dependent layers override isolation rules. For example, if layer 1 depends on layer 2 and layer 1 has this option enabled, layer 1 will still be able to see layer 2.
To Isolate a Layer
- Select a layer.
- Right-click and select the type of layer isolation you want. You can select multiple types of layer isolation for the same layer.
Layer isolation does not resolve conflicts between multiple versions of Microsoft Outlook or Firefox.
Layer isolation does not work with Java 1.4. However, there is a way of isolating layers through the registry that works with Java 1.4. For instructions on how to run multiple versions of Java--including 1.4--see the following Connect article: Virtualizing Java with Symantec Workspace Virtualization.