Here is the information I could get released...
First it's important to note that a DLO Maintenance Server is only needed if you are implementing the Delta File Transmission option.
The DLO Maintenance Server deletes files that are no longer supposed to be saved in the Network Storage Location based on file retention settings. The DLO Maintenance Server gets the information as to what file revisions to groom based on a delta map maintained on the users desktop/laptop. The users desktops/laptops will communicate with the DLO Maintenance Server via MS RPC. If you use delta file transmission options the local user data folder must be enabled but can be set to maintain 0 (zero) versions. Ideally the maintenance server and network user data folder server will be the same system, but in cases where the network user data folder is not a Windows system that will not be possible. In those cases the DLO Maintenance Server will need to perform file IO via LAN to groom outdated file versions in the network user data folder. So there needs to be a fast, reliable connection between the DLO Maintenance Server and the server where the network user data folder is hosted if they are not the same system. The DLO Maintenance Server should also be robust enough to handle the computational tasks at times when file grooming will take place. A delta file transmission strategy could result in the need to maintain delta file data that contains previous file versions, that could have otherwise been groomed, as base files. This means it is possible that more file revisions than configured could be retained and available for restore operations.