Share via

Detection method for Office MSP file or any MSP file.

  • Article

Question

Friday, September 25, 2015 2:11 PM

HI,

I'm deploying an MSP file for Office 2013 after deploying Office. It has been created with the OCT tool. For the first deployment is fine but, which detection method should I use to see if the MSP has been applied already or not? I couldn't find a specific registry key. Generally, where can I find a registry for MSP files?

Thank you very much in advance,

Pablo

All replies (8)

Thursday, October 1, 2015 1:37 PM âś…Answered

Thank you all for helping!

Here our solution

  1. After creating the MSP file right-click on it.
  2. Select "Properties", "Details" tab.
  3. Look for "Revision number"
  4. Copy the number including brackets.
  5. Do not edit the MSP file anymore, otherwise a new revision number will be created.
  6. In SCCM open the application and under "Detection Method" choose "Registry key"
  7. Value: Count
  8. Data Type: Integer
  9. Hive HLM, Key: SOFTWARE\Microsoft\Office\15.0\User Settings\xxxxxxxxxxxxxxx}
  10. Replace {xxxxxxxxxxxxxxx}with the Revision number you copied before.
  11. Once more, if you edit the MSP file a new revision number will be created, thus you will have to copy it once more and repeat step 10.
  12. Works for us...and thank you once more

Friday, September 25, 2015 5:48 PM

Have a look in 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Patches

You could also just look for a specific registry key that the patch creates, any capture tool, procmon will show you the info.

Friday, September 25, 2015 6:08 PM

It is also possible to pick a file that the MSP updates (usually the KB lists the files being updated and their version number) and use that as detection of the MSP applying.

James

Friday, September 25, 2015 6:32 PM

You can actually put the MSP File directly into the "Updates" Folder of your Office 2013 Source. All MSP Files in this Folder are getting auto applied during the Office Installation.

Simon Dettling | Twitter

My posts are provided 'AS IS' without warranty of any kind.

Tuesday, September 29, 2015 3:09 AM | 1 vote

Setup will copy the MSP to c:\windows\installer as well as creating a registry entry in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Patches although file names are not consistent so that's probably not a good detection method. 

I guess, you could detect at the file level for something that your OCT MSP has customized, an app that it installed or changed for eg. 

HughMc

Thursday, October 1, 2015 1:38 PM

Thank you, I found a solution.

Thursday, October 1, 2015 1:39 PM | 1 vote

Thank you, I found a solution.

Thursday, October 1, 2015 1:45 PM

This is correct. The problem is that we just have three different type of Office users, for instance one group without Outlook, another without Access and the third one with all modules plus some proofing tools.  With three different MSP files, putting one MSP in the update folder every time we have to deploy to adifferent group is not very convenient.

Thank you anyway