You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually every bit of config data is visible in the RSOP output. But the LCM settings are missing the pull server URI and the RegistrationKey which is in the Meta MOFs (so it does exist) but not in the RSOP.
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 rootnode 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...
Usually every bit of config data is visible in the RSOP output. But the LCM settings are missing the pull server URI and the RegistrationKey which is in the Meta MOFs (so it does exist) but not in the RSOP.
A repo is here: https://github.com/raandree/DatumTest
The RSOP output for node PreServer1
The meta.mof with the content that is missing in RSOP.
Is this by design or does something go wrong?
The text was updated successfully, but these errors were encountered: