Microsoft Office creates a Visual C++ Runtime dependency on Windows Vista and Windows 7
The most common issue that is encountered when capturing Microsoft Office 2007/2010 is handling the dependency on the Microsoft Visual C++ 2005 (Office 2007) or Visual C++ 2008 SP1 (Office 2010) runtime. During Office installation, if the Visual C++ runtime is not available on the computer, Office installs it. For most applications, installing a dependency is not a problem. The dependency is captured to the layer with the application. With Office, however, the installation uses transactions to install the Visual C++ runtime. These transactions cause some of the installation data to be written to the base instead of to the layer. The easiest way to resolve this issue is to distribute the Visual C++ runtime as part of your base image or through software distribution. Distributing it as part of your base image makes it available for Office and all other applications that use this runtime. If that is not an option, it is possible to capture and deploy Office using Symantec Workspace Virtualization. Since everything is in the base after the installation, the layer works properly when it is tested on the computer on which it was captured. However, if the layer is migrated from one computer to another, the leaked items that were installed to the base rather than the layer (in this case, Microsoft Visual C++ Redistributable's registry keys and SxS files) are not present within the layer. Accordingly, Office runs a repair to reinstall all of the missing components. Because this repair is also transacted, everything is again captured to the base, rather than the layer. To successfully capture Office and avoid reoccurring repair installations, install Microsoft Visual C++ Runtime to the base before running the virtualized application. Because Office expects a specific version, that specific version needs to be installed in order for the capture to be completed properly. More than one version of Visual C++ Runtime can be present simultaneously on a computer, and is it not backward-compatible (like .Net).
In summary, the best practice for capturing Office 2007 or 2010 is to first have Microsoft Visual C++ installed into the base before you capture Office. You can capture using the above method without the required Microsoft Visual C++ Redistributable in the base, as long as it is installed on the client computer before Office is run. You can do capture using the above method because the layer sees what is in the layer before it sees what is in the base. Installing Microsoft Visual C++ to the base helps keep the Visual C++ libraries from becoming outdated if they are installed in the layer. Windows Update or another application might update the C++ libraries in the base. If you have the Visual C++ libraries in the layer, that version is used even if a newer version is present in the base.