Desktop Authority 9.2 - Desktop Authority Management Suite (DAMS) - Desktop Authority - Dell Community

Desktop Authority 9.2

Desktop Authority 9.2

This question is answered

DA 9.2 is not synchronizing the Computer and User files.  They do not match the master server.  Checked with admins and AD replication is working fine.  Anyone have any input?

Verified Answer
  • Hi Hdwrguy,

         The Administrative Service, which is installed on each server in the list in the server manager, reports back the list of file properties for both the Computer and User management files (along with date, time, size, hashes, etc..) back to the DA server (where you installed the management console to). The Manager Service running on the DA server then accepts that information and writes it to the database. When the server manager grid is refreshed, the file properties of the files listed in the database and the local files located in the replication source folder are compared to see if they match. If they do not match, you should see an exclamation mark which you can click on to see a brief explanation of the problem. Then you can click on the “more info” link within the exclamation dialog and you will then see a list of the specific files and their properties that don’t match both locally and remotely. To correct this issue, you can either copy the files manually from a location that has a good status or simply set that unsynchronized server as a replication target and see what happens when you either copy or replicate to the unsynchronized target. Either one of those actions should provide you with enough information to determine the source of the problem.

All Replies
  • Hi Hdwrguy,

         The Administrative Service, which is installed on each server in the list in the server manager, reports back the list of file properties for both the Computer and User management files (along with date, time, size, hashes, etc..) back to the DA server (where you installed the management console to). The Manager Service running on the DA server then accepts that information and writes it to the database. When the server manager grid is refreshed, the file properties of the files listed in the database and the local files located in the replication source folder are compared to see if they match. If they do not match, you should see an exclamation mark which you can click on to see a brief explanation of the problem. Then you can click on the “more info” link within the exclamation dialog and you will then see a list of the specific files and their properties that don’t match both locally and remotely. To correct this issue, you can either copy the files manually from a location that has a good status or simply set that unsynchronized server as a replication target and see what happens when you either copy or replicate to the unsynchronized target. Either one of those actions should provide you with enough information to determine the source of the problem.