Group: Forum Members
Happy to help. As to why Reflect works the way it does, the answer to that probably lies in Reflect's history. The Edit Defaults > Network interface was added for Reflect V7. Prior to V7, scheduled tasks had to run as a specific user account; there was no option to run as SYSTEM. So in that case, even network destinations had to be accessible by that user account, unless alternate arrangements were made with a script. The problem with using "real" user accounts is that people would often use their own admin user account rather than creating a dedicated account for Reflect backups, but that meant that when they changed their Windows account password, their scheduled backups would break until they updated the stored password in Reflect. Reflect V7 adding support for running as SYSTEM solved that problem, but the SYSTEM account has no implicit access to network locations the way "real" user accounts can. So Reflect added this Edit Defaults > Network interface to allow credentials to be stored in order for network locations to be reachable even while the backup was running as SYSTEM.
Or maybe it's just because using Reflect to make backups OF network locations rather than backups TO network locations just isn't a common use case. For NAS shares hosted on a full server, you could of course install backup software directly on that server, and even many NAS appliances support built-in apps that can perform backups. In that case you wouldn't have to pull data across the network to your PC just to push it out from your PC to some other network location.
But if adding support for checking stored credentials when attempting to connect to a source would be valuable to you, then consider creating a thread to request that in the Wish List section of the forum. Macrium is much more responsive than most developers when it comes to bug reports and enhancement requests submitted from users.