Ftp客户端

开发平台：

Visual C++

Help-Admin-Strings.strings：源码内容

Specify the state (if applicable) in which the server or corporation is located.
Specify the 2-digit country code for the country in which the server or corporation is located.
Specify the password used to secure the private key.
Specify the full organization name.
Specify the common name of the certificate. The IP address or the Fully Qualified Domain Name (FQDN) that Users use to connect must be listed here. NOTE: If the Common Name is not the IP address or FQDN used by clients to connect, clients may be prompted that the certificate does not match the domain name they are connecting to.
Specify the business unit the server resides in.
Click the Create button to complete certificate creation.
::END
$SSL_CREATE_CERT_TXT$::
Serv-U creates 3 files using the provided information: A self-signed certificate (.crt) that can be used immediately on the server but isn't
authenticated by any known certificate authority, a certificate request (.csr) that can be provided to a certificate authority for authentication,
and a private key file (.key) that is used to secure both certificate files. It is extremely important that the private key be kept in a safe and
secure location. If your private key is compromised, then your certificate can be used by malicious individuals.
::END
$SSL_VIEW_CERT$=Viewing The Certificate
$SSL_VIEW_CERT_TXT$::
To view the SSL certificate once it is configured, click the View Certificate button. All identifying information about the
certificate, including the dates during which the certificate is valid, are displayed in a new dialog.
::END
$SSL_ADVANCED$=Advanced SSL Options
$SSL_ADVANCED_TXT$::
These advanced SSL options can only be configured at the Server level. All Domains inherit this behavior, which cannot be individually overridden.
Enable Low Security Ciphers - Checking this box enables low-security SSL ciphers to be used. Some older or international clients may not
support today's best SSL ciphers. Because these ciphers are considered insecure by today's computing standards, Serv-U does not accept these ciphers
by default.
Disable SSLv2 Support - There are several different versions of SSL supported by Serv-U. An older version, SSLv2, has documented security
weaknesses that make it less secure than SSLv3 and TLS. However, it may be necessary to support SSLv2 for compatibility with exported clients or
old client software. Checking this box disables support for the older SSLv2 protocol.
::END
$FIPS_MODE_HEADER$=FIPS Options
$FIPS_MODE_TXT$::
Enable FIPS 140-2 mode - FIPS 140-2 is a set of rigorously tested encryption specifications set by the National Institute of Standards and
Technology (NIST). Enabling FIPS 140-2 mode limits Serv-U to encryption algorithms certified to be FIPS 140-2 compliant and ensures the highest level
of security for encrypted connections.
::END
$SFTP_SETUP_HEADER$=SFTP (Secure File Transfer over SSH2)
$SFTP_SETUP_EXISTING$=Using An Existing Private Key
$SFTP_SETUP_EXISTING_LIST$::
Obtain a private key file.
Place the private key file in a secured directory in the server. Use the Browse button in Serv-U to select the file.
Enter the password for the private key file.
Click the Save button.
::END
$SFTP_SETUP_CREATE$=Creating A Private Key
$SFTP_SETUP_CREATE_LIST$::
Click the Create Private Key button.
Enter the name of the private key, (e.g., "MyDomain Key"), which is also used to name the storage file.
Enter the output path of the certificate, (e.g., C:Program FilesRhinoSoft.comServ-U).
Select the Key Type (default of DSA is preferred, but RSA is available).
Select the Key Length (default of 1024 bits provides best performance, 2048 bits is a good median, while 4096 bits provides best security).
Enter the password to use for securing the private key file.
::END
$SFTP_KEY_SETUP_HEADER$=SFTP (Secure File Transfer over SSH2) for Users and Groups
$SFTP_SETUP_EXISTING_PUBLIC$=Using An Existing Public Key
$SFTP_SETUP_EXISTING_LIST_PUBLIC$::
Obtain a public key file.
Place the public key file in a secured directory in the server. Use the Browse button in Serv-U to select the file.
Click the Save button.
::END
$SFTP_SETUP_CREATE_PAIR$=Creating A Key Pair
$SFTP_SETUP_CREATE_LIST_PAIR$::
Click the Create Key Pair button.
Enter the name of the key pair, (e.g., "MyKey"), which is also used to name the storage file.
Enter the output directory of the certificate, (e.g., C:Program FilesRhinoSoft.comServ-U).
Select the Key Type (default of DSA is preferred, but RSA is available).
Select the Key Length (default of 1024 bits provides best performance, 2048 bits is a good median, while 4096 bits provides best security).
Enter the password to use for securing the key file.
::END
$SFTP_SETUP_CIPHER_MAC$=SSH Ciphers and MACs
$SFTP_SETUP_CIPHER_MAC_TXT$::
By default, all supported SSH ciphers and MACs (Message Authentication Codes) are enabled for use by the Server. If your specific security needs dictate that
only certain ciphers or MACs can be used, you can individually disable unwanted ciphers and MACs by unchecking the appropriate boxes.
::END
$SD_SESSIONS_HEADER$=Server & Domain Sessions
$SD_SESSIONS_TXT$::
The Server & Domain Session tab displays the current File Server session activity. When viewing the Sessions page from the Server, all connected sessions
from all Domains are displayed. When viewed while administering a Domain, only that Domain's current sessions are displayed. From this page, an overall
picture of the current activity on the File Server can be seen. In addition, individual sessions can be viewed including their current status, connection
state, and transfer information.
To view the detailed information on a specific session, select the session. The Active Session Information group is populated with the
details of the currently highlighted session. This information is frequently updated to provide you with an accurate and up-to-date snapshot of that session's
activities.
Depending upon the type of connection made by that session, (e.g., FTP, HTTP, or SFTP), certain additional functions are available.
::END
$SD_SESSIONS_DISCONNECT$=Disconnect
$SD_SESSIONS_DISCONNECT_TXT$::
Any type of session can be disconnected at any time by clicking the Disconnect button. Clicking the button brings up another dialog with
additional options for how the disconnect should be performed. There are 3 types of disconnect options available:
::END
$SD_SESSIONS_DISCONNECT_LIST$::
Disconnect - Immediately disconnects the session. Another session can be immediately established by the disconnected client. This is also known as "kicking" the user.
Disconnect and ban IP - Immediately disconnects the session and bans their IP address for the specified number of minutes, preventing them from immediately reconnecting.
Disconnect and block IP permanently - Immediately disconnects the session and adds a deny IP access rule for their IP address, preventing them from ever reconnecting from the same IP address.
::END
$SD_SESSIONS_DISCONNECT_TXT2$::
When disconnecting a session from the Server Session view, an additional option is available called Apply IP rule to. This combo box allows
you to select where you would like the temporary or permanent IP ban to be applied - for the entire Server or just the Domain the session is connected to.
In addition to disconnecting the session, the User account in use by the session can also be disabled by checking the box labeled Disable user account.
If the current session is using the FTP protocol, a message can be sent to the user before disconnecting them by typing it in the box labeled Message
to user. This option is not available for HTTP or SFTP sessions as neither protocol defines a method for chatting with users.
::END
$SD_SESSIONS_SPY$=Spy & Chat
$SD_SESSIONS_SPY_TXT$::
Any type of session can be spied on by clicking the Spy & Chat button or double-clicking on a session from the list. Spying on a user
displays all the detailed information normally visible by highlighting the session, but also includes a complete copy of the session's log since it first
connected to the File Server. This allows an administrator to browse the log and view all actions taken by the session's user.
If the current session is using the FTP protocol, additional options are available for chatting with the user. The Chat group shows all
messages sent to and received from the session since beginning to "spy" on the session. To send a message to the session, enter the message text in the box
labeled Message Content and click the Send button. When a message is received from the session, it is automatically
displayed here.
NOTE: Not all FTP clients support chatting with system administrators. The command used to send a message to the server is SITE MSG. In
order for a client to receive messages, the client application must be capable of receiving unsolicited responses from the server (instead of just discarding
them).
::END
$SD_SESSIONS_BROADCAST$=Broadcast
$SD_SESSIONS_BROADCAST_TXT$::
A message can be sent to all currently connected FTP sessions by clicking the Broadcast button. Sending a message via broadcast is equivalent
to opening the Spy & Chat dialog to each individual FTP session and sending it a chat message.
::END
$SD_SESSIONS_ABORT$=Abort
$SD_SESSIONS_ABORT_TXT$::
If a session is performing a file transfer, the file transfer can be terminated without disconnecting the session by clicking the Abort button.
After confirming the abort command, the current file transfer for that session is terminated by the Server. Some clients, especially FTP and SFTP clients, may
automatically restart the aborted transfer making it appear that the abort failed. If this is the case, try Disconnecting the session instead.
::END
$SD_STATS_HEADER$=Server & Domain Statistics
$SD_STATS_TXT$::
The Server & Domain Statistics pages show detailed statistics on the use of the Server for use in benchmarking and records keeping. Statistics viewed at the
Server level are an aggregate of those accumulated by all Domains on the Server. Statistics viewed for an individual Domain are for that Domain only. The
displayed information includes:
::END
$SD_UP_TIME$=Up Time
$SD_UP_TIME_TXT$::
The amount of time since the File Server was started if viewing Server Statistics, or the amount of time since the Domain came online if viewing a specific
Domain's statistics.
::END
$SD_STATS_SESSION$=Session Statistics
$SD_STATS_SESSION_CURRENT$=Current Sessions
$SD_STATS_SESSION_CURRENT_TXT$::
The number of sessions currently connected.
::END
$SD_STATS_SESSION_DAY$=24 Hrs Sessions
$SD_STATS_SESSION_DAY_TXT$::
The number of sessions that have connected in the past 24 hours.
::END
$SD_STATS_SESSION_TOTAL$=Total Sessions
$SD_STATS_SESSION_TOTAL_TXT$::
The total number of sessions that have connected since being placed online.
::END
$SD_STATS_SESSION_MAX$=Highest Num Sessions
$SD_STATS_SESSION_MAX_TXT$::
The highest number of concurrent sessions that has been recorded since being placed online.
::END
$SD_STATS_SESSION_AVG$=Average Session Length
$SD_STATS_SESSION_AVG_TXT$::
The average length of time a session has remained connected.
::END
$SD_STATS_SESSION_LONGEST$=Longest Session
$SD_STATS_SESSION_LONGEST_TXT$::
The longest recorded time for a session.
::END
$SD_STATS_LOGIN$=Login Statistics
$SD_STATS_LOGIN_TXT$::
These statistics can apply to either a domain or the entire server depending on the statistics currently being viewed.
Login statistics differ from session statistics because they apply to a login (providing a login ID and password)
as opposed to connecting and disconnection.
::END
$SD_STATS_LOGINS$=Logins
$SD_STATS_LOGINS_TXT$::
The total number of successful logins.
::END
$SD_STATS_LOGOUTS$=Logouts
$SD_STATS_LOGOUTS_TXT$::
The total number of logouts.
::END
$SD_STATS_CURRENT_LOGINS$=Currently Logged In
$SD_STATS_CURRENT_LOGINS_TXT$::
The number of sessions currently logged in.
::END
$SD_STATS_MOST_LOGINS$=Most Concurrent Logins
$SD_STATS_MOST_LOGINS_TXT$::
The highest number of simultaneously logged in sessions.
::END
$SD_STATS_LAST_LOGIN$=Last Login Time
$SD_STATS_LAST_LOGIN_TXT$::
The last recorded valid login time (not the last time a connection was made).
::END
$SD_STATS_LAST_LOGOUT$=Last Logout Time
$SD_STATS_LAST_LOGOUT_TXT$::
The last recorded valid logout time.
::END
$SD_STATS_AVERAGE_LOGIN$=Average Duration Logged In
$SD_STATS_AVERAGE_LOGIN_TXT$::
The average login time for all sessions.
::END
$SD_STATS_LONGEST_LOGIN$=Longest Duration Logged In
$SD_STATS_LONGEST_LOGIN_TXT$::
The longest amount of time a session was logged in.
::END
$SD_STATS_SHORTEST_LOGIN$=Shortest Login Duration Seconds
$SD_STATS_SHORTEST_LOGIN_TXT$::
The shortest amount of time a session was logged in.
::END
$SD_STATS_TRANSFER$=Transfer Statistics
$SD_STATS_TRANSFER_DL_SPEED$=Download Speed
$SD_STATS_TRANSFER_DL_SPEED_TXT$::
Cumulative download bandwidth being currently being used.
::END
$SD_STATS_TRANSFER_UL_SPEED$=Upload Speed
$SD_STATS_TRANSFER_UL_SPEED_TXT$::
Cumulative upload bandwidth being currently being used.
::END
$SD_STATS_TRANSFER_AVG_DL_SPEED$=Average Download Speed
$SD_STATS_TRANSFER_AVG_DL_SPEED_TXT$::
The average download bandwidth used since being placed online.
::END
$SD_STATS_TRANSFER_AVG_UL_SPEED$=Average Upload Speed
$SD_STATS_TRANSFER_AVG_UL_SPEED_TXT$::
The average upload bandwidth used since being placed online.
::END
$SD_STATS_TRANSFER_DL$=Downloaded
$SD_STATS_TRANSFER_DL_TXT$::
The total amount of data, and number of files, downloaded since being placed online.
::END
$SD_STATS_TRANSFER_UL$=Uploaded
$SD_STATS_TRANSFER_UL_TXT$::
The total amount of data, and number of files, uploaded since being placed online.
::END
$SD_STATS_SAVE$=Save Statistics
$SD_STATS_SAVE_TXT$::
User and group statistics can be saved directly to a CSV file for programatic analysis and review. In order to save statistics to a file, first select the User
or Group you wish to generate a statistics file for and then click the "Save Statistics" button on the bottom of the page.
::END
$UG_STATS_HEADER$=User & Group Statistics
$UG_STATS_TXT$::
The User & Group Statistics pages show detailed statistics based on individual user or group activity. Statistics viewed for a user or group are for that user or group only. The
displayed information includes:
::END
$UG_STATS_SESSION$=Session Statistics
$UG_STATS_SESSION_CURRENT$=Current Sessions
$UG_STATS_SESSION_CURRENT_TXT$::
The number of sessions currently connected.
::END
$UG_STATS_SESSION_DAY$=24 Hrs Sessions
$UG_STATS_SESSION_DAY_TXT$::
The number of sessions that have connected in the past 24 hours.
::END
$UG_STATS_SESSION_TOTAL$=Total Sessions
$UG_STATS_SESSION_TOTAL_TXT$::
The total number of sessions that have connected since being placed online.
::END
$UG_STATS_SESSION_MAX$=Highest Num Sessions
$UG_STATS_SESSION_MAX_TXT$::
The highest number of concurrent sessions that has been recorded since being placed online.
::END
$UG_STATS_SESSION_AVG$=Average Session Length
$UG_STATS_SESSION_AVG_TXT$::
The average length of time a session has remained connected.
::END
$UG_STATS_SESSION_LONGEST$=Longest Session
$UG_STATS_SESSION_LONGEST_TXT$::
The longest recorded time for a session.
::END
$UG_STATS_LOGIN$=Login Statistics
$UG_STATS_LOGIN_TXT$::
These statistics can apply to either a user or a group of users depending on the statistics currently being viewed.
Login statistics differ from session statistics because they apply to a login (providing a login ID and password)
as opposed to connecting and disconnection.
::END
$UG_STATS_LOGINS$=Logins
$UG_STATS_LOGINS_TXT$::
The total number of successful logins.
::END
$UG_STATS_LOGOUTS$=Logouts
$UG_STATS_LOGOUTS_TXT$::
The total number of logouts.
::END
$UG_STATS_CURRENT_LOGINS$=Currently Logged In
$UG_STATS_CURRENT_LOGINS_TXT$::
The number of sessions currently logged in.
::END
$UG_STATS_MOST_LOGINS$=Most Concurrent Logins
$UG_STATS_MOST_LOGINS_TXT$::
The highest number of simultaneously logged in sessions.
::END
$UG_STATS_LAST_LOGIN$=Last Login Time
$UG_STATS_LAST_LOGIN_TXT$::
The last recorded valid login time (not the last time a connection was made).
::END
$UG_STATS_LAST_LOGOUT$=Last Logout Time
$UG_STATS_LAST_LOGOUT_TXT$::
The last recorded valid logout time.
::END
$UG_STATS_AVERAGE_LOGIN$=Average Duration Logged In
$UG_STATS_AVERAGE_LOGIN_TXT$::
The average login time for all sessions.
::END
$UG_STATS_LONGEST_LOGIN$=Longest Duration Logged In
$UG_STATS_LONGEST_LOGIN_TXT$::
The longest amount of time a session was logged in.
::END
$UG_STATS_SHORTEST_LOGIN$=Shortest Login Duration Seconds
$UG_STATS_SHORTEST_LOGIN_TXT$::
The shortest amount of time a session was logged in.
::END
$UG_STATS_TRANSFER$=Transfer Statistics
$UG_STATS_TRANSFER_DL_SPEED$=Download Speed
$UG_STATS_TRANSFER_DL_SPEED_TXT$::
Cumulative download bandwidth being currently being used.
::END
$UG_STATS_TRANSFER_UL_SPEED$=Upload Speed
$UG_STATS_TRANSFER_UL_SPEED_TXT$::
Cumulative upload bandwidth being currently being used.
::END
$UG_STATS_TRANSFER_AVG_DL_SPEED$=Average Download Speed
$UG_STATS_TRANSFER_AVG_DL_SPEED_TXT$::
The average download bandwidth used since being placed online.
::END
$UG_STATS_TRANSFER_AVG_UL_SPEED$=Average Upload Speed
$UG_STATS_TRANSFER_AVG_UL_SPEED_TXT$::
The average upload bandwidth used since being placed online.
::END
$UG_STATS_TRANSFER_DL$=Downloaded
$UG_STATS_TRANSFER_DL_TXT$::
The total amount of data, and number of files, downloaded since being placed online.
::END
$UG_STATS_TRANSFER_UL$=Uploaded
$UG_STATS_TRANSFER_UL_TXT$::
The total amount of data, and number of files, uploaded since being placed online.
::END
$SD_LOG$=Server & Domain Log
$SD_LOG_TXT$::
The Server & Domain Log tab shows logged activity for the Server or Domain.
The Server Log shows File Server startup, configuration, and shutdown information. It does not show Domain activity information. To activity logs, view
the appropriate Domain's log instead. In addition to status information about libraries, licensing, and the current build that is logged when the File Server
is first starts, the Server Log also contains information about all Domain listener status, Universal Plug-and-Play (UPnP) status information, and PASV port
range status. The information contained in the Server Log is also saved to a text file located in the installation directory that is named
Serv-U-StartupLog.txt. This file is replaced each time the Serv-U File Server is started.
The Domain Log contains information about and activity pertaining to the currently administered Domain only. This includes the status of the Domain's listeners
and any configured activity log information. For more information on the types of activity information that be placed in the Domain Log, see the Help section
entitled $LINK_HELP_LOG_SETTINGS$.
Information contained in the log can be highlighted by clicking and dragging the mouse cursor over the desired portion of the log. Once highlighted, the
selected portion can be copied to the clipboard.
::END
$SD_LOG_FREEZE$=Freeze Log
$SD_LOG_FREEZE_TXT$::
Check this box to temporarily pause refreshing of the log. This is useful on busy systems so a certain section of the log can be highlighted and copied
before it is scrolled out of view. Once finished, uncheck the box to resume automatic updating of the log.
::END
$SD_LOG_SELECT_ALL$=Select All
$SD_LOG_SELECT_ALL_TXT$::
Clicking this button automatically freezes the log and highlights all currently displayed log information so that it can be copied to the clipboard.
::END
$SD_LOG_CLEAR$=Clear Log
$SD_LOG_CLEAR_TXT$::
When the log has become too large for you to view at once, click this button to erase the currently displayed log information. Only log information received
after clicking the button is displayed.
::END
$SD_LOG_LEGEND$=Legend
$SD_LOG_LEGEND_TXT$::
To make viewing the different components of the log easier, each different type of logged message is color-coded for quick identification. Clicking this
shows the legend in a draggable dialog. Drag the legend dialog to a convenient location so it can be used for reference while browsing the log.
::END
$SD_LOG_FILTER$=Filter Log
$SD_LOG_FILTER_TXT$::
To quickly find and read through specific sections of the log, it can be filtered based upon a search string. Clicking this button brings up the Filter Log
dialog. Providing a search string and clicking the Filter button refreshes the log to only display log entries containing the search string.
To view the entire contents of the log again, open the Filter Log dialog and click the Reset button.
::END
$SD_LOG_DOWNLOAD$=Download Log
$SD_LOG_DOWNLOAD_TXT$::
To download the full log file from Serv-U, click the "Download Log" button. If you have permission to download the file your web browser will prompt you to
choose a location to save the file, or begin downloading the file automatically.
::END
$DOMAIN_OVERVIEW_HEADER$=Domain Overview
$DOMAIN_OVERVIEW$::
At the core of the Serv-U File Server is the Serv-U Domain. At the most basic level, a Serv-U Domain is set of user accounts and listeners that allow Users to
connect to the Server to access files and folders. Serv-U Domains can also be configured further to restrict access based on IP address, limit bandwidth usage,
enforce transfer quotas, and more. Virtually every settings available at the Server level can be overridden for each individual domain. Careful advanced
planning allows you to specify an acceptable level of default options at the Server level to minimize the amount of configuration required for a Domain.
Serv-U can support any number of Domains on the File Server. Domains can share listeners, or they can each be hosted on a unique IP address if the system has
multiple IP addresses. However, the maximum number of Domains that can be created on an installation is dictated by the license. For more information on the
different Editions of Serv-U, see the Help documentation on $LINK_HELP_EDITIONS$.
When running a new installation of the Serv-U File Server for the first time, you are prompted to create your first Domain using the New Domain Wizard. Follow
the instructions on each page of the wizard to get your first Domain created. For more information, see the $LINK_HELP_GUIDE$.
::END
$DOMAIN_MANAGING$=Managing Domains
$DOMAIN_MANAGING_TXT$::
The Domain currently being managed is always displayed in the header of each page next to "Managing". There are several ways in which the active Domain can
be changed. From the console page of the Serv-U Management Console, the Manage Domain button brings up a list of the Domains available on
the File Server. Double-click a Domain or highlight one and click the Select button to make that Domain active. The Domain list is also
available from any Domain configuration page by clicking the Change Domain button found in the footer of the page.
If supported by your license, you can create another new Domain at any time by clicking the New Domain button on the console page. This
button is also directly available from the aforementioned Domain dialog containing the list of available Domains. After changing the active Domain, the
current page automatically reloads to reflect the new active Domain's settings.
The Delete button found on the Domain list dialog immediately deletes a Domain and all of its Users and Groups. This action cannot be undone.
::END
$DOMAIN_NAME_DESCRIPTION_HEADER$=Domain Name & Description
$EDITING_NAME_DESCRIPTION$::
Each Domain must be uniquely identified with a Domain Name. If a name is provided that is not unique, an error message is shown indicating
that a unique name is required for each Domain. The Domain Name is used purely for administrative purposes and is not visible or accessible
to Users.
In addition, each Domain can have additional descriptive information associated with it through the Description. Like the Domain
Name, the Description text is also only available to users with administrative access. This field is useful for describing the
purpose of the domain or summarizing the resources made available by the Domain's existence on the File Server.
Domains can be temporarily disabled by unchecking the Enable domain checkbox. While disabled, the Domain is completely inaccessible to all
Users. The Domain still exists on the File Server, all settings are preserved, and it can still be administered while it is disabled. To make the Domain
accessible to Users again, check the Enable domain checkbox.
After making changes to any of the above Domain settings, click the Save button to apply the changes.
::END
$DOMAIN_INFO_HOMEDIR$=Domain Home Directory
$DOMAIN_INFO_HOMEDIR_TXT$::
System Administrators can limit the disk space available to a Domain by configuring a home directory for the Domain and specifying a maximum size. The
Domain's home directory does not affect User directory access rules, nor does it restrict the paths that are available to a User in any way. However,
in order to calculate the amount of disk space in use by a Domain, Serv-U must know the root directory under which it expects all Domain files to be stored.
To specify the Domain home directory, enter a path in the field labeled Domain Home Directory. The Browse button can also
be used to select a path. When creating a Domain Administrator account for this Domain, it is suggested that their home directory be the same, which ensures
that all Users of the Domain are placed in a subdirectory of the Domain's home directory. Enter the amount of disk space, in megabytes (MB), available to the
Domain in the Maximum Size field. Leaving this field blank or entering "0" does not impose a maximum size on the Domain. When a limit is
imposed, any upload that would cause this maximum size to be exceeded is rejected by the Server.
Click the Save button to apply these changes.
NOTE: Calculating the amount of disk space in use by a Domain can be a time consuming operation depending on the directory structure.
::END
$DOMAIN_LISTENERS_HEADER$=Domain Listeners
$DOMAIN_LISTENERS$::
The Serv-U File Server offers a highly configurable interface for enabling the different file sharing protocols on a Domain. Listeners are added,
edited, and deleted using the appropriately labeled button. Each Domain can listen on multiple ports and IP addresses by adding a listener bound
to the desired IP address and port. In addition to selecting these connection attributes for a listener, a file sharing protocol must also be
selected. A listing and short description of the file sharing protocols supported by the Serv-U File Server follows.
::END
$LISTENER_FTP$=FTP - File Transfer Protocol
$LISTENER_FTP_TXT$::
FTP is the traditional protocol for transferring files over the Internet. It normally operates on the default port 21. Traditionally, FTP is handled
in plain-text, however SSL connections are explicitly supported through the use of the AUTH command.
::END
$LISTENER_FTPS$=FTPS - File Transfer Protocol using SSL
$LISTENER_FTPS_TXT$::
FTPS is identical to FTP, however connecting to a listener configured for FTPS means that an SSL connection is required before any protocol communication
is performed. This is commonly referred to as Implicit FTPS, which normally takes place on the default port 990.
::END
$LISTENER_SFTP$=SFTP - Secure File Transfer Using SSH2
$LISTENER_SFTP_TXT$::
SFTP is a secure method of transferring files through a secure shell session. It performs all protocol communications and data transfers over the same port
eliminating the need to open multiple ports in firewalls as is commonly required when using FTP. SFTP sessions are always encrypted. SFTP operates on the
default port 22.
::END
$LISTENER_HTTP$=HTTP - Hypertext Transfer Protocol
$LISTENER_HTTP_TXT$::
HTTP is the protocol used to browse Web sites. It's also a simple method for downloading and transferring files. One benefit to adding an HTTP listener to
a Domain is the availability of the Web Client, which allows users to transfers files to and from your File Server without the need for a stand-alone
client. HTTP traditionally operates on port 80.
::END
$LISTENER_HTTPS$=HTTPS - Hypertext Transfer Protocol using SSL
$LISTENER_HTTPS_TXT$::
HTTPS is identical to HTTP except all communications are secured using SSL. Like FTPS, a secure connection is implied when connecting to a listener running
the HTTPS protocol. The default port for HTTPS is 443.
::END
$LISTENER_ADDING$=Adding a Listener
$LISTENER_ADDING_TXT$::
After clicking the Add button, the listener configuration dialog is shown. After configuring each of the listener options, click the
Save button to add the listener to the Domain.
::END
$LISTENER_TYPE$=Type
$LISTENER_TYPE_TXT$::
Select the desired file sharing protocol that is to be supported by this listener. Each listener can only support a single protocol. To add more file sharing
protocols to the Domain, create new listeners for each protocol. A brief description of the support file sharing protocols is found above.
::END
$LISTENER_IP_ADDRESS$=IP Address
$LISTENER_IP_ADDRESS_TXT$::
A listener can be bound to a single IP address by entering it here. If the File Server does not have an external IP address, (e.g., it's behind a router), this
field can be left blank. Leaving the field blank tells Serv-U to listen on all available IP addresses.
::END
$LISTENER_PASV_IP$=PASV IP Address or Domain Name (FTP ONLY)
$LISTENER_PASV_IP_TXT$::
If the listener is supporting the FTP protocol, this additional field is available to specify a separate IP address to use for PASV mode data transfers. Entering
an IP address here ensures that PASV mode works properly on both unsecured and secured connections. If the File Server does not have an external IP address, try
using $LINK_DNS4ME$ and entering your DNS4Me domain name in this field. Serv-U resolves your DNS4Me domain name to ensure it always has the proper external IP
address for PASV command responses.
::END
$LISTENER_SSL_ONLY$=Use only with SSL connections
$LISTENER_SSL_ONLY_TXT$::
This option allows the PASV IP Address or domain name to only be used for SSL connections where it is always necessary to provide the PASV IP Address to
connecting clients. When this option is enabled, the IP Address specified for PASV mode will not be provided to clients connecting via non-SSL FTP.
::END
$LISTENER_USE_LAN$=Use with LAN connections
$LISTENER_USE_LAN_TXT$::
Normally, Serv-U does not use the PASV IP Address for connections coming from the Local Area Network (computers on the same network as Serv-U). When this
option is enabled, the PASV IP Address is also used for LAN connections.
::END
$LISTENER_PORT$=Port
$LISTENER_PORT_TXT$::
The default port for the selected protocol is automatically provided. However, any port between 1 and 65535 can be used. When using a non-standard port, clients
must know the proper port in advance when attempting to connect to the Domain. If using a non-standard port, we recommend using a value above 1024 to prevent
potential conflicts.
::END
$LISTENER_ENABLE$=Enable listener
$LISTENER_ENABLE_TXT$::
A listener can be temporarily disabled by unchecking this box. While disabled, listeners are displayed with a different icon in the list.
::END
$LISTENER_PURE_VIRTUAL$=Pure Virtual Domains
$LISTENER_PURE_VIRTUAL_TXT$::
Serv-U supports the ability for multiple Domains to "share" the same listeners. In other words, one Domain can possess the necessary listener configurations
while the other Domain "piggybacks" on the first one. In this way, the second Domain exists in a virtual way. To have a Domain "piggyback" on the listener
configurations of existing Domains, leave the listener list blank for the Domain. The "piggybacking" Domain needs to have at least one
$LINK_HELP_VIRTUAL$ defined for it.
This method of "piggybacking" only works with the FTP and HTTP protocols as they are the only two file sharing protocols that specify a method for identifying
the desired host after a connection is established. For FTP connections, the client must issue a HOST command to identify the desired domain. For HTTP
connections, the browser automatically handles providing the necessary host header to Serv-U based upon the domain name used to establish the HTTP connection.
::END
$VIRTUAL_HOSTS_HEADER$=Virtual Hosts
$VIRTUAL_HOSTS$::
Virtual Hosts provide a way for multiple Domains to share the same IP and Listener port numbers. Normally, each domain listener must use a unique IP address
and port number combination. With Virtual Hosts, it's possible to host multiple Domains on a system that only has one unique IP address without having to
use non-standard port numbers. The Domains can share the same listeners by proper implementation of Virtual Hosts. This feature is only available when the
current license supports hosting multiple Domains.
To configure Virtual Hosts for a Domain, click on the Add button and type in the Virtual Host name for the Domain. The Virtual Host name
is usually the fully qualified domain name used to connect to the Domain such as "ftp.Serv-U.com".
The method used by a client to connect to a desired Virtual Host depends upon the protocol being used to connect to Serv-U.
FTP
FTP users can use one of two methods to connect to a specific Virtual Host. If supported by the FTP client, the HOST command can be issued to Serv-U before
login to identify the Virtual Host. Otherwise, the virtual host can be provided with the login ID in the following format: virtual_host_name|login ID.
The Virtual Host name is entered first, followed by the vertical bar character ('|'), then the login ID.
SFTP
SFTP users wishing to connect to a specific virtual host must use the specially crafted login ID format as described above in the FTP section.
HTTP
For HTTP users, the browser automatically provides Serv-U with the hostname used to reach the site allowing Serv-U to identify the Virtual Host from the fully
qualified domain name entered into the browser's navigation bar.
::END
$VIRTUAL_HOSTS_CASEFILE1_HEADER$=Case File - Virtual Hosts
$VIRTUAL_HOSTS_CASEFILE1_BODY$::
Multiple Domains are being configured on the same Server, which has one IP address and two Fully Qualified Domain Names (FQDN) pointing to it. Because Users
connecting to both Domains must use port 21 for connections, configure Virtual Hosts on each Domain so that Serv-U can distinguish between requests for the
two Domains. After setting up the same listener properties on each Domain, open the Virtual Hosts tab, click Add, and then type in the FQDN
that clients should use to connect to the Domain (such as ftp.Serv-U.com).
After connecting to the Server with FTP, Users can send a HOST ftp.Serv-U.com command to connect to the appropriate Domain on the File Server.
FTP and SFTP users could also identify the Virtual Host through their login ID of ftp.Serv-U.com|login ID. If connecting via HTTP, Users
can connect to this Domain by visiting http://ftp.Serv-U.com.
::END
$DIRECTORY_ACCESS_HEADER$=Directory Access Rules
$DIR_ACCESS_BASICS$::
Directory Access rules define the areas of the system that are accessible to user accounts. While traditionally restricted to the User and Group levels,
Serv-U extends the usage of Directory Access rules to both the Domain and Server levels through the creation of global Directory Access rules. Directory
Access rules specified at the Server level are inherited by all Users of the File Server. When specified at the Domain level, they are only inherited by
Users belonging to that Domain. The traditional rules of inheritance apply where rules specified at a lower level, (e.g., the User level), override
conflicting or duplicates rules specified at a higher level, (e.g., the Server level).
When setting the Directory Access path, the %USER%, %HOME%, and %DOMAIN_HOME% variables are available to simplify the process. For example, use
%HOME%/ftproot/ to create a Directory Access rule that specifies the "ftproot" folder in the user's home directory. Directory access rules specified in
this manner are "portable" in the event that the actual home directory changes while maintaining the same subdirectory structure. This leads to less
maintenance for the File Server administrator. If the %USER% variable is specified in the path, it is replaced with the user's login ID. This variable
is useful in specifying a Group's home directory to ensure that Users inherit a logical and unique home directory. Finally, the %DOMAIN_HOME% macro may
also be used to identify the user's home directory. For example, to place a users and their home directory into a commmon directory use %DOMAIN_HOME%%USER%.
Directory Access rules are applied in the order they are listed. The first rule Serv-U encounters in the list that matches the path of a client's request
is the one that's applied for that rule. In other words, if a rule exists that denies access to a particular subdirectory but is listed below the
rule that grants access to the parent directory, then a User still has access to the subdirectory in question. The arrows on the right side of the
Directory Access list are used to re-arrange the order in which the rules are applied.
A listing and description of each available directory access permission follows.
::END
$FILE_PERMS_HEADER$=File Permissions
$FILE_PERMS_READ$=Read
$FILE_PERMS_READ_TXT$::
Allows Users to read, (i.e., download) files. This permission does not allow Users to list the contents of a directory, which is granted by the
List permission.
::END
$FILE_PERMS_WRITE$=Write
$FILE_PERMS_WRITE_TXT$::
Allows Users to write, (i.e., upload) files. This permission does not allow Users to modify existing files, which is granted by the Append
permission.
::END
$FILE_PERMS_APPEND$=Append
$FILE_PERMS_APPEND_TXT$::
Allows Users to append data to existing files. This permission is normally used to grant Users the ability to resume transferring to partially uploaded
files.
::END
$FILE_PERMS_RENAME$=Rename
$FILE_PERMS_RENAME_TXT$::
Allows Users to rename existing files. Previous versions of Serv-U required Delete and Write permissions to rename
files. Starting with version 7.0, Rename is an explicit permission.
::END
$FILE_PERMS_DELETE$=Delete
$FILE_PERMS_DELETE_TXT$::
Allows Users to delete files.
::END
$FILE_PERMS_EXECUTE$=Execute
$FILE_PERMS_EXECUTE_TXT$::
Allows Users to remotely execute files. Execute access is meant for remotely starting programs and usually applies to specific files. This is a very
powerful permission and great care should be used in granting it to Users. A User with Write and Execute permissions
can essentially install any program of their choosing on your system.
::END
$DIR_PERMS_HEADER$=Directory Permissions
$DIR_PERMS_LIST$=List
$DIR_PERMS_LIST_TXT$::
Allows Users to list the files contained in the directory.
::END
$DIR_PERMS_CREATE$=Create
$DIR_PERMS_CREATE_TXT$::
Allows Users to create new directories within the directory.
::END
$DIR_PERMS_RENAME$=Rename
$DIR_PERMS_RENAME_TXT$::
Allows Users to rename existing directories within the directory. Previous versions of Serv-U required Delete and Write
permissions to rename directories. Starting with version 7.0, Rename is an explicit permission.
::END
$DIR_PERMS_DELETE$=Delete
$DIR_PERMS_DELETE_TXT$::
Allows Users to delete existing directories within the directory. NOTE: If the directory contains files, the User also needs to
have the Delete files permission in order to delete the directory.
::END
$SUBDIR_PERMS_HEADER$=Subdirectory Permissions
$SUBDIR_PERMS_INHERIT$=Inherit
$SUBDIR_PERMS_INHERIT_TXT$::
Allows all subdirectories to inherit the same permissions as the parent directory. The Inherit permission is appropriate for most
circumstances, but if access must be restricted to subfolders (as is the case when implementing Mandatory Access Control), uncheck Inherit and grant
permissions specifically by folder.
::END
$WINDOWS_USER_ACCESS$=Access as Windows User
$WINDOWS_USER_ACCESS_TXT$::
For a variety of reasons, files and folders may be kept on external servers in order to centralize file storage or provide additional layers of security.
In this environment, files can be accessed by UNC path (\servernamefolder) instead of the traditional "C:ftprootfolder" path. However, accessing
folders stored across the network poses an additional challenge - Windows services are run under the "Local System" account by default, which has no access
to network resources.
To mitigate this problem for all of Serv-U, it is possible to configure the "Serv-U File Server" service to run under a network account. The alternative,
preferred when many servers exist or if the Serv-U File Server service needs to run under "Local System" for security reasons is to configure a Directory Access
rule to use a specific Windows User for file access. By clicking on the "Advanced" button it is possible to specify a specific Windows user for each individual
Directory Access rule. Just like in Windows Authentication, directory access is subject to NTFS permissions, though in this case also to the configured permissions
in Serv-U.
::END
$QUOTA_PERMS_HEADER$=Quota Permissions
$QUOTA_PERMS_MAXSIZE$=Maximum size of directory contents
$QUOTA_PERMS_MAXSIZE_TXT$::
Setting the maximum size actively restricts the size of the directory contents to the specified value. Any attempted file transfers that cause the
directory contents to exceed this value are rejected. This feature serves as an alternative to the traditional quota feature that relies upon tracking
all file transfers (uploads and deletions) to calculate directory sizes and is not able to consider changes made to the directory contents outside of
a User's File Server activity.
::END
$DIR_ACCESS_CASEFILE1_HEADER$=Mandatory Access Control
$DIR_ACCESS_CASEFILE1_TXT$::
Serv-U enables the use of Mandatory Access control in cases where Users need to be granted access to the same home directory but should not be able to
necessarily access the subdirectories below it. To implement Mandatory Access Control at a directory level, simply disable the "Inherit" permission as
shown below (assume the rule applies to "D:ftproot"):
::END
$DIR_ACCESS_CASEFILE1_TXT2$::
Now, the user has access to the "ftproot" folder but to no folders below it. Permissions must individually be granted to subfolders that the user needs
access to, providing the security of Mandatory Access Control in the Serv-U File Server.
::END
$DIR_ACCESS_CASEFILE2_HEADER$=Restricting File Types
$DIR_ACCESS_CASEFILE2_TXT$::
If Users are using storage space on the Serv-U File Server to store non-work-related files such as MP3 music files, this can be prevented by configuring
a Directory Access rule placed above the main Directory Access Rule (use the arrows on the right to reorder rules) to prevent MP3 files
from being transferred as shown below. In the text entry for the rule, enter "*.mp3" and use the permissions shown below:
::END
$DIR_ACCESS_CASEFILE2_TXT2$::
The rule denies permission to any transfer of files with the .mp3 extension and can be modified to reflect any file extension. Similarly, if accounting
employees only need to transfer files with the .mdb extension, configure a pair of rules that grants permissions for .mdb files but denies access to all
other files, as shown below. In the first rule enter the path that should be the user's home directory or directory they need access to, and in the
second rule enter the extension of the file that should be accessed (such as "*.mdb"):
::END
$DIR_ACCESS_CASEFILE2_TXT3$::
These rules only allow users to access .mdb files within the directories specified, and can be adapted to any file extension or set of file extensions.
::END
$VIRTUAL_PATHS_HEADER$=Virtual Paths
$VIR_PATHS$::
Virtual Paths allow Users to gain access to files and folders outside of their own home directory. A Virtual Path only defines a method of mapping an
existing directory to another location on the system to make it visible within a User's accessible directory structure. In order to actually have access
to the mapped location, the User must still have a Directory Access rule specified for the physical path of a Virtual Path.
Like $LINK_HELP_DIRACCESS$, Virtual Paths can be configured at the Server, Domain, Group, and User levels. Virtual Paths created at the Server level are
available for use by all Users of the File Server. When created at the Domain level, they are only accessible by Users belonging to that Domain. Serv-U's
granular file access controls even allow for Virtual Paths created specifically for individual Users or Groups.
::END
$VIRTUAL_PATHS_PHYSICAL$=Physical Path
$VIRTUAL_PATHS_PHYSICAL_TXT$::
The physical path is the actual location on the system, or network, that is to be placed in a virtual location accessible by a User. If the physical path
is located on the same computer, a full path should be used, such as "D:inetpubftppublic". A UNC path can also be used, such as "\Serversharepublic".
In order for a Virtual Path to be visible to a User, they must have a Directory Access rule specified for the physical path.
::END
$VIRTUAL_PATHS_VIRTUAL$=Virtual Path
$VIRTUAL_PATHS_VIRTUAL_TXT$::
The virtual path is the location that the physical path should appear in for the User. The %HOME% macro is commonly used in the virtual path to place the
specified physical path in the home directory of the User. When specifying the virtual path, the last specified directory is used as the name displayed in
directory listings to the User. For example, a virtual path of "%HOME%/public" places the specified physical path in a folder named "public" within the
User's home directory. A full path without any macros can also be used.
::END
$VIRTUAL_PATHS_INCLUDE_IN_MAX_SIZE$=Include in "Maximum Directory Size" calculations
$VIRTUAL_PATHS_INCLUDE_IN_MAX_SIZE_TXT$::
When checked, the Virtual Path is included in Maximum Directory Size calculations. When unchecked, the Virtual Path is not included in the Maximum Directory
Size calculations. Maximum Directory Size limits the size of directories affecting how much data can be uploaded.
::END
$VIRTUAL_PATHS_CASEFILE1_HEADER$=Case File - Using Virtual Paths
$VIRTUAL_PATHS_CASEFILE1_BODY$::
A Group of web developers have been granted access to the directory "D:ftprootexamplesite.com" for web development purposes. The developers also need
access to an image repository located at "D:corpimages". To avoid granting the Group access to the root D drive, a Virtual Path must be configured so that
the image repository appears to be contained within their home directory. Within the web developer's Group, add a Virtual Path to "bring the
directory to the users" by specifying "D:corpimages" as the Physical Path and "D:ftprootexamplesite.comcorpimages" as the Virtual
Path. Be sure to add a Group level Directory Access rule for "D:corpimages" as well. The developers now have access to the image repository without
compromising security or relocating shared resources.
::END
$VIRTUAL_PATHS_CASEFILE2_HEADER$=Case File - Creating Relative Virtual Paths
$VIRTUAL_PATHS_CASEFILE2_BODY$::
Continuing with the example from above, if the web developer's Group home directory is relocated to another drive, not only does the home directory have to be
updated, but the Virtual Path also needs to be updated to reflect this change. This can be avoided by using the %HOME% macro to create a relative Virtual
Path location that eliminates the need to update the path should the home directory change. Instead of using "D:ftprootexamplesite.comcorpimages" as the
Virtual Path, use "%HOME%corpimages". This tells Serv-U to place the "corpimages" Virtual Path within the Group's home directory - whatever
that may be. If the home directory changes at a later date, the Virtual Path still appears there.
::END
$DOMAIN_LOGS_HEADER$=Configuring Domain Logs
$CONF_DOMAIN_LOGS$::
The Serv-U File Server allows for a great deal of customization in logging Domain events and activity. Logging is broken into two sections: File and Screen. To
enable a logging option, check the appropriate box in the File or Screen column. When an option is checked from the "File" column, the appropriate logging
information is saved to the specified log file if Enable logging to file is checked. When an option is checked from the "Screen" column, then the
event is displayed in the log when viewed from the Serv-U Management Console. The log can be configured to show as much or as little information as you desire.
After configuring the desired logging options, click the Save button to save the changes.
::END
$DOMAIN_LOG_FILE_SETTINGS$=Logging to File Settings
$DOMAIN_LOG_FILE$=Log file path
$DOMAIN_LOG_FILE_TXT$::
The log file must be given a name before information can be saved to a file. The Browse button can be used to select an existing file or directory
location for the log file. The log file path supports certain wildcard characters as outlined below. Wildcard characters referencing the date applies to the day
that the log file is created. When combined with the Automatically rotate log file option, wildcards provide an automatic way to archive Domain
activity for audits, such as those required by HIPAA. The available wildcard characters are:
::END
$DOMAIN_LOG_FILE_LIST$::
%D - The current day of the month
%M - The name of the current month
%N - The numeric value of the current month (1-12)
%Y - The 4-digit value of the current year, (e.g., %COPYRIGHT_END_YEAR%)
%X - The 2-digit value of the current year, (e.g., %SHORT_COPYRIGHT_END_YEAR% for %COPYRIGHT_END_YEAR%)
%S - The name of the Domain whose activity is being logged
::END
$DOMAIN_LOG_ENABLE_FILE$=Enable logging to file
$DOMAIN_LOG_ENABLE_FILE_TXT$::
Check this box to Serv-U to begin saving log information to the file specified in the Log file path. If this option is not checked, Serv-U does
not log any information to the file, regardless of the individual options checked in the "File" column.
::END
$DOMAIN_LOG_ROTATE$=Automatically rotate log file
$DOMAIN_LOG_ROTATE_TXT$::
To ensure that log files remain a manageable size and can be easily referenced during auditing, Serv-U supports the ability to automatically rotate the log file
on a regular basis. By specifying a Log file path containing wildcards referencing the current date, Serv-U can rotate the log file and create
a unique file name every day, week, month, or year.
::END
$DOMAIN_LOG_PURGE$=Purge Old Log Files
$DOMAIN_LOG_PURGE_TXT$::
Serv-U supports the ability to automatically purge old log files by setting a maximum number of files to keep and/or a maximum size limit in MB's. Setting these
options to "0" means the setting is unlimited and the limit is not applied.
CAUTION: Log files are purged based only on the current log file path name. Log file variables are replaced with Windows wildcard values used
to search for matching files. For example:
C:Logs%Y:%N:%D %S Log.txt is searched for C:Logs????:??:?? * Log.txt
C:Logs%Y:%M:%D %S Log.txt is searched for C:Logs????:*:?? * Log.txt
C:Logs%S%Y:%M:%D Log.txt is searched for C:Logs--DomainName--????:*:?? Log.txt
Log variables are wildcarded like this:
%D --> ??
%N --> ??
%M --> *
%Y --> ????
%X --> ??
%S --> *
Anything matching the wildcarded path name can be purged. Use caution; it's best practice to place log files into a single directory to avoid unexpected
file deletion.
::END
$DOMAIN_LOG_NO_LOG$=Do Not Log IPs
$DOMAIN_LOG_NO_LOG_TXT$::
Serv-U supports the ability to specify IP addresses that are exempt from logging. Activity from these IP addresses is not logged to the location specified by the
rule - the Screen, a File, or both. This is useful to exempt IP addresses for administrators that may otherwise generate a lot of logging information that can
obfuscate Domain activity from regular users. It can also be used to save on log space and reduce overhead. Simply click the Do Not Log IPs
button and add IP addresses as appropriate.
::END
$ABOUT_USERS_HEADER$=About User Accounts
$ABOUT_USER_ACCTS$::
A User account is required in order to provide access to the File Server. At its most basic level, a User account defines login credentials, (i.e., login ID
and password), a home directory, and a set of $LINK_HELP_DIRACCESS$ that defines the areas of the system accessible to the User and the actions they can
perform in those locations. Each active session on the File Server has a User account associated with it that identifies the client to the administrator.
User accounts can be defined in various ways on the Serv-U File Server, including:
::END
$ABOUT_USERS_LIST$::
Domain Users - Defined at the Domain level, Domain Users can only login to the Domain under which they are created.
Global Users - Defined at the Server level, Global Users are accounts that can login to any Domain on the File Server.
Database Users - Available at both the Server and Domain level, Database Users are stored in an external database accessible through ODBC and supplement the local account database.
Windows Users - Defined at the Domain level, Windows Users are Windows accounts either on the local system or accessible through a domain controller that supplement the local account database and allows a client to login to the File Server using their Windows login credentials.
::END
$ABOUT_USER_ACCTS2$::
Since User accounts can be assigned at the various levels with the same login ID, a hierarchy is used by Serv-U to determine which account takes precedence.
The User account types listed above are listed in the order of precedence. Where User accounts can be specified at both the Domain and Server levels, the
Domain level account always takes precedence over the Server one.
When creating Users, consider what kind of access they need, and select the appropriate location for the User account accordingly - time and effort can be
saved by entering such settings at the Server level to remove the need for multiple User accounts at the Domain level.
On Serv-U Corporate, User accounts can be organized into Collections in order to make account management more logical and organized. This can be useful when
managing all Users from a department or physical location. For example, all Users in the accounting department can be placed in a Collection named
"Accounting", or all Users at an office in Topeka can be placed in a collection named "Topeka Users".
To create a Collection, click the Add button in the "Users" window within the Select user collection group. In the new
dialog, enter the name of your Collection and click the Save button. Users can now be added this new Collection by selecting it and clicking
the Add button below the User list. To move a User from one Collection to another, click the Move button below the User list
and select the destination Collection for the highlighted User accounts.Collections can also be Renamed or Deleted using the appropriate button.
NOTE: When deleting a Collection, all User accounts contained in that Collection are deleted, too. If the User accounts should be kept, be
sure to move them before deleting the Collection.
By default, all Users are created in the "General" User Collection.
::END
$ABOUT_USER_WIZARD$=New User Wizard
$ABOUT_USER_WIZARD_TXT$::
A wizard is available to assist in creating a new User account by clicking on the Wizard button. The New User Wizard walks you through the
4 steps required to create a User account with the minimum number of required attributes. Once created, the User can be edited to configure more advanced
settings such as Group membership or additional Directory Access rules. For more information on using the New User Wizard, see the Creating Your
First User Account section of the $LINK_HELP_GUIDE$.
::END
$ABOUT_USER_TEMPLATE$=User Template
$ABOUT_USER_TEMPLATE_TXT$::
While the New User Wizard offers a way to quickly create a User account with the minimum number of required attributes, most File Server administrators have
a collection of settings they want all User accounts to abide by. Groups are the best way to accomplish this task, however there are times when it may not
be the desired course of action.
Serv-U allows an administrator to configure a template for new User accounts by clicking on the Template button. Once opened, the template
User can be configured just like any other User account, with the exception of a login ID. After these settings are saved to the template, all new User
accounts that are manually created are done so with their default settings set to those found within the template.
::END
$ABOUT_USER_COPY$=Copying User Accounts
$ABOUT_USER_COPY_TXT$::
User Templates offer a way for large numbers of users to be created with the same settings. In cases where only the settings of a single user must be duplicated
or there is a need for multiple user templates, the "Copy" button can be used to create a copy of a user account lacking only the username and the password. To
Copy a user, select the user account and choose "Copy".
::END
$ABOUT_USER_PASS_RECOVERY$=Recover Password
$ABOUT_USER_PASS_RECOVERY_TXT$::
Serv-U supports password recovery both through the Management Console and through the Web Client. For Password Recovery to be available, the SMTP Options for the
Server or Domain must be configured, and the user account must have an email address listed. To use Password Recovery from the Management Console, select
a user account and click on the "Recover Password" button. If the password is stored using one-way encryption, the password will be reset and the new password
sent to the user's email address. If the password is stored using two-way encryption or no encryption, the original password will be sent by email.
Password Recovery from the Web Client requires that the "Allow users to recover password" limit be enabled for the user account. Once this option is enabled,
users can use the "Recover Password" option in the Web Client as long as they are using a Serv-U Silver or Gold Edition license. Password Recovery
from the Web Client otherwise works the same as from the Management Console.
::END
$IMPORT_USER_ACCOUNTS$=Importing/Exporting User Accounts
$IMPORT_USER_ACCOUNTS_TXT$::
User accounts can be imported and exported using the "Import" and "Export" buttons on the top of the screen. The "Export" button will export all users in either
the current domain/server or the current Collection to a comma-separated values file (CSV file) which can be viewed in Excel and analyzed by database engines, among other things. Additionally,
by creating a CSV file using the same format as the export it is possible to import lists of users from CSV files into Serv-U.
::END
$USER_INFO_HEADER$=User Information
$USER_INFO_TXT$::
A User account consists of many attributes and settings. The User Information tab contains general information about the User account including login
credentials, the home directory, and the type of account. Detailed information on each of the available attributes is found below.
::END
$USER_INFO_USERNAME$=Login ID
$USER_INFO_USERNAME_TXT$::
The login ID is provided by the client as one part of authenticating the session to the File Server. In addition to the login ID,
clients must provide a password to complete authentication. Login IDs must be unique for each account specified at that level. Login IDs may not
contain any of the following special characters: / < > | : ? *.
NOTE: There are two special login IDs: "Anonymous" and "FTP". These login IDs are synonymous with one another and can be used for guests
on your File Server. These users do not require a password, which should be left blank in this case. Instead, Serv-U requires users who log on with one of
these accounts to provide their email address to complete the login process.
::END
$USER_INFO_PASSWORD$=Password
$USER_INFO_PASSWORD_TXT$::
The password is the second item required for a session to be authenticated with the File Server. The password should be kept a secret and not shared with
anyone other than the person that owns the account. A strong password contains at least 6 characters including a mix of upper and lowercase letters and at
least one number. Restrictions can be placed on the length and complexity of passwords through limits. See the Help documentation on $LINK_HELP_USER_LIMITS$
for more information.
::END
$USER_INFO_PASSWORD_GEN_TXT$::
Additionally, the "Lock" icon next to the "Password" field allows a new random password to be generated for a user. This new password will follow defined
password length requirements. By default, all passwords are 8 characters long and are complex. If the "Minimum Password Length" is equal to or less than
four characters, the password will be four characters long - otherwise, generated passwords will follow the specified domain value.
::END
$USER_INFO_ADMIN$=Administration Privilege
$USER_INFO_ADMIN_TXT$::
A User account can be granted one of three types of administrative privileges: No Privilege, System Administrator, or Domain Administrator. The value of this
attribute can be inherited through Group membership.
A User account with No Privilege is a regular user account that can only login to transfer files to and from the File Server. The Serv-U Management Console
is not available to these User accounts.
A System Administrator has the ability to perform any File Server administration activity including creating and deleting Domains, User accounts, or even
updating the File Server's license. A User account with System Administrator privileges that is logged in through HTTP remote administration can essentially
administer the server as they had physical access to the machine.
A Domain Administrator can only administrative duties for the Domain to which their account belongs. A Domain Administrator is also restricted from performing
Domain-related activities that may affect other Domains. The Domain-related activities that may not be performed by Domain Administrators consists of
configuring their Domain listeners or configuring ODBC database access for the Domain.
::END
$USER_INFO_ADMIN_READ_ONLY$::
Serv-U also supports read-only administrator accounts which can allow administrators to log in and view configuration options at the domain or server level,
greatly aiding remote problem diagnosis when working with outside parties. Read-only administrator privileges are identical to their full-access equivalents,
except that they cannot change any settings or create/delete/edit user accounts.
::END
$USER_INFO_ADMIN_NOTE$::
NOTE: When configuring a User account with administrative privileges, take care in specifying their home directory. An administrator with a
home directory other than "" (root) that is locked in their home directory may not use file paths outside of their home directory when configuring the File
Server.
::END
$USER_INFO_TYPE$=Account Type
$USER_INFO_TYPE_TXT$::
By default, all accounts are permanent and exist on the File Server until manually deleted or disabled. An account can be configured to be automatically
disabled or even deleted on a specified date by configuring the Account Type. After selecting the appropriate type, the Account
Expiration Date control appears. Click on the calendar or expiration date to select when the account should be disabled or deleted.
::END
$USER_INFO_WEB_CLIENT$=Default Web Client
$USER_INFO_WEB_CLIENT_TXT$::
If your Serv-U license enables the use of FTP Voyager JV, then users connecting to the File Server through HTTP can choose which client they want to use after
logging in. Instead of asking users which client they want to use, a default client can also be specified. If this option is changed, it overrides the option
specified at the Server or Domain level. It can also be inherited by a User through Group membership. Use the Inherit default value option
to reset it to the appropriate default value.
::END
$USER_INFO_EMAIL_ADDRESS$=Email Address
$USER_INFO_EMAIL_ADDRESS_TXT$::
Serv-U Events can use the "Email Address" field when sending email notifications to groups, and password recovery using the Web Client requires an email address
to send a recovered password to a user. Enter an email address here to allow email notifications or password recovery for the user account.
::END
$USER_INFO_ENABLE$=Enable account
$USER_INFO_ENABLE_TXT$::
Uncheck this box to disable the current account. Disabled accounts remain on the File Server but cannot be used to login. To re-enable the account, check the
Enable account box again.
::END
$USER_INFO_FULL_NAME$=Full Name
$USER_INFO_FULL_NAME_TXT$::
The full name of the account is available to specify additional identifying information about the account. It is not used by clients when they login.
::END
$USER_INFO_PASS_TYPE$=FTP Password Type
$USER_INFO_PASS_TYPE_TXT$::
All passwords are stored in an encrypted, unreversible state in Serv-U's configuration files (unless the File Server is configured to not encrypt stored
passwords through a $LINK_HELP_USER_LIMITS$). In addition to the Regular Password option, two additional types of password storage are
available for accounts that use the FTP protocol: MD4 and MD5 OTP S/KEY passwords. This type of password setting allows the
user to login via FTP without sending the password to the File Server as plain text. These options only apply to the FTP protocol. Setting this option does
not affect a User's ability to login via other protocols.
::END
$USER_INFO_HOMEDIR$=Home Directory
$USER_INFO_HOMEDIR_TXT$::
The home directory for a User account is where the User is placed immediately after logging in to the File Server. Each User must have a home directory
assigned to it, although it can be specified at the Group level if the User is a member of a Group. Home directories must be specified using a full path
including the drive letter or UNC share name. If the home directory is not found, Serv-U can be configured to create it.
When specifying the home directory, the %USER% macro can be used to insert the login ID in to the path. This is used mostly to configure a default home
directory at the Group level or within the new User template to ensure that all new Users have a unique home directory. When combined with a Directory Access
Rule for %HOME%, a new User can be configured with a unique home directory and the proper access rights to that location with a minimal amount of effort.
The %DOMAIN_HOME% macro may also be used to identify the user's home directory. For example, to place a user's home directory into a commmon location use
%DOMAIN_HOME%%USER%.
The home directory can be specified as "" (root) in order to grant system-level access to a User, allowing them the ability to access all system drives. In
order for this to work properly, the User must not be locked in their home directory.
::END
$USER_SSH_PUBLIC_PATH$=SSH Public Key Path
$USER_SSH_PUBLIC_PATH_TXT$::
The SSH public key can be used to authenticate a user when logging into the the Serv-U File Server. The public key path should point to the key file in a secured
directory on the server. This path can include the following macros:
%HOME% - The Home Directory of the user account
%USER% - The Login ID, used if the public key will have the Login ID as part of the file name
%DOMAIN_HOME% - The Home Directory the Domain, set in Domain Details | Settings, used if the keys will be in a central folder relative to the domain Home Directory
Examples:
%HOME%SSHpublic.pub
%HOME%%USER%.pub
%DOMAIN_HOME%SSHKeys%USER%.pub
<a href="Help-SSH-Key-Pair.htm">Click here</a> for information on creating a SSH key pair.
::END
$USER_INFO_LOCK_HOMEDIR$=Lock user in home directory
$USER_INFO_LOCK_HOMEDIR_TXT$::
A user that is locked in their home directory may not access paths above their home directory. In addition, the actual physical location of their home
directory is masked as Serv-U always reports it as "/" (root). The value of this attribute can be inherited through Group membership.
::END
$USER_INFO_ALWAYS_LOGIN$=Always Allow Login
$USER_INFO_ALWAYS_LOGIN_TXT$::
Enabling this option means that the User account is always permitted to login, regardless of restrictions placed upon the File Server such as IP access rules
or a maximum number of sessions. It is useful as a fail-safe in order to ensure that critical system administrator accounts can always remotely access the
File Server under all conditions. As with any option that allows bypassing access rules, care should be taken in granting this ability. The value of this
attribute can be inherited through Group membership.
::END
$USER_INFO_DESCRIPTION$=Description
$USER_INFO_DESCRIPTION_TXT$::
The description allows for the entry of additional notes that are only visible by administrators.
::END
$LOGIN_AVAILABILITY$=Availability
$LOGIN_AVAILABILITY_TXT$::
This feature limits when users can connect to this server. Limitations may be placed on the time-of-day as well as the day-of-the-week. When logging in outside the specified available times users are presented a message that the user account is currently unavailable.
::END
$USER_GROUPS_HEADER$=Group Memberships
$USER_GROUPS_OLD$::
A User can be a member of any number of Groups. Groups provide a convenient way of applying a base set of User attributes and settings to multiple Users.
For more information on configuring Groups, see the Help documentation on $LINK_HELP_GROUPS$.
Because a User can be a member of multiple Groups, the order in which Group memberships are presented is important. The first Group membership for a User
encountered by Serv-U for a User that provides a value for an attribute is the value that is used. Use the arrows on the right side of the Group membership
list to re-arrange the order of Group memberships as desired.
Use the Add and Delete buttons to add additional Group memberships to the User or remove the User from the
selected Groups, respectively.
::END
$USER_GROUPS$::
A User can be a member of any number of Groups. Groups provide a convenient way of applying a base set of User attributes and settings to multiple Users.
For more information on configuring Groups, see the Help documentation on $LINK_HELP_GROUPS$.
Because a User can be a member of multiple Groups, the order in which Group memberships are presented is important. The first Group membership for a User
encountered by Serv-U for a User that provides a value for an attribute is the value that is used. Use the arrows on the right side of the Group membership
list to re-arrange the order of Group memberships as desired.
Use the left and right arrow buttons to add additional Group memberships to the User or remove the User from the
selected Groups, respectively.
::END
$WELCOME_MESSAGE_HEADER$=Welcome Message
$WELCOME_MESSAGE_BODY$::
The welcome message is a message that is traditionally sent to the FTP client during a successful User login. Serv-U extends this ability to HTTP so that
Users accessing the File Server through the Web Client or FTP Voyager JV also receive the welcome message. This feature is not available to Users
logging in via SFTP over SSH2 as the protocol does not define a method for sending general text information to the User.
The welcome message can contain general information about the Server's status, a special message for the User, disclaimers, or other legal notices. There are
two ways to configure a welcome message. The first method involves specifying the path to a file containing the desired welcome message in the
Message File Path field. The Browse button can be used to select an existing file on the system.
As an alternative, the text of the welcome message can be explicitly provided to Serv-U in the space provided. In order to override an explicit welcome
message at the User level, the Override inherited group welcome message box must be checked first. The provided text is then sent to the
User instead of the contents of the file specified in the Message File Path field.
These values can be inherited by the User through Group membership.
System variables are also available which can be used in the welcome message. For a comprehensive list of the available system variables, see the Help
documentation on $LINK_HELP_SYSTEM_VARS$.
::END
$QR_HEADER$=Transfer Ratio and Quota Management
$QR_TXT$::
Transfer Ratios and Quotas are just one of the many ways in which file transfers are managed on the Serv-U File Server. For more information on each of these
options, continue reading.
::END
$QR_RATIOS$=Transfer Ratio
$QR_RATIOS_TXT$::
Transfer ratios are a convenient way of encouraging file sharing on your File Server. By specifying an appropriate transfer ratio setting, you can grant
"credits" to the User for transferring a specified number of bytes or complete files. This is commonly used to grant a User the ability to download 'x'
megabytes of data or files for every 'y' megabytes of data or files that they upload.
To enable transfer ratios for the current User account, check the box labeled Enable transfer ratio. Select the appropriate type of ratio
to impose on the User account. Ratios can be tracked in terms of megabytes or complete files. They can also be tracked per session established or for all
sessions established by the User account.
The ratio itself is configured by assigning a numeric value to both the Uploads and Downloads side of the ratio. For
example, a 3/1 ratio that is counting files over all sessions means that the User account must upload 3 files in order to have the ability to download 1 file.
The current credit for the User account is displayed in the Credit field. This value is the current value and can be initialized to a
non-zero value to grant the User initial credits.
::END
$QR_QUOTA$=Quota
$QR_QUOTA_TXT$::
Quotas are another way to limit the amount of data that is transferred by a User account. When a Maximum quota value is assigned to the User,
they are not able to use more disk space than that value. The Current field shows how much disk space is currently being used by the User
account. When initially configuring a quota, both fields must be filled in. From that point on, Serv-U tracks the file uploads and deletions made by the
User and updates the Current value as appropriate.
NOTE: One considerable drawback to using quotas is that in order for the Current value to remain accurate, changes must not
be made to the contents of the directories that are accessible by the User account outside of Serv-U. Because these changes take place outside of a File
Server connection, Serv-U cannot track them and update the current quota value. As an alternative to quotas, consider imposing a maximum size on the contents
of a directory when specifying the Directory Access rules for the User account. For more information on this option, see the Help documentation on
$LINK_HELP_DIRACCESS$.
::END
$QR_FREE_FILES$=Ratio Free Files
$QR_FREE_FILES_TXT$::
Files listed in the ratio free file list are exempt from any imposed transfer ratios. In other words, if a User must upload files in order to earn credits
towards downloading a file, a file that matches an entry in this list can always be downloaded by Users, even if they have no current credits. This is
commonly used to make special files, such as a "read me" or a directory information file, always accessible by Users.
The '*' and '?' wildcard characters may be used when specifying a ratio free file. Using '*' specifies a wildcard of any kind of character and any length.
For example, entering "*.txt" makes any file with a .txt extension free for download, regardless of the actual filename. A '?' may be used to represent a
single character within the filename or directory.
In addition, full or relative paths may be used when making an entry. If a full path is used when specifying a filename, then only that specific file is
exempt from transfer ratios. If a relative path is used, such as entering just "readme.txt", then the provided file is exempt from transfer ratios regardless
of the directory it is located in.
::END
$WINDOWS_AUTH_HEADER$=Windows Authentication
$WINDOWS_AUTH_BASICS$::
By enabling Windows authentication, Users can login to Serv-U using their Windows
login credentials as provided by the local Windows account database or a specific Windows Domain Server. When logging in using their Windows account, Users
are placed in the home directory for their Windows account eliminating the need to manually specify a home directory.
To enable Windows authentication, check the box labeled Enable Windows authentication. If the Windows Domain Name field
is left empty, Serv-U uses the system's local Windows account database to authorize User logins. If the system is a member of a Windows Domain, the domain
name can be entered in this field to have User logins authorized by the Domain Server. After changing this field, click the Save button
to apply the changes.
::END
$WINDOWS_AUTH_USE_GROUP_HOMEDIR$=Use Windows User Group home directory instead of account home directory
$WINDOWS_AUTH_USE_GROUP_HOMEDIR_TXT$::
By default, Serv-U uses the Windows account's home directory when a client logs in using a Windows User account. Enabling this option causes Serv-U to use the
home directory specified in the Windows User Group instead. If no home directory is specified at the group level, then the Windows User account's home
directory is still used.
::END
$WINDOWS_AUTH_GROUP$=Configure Windows User Group
$WINDOWS_AUTH_GROUP_TXT$::
Windows User accounts are not visible or configurable on an individual basis in Serv-U. To aid in configuring the many advanced options of a local User
account, all Windows User accounts are a member of a special Windows User Group. Clicking the Configure Windows User Group button allows
this Group to be configured just like a normal Group. All settings configured in this Group are inherited by Windows User accounts. This feature can be
used to add IP access rules, specify bandwidth limitations, or add additional Directory Access rules.
For more information, see the Help documentation section on configuring $LINK_HELP_GROUPS$.
::END
$ABOUT_GROUPS_HEADER$=About Groups
$ABOUT_GROUPS_TXT$::
Groups are a method of sharing common configuration options with multiple User accounts. Configuring a Group is just like configuring a User account.
Virtually every configuration option available for a User account can be set at the Group level. In order for a User to inherit a Group's settings, it must
be a member of the Group. Permissions and attributes inherited by a User through Group membership can still be overridden at the User level. A User can be a
member of multiple Groups in order to acquire multiple collections of permissions, such as directory or IP access rules.
Like User accounts, Groups can be created at multiple different levels, including:
::END
$ABOUT_GROUPS_TYPES$::
Global Groups
Domain Groups
Database Groups - available at both the Server and Domain levels
::END
$ABOUT_GROUPS_TXT2$::
However, Groups are only available to User accounts that are defined at the same level. In other words, a Global User, (i.e., a User defined at the Server
level), can only be a member of a Global Group. Likewise, a User defined for a specific Domain can only be a member of a Group also created for that Domain.
This restriction also applies to Groups created in a database in that only Users created within a database at the same level can be members of those Groups.
Use the Add, Edit, and Delete buttons to manage the available Groups.
::END
$ABOUT_GROUPS_TEMPLATE$=Group Template
$ABOUT_GROUPS_TEMPLATE_TXT$::
Serv-U allows an administrator to configure a template for creating new Groups by clicking on the Template button. Once opened, the template
Group can be configured just like any other Group object, with the exception of giving it a name. After these settings are saved to the template, all new
Groups are created with their default settings set to those found within the template. This is a great way to configure some basic settings that you want all
of your Groups to use by default to save you time when creating new Groups.
::END
$ABOUT_GROUPS_NTUSER$=Configure Windows User Group
$ABOUT_GROUPS_NTUSER_TXT$::
Administrators have the ability to allow clients to login to the File Server using the local Windows user database or one that
is made accessible through a domain server. These User accounts do not exist in the local Serv-U User database and cannot be configured on an individual basis.
To aid in configuring these accounts, all Users logged in through this method belong to the Default Windows User Group. Clicking this button allows this Group
to be configured like normal. However, changes that are made to this Group only apply to Windows User accounts.
::END
$GROUP_INFO_HEADER$=Group Information
$GROUP_INFO$::
Virtually every attribute available for a User account can be configured at the Group. Group level settings are inherited by the Group members and can be
overridden at the User level. The Group Information tab contains general information about the Group including the name, home directory, and the default
administrative privilege for Group members. Detailed information on each of the available attributes is found below.
::END
$GROUP_INFO_NAME$=Group Name
$GROUP_INFO_NAME_TXT$::
The Group name is a unique identifier that must be unique for each Group specified at that level (Server or Domain). Group names may not contain any of the
following special characters: / < > | : ? *.
::END
$GROUP_INFO_DIRACCESS$=Apply group directory access rules first
$GROUP_INFO_DIRACCESS_TXT$::
As outlined in the Help documentation section on $LINK_HELP_DIRACCESS$, the order in which Directory Access Rules are listed has significance in determining
the resources that are available to a User account. By default, Directory Access Rules specified at the Group level take precedence over ones specified
at the User level. However, there are certain instances where this you may want the User level rules to take precedence. Unchecking this box places the
Group's Directory Access Rules below the User's.
::END
$GROUP_MEMBERS_HEADER$=Group Members
$GROUP_MEMBERS$::
The User accounts that are members of the currently selected Group are displayed on this tab. It can be used to get a quick overview of what Users are
currently inheriting the Group's settings at this time. Currently, Users cannot be added or removed from the Group using this interface. Adding or
removing a Group membership must be done from the appropriate User's account properties window.
::END
$SYSTEM_VARIABLES_HEADER$=System Variables
$SYSTEM_VARIABLES_BODY1$::
Certain configurable messages in Serv-U can be customized to include a wide range of variables as outlined in the list below. These variables are replaced
at run-time with the appropriate value allowing up-to-date statistics and feedback to be provided to logged in Users. Some of the places where these
variables can be used include in Event messages, a customized FTP command response, or a Welcome Message.
All available variables and a short explanation of each is included below. Statistical information, unless otherwise specified, is calculated since the
Serv-U File Server was last started.
::END
$SYS_VARS_SERVER_INFO$=Server Information
$SYS_VARS_SERVER_INFO_LIST$::
$ServerName - The full name of the server, (i.e., Serv-U)
$ServerVersionShort - The first two digits of the current version of the Serv-U File Server, (e.g., 7.0)
$ServerVersionLong - The full version number of the Serv-U File Server, (e.g., 7.0.0.3)
$OS - The name of the operating system, (e.g., Windows XP)
$OSVer - The full version number of the operating system, (e.g., 5.1.2600)
::END
$SYS_VARS_SERVER_INFO_LIST_FUTURE_FEATURE$::
$ComputerName - The name of the computer retrieved from the operating system, normally the same as the UNC name on a Windows network (e.g., WEB-SERVER-01)
$LogFilePath - Retrieves the path to the log file (Log File Deleted Event only)
::END
$SYS_VARS_SERVER_STATS$=Server Statistics
$SYS_VARS_SERVER_STATS_LIST$::
$ServerDays - The total number of days the Server has been online continuously
$ServerHours - The number of hours from 0 to 24 the Server has been online, carries over to $ServerDays
$ServerMins - The number of minutes from 0 to 60 the Server has been online, carries over to $ServerHours
$ServerSecs - The number of seconds from 0 to 60 the Server has been online, carries over to $ServerMins
$ServerKBup - The total number of kilobytes uploaded
$ServerKBdown - The total number of kilobytes downloaded
$ServerFilesUp - The total number of files uploaded
$ServerFilesDown - The total number of files downloaded
$ServerFilesTot - The total number of files transferred, essentially ($ServerFilesUp + $ServerFilesDown)
$LoggedInAll - The total number of established sessions
$ServerUploadAvgKBps - The average upload rate in KB/s
$ServerDownloadAvgKBps - The average download rate in KB/s
$ServerAvg - The average data transfer rate (uploads and downloads) in KB/s
$ServerUploadKBps - The current upload transfer rate in KB/s
$ServerDownloadKBps - The current download transfer rate in KB/s
$ServerKBps - The current aggregate data transfer rate in KB/s
$ServerSessions24HPlusOne - The total number of sessions in the past 24 hours plus one additional session
$ServerSessions24H - The total number of sessions in the past 24 hours
::END
$SYS_VARS_DOMAIN_STATS$=Domain Statistics
$SYS_VARS_DOMAIN_STATS_LIST$::
$DomainKBup - The total number of kilobytes uploaded
$DomainKBdown - The total number of kilobytes downloaded
$DomainFilesUp - The total number of files uploaded
$DomainFilesDown - The total number of files downloaded
$DomainFilesTot - The total number of files transferred, essentially ($DomainFilesUp + $DomainFilesDown)
$DomainLoggedIn - The total number of sessions currently connected
$DomainUploadAvgKBps - The average upload rate in KB/s
$DomainDownloadAvgKBps - The average download rate in KB/s
$DomainAvg - The average aggregate data transfer rate (uploads and downloads) in KB/s
$DomainUploadKBps - The current upload transfer rate in KB/s
$DomainDownloadKBps - The current download transfer rate in KB/s
$DomainKBps - The current aggregate data transfer rate in KB/s
$DomainSessions24HPlusOne - The total number of sessions in the past 24 hours plus one additional session
$DomainSessions24H - The total number of sessions in the past 24 hours
::END
$SYS_VARS_USER_STATS$=User Statistics - Applies to all sessions attached to the User account
$SYS_VARS_USER_STATS_LIST$::
$UserKBUp - The total number of kilobytes uploaded
$UserKBDown - The total number of kilobytes downloaded
$UserKBTot - The total amount of kilobytes transferred
$UserLoggedIn - The total number of sessions
$UserUploadAvgKBps - The average upload rate in KB/s
$UserDownloadAvgKBps - The average download rate in KB/s
$UserAvg - The average aggregate data transfer rate (uploads and downloads) in KB/s
$UserUploadKBps - The current upload transfer rate in KB/s
$UserDownloadKBps - The current download transfer rate in KB/s
$UserKBps - The current aggregate data transfer rate in KB/s
$UserSessions24HPlusOne - The total number of sessions in the past 24 hours plus one additional session
$UserSessions24H - The total number of sessions in the past 24 hours
::END
$SYS_VARS_LAST_TRANSFER_STATS$=Last Transfer Statistics - Applies to the most recently completed successful data transfer
$SYS_VARS_LAST_TRANSFER_STATS_LIST$::
$TransferBytesPerSecond - The effective (compressed) transfer rate in bytes/s
$TransferKBPerSecond - The effective (compressed) transfer rate in KB/s
$TransferBytes - The effective (compressed) number of bytes transfered, formatted for display, e.g., 32,164
$NoFormatTransferBytes - The effective (compressed) number of bytes transfered, unformatted, e.g., 32164
$TransferKB - The effective (compressed) number of kilobytes transfered, formatted for display
$ActualTransferBytesPerSecond - The actual (uncompressed) transfer rate in bytes/s
$ActualTransferKBPerSecond - The actual (uncompressed) transfer rate in KB/s
$ActualTransferBytes - The actual (uncompressed) number of bytes transfered, formatted for display, e.g., 32,164
$NoFormatActualTransferBytes - The actual (uncompressed) number of bytes transfered, unformatted, e.g. 32164
$ActualTransferKB - The actual (uncompressed) number of kilobytes transfered, formatted for display
$CompressionRatio - The ratio of compression for the transfer expressed as a percentage of the expected amount of data transfered. For example, a value of 100.00 means the data could not be compressed. A value of 200.00 means the data compressed to half its original size.
$CurrentCompressedTransferBytes - The current effective (compressed) number of bytes transfered so far, unformatted, e.g., 32164 (FTP only)
$CurrentUncompressedTransferBytes - The current actual (uncompressed) number of bytes transfered so far, unformatted, e.g. 32164 (FTP only)
::END
$SYS_VARS_DATE$=Date/Time
$SYS_VARS_DATE_LIST$::
$Date - The current date according to the Serv-U File Server, in the system's local date format
$Time - The current time according to the Serv-U File Server, in the system's local time format
::END
$SYS_VARS_SERVER_SETTINGS$=Server Settings
$SYS_VARS_SERVER_SETTINGS_LIST$::
$MaxUsers - The maximum number of sessions allowed to login, which could be limited by the license
$MaxAnonymous - The maximum number of anonymous users allowed to login
::END
$SYS_VARS_USER_INFO$=Session Information - Applies to the current session
$SYS_VARS_USER_INFO_LIST$::
$Name - The login ID of the attached User account
$IP - The client IP address
$IPName - The reverse DNS name as obtained by performing a reverse DNS lookup on $IP
$Dir - The session's current directory
$Disk - The local drive letter being accessed
$DFree - The amount of free space on $Disk in MB
$FUp - The total number of files uploaded
$FDown - The total number of files downloaded
$FTot - The total number of files transferred, essentially ($FUp + $FDown)
$BUp - The total number of kilobytes uploaded
$Bdown - The total number of kilobytes downloaded
$BTot - The total number of kilobytes transferred
$TConM - The total number of minutes the session has been connected
$TConS - The number of seconds from 0 to 60 that the session has been connected, carries over to $TconM
$RatioUp - The 'upload' portion of the applied ratio, "N/A" if not in use
$RatioDown - The 'download' portion of the applied ratio, "N/A" if not in use
$RatioType - The type of ratio being applied, either per session or per User
$RatioCreditType - The type of ratio credit granted for transfers, either per bytes or per complete file
$RatioCredit - The current transfer credit for the applied ratio, either megabytes or complete files
$QuotaUsed - Displays how much disk quota is currently being used in MB, "Unlimited" if no quota is in use
$QuotaLeft - Displays how much disk quota is available in MB, "Unlimited" if no quota is in use
$QuotaMax - Displays the maximum amount of disk space that can be used in MB, "Unlimited" if no quota is in use
::END
$SYS_VARS_USER_INFO_NOTE$::
NOTE: Using the $IPName variable inside of an event or sign-on message can cause a slight delay while the reverse DNS information for $IP
is retrieved.
::END
$SYS_VARS_USER_INFO_8_0_LIST$::
$Protocol - The current protocol being used (FTP, FTPS, HTTP, HTTPS, or SFTP (SSH2))
$DomainName - The current domain that the session is logged into
$DomainDescription - The description of the current domain that the session is logged into
$TimeRemaining - The time remaining when blocking an IP address for an amount of time (available only in Event notifications)
::END
$SYS_VARS_USER_INFO_LIST_FUTURE$::
$LocalHomeDirectory - The local home directory. It should only be used for events that need this specific information such as user creation.
$Password - The password associated with the user account. It is intended only for events. It should NOT be used for welcome messages.
$UserEmailAddress - The user's email address.
$FullName - The user's full name as entered into the "Full Name" field for a user account.
$SpaceFullName - The same as "$FullName" with the addition of a space before the user's full name. Blank (no space or name) when the user's full name is empty.
$FullNameSpace - The same as "$FullName" with the addition of a space after the user's full name. Blank (no space or name) when the user's full name is empty.
::END
$SYS_VARS_FILE_INFO$=File Information - Applies to the last remotely accessed file, which is not necessarily the last transferred file
$SYS_VARS_FILE_INFO_LIST$::
$PathName - Retrieves the full remote path
$FileName - Retrieves just the filename from $PathName
$FileSize - Retrieves the size, in bytes, of the file from $FileName
::END
$SYS_VARS_FILE_INFO_8_0_LIST$::
$FileSizeFmt - A formatted version of the file size, containing the thousands separator (comma or period depending on the computer's regional settings)
$FileSizeKB - A formatted floating point value representing the file size in KB
$LocalPathName - Retrieves the fully qualified local path name for an operation, as it relates to Windows. For example "C:TempFile.fid" instead of "/Temp/file.fid"
$LocalFileName - Retrieves the name of the file as it is stored on the local computer. See $LocalPathName for details
$OldLocalPathName - Same as $LocalPathName, but contains the path prior to renaming
$OldLocalFileName - Same as $LocalFileName, but contains the file name prior to renaming
$OldPathName - Retrieves the remote path name prior to renaming
$OldFileName - Retrieves the remote file name prior to renaming
::END
$SYS_VARS_USAGE_STATS$=Current Activity
$SYS_VARS_USAGE_STATS_LIST$::
$UNow - The current number of sessions on the Serv-U File Server
$UAll - The total number of sessions that have connected to the Serv-U File Server since it was last started
$U24h - The total number of sessions that have connected to the Serv-U File Server in the last 24 hours
$UAnonAll - The current number of sessions attributed to the anonymous user on the Serv-U File Server
$UAnonThisDomain - The current number of sessions attributed to the anonymous user on the connected Domain
$UNonAnonAll - The current number of sessions not attributed to the anonymous user on the Serv-U File Server
$UNonAnonThisDomain - The current number of sessions not attributed to the anonymous user on the connected Domain
$UThisName - The current number of sessions attributed to the connected User account
::END