Installing Aligned Elements Web Server
  • Elements SPA Installation
  • Preparing the Windows Server
    • Before you get started
    • Install and Configure SQL Server for Aligned Elements
    • Install .NET 4.8
    • Install/Activate the IIS
    • Enable ASP.NET 4.5/4.6/4.7
    • Optional: IIS Always running part 1
    • Installing Web Platform Installer and Web deploy
    • Install URL Rewrite Module
    • Install IIS Crypto to disable Weak Ciphers and Protocols
  • Deploying the Aligned Elements Web Solution
    • Install the Aligned Elements Web Server Package
    • Setting HTTP Strict Transport Security (HSTS)
    • Optional: Open Ports in the Network on Azure hosted Virtual Machines
    • Optional: Get a SSL certificate from Let’s Encrypt
    • Binding your SSL certificate to the Aligned Elements web site
    • Creating the „Temp“ and „Files“ directories
    • Remove stdole.dll from bin directory
    • Move ElementsSPA.xml from the "App_Data" folder to the "bin" folder
    • Add the Aligned Elements License Files
    • Set the necessary security permissions for directories
    • Optional: IIS Always running part 2
    • Install necessary Unicode Font
    • Install and Configure File Server Resource Manager
  • Configure Application Options in web.config
    • Configure Application Options in web.config
    • Set the Server and connection string
    • Always Require SSL
    • Referring to the Project Templates
    • Email Configuration
    • Word Add-in Configuration and deployment
      • Distribute an Add-in using the Office 365 admin center
      • Distribute the Add-in using sideloading for Windows
      • Distribute the Add-in using sideloading for Mac
    • Optional: Integration of the Aligned Elements Automation Tool
      • Importing Dashboards with Rename using the Automation Script
    • Optional: Enabling Active Directory Integration
  • Optional: Configuration of AI Features
  • Optional: Enable editing of Configuration Sections from the UI
  • Create an Initial User
    • Option 1: Aligned Elements Projects already exist
    • Option 2: New Web server, no Aligned Elements Projects exist
  • Upgrading the Aligned Elements Web Server
    • Upgrading a Server
  • Troubleshooting
    • Generic Server Error
    • Missing version of stdole.dll
    • Missing Dependencies for Txic.dll
    • Error shown: Could not load file or assembly “System.Net.Http”
    • 500 Internal Server Error
    • Error when trying to start application
    • The server is not starting after upgrading to v2.5 SP 4 Part 1
    • The server is not starting after upgrading to v2.5 SP 4 Part II
    • Load a project works but when clicking on a design Item, you are re-directed to the login
    • The application cannot connect to the license server
    • The urls in email notifications are incorrect/missing port information
    • Missing Font
    • Mismatch of server name between Windows-client and Web.
  • Cannot upload Templates
  • Running 'ElementsSPAPackage.deploy.cmd' closes the Command-Prompt window
  • Web.config Settings
    • Settings of the Web.config
  • Configuring Aligned Elements
    • Introduction to rvt templates
    • Type Info Element
    • Compulsory Trace Holders Element
  • Attributes Element
    • String Attribute
    • Enum Attribute
    • Rich Text Attribute
    • Dynamic List Attribute
    • Multiselect Attribute
    • Enum User Attribute
    • Date Time Attribute
    • Boolean Attribute (Checkbox)
    • Int Attribute
    • Double Attribute
    • Int Range Attribute
    • File Attribute
    • Table Attribute
    • Traced Objects Attribute
    • Approval Attribute
  • Trace Holders Element
  • Positive Cues Element
  • Validation Rules Element
    • Traced To Rule
    • Traced From Rule
    • Illegal Trace To Rule
    • Illegal Trace From Rule
    • Obsolete Linked Trace Rule
    • Suspect Trace Rule
    • Missing Execution In TestRun Rule
    • Incoming Suspect Trace Rule
    • Object In File Rule
    • Objects In File Up To Date Rule
    • Not Reviewed Rule
    • Object In Completed Signature Rule
    • Has Open Issue Rule
    • Related Attribute Value Rule
    • Date Overdue Rule
    • Executed From Last Revision Rule
    • Signature Missing Rule
    • Linked Attribute Value Rule
    • Objects In File Not Reviewed Rule
  • Attribute Workflows
    • Sign Action
    • Email Action
    • Set Attribute Action
    • Copy File Action
    • Lock Action
    • Unlock Action
    • Generate Object Action
    • Add PDF Footer
Powered by GitBook
On this page
  • Install the File Server Resource Manager
  • Configure the File Server Resource Manager
  • Create a File Group for the Temp folder
  • Create File Screens
  • Create a File Screen for the Files folder
  • Create a File Screen for the Temp folder
  • Create a File Screen for the Tests folder

Was this helpful?

  1. Deploying the Aligned Elements Web Solution

Install and Configure File Server Resource Manager

PreviousInstall necessary Unicode FontNextConfigure Application Options in web.config

Last updated 1 year ago

Was this helpful?

Install the File Server Resource Manager

To isolate and protect the area where user uploaded files reside, we will install the Windows File Server Resource Manager. Similar to the IIS, this application is already available on Windows Servers and just needs to be activated.

1. On your Windows Server, open Server Manager and select the Dashboard. Click Add roles and features.

2. Click Installation Type => Role-based or feature-based installation and then click Next.

3. On the Server Selection dialog box, click Select a server from the server pool. In the Server Pool list, select your server and then click Next.

4. In Server Roles, find the entry File Storage Services and expand the node tree. Find the sub-node File and iSCSI Services and expand it. Select the checkboxes for File Server Resource Manager. Click Next.

  1. In the Features section, click Next.

  2. In the Confirmation section, click Install and wait for the installation to finish.

Configure the File Server Resource Manager

On your Windows Server, open Server Manager and select the Dashboard. Click Tools and find the File Server Resource Manager, click to open it.

We can use the File Server Resource manager to prevent files of certain types to be uploaded and executed on the server by a malicious user.

Create a File Group for the Temp folder

The File Server Resource manager supplies a number of standard file groups that we can use, but a special File group is needed for the Temp folder.

To create a designate File Group for the Temp folder, right-click on the File Group Node and select Create File Group...

In the displayed dialog, enter the File Group Name "Web Page Files in Temp".

Add the following files to include in the group:

  • *.asp

  • *.aspx

  • *.cgi

  • *.css

  • *.dhtml

  • *.hta

  • *.htm

  • *.mht

  • *.php

  • *.php3

  • *.shtml

  • *.url

Save the File Group.

Create File Screens

The next step is to define File Screen for the three folders:

  • Files

  • Temp

  • Tests

Create a File Screen for the Files folder

Right-click on the File Screens node and select Create File Screen.

In the File screen path, type or browser to the path of the Files folder.

Click the button Custom Properties... and:

  • Select Active Screening

  • Select the File Groups Executable Files and Web Page Files

Click on the tab Event Log and check the checkbox Send Warning to event log. Then click OK.

Create a File Screen for the Temp folder

Create another File screen and in this case:

  • Browse to / type in the path to the Temp folder

  • Select the File groups Executable Files and Web Page Files in Temp

Create a File Screen for the Tests folder

Create another File screen and in this case:

  • Browse to / type in the path to the Tests folder

  • Select the File groups Executable Files and Web Page Files

When finished, the File Server Resource Manager should look like the image below.