Bug: WMF5 PullServer Configuration still accepts "IsComplianceServer" attribute
When provisioning a new PullServer using WMF5, the "IsComplianceServer = $true" can still be specified a a valid attribute in the configuration despite the service being replaced by the reporting server role.
It seems benign, however if this is done the resulting Pull Server will no longer work with ConfigurationNames and only work with ConfigurationID configured nodes. The process generates no errors, nodes will even state that registration of AgentID was successful, but clients will silently receive no files when they query for the appropriate <configurationname>.mof.
This makes for a very difficult bug to track down if someone were to adopt thier old WMF4 configuration to build a new Pull Server on WMF5.
Thank you for your feedback! We recognize that this adds confusion to the deployment of the WMF 5.0 pull server and are looking into a solution.