Skip to main content

File Server

Register, secure, and manage file servers used for patch storage, distribution, and upgrades.

The File Server is designed to streamline the registration, management, and secure communication of file servers with ServiceOps. It includes the following tabs:

  • Configuration: Configure patch cleanup and storage alert settings.
  • Server List: Displays a list of all the installed and connected file servers with options to test connectivity, edit, delete, or upgrade them in bulk using packages from the File Server Build tab.
  • Credential Profile: Enables the creation and management of credentials required to establish a secure connection between ServiceOps and the file servers.
  • File Server Build: Enables to upload the file server packages with builds supported from v8.6.4 onwards.

This enhanced structure improves visibility and strengthens security. Previously, communication between file servers and ServiceOps occurred without authentication, posing a potential risk and limiting UI visibility. With this new approach, all file server installations must be authorized via the Credential Profile, ensuring a more secure and manageable setup.

note
  • From version 8.6.5, backward compatibility with older file servers has been discontinued. It is now mandatory to upgrade all existing file servers to the latest build to ensure continued functionality and integration with ServiceOps.
  • If a file server becomes unavailable or goes offline during an ongoing download task, the system will automatically resume the download once the file server becomes available again.

Configuration​

Use the Configuration tab to manage patch cleanup and storage alert settings for the file server.

You can configure the following options:

  1. Remove Superseded Patches: Automatically deletes patches from the file server that have been replaced by newer versions released by the vendor. Enabling this helps conserve storage space and ensures only the most current patches are available for deployment. This option is disabled by default.
  2. Remove Older Patches: Configures the system to automatically delete patches that are older than a specified number of months, calculated from their release date. When enabled, specify the Older Releases (Months) value. This feature helps maintain a lean patch repository by removing outdated patches. This option is disabled by default.
  3. Notify On Space Over Utilization: Activates a notification system that alerts specified recipients when the file server's storage usage exceeds a predefined threshold. This proactive alert helps prevent storage-related issues that could impact patch distribution. When enabled, the following parameters can be configured:
    • Threshold Size (GB): Define the maximum storage size in Gigabytes (GB) that the file server can utilize before a notification is triggered.
    • Notify To: Select the recipients who will receive these notifications form the dropdown. You can select multiple recipients.

When you are done, click Update to save the changes.

note

From v8.6.5 the URL field and Test Connection button have been removed from Patch Storage Configuration page to eliminate redundancy; connection testing can now be performed directly from the File Server list page via the new Test Connection action for each file server.

Test Connection Behavior Based on Version:

  • For versions earlier than v8.6.2: The system tests the File Server connection using the URL specified directly in the URL field.

  • For version v8.6.2 to v8.6.4:

    • If a File Server is configured under Patch Management > Deployment Management > Remote Offices > Local Office, the system prioritizes this setting and performs the Test Connection against the File Server defined there—even if a URL is specified in the Patch Storage Configuration.
    • If no File Server is defined in the Local Office configuration, the system defaults to testing the connection using the URL specified in the Patch Storage Configuration.

    Test Connection

Server List​

Displays a list of all installed and connected file servers (Windows and Linux) with options to test connectivity, edit, delete, or upgrade them in bulk using packages from the File Server Build tab. A green indicator signifies an active file server, while a yellow indicator denotes an inactive one. For more details on installation, refer to the File Server Installation section. This allows administrators to monitor the file servers currently in use and ensure they are properly integrated with the system.

The table below provides details about the installed and connected file servers:

ParameterDescription
NameThe unique name assigned to the file server. You can edit the name of the file server.
Host NameThe hostname of the server where the file server is installed.
IP AddressThe IP address of the file server.
File Server UrlThe URL used to access the file server. You can edit the URL of the file server.
OSThe operating system running on the file server (e.g., Microsoft Windows, Ubuntu).
Last Sync DateThe date and time when the file server last synchronized with ServiceOps. For example: If Mon, Dec 22, 2025 10:00:00 AM, then the last sync date will be Mon, Dec 22, 2025. This will be updated automatically by the system whenever the file server synchronizes with ServiceOps.
Credential ProfileThe credential profile used to establish a secure connection with the file server.
VersionThe version of the file server software installed.
Local File ServerIndicates whether the file server is local (Yes) or remote (No).
ActionsProvides options to perform actions such as testing connectivity, editing server details, or deleting the file server.

To upgrade the file server in bulk, follow the steps below:

  1. Select the file servers you want to upgrade. You can select multiple file servers at once. The version to which the file server will be upgraded is dependent on the version available in the File Server Build tab.
  2. Click Take Action.
  3. Choose the Upgrade option from the dropdown menu.
  4. The upgrade process will be initiated.
  5. You can view the upgrade status on the File Server Build History page.

Credential Profile​

This tab enables the creation and management of credentials required to establish a secure connection between ServiceOps and the File servers. These credentials are used to generate an authorization key, which is essential during the file server installation. It also provides a default credential which can be used directly while installation.

Here, you have the below options:

  1. Search: You can search for the required credential profiles.
  2. Filter: You can filter the profiles by selecting the desired option. The options are: All, - Enabled, Disabled, and Archived.
  3. Refresh: You can refresh the credential profiles list to view the latest one.
  4. Add Credential Profile: You can create custom credential profiles.
  5. Bulk Archive: you can select multiple credential and archive them in bulk.
  6. Enable/Disable: You can enable or disable the credential. By default it is enabled.
  7. Edit: You can edit the required credential.
  8. Delete: You can delete the required credential. A confirmation dialog will appear. Click Yes to continue or Cancel to stop the process.

Adding Credential Profile

To add a credential profile,

  1. Click the Add Credential Profile button and the following popup appears.

  • Enter the Credential Profile name.
  • Enter a brief description about the profile.
  • Click Add.
  1. Once done the profile will be available on the list page as shown below.

  1. You can now edit this profile and get the Secure Auth key required for File Server installation.

File Server Build​

This tab enables to upload the required File Server build package for auto-upgrade and also view the upgrade history. You can get the File Server Build from the Download Links page.

note

This feature is supported from v8.6.4 onwards.

To upload the build,

  1. Click the Attach files button and upload the required build. Currently, Windows and Linux builds can be uploaded.

  1. Once uploaded, go to the Server List tab.
  2. Select the file servers that must be upgraded.

  1. Choose the Upgrade option and the process will be initiated.
  2. View the process status by clicking the History button.

  1. Once upgraded, the file server version will be updated in the Server List tab as shown below.

After configuring the file server for fetching the patches, it's recommended to configure Patch Control to define approval policies and manage exclusions for the patches. This ensures systematic patch management aligned with your organizational policies.

For details, see Patch Control.