Xackup cannot access my Mapped Network drive

By default, the Xackup Service runs under the LocalSystem account.

Windows services running under the LocalSystem account typically don't have access to network resources, including mapped drives. This limitation is due to the security context in which services run.

Here are a few potential reasons why LocalSystem might not see your mapped drives:

1. Security Context: Services running as LocalSystem have a very high level of privileges, but they don't have the same network access as a user account. Mapped drives are typically associated with user sessions, and LocalSystem doesn't have the same network access as a user logged into the system.

2. 
   

3. Session Isolation: Mapped drives are often associated with user sessions, and services running as LocalSystem run in a different session with limited access to the desktop and user-specific resources.

4. 
   

5. Drive Mapping Scope: Drive mappings are user-specific and are created in the context of a user session. LocalSystem, being a system account, doesn't have access to these user-specific mappings.

If you need a service to access network resources, consider running the service under a specific user account that has the necessary network permissions. Be cautious with this approach and ensure that the user account used for the service has the minimum required privileges to perform its tasks.

Alternatively, you can try accessing network resources using UNC paths directly instead of relying on mapped drives. UNC paths (e.g., \\server\share\) are not tied to a specific user session and might be accessible by services running under LocalSystem.

Remember that the choice of approach depends on your specific use case and security requirements. Always follow the principle of least privilege and ensure that your application or service has the minimum required permissions to perform its tasks.