dennisl68-castra
dennisl68-castra
I recently discovered the tracing feature of the module xDscDiagnostics. Using `Get-xDscOperation | select -ExpandProperty Allevents | ft -Wrap` on a DC brings out the same issue... ~~~~ PS C:\Users\Administrator>...
Using the KeyName `ADKDSKey` made the issue go away :)
@IlleNilsson Could you please have a look at the failed Unit tests? They don't seem very hard to fix...
@IlleNilsson Perhaps you could review the failed Unit Tests in this Pull Request (look at the Details of each failed stage of Review requested) and remedy the failures of your...
@johlju The build isn't available anymore so I can't review the failed tests... I'll try to find some of the issues by hand and then pushing the changes to trigger...
> If you can add unit tests to the changes in the PR so they changes is being tested. That would help as I need that to merge the code....
As we will drop the use of xCluster, I will not pursue this Pull Request.
This would be handled in issue, 'Switch to CIM cmdlets #8'.
Since PoSH 7.1 is 99% compatbile with PoSH 5.1, it's a shame that the WMI-dependency still exists in this module... Why not just drop the WMI-support and move to a...
I've got the same issue (as listed by duplicate). PoSH 5.1 does load modules dynamically. Impot-Module is normally not a requirement as long as the module is stored in a...