Microsoft Applocker/ Windows Defender is causing GroupShare installer to fail when “Calling Chef” with error "System.Exception: ConfigureChefDeployments returned with code 1"

Article Number:000016202 | Last Updated:6/14/2021 9:52 AM

Scope/Environment

Symptoms/Context

The following error is returned at the installer stage “Configuring System”:

System.Exception: ConfigureChefDeployments returned with code 1 at Sdl.Distribution.ServerInstall.Wizard.PostInstallStep.b__3_1(Object sender, RunWorkerCompletedEventArgs args) at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e) at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) at System.Windows.Threading.DispatcherOperation.InvokeImpl()

User-added image

The installation log is not returning any “deeper” details beside at the last step, where it tries to execute the chefsolo.bat.

Resolution

Add exception to AppLocker:

An AppLocker rule needs to be defined to allow the user group (in which the current user is logged on to the system) is allowed to execute .ps1, .bat, .cmd, .vbs, and .js file formats.

Details on how to define exceptions, please find in the following Microsoft article: Add exceptions for an AppLocker rule

On other instances, removing Windows Defender from the application server during installation was the effective solution.

Root Cause

The Microsoft AppLocker/ Windows Defender is blocking the execution of relevant ChefSolo files that are required to be executed to allow the installation/configuration of all the GroupShare components.

Reference

Send Article Feedback