Open Yvand opened 3 years ago
Hi @Yvand, thanks for submitting this.
The problem with adding the -Restart
into the resource is that it will cause the resource to restart the machine - which isn't recommended - it disrupts the DSC LCM. Instead using the $global:DSCMachineStatus = 1
is the recommended approach.
Have you configured your LCM to allow reboots?
Have you tried adding a PendingReboot after the computer rename?
Hi @PlagueHO,
Details of the scenario you tried and the problem that is occurring
This problem happens only with the SharePoint public images of Azure: When resource "Computer" joins the VM to the domain, this error systematically occurs just after resource completes: "The WS-Management service cannot process the request. The WMI service or the WMI provider returned an unknown error: HRESULT 0x80041033"
Verbose logs showing the problem
Notice that the error is not in resource Computer, but just after:
Suggested solution to the issue
I found a dirty workaround that works 90% of the time: I edited function Set-TargetResource in DSC_Computer.psm1 to add the following if this is a SharePoint VM:
The DSC configuration that is used to reproduce the issue (as detailed as possible)
It repro every time, merely by joining an AD domain:
I made an az cli script that creates a DC and a SP VM and fully repro from scratch:
The operating system the target node is running
It reproduces on SharePoint 2019/2016/2013 public images of Azure. Below is the output for the SharePoint 2019 VM:
Version and build of PowerShell the target node is running
Version of the DSC module that was used ('dev' if using current dev branch)
ComputerManagementDsc 8.4.0