<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Knowledge Base</title>
    <description />
    <link>https://kb.ctera.com/docs</link>
    <atom:link href="https://kb.ctera.com/rss/en" rel="self" type="application/rss+xml" />
    <item>
      <title>Migrating Shares</title>
      <description>Migrate shares to the CTERA Edge Filer.
The shares are created on the edge filer, and cloud drive folders are created on the portal under root cloud drive folders. The cloud drive folders are not created at the root cloud folder level but at the subfolder level because ACL permissions cannot be managed at the root cloud folder level, only at the subfolder level.
Notes

Before starting a migration, all non-essential features like local deduplication, antivirus,  and CTERA Ransom Protect should be ...</description>
      <pubDate>Tue, 08 Sep 2026 16:10:05 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Edge Filer &gt; 7.13.x (EA Version) &gt; Migrate a File Server to a CTERA Edge Filer</category>
      <link>https://kb.ctera.com/docs/migrating-shares-3-1-1-1-1</link>
      <guid>https://kb.ctera.com/docs/migrating-shares-3-1-1-1-1</guid>
    </item>
    <item>
      <title>Migrating Shares</title>
      <description>Migrate shares to the CTERA Edge Filer.
The shares are created on the edge filer, and cloud drive folders are created on the portal under root cloud drive folders. The cloud drive folders are not created at the root cloud folder level but at the subfolder level because ACL permissions cannot be managed at the root cloud folder level, only at the subfolder level.
Notes

Before starting a migration, all non-essential features like local deduplication, antivirus,  and CTERA Ransom Protect should be ...</description>
      <pubDate>Tue, 08 Sep 2026 16:09:38 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Edge Filer &gt; 7.12.x (GA Version) &gt; Migrate a File Server to a CTERA Edge Filer</category>
      <link>https://kb.ctera.com/docs/migrating-shares-3-1-1-1</link>
      <guid>https://kb.ctera.com/docs/migrating-shares-3-1-1-1</guid>
    </item>
    <item>
      <title>Migrating Shares</title>
      <description>Migrate shares to the CTERA Edge Filer. The shares are created on the edge filer and cloud drive folders are created on the portal under root cloud drive folders. The cloud drive folders are not created at the root cloud folder level but at the subfolder level because ACL permissions cannot be managed at the root cloud folder level, only at the subfolder level.
Notes

Before starting a migration, all non-essential features like local deduplication, antivirus,  and CTERA Ransom Protect should be  ...</description>
      <pubDate>Tue, 08 Sep 2026 16:09:06 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Edge Filer &gt; 7.11.x (GA Version) &gt; Migrate a File Server to a CTERA Edge Filer</category>
      <link>https://kb.ctera.com/docs/migrating-shares-3-1-1</link>
      <guid>https://kb.ctera.com/docs/migrating-shares-3-1-1</guid>
    </item>
    <item>
      <title>CTERA InsightAI</title>
      <description>CTERA InsightAI is a Software as a service (SaaS) tool, hosted by CTERA, that provides the best way to make sure you remain up and running. CTERA InsightAI is deeply integrated with CTERA’s Intelligent Data Platform providing real-time monitoring of CTERA Portal and CTERA Edge Filers, from one central Web-based interface. By delivering end-to-end observability across edge locations, organizations can make data-driven decisions that enhance security, optimize storage, and reduce costs. By knowing ...</description>
      <pubDate>Tue, 08 Sep 2026 15:50:04 GMT</pubDate>
      <category>Product Documentation &gt; CTERA InsightAI</category>
      <link>https://kb.ctera.com/docs/ctera-saas-insight1</link>
      <guid>https://kb.ctera.com/docs/ctera-saas-insight1</guid>
    </item>
    <item>
      <title>Discovering Shares</title>
      <description>Optionally, survey the source file server to discover which shares to migrate.
Note

This article uses an edge filer fully deployed and connected to a portal. For the discovery you can deploy an edge filer that does not have a data disk defined nor is connected to a portal. The following installation is for ESXi but you can also install the edge filer in AWS or Azure using their marketplace or on other platforms, such as Proxmox.
To install the CTERA Edge Filer for discovery in the vSphere Clien ...</description>
      <pubDate>Tue, 08 Sep 2026 14:12:31 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Edge Filer &gt; 7.12.x (GA Version) &gt; Migrate a File Server to a CTERA Edge Filer</category>
      <link>https://kb.ctera.com/docs/discovering-shares-3-1-1-1</link>
      <guid>https://kb.ctera.com/docs/discovering-shares-3-1-1-1</guid>
    </item>
    <item>
      <title>Discovering Shares</title>
      <description>Optionally, survey the source file server to discover which shares to migrate.
Note

This article uses an edge filer fully deployed and connected to a portal. For the discovery you can deploy an edge filer that does not have a data disk defined nor is connected to a portal. The following installation is for ESXi but you can also install the edge filer in AWS or Azure using their marketplace or on other platforms, such as Proxmox.
To install the CTERA Edge Filer for discovery in the vSphere Clien ...</description>
      <pubDate>Tue, 08 Sep 2026 14:12:05 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Edge Filer &gt; 7.13.x (EA Version) &gt; Migrate a File Server to a CTERA Edge Filer</category>
      <link>https://kb.ctera.com/docs/discovering-shares-3-1-1-1-1</link>
      <guid>https://kb.ctera.com/docs/discovering-shares-3-1-1-1-1</guid>
    </item>
    <item>
      <title>Automatically Assigning Plans</title>
      <description>Automatic plan assignment allows you to define a policy that determines which subscription plans will be assigned to which users.
You can automatically assign subscription plans based on the following user attributes:

Username
User Groups
Role
First Name
Last Name
Company
Billing ID
Comment

The policy rules are processed in ascending order. The first rule that matches applies. You can change the rules’ order by using the Move Down/Move Up buttons. You can also choose to apply a default plan in ...</description>
      <pubDate>Tue, 08 Sep 2026 13:00:28 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Portal &gt; 8.4.x (EA Version) &gt; Team Administrator Guide &gt; Provisioning</category>
      <link>https://kb.ctera.com/docs/automatically-assigning-plans-6-1-1</link>
      <guid>https://kb.ctera.com/docs/automatically-assigning-plans-6-1-1</guid>
    </item>
    <item>
      <title>Configuring the CTERA Portal as a Precondition to Setting Up the CTERA Edge Filer</title>
      <description>Before setting up the CTERA Edge Filer, the CTERA Portal administrator has to configure the CTERA Portal to which the CTERA Edge Filer will connect.
To configure the CTERA Portal:

Sign in to the CTERA Portal as a team portal administrator.

In a Web browser open http://&lt;virtualportal_name&gt;.&lt;DNS_Suffix&gt;/ServicesPortal.
where, &lt;virtualportal_name&gt; is the name of the portal, and &lt;DNS_Suffix&gt; is the DNS suffix for the CTERA Portal installation.
This opens the interface to the portal.
Note

If the C ...</description>
      <pubDate>Tue, 08 Sep 2026 12:43:03 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Edge Filer &gt; 7.11.x (GA Version) &gt; First Time Setup</category>
      <link>https://kb.ctera.com/docs/configuring-the-ctera-portal-as-a-precondition-to-setting-up-the-ctera-edge-filer-4-1-1</link>
      <guid>https://kb.ctera.com/docs/configuring-the-ctera-portal-as-a-precondition-to-setting-up-the-ctera-edge-filer-4-1-1</guid>
    </item>
    <item>
      <title>Configuring the CTERA Portal as a Precondition to Setting Up the CTERA Edge Filer</title>
      <description>Before setting up the CTERA Edge Filer, the CTERA Portal administrator has to configure the CTERA Portal to which the CTERA Edge Filer will connect.
To configure the CTERA Portal:

Sign in to the CTERA Portal as a team portal administrator.

In a Web browser open http://&lt;virtualportal_name&gt;.&lt;DNS_Suffix&gt;/ServicesPortal.
where, &lt;virtualportal_name&gt; is the name of the portal, and &lt;DNS_Suffix&gt; is the DNS suffix for the CTERA Portal installation.
This opens the interface to the portal.
Note

If the C ...</description>
      <pubDate>Tue, 08 Sep 2026 12:42:39 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Edge Filer &gt; 7.12.x (GA Version) &gt; First Time Setup</category>
      <link>https://kb.ctera.com/docs/configuring-the-ctera-portal-as-a-precondition-to-setting-up-the-ctera-edge-filer-4-1-1-1</link>
      <guid>https://kb.ctera.com/docs/configuring-the-ctera-portal-as-a-precondition-to-setting-up-the-ctera-edge-filer-4-1-1-1</guid>
    </item>
    <item>
      <title>Configuring the CTERA Portal as a Precondition to Setting Up the CTERA Edge Filer</title>
      <description>Before setting up the CTERA Edge Filer, the CTERA Portal administrator has to configure the CTERA Portal to which the CTERA Edge Filer will connect.
To configure the CTERA Portal:

Sign in to the CTERA Portal as a team portal administrator.

In a Web browser open http://&lt;virtualportal_name&gt;.&lt;DNS_Suffix&gt;/ServicesPortal.
where, &lt;virtualportal_name&gt; is the name of the portal, and &lt;DNS_Suffix&gt; is the DNS suffix for the CTERA Portal installation.
This opens the interface to the portal.
Note

If the C ...</description>
      <pubDate>Tue, 08 Sep 2026 12:41:52 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Edge Filer &gt; 7.13.x (EA Version) &gt; First Time Setup</category>
      <link>https://kb.ctera.com/docs/configuring-the-ctera-portal-as-a-precondition-to-setting-up-the-ctera-edge-filer-4-1-1-1-1</link>
      <guid>https://kb.ctera.com/docs/configuring-the-ctera-portal-as-a-precondition-to-setting-up-the-ctera-edge-filer-4-1-1-1-1</guid>
    </item>
    <item>
      <title>Change the Device Connectivity Port from TCP 995</title>
      <description>By default, a CTERA Edge Filer and CTERA Drive Share/Protect (Agent) establish a connection and perform cloud backup and synchronization with CTERA Portal over port TCP 995. These devices can be configured to connect to the CTERA Portal over a different port by changing this default port in the portal configuration.
Step-by-step guide
To change the default port used by devices to connect to the portal:

Access the DNS Manager and for the portal server click Forward Lookup Zones.
Open the domain  ...</description>
      <pubDate>Tue, 08 Sep 2026 11:17:14 GMT</pubDate>
      <category>How-tos &gt; CTERA Portal How-tos</category>
      <link>https://kb.ctera.com/docs/how-to-8</link>
      <guid>https://kb.ctera.com/docs/how-to-8</guid>
    </item>
    <item>
      <title>Setting Up CTERA Ransom Protect</title>
      <description>You can enable the behavioral engine and the honeypot engine independently of each other.
To enable Ransom Protect: behavior and honeypot engines:

In the Configuration view, select Security &gt; Ransom Protect in the navigation pane.
The Ransom Protect page is displayed.

Click Settings.

To enable setting ransomware protection, slide Enable Behavioral Detection on.

The Detection Threshold is the number of suspicious events that must occur before ransomware protection is triggered. If the thresho ...</description>
      <pubDate>Tue, 08 Sep 2026 10:42:33 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Edge Filer &gt; 7.9.x (GA Version) &gt; Administrator Guide &gt; Protecting the Data &gt; Ransomware Protection: CTERA Ransom Protect</category>
      <link>https://kb.ctera.com/docs/setting-up-ctera-ransom-protect-1</link>
      <guid>https://kb.ctera.com/docs/setting-up-ctera-ransom-protect-1</guid>
    </item>
    <item>
      <title>Blocking Malicious Users</title>
      <description>Users that you suspect of triggering ransomware attacks can be blocked by adding them to a Blocked Users group. Blocked users are prevented from accessing the edge filer by all authenticated protocols, including SMB, NFS, FTP, and the edge filer user interface.
Users can be blocked automatically or manually. Users that trigger a ransomware incident can be automatically added to a Blocked Users group.
Note

When users are added to the Blocked Users group, their existing SMB sessions are immediate ...</description>
      <pubDate>Tue, 08 Sep 2026 10:40:32 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Edge Filer &gt; 7.9.x (GA Version) &gt; Administrator Guide &gt; Protecting the Data &gt; Ransomware Protection: CTERA Ransom Protect</category>
      <link>https://kb.ctera.com/docs/blocking-malicious-users-2-1</link>
      <guid>https://kb.ctera.com/docs/blocking-malicious-users-2-1</guid>
    </item>
    <item>
      <title>Red Hat OpenShift</title>
      <description>Installing the CTERA Edge Filer in a Red Hat OpenShift Environment
Installing the CTERA Edge Filer involves creating and configuring a virtual machine and then performing an initial configuration, described in First Time Setup.
The CTERA Edge Filer can be installed in a Red Hat OpenShift environment.
Contact CTERA, and request the latest qcow2 CTERA Edge Filer disk image. Add this image to the machine where you run the Red Hat OpenShift console.
Warning

The CTERA Edge Filer installation must be ...</description>
      <pubDate>Sun, 06 Sep 2026 12:41:51 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Edge Filer &gt; 7.13.x (EA Version) &gt; Installing a CTERA Edge Filer &gt; Additional Platforms</category>
      <link>https://kb.ctera.com/docs/red-hat-openshift-2</link>
      <guid>https://kb.ctera.com/docs/red-hat-openshift-2</guid>
    </item>
    <item>
      <title>Red Hat OpenShift</title>
      <description>Installing the CTERA Edge Filer in a Red Hat OpenShift Environment
Installing the CTERA Edge Filer involves creating and configuring a virtual machine and then performing an initial configuration, described in First Time Setup.
The CTERA Edge Filer can be installed in a Red Hat OpenShift environment.
Contact CTERA, and request the latest qcow2 CTERA Edge Filer disk image. Add this image to the machine where you run the Red Hat OpenShift console.
Warning

The CTERA Edge Filer installation must be ...</description>
      <pubDate>Sun, 06 Sep 2026 12:40:03 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Edge Filer &gt; 7.12.x (GA Version) &gt; Installing a CTERA Edge Filer &gt; Additional Platforms</category>
      <link>https://kb.ctera.com/docs/red-hat-openshift-1</link>
      <guid>https://kb.ctera.com/docs/red-hat-openshift-1</guid>
    </item>
    <item>
      <title>Customizing Administrator Roles</title>
      <description>By default, CTERA Portal includes built-in roles for administrators. CTERA Portal includes the following roles for global administrators:
Compliance Officer  – The administrator can manage CTERA Vault on folders. For details, see Folder (WORM) Compliance: CTERA Vault.
Read Only Administrator – The administrator has read-only permissions throughout the portal.
Read/Write Administrator – The administrator has read/write permissions throughout the portal.
Support – The administrator has read/write  ...</description>
      <pubDate>Sun, 06 Sep 2026 12:26:24 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Portal &gt; 8.4.x (EA Version) &gt; Global Administrator Guide &gt; Managing Global Administrators</category>
      <link>https://kb.ctera.com/docs/customizing-administrator-roles-5-1-1</link>
      <guid>https://kb.ctera.com/docs/customizing-administrator-roles-5-1-1</guid>
    </item>
    <item>
      <title>Adding the CTERA MCP Server to an AI Agent</title>
      <description>The MCP client, such as Claude Desktop, used to communicate with CTERA MCP Server, must be configured for secure access to the CTERA MCP Server. Once connected, the MCP client will be able to perform actions on the specific portal which has the CTERA MCP Server enabled. Security is enabled using OAuth 2.0. All access to the CTERA MCP Server is authorized by OAuth 2.0.
Only those tools listed in the MCP Server Settings page are availble, such as creating an item, copying, moving, or renaming an i ...</description>
      <pubDate>Sun, 06 Sep 2026 11:02:17 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Portal &gt; 8.3.3300x (GA Version) &gt; Global Administrator Guide &gt; CTERA Services &gt; Managing the MCP Server Service</category>
      <link>https://kb.ctera.com/docs/using-the-ctera-mcp-server</link>
      <guid>https://kb.ctera.com/docs/using-the-ctera-mcp-server</guid>
    </item>
    <item>
      <title>Adding the CTERA MCP Server to an AI Agent</title>
      <description>The MCP client, such as Claude Desktop, used to communicate with CTERA MCP Server, must be configured for secure access to the CTERA MCP Server. Once connected, the MCP client will be able to perform actions on the specific portal which has the CTERA MCP Server enabled. Security is enabled using OAuth 2.0. All access to the CTERA MCP Server is authorized by OAuth 2.0.
Configuring Access to the CTERA MCP Server
You configure access to the CTERA MCP server after enabling AI integrations.

In the g ...</description>
      <pubDate>Sun, 06 Sep 2026 11:01:55 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Portal &gt; 8.4.x (EA Version) &gt; Global Administrator Guide &gt; AI Content Services &gt; Managing AI Integrations</category>
      <link>https://kb.ctera.com/docs/using-the-ctera-mcp-server-1</link>
      <guid>https://kb.ctera.com/docs/using-the-ctera-mcp-server-1</guid>
    </item>
    <item>
      <title>Managing AI Integrations</title>
      <description>CTERA Portal has a built in Model Context Protocol (MCP) server and n8n Filesystem Node.
You require two NICs for each portal server to use the CTERA MCP server or n8n. In order not to compromise security, the internal NIC must not be accessible from the external network.
Both NICs can be on the same VLAN but the internal NIC must have a different IP than the external NIC. CTERA strongly recommends a separate VLAN or proper firewall rules.
By default, the NICs are eth0 for the external interface ...</description>
      <pubDate>Sun, 06 Sep 2026 11:00:01 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Portal &gt; 8.4.x (EA Version) &gt; Global Administrator Guide &gt; AI Content Services &gt; Managing AI Integrations</category>
      <link>https://kb.ctera.com/docs/managing-the-mcp-server-service-1</link>
      <guid>https://kb.ctera.com/docs/managing-the-mcp-server-service-1</guid>
    </item>
    <item>
      <title>Managing the MCP Server Service</title>
      <description>The Model Context Protocol (MCP) is an open standard designed to let AI assistants and agents securely interact with enterprise systems through natural language.
The Model Context Protocol (MCP) in CTERA lets AI assistants and agents securely interact with the CTERA platform as a framework for defining and managing a variety of context-based configurations across the platform. This feature facilitates dynamic policy enforcement and adaptive user experiences by leveraging contextual data to tailo ...</description>
      <pubDate>Sun, 06 Sep 2026 10:58:00 GMT</pubDate>
      <category>Product Documentation &gt; CTERA Portal &gt; 8.3.3300x (GA Version) &gt; Global Administrator Guide &gt; CTERA Services &gt; Managing the MCP Server Service</category>
      <link>https://kb.ctera.com/docs/managing-the-mcp-server-service</link>
      <guid>https://kb.ctera.com/docs/managing-the-mcp-server-service</guid>
    </item>
  </channel>
</rss>