Recent builds added an MCC for syncing a client with the server. It's not silent, because it may need to reload the library which is a drastic action. (stops playback, shows home)
Well, I presume that said mcc command must be triggered somehow by the user. I implemented the command using a theater view root item.
In other words, the command could be silent because it is triggered by the user. Likewise, if an administrator triggers a reload of the clients
from the server she is probably in control of the network anyways...
I do agree with Mr. Haugen that the update seems drastic since the entire library must be reloaded. Ideally, discrete library operations on the server should be replicated on the client (and vice versa). But that implies, I should think, a more extensive software job.