With Microsoft Office 2010 we have the Office deployment kit for the initial App-V deployment and also the activation components that are added to it. However, it is a bit different to patch the Office 2010 deployment compared to other software packages. Below I demonstrate how easy it is to update your virtualized Office 2010 package with any future update patches.
Virtual package of the Office 2010.
Office 2010 deployment kit http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=10386
OS: Windows Server 2003 Ent, x86, Version 5.2.3790, SP2 build.
App-V: App-V Sequencer 4.6 SP1, Version 184.108.40.20670
Here I have used Windows Server 2003 as the OS but you can use the client OS appropriate for your specific environment.
I installed Windows Server 2003 with SP2 on a clean computer. It is a standard recommendation that you use the clean machine for every sequence you have. If using virtual machines you can take advantage of “snapshots”.
I installed the App-V 4.6 SP1 Sequencer.
I copied my Office 2010 package, the update patches and the Office deployment kit to the server.
I installed the Office deployment kit on the Sequencer computer and configured the machine using KB983462 - http://support.microsoft.com/kb/983462:
a. I ran msiexec /i OffVirt.msi 32-bit:ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core
b. I ran msiexec /i OffVirt.msi PROPLUS=1 (you can select the license that you have)
Now that we had the sequencer configured and ready to go, I opened my original Office 2010 package using the “Modify an existing virtual application package” option on sequencer:
Next I selected “Update Application in Existing Package”.
Browse for the “O2010x32.sprj” file. (This is the file name I have for my office package – yours will likely be different.) Once located it will load the package.
Press next on Prepare Computer screen, and make sure there are no errors on the screen. If you see any errors or warnings on this screen, make sure you resolve them and then proceed further. Not resolving these errors can result into unexpected behavior.
Click on “Select the installer for the upgrade or update”.
OPTIONAL : If the update does not have an associated installer file and you plan to run all installation steps manually, select the Select this option to perform a custom installation check box, and then click Next.
Click “Select “Perform a custom installation” and browse for installer file.
Click on “Run”
Next select the installer and install your patch.
Once all the required patches\updates are installed, by any of the above methods, check “I am finished installing” and continue to save the package.
Next step will collect the system changes and provide with Installation report.
Review the Installation report to make sure there are no errors.
Run the programs to make sure they have a good Feature Block. Feature Block 1 does need be redefined during an update. If you fail to do this you could end up with a 2gb package that has to stream after an update.
On Create Package, you can select the Save the package now, or continue to Modify it if required.
That’s all to it and now you’re ready to roll out your updated package.
For general update steps refer: How to Modify an Existing Virtual Application Package http://technet.microsoft.com/en-us/library/gg507649.aspx
Dhaval M Bhadeshiya | System Center Support 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 The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager The AVIcode Team blog: http: http://blogs.technet.com/b/avicode The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv
You guys need to stop using the term "easy" in regards to sequencing Office 2010. As long as you don't use any plugins, proxies or communicator then yeah, it's easy, if you actually USE office...it's not.
As a person who is currently trying to get a streamlined install with Office 2010 SP1 and Cumulative updates installed without it puking on it's shoes over and over, consider this a request.
To install SP1, you have to be carefull
I had to install, VCREDIS 2005, 2008x86,x64 and Silverlight for the Lync part of my package before starting to upgrade the package
After installing all prerequist, Office virtual toolkit as shown on this blog and adding "VSL" in the registry
Then Upgrade the package in AppV sequencing tool
Finally launch the SP1 installation File
My SP1 installation finnaly went successfull