ACC-VC File-Based Discovery conf files won't sync to MID Servers or be able to be used by the checks on Domain Separated MID ServersDescriptionACC-VC File-Based Discovery conf files won't sync to MID Servers or be able to be used by the checks on Domain Separated MID Servers, because these 2 records have sys_domain set as 'sn_acc_vis_content' instead of 'global'. Note: There is another problem similar to this for the SAMMeteringConfig.json file. See PRB1906947 ACC-VC SAM check conf file won't sync to MID Servers or be able to be used by the checks on Domain Separated MID ServersSteps to Reproduce On a domain separated instance, with a MID server in a leaf domainInstall ACC-VC 1.1.0 which adds File based discoveryCheck the agent\static\acc_config folder on the mid server. Actual behaviourThese 2 files will not have synched to the mid server:AgentFBDUnixParameters.json/sn_agent_configuration_file.do?sys_id=16df34c43b229610e5cfc337f4e45acbAgentFBDWindowsParameters.json/sn_agent_configuration_file.do?sys_id=16df34c43b229610e5cfc337f4e45acb which means the File-based Discovery background check won't have them, and won't work. Expected behaviour:These records should be sys_domain=global, should sync, and so can be used by the check. WorkaroundThis problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available. The workaround is to change the domain value of the 2 records from "sn_acc_vis_content" to "global": AgentFBDUnixParameters.json/sn_agent_configuration_file.do?sys_id=16df34c43b229610e5cfc337f4e45acbAgentFBDWindowsParameters.json/sn_agent_configuration_file.do?sys_id=16df34c43b229610e5cfc337f4e45acb See PRB1906947 ACC-VC SAM check conf file won't sync to MID Servers or be able to be used by the checks on Domain Separated MID Servers for an update set covering all 3 records.Related Problem: PRB1857660