Bear with me here because this may be a tricky question.
I have a slipstreamed installation packages for the CRM 2013 Outlook Client. Up until now I have only needed the 32bit client version so that's all I prepared. The package is updated with SP1 and SP1 UR2.
A new set of circumstances brought up the need for deploying the 64bit client as well (not on the same PC naturally). Put aside any advice about not using Office 64bit and the fact that Microsoft recommends against it (I already tried speaking against it to no avail). When trying to use the same methods as the 32bit client I attempt to go through the following steps:
- Extract:
- CRM2013-Client-ENU-amd64.exe (base)
- CRM2013-Client-KB2941390-ENU-amd64.exe (client SP1)
- CRM2013-Client-KB2963850-ENU-amd64.exe (client SP1 UR2)
- CRM2013-Mui-KB2941390-ENU-amd64.exe (English MUI SP1)
- CRM2013-Mui-KB2963850-ENU-amd64.exe (English MUI SP1 UR2)
- Update Client.msi to SP1.
- Update Client.msi to SP1 UR2.
- Update MUISetup_1033_amd64.msi to SP1.
- Update MUISetup_1033_amd64.msi to SP1 UR2.
Steps 1-3 work just fine but then step 4 fails with the following error.
Source file not found: C:\Temp\Base\Server\LangPacks\1033\sql\6.0\Metadata\Xml\Account.xml. Verify that the file exists and that you can access it.
Indeed that folder does not exist because I am attempting to patch the client installation and not the server. The installation appears to be complaining about missing server folders that should not even exist in a client.
Trying to search for optional installation flags or parameters hasn't helped. Even running through a verbose log file of the installation brought no enlightenment about any possible options.
Solutions I would rather not implement:
- Manually creating the missing folder structure and files to avoid this error. There are hundreds of files in the missing folder structure.
- Apply the full English language pack to the base installation folder. Might work but complicates the solution and takes me to the land of unsupported installations.