Submit a ticketCall us
Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > Serv-U - Knowledgebase Articles > Configure Serv-U and FTP Voyager Scheduler to access network files or folders

Configure Serv-U and FTP Voyager Scheduler to access network files or folders

Updated March 31, 2017


The following instructions describe how to switch these services from LocalSystem to another Windows user so Serv-U or FTP Voyager Scheduler can access remote shares. Any Serv-U deployment that accesses remote Windows shares, NAS, SAMBA shares, or mapped drives requires these instructions.



All Serv-U versions


Any Serv-U deployment that accesses remote Windows shares, NAS, SAMBA shares, or mapped drives requires these instructions.

Note: If FTP Voyager is only used to access remote shares through its side by side interactive mode, the following procedure is no longer required.

Modify the Run As Service Account (Recommended)

To configure Serv-U/FTP Voyager Scheduler, run under a user account that has network privileges to the UNC path. In an Active Directory environment, this user may be a member of the Domain Admins group. In a Windows Workgroup, this will be a user who exists on both the local machine and the remote network resource, with the same user name and password on both machines.

To change the user account under which a RhinoSoft service runs:

  1. Navigate to the Control Panel > Administrative Tools > Services menu.
  2. Right-click either the Serv-U File Server or FTP Voyager Scheduler, and select Properties.
  3. Click Log on tab and select This account radio.
  4. Click Browse to select the correct user account in your domain. In Windows Active Directory, the user account will be in the form of username@domainname.ext, and in a workgroup this will be in the form of SERVERNAME\username.

    Selecting the log on user

  5. Once the correct user is displayed, click OK to save the settings.
    Note: If running in a workgroup, check if the same account exists remotely on the network server.
  6. Right-click Service and restart.

If you encounter an error when starting the service, you are encountering a user account issue, which will need to be diagnosed within the properties of the Serv-U File Server/FTP Voyager Scheduler service. Avoid this by using the Check Name option to make sure that your entry is correct.

Note: Windows System Services cannot recognize mapped network drives by letter. Any network location specified must be placed in UNC format (\\server\share).


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Run Service Application In Foreground (Fallback)

If it is not possible to run Serv-U or FTP Voyager Scheduler as a service under an administrative user account, run the application in the foreground instead of as a service. Do this by right-clicking on the related Tray Monitor icon and uncheck Start XXX as Service. This prevents the application to stop running as a service and restart running in the foreground, using the account privileges of the user who started the application.

Note: The application must be left running in the foreground and the user cannot log out of the server without shutting down the application. RhinoSoft recommends using the run as instructions instead in almost every possible situation.



UAC Blocks Network Drives

In Windows Vista, Windows 7, Windows 8, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012 User Account Control (UAC, an extra security mechanism) prevents network services from accessing mapped network drives even if they are running as an application. There is no way to bypass this behavior in UAC. To resolve this, UAC must be disabled using the steps in this Windows User Account Control (UAC).



Last modified