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 ServersDescriptionACC-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, because this records has sys_domain set as 'sn_acc_vis_content' instead of 'global'. Steps to Reproduce On a Domain Separated instance, install ACC-vC 1.3.0 or later (May 2025 release). This version removed the dependency on osquery, and changed the checks.Check the agent\static\acc_config folder on the mid server. Actual behaviour: This file will not have synched to the mid server:SAMMeteringConfig.json</sn_agent_configuration_file.do?sys_id=020cbe562b00ae104847f38f5e91bf6e which means the SAM Background Data collection ( Non OsqueryD ) check for software information, last usage information and total usage metering information of all the softwares 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. Changing the records to sys_domain=global will workaround the issue. Due to the complication that the records are in ACC-VC scope, but the attachments of those records are in Global scope, and Update Sets must be for 1 scope only, and there is also a business rule 'Prevent insert with no attachments' that deactivates the record if there is no attachment, applying a working via Update Sets is not going to be easy. Instead, as an admin user, follow these steps: Change your session's Application Scope to 'Agent Client Collector for Visibility Content'Open a list of the bad records:https://<instance name>.service-now.com/sn_agent_configuration_file_list.do?sysparm_query=sys_domain%3Dsn_acc_vis_contentExport that list as XML, to a fileDocs: Export data to XMLOpen that file in a text editor, and change every line like this:<sys_domain>sn_acc_vis_content</sys_domain>to this:<sys_domain>global</sys_domain>Save the file.The attached sn_agent_configuration_file (sys_domain=sn_acc_vis_content).xml has had the above steps done. Then...Import that modified XML file back into the instance. Docs: Import data from XMLImportant: That will have corrected the files, but now this will be treated as a customisation and those files will never be upgraded in future, unless you do...Open a list of the Customer Update record that just tracked that customisation:https://<instance name>.service-now.com/sys_update_xml_list.do?sysparm_query=GOTOnameSTARTSWITHsn_agent_configuration_file_&sysparm_view=Configure the List Layout to add the 'Replace on upgrade' column.Change the value of 'Replace on upgrade' from false to true.Related Problem: PRB1906947