SPProductUpdate and SPLanguagePack conflict

Details of the scenario you try and problem that is occurring: This was originally reported on the “SharePointDSC Best Practices and Gotchas Post” http://nikcharlebois.com/sharepoint-dsc-gotchas-and-best-practices/

In theory, it should be possible for someone to install, in order, a PU, a Language specific patch, and then run the config wizard. That scenario works just fine if done manually. However, with the SPDSC module, if you specify two SPProductUpdate blocks in a row, and then call the SPConfigWizard, it will skip over the second one because of the way we use B2B and will throw the following message:

Write-Verbose -Message ("An upgrade is pending. " + ` “To prevent a possible loop, the install will be skipped”)

If this can be done manually, then we should look at having the DSC module allow it as well, given that Language specific patches are now separate from the main CU/PU.

The DSC configuration that is using the resource: N/A

Version of the Operating System and PowerShell the DSC Target Node is running: Win 2016/WMF 5.1

Version of the DSC module you’re using: 1.9.0.0

[NikCharlebois]

Ok, I’ve got the code written to obtain the GUID and will commit it into the Util module. Great catch Colombo @ykuijs

[andikrueger]

I’m done with integration testing on SharePoint Server 2016 - Why are SharePoint update THAT time consuming?

The updated mechanism does a great job. It’s possible to leave all prior SPProductUpdates and SPInstallLanguagePack Resources in a configuration 😃

Please find attached my test configuration and the log of the DSC configuration. SPProductUpdateTestConfiguration.txt log.txt