RSOP not including LcmConfig (because it's static) about datum

[gaelcolas]

Yeah, by design. Can be suboptimal but not a lot of effort has been put in Get-DatumRsop.
In short, this function only lookup based on the Configurations pivot.

For a given node it resolves the array of configurations items from the 'configurations' key.
Then for each configuration, does a lookup of that config for that node and merge into the root node element.

So it builds the rsop by doing a Lookup foreach item in the configurations key, because that's the only thing we know (the pivot).

If we'd want to add the LCM configs, we ought to do something similar than what you can find in RootMetaMof.ps1:
Adding here the following...

$RSOPNode.Add('LcmConfig',@{})
'LcmConfig\Settings','LcmConfig\ConfigurationRepositoryShare','LcmConfig\ResourceRepositoryShare','LcmConfig\ConfigurationRepositoryWeb','LcmConfig\ResourceRepositoryWeb','LcmConfig\ReportServerWeb','LcmConfig\PartialConfiguration' | % { $KeyToAddToNode = Resolve-NodeProperty -PropertyPath $_ -DefaultValue $null; $RSOPNode.LcmConfig[$_] = $KeyToAddToNode;  }

This is rough and not tested, but illustrates the idea :)

[raandree]

Solved in b7da69d.