Sequencing Microsoft Office 2010 and Dynamics CRM 2011 using App-V 4.6 SP1
Hi everyone, Alvin Morales here. Recently a customer wanted to sequence Microsoft Office 2010 with Dynamics CRM 2011 using the Offline mode with Outlook, and although we don't have an official support statement on this (meaning we haven’t fully tested it) we were able to get it working with a few minor steps. Keep in mind that this was done on a "best effort" basis and it worked in this customers environment but we don’t officially guarantee these steps will necessarily work in yours. Either way, it should give you a good start on implementing something similar.
Before sequencing, you need to determine if you want offline mode or online mode. If offline mode is going to be used then SQL Express needs to be installed locally on the sequencer as well as the target machines with an instance name of CRM.
- Install the Visual C++ 2010 redistributable files locally on the sequencer and the target clients. You can find the files at the links below:
- Install Windows Identity Foundation (KB974405) locally on the sequencer and target clients
- Install the deployment kit for office 2010 following the Office 2010 sequencing guide (Prescriptive Guidance for Sequencing Office 2010 in App-V 4.6 SP1).
- Copy all media files locally
I’m going to assume you’re already familiar with the basic mechanics of sequencing (virtualizing) applications using Microsoft Application Virtualization. If this is not the case, please see the App-V 4.6 Service Pack 1 Sequencing Guide.
- Install Microsoft Office 2010 pointing to Q drive. Select run all from my computer
- Once Office setup is complete, select run another setup in the sequencer and run the splash.exe from the CRM media
- From this window select Install Microsoft Dynamics CRM for Outlook
- Select custom install and select offline mode if you have SQL express installed locally. Change the path to Q: and create a subfolder within the main package to install CRM.
- Once the install is done, enable local interaction on all OSD files and save the package (see https://blogs.technet.com/b/appv/archive/2007/09/20/a-look-under-the-covers-the-local-interaction-allowed-tag.aspx for more details).
- Install all necessary prereq files on the target machines and publish the package
That’s pretty much it. Good luck and happy sequencing!
Hope this helps,
Alvin Morales | Senior Support Escalation Engineer
App-V Team blog: https://blogs.technet.com/appv/
AVIcode Team blog: https://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: https://blogs.technet.com/configurationmgr/
DPM Team blog: https://blogs.technet.com/dpm/
MED-V Team blog: https://blogs.technet.com/medv/
OOB Support Team blog: https://blogs.technet.com/oob/
Opalis Team blog: https://blogs.technet.com/opalis
Orchestrator Support Team blog: https://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: https://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: https://blogs.technet.com/mdm/
SCVMM Team blog: https://blogs.technet.com/scvmm
Server App-V Team blog: https://blogs.technet.com/b/serverappv
Service Manager Team blog: https://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: https://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: https://blogs.technet.com/sus/
The Forefront Server Protection blog: https://blogs.technet.com/b/fss/
The Forefront Identity Manager blog : https://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: https://blogs.technet.com/b/isablog/
The Forefront UAG blog: https://blogs.technet.com/b/edgeaccessblog/