Recently I came across a request with virtual Office 2010 and SharePoint 2007 where Multiple uploads and Datasheet view were not available.
The reason for this was that each component used a plugin in Internet Explorer that was not available during Internet Explorer launch. Then when VirtualOWSSuppmanager is launched it doesn’t find the plugins causing the features to not be displayed.
We took some time and figured out what was needed to make the multiple uploads and the datasheet view to work. One possible solution and the one that will provide all the functionalities within SharePoint 2007 is to bring the internet Explorer to the virtual environment. The reason for this is that some functionality, especially the toolbar in datasheet view, calls for registry keys that are only available in the virtual environment. Since the VirtualOWSSUPPmanager is just a layer called after Internet Explorer is launched, the process can’t query all the keys in the virtual registry.
If you decide you want the multiple upload features and the datasheet view you can use the following steps to accomplish this task. For these features to work you will need to copy the files required to the local box so the plugins are available when Internet Explorer is launched. The files can be copied from media, a local install of Office or the Sequencer machine. To accomplish this, the following files need to be copied to the local box in the following paths:
In C:\Program Files\Microsoft Office\Office14:
Here's a shot of the contents of the 1033 folder:
In C:\Program Files\Common Files\Microsoft Shared\Office14:
Here's a screenshot of the contents of the 1033 folder:
Here's a screenshot of the contents of the Cultures folder:
These files are not enough for the features to work though as we also need a series of registry keys to enable the features. Most of these keys are in HKEY_CLASSES_ROOT\CLSID but there are other locations we'll need to address as well. I have attached a text file at the bottom of the page that you can download to make these registry changes easily. To user it, simply down load it then rename the file to .REG and import it.
Since we need to install the Deployment kit for Office 2010 to all machines, all these steps can be easily wrapped into a single MSI and deployed to all machines via System Center Configuration Manager 2007.
Note: On some of the machines we tested, after selecting the Multiple uploads option we were presented with an error about mshtml. If you encounter this error you will need to find the Microsoft.mshtml.dll and copy this via explorer.exe to c:\windows\assembly for it to register properly.
Hope this helps you with your Office 2010 deployments using Microsoft Application Virtualization.
Note: A special thanks to our very own Justin Luyt and Scotland Welch for their help in gathering the information for this solution.
Download the REG file here: REGFile.zip
Alvin Morales | Senior Support Escalation Engineer
The App-V Team blog: http://blogs.technet.com/appv/ The WSUS Support Team blog: http://blogs.technet.com/sus/ The SCMDM Support Team blog: http://blogs.technet.com/mdm/ The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/ The SCVMM Team blog: http://blogs.technet.com/scvmm/ The MED-V Team blog: http://blogs.technet.com/medv/ The DPM Team blog: http://blogs.technet.com/dpm/ The OOB Support Team blog: http://blogs.technet.com/oob/ The Opalis Team blog: http://blogs.technet.com/opalis
Kind of defeats the purpose of App-V when you still have to dump a bunch of DLL's (exactly what you don't want riding local) on the local FS.
I'm not sure it completely defeats the purpose of App-V as there are many more significant advantages to deploying a virtualized version of Office with App-V but I hear what you're saying. And this is just one possible solution. As the article states, you can also bring an instance of IE into the virtual environment if you need/want this functionality.
Publishing IE seems a lot easier. If you do publish IE is there even a requirement to install the SharePoint proxies in the sequence?
Can you please elaborate on the steps above? Once I copy the 1033 folder and DLLs where do I paste them?
Will there be an updated Office 2010 App-V deployment toolkit released that will perform this automatically?
Can you please update the link to Multipleupload-datasheetview-keys.txt
Sorry, the link should be working now.