Hi Daniel
Thank for your response
The particularity of Exchange, it is because some configurations are local on the server and other configuration are store in Active Directory. To be able to read, modify those configuration you need to have some rights in Exchange.
Example if you want to check some attribute about one mailboxDatasase you need to get-Malboxdatabase –SomeAttributs as example. (This information are store in AD). After, if the configuration has drift, DSC will call the Set Function in the Custom Resource and the set function will use the Exchange cmdlet set-MailboxDatabase –SomeAttributes XYZ to configure this setting as the initial configuration
The DSC cannot Read or Write the Exchange configuration because the LCM run as Local System Account on the Exchange Server et the LCM have no permission to access AD.
Exchange use the remote execution to pass the PowerShell cmdLet
Yes effectively if we don't find any solution with DSC, we have SCOM and we will pull the Exchange configuration with the SCOM and compare the configuration and if the configuration drift, another script will adjust the Drift with the initial configuration.
For now we prefer try to find a solution with DSC, if we can find some solution, because we have also other environments Hyper-V and other programs that we want to use with DSC
We have created many DSC Custom resources to install all Exchange prerequisite, because we need only local Administrator for that
Thank Alot