The difference between the two solutions is minimal (and the choice between the two is usually to be determined only in more specific situations), except for the fact that impersonating allows you to continue to see the AutoRun window of the backups in the primary session. The authentication issue has an easy solution since Iperius allows one to install the service using a specific account and to impersonate a certain user account for backup operations. In this case, let’s make sure we have entered the complete network path (example: Īsackup) and not a mapped network drive. In fact, a Windows service cannot access mapped network drives, simply because they do not exist in the service session (but are automatically reconnected, and therefore created, only at user logon). In this case, scheduled backups, since they are run by the service, will also run using this user account, which generally does not have access to network paths, nor may it have the necessary privileges to access certain folders.Īnother possible cause is the use of mapped network drives instead of the full network path. When Iperius is installed as a Windows service and the default settings are left as they are, the service will be started using the local system account, or SYSTEM. The cause of this problem is very simple. These errors generally occur only when the backup is run in the automatic mode according to a schedule, while backups run manually complete successfully.

A common problem that one can encounter when installing Iperius Backup as a service and setting up a schedule for it is to encounter errors accessing network paths.

Iperius Backup Full 7.8.6 free download