From File Service 1.2 onward, it is possible to add a node to the File Service to facilitate access to files on storage not accessible to File Service. This may occur when the File Service is deployed in the cloud but the archive of large files is kept behind a firewall on-premises. 

When an enabled Curator application such as Curator for Adobe 3.4 or Clip Link 3.5 or newer requests a file that File Service cannot access, the File Service will return a redirect pointing to the appropriate FS Node that can access that storage. The application's redirected request then triggers FS Node to obtain the file location from the File Service, and the FS Node retrieves the file from the storage and returns it to the client application.

The prerequisites are the installation of the File Server node of  Microsoft .Net 6.0, .Net Core 3.1 Hosting Bundles, .Net Framework 4.8, IIS, and Web Deploy 3.6. To install and configure the File Service Node, you will need to log on as an admin user to the Curator in a browser from a storage server that requires the FS Node installation. Also, you will need to have privileges to deploy an application in the IIS on that server.

In Curator Gateway configure the Curator File Service Node client. 
You must set the URIs of the nodes as Authorised Redirect URIs.

For Root URI, you may optionally enter an address of one of the Nodes you are going to install so that it can be opened from My apps: https://IIS_NODE1/CuratorFileServiceNode; 

Authorised Redirect URIs, this is the critical address, you need an entry for each of the Nodes. Add an additional line and in each set an address of a node e.g.  
https://IIS_NODE1/CuratorFileServiceNode 
https://IIS_NODE2/CuratorFileServiceNode

 Save the Client (an example is shown below):

In Curator File Service add a node.

Select the Nodes tab and Plus symbol top right to start adding the node:

Use Download Node button to download a preconfigured installer file CuratorFileServiceNode.zip. to your storage server where the node needs to be installed.

Once you have named the node and entered Base URI for CFSNode, select the store that points to the location on the storage server (this will typically be a UNC path that is not accessible from the Curator File Service Server). 

Then select Create.

The created node at this point will show the Status "Registering" () 

Import the downloaded CuratorFileServiceNode.zip to IIS with the Web Deploy in the same way as Installing  Web Applications. Verify that the Application Package Information as preconfigured in the Installer is correct:

Select Next. This completes the installation of a node.

Open the Curator File Service Node address in the browser.

Select Configure. The configured node will show the master File Server address and connection Thumbprint:

 Check on the Curator File Service website. The node should now show the status Configured (ticked).

The selected store will now show a declared Node against it:

This concludes the configuration of a File Service Node.