Requirements

inPoint Server System Requirements

Hardware Requirements

• Processor: Quad-Core 2.x GHz (recommended)
• RAM: 16 GB (recommended)
• HDD:
• 75 GB of HDD space for application and log files
• 15% of archived Volume for Fulltext-Index

Software Requirements

• OS:

  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows Server 2019

• .NET versions:

  • 3.5
  • 4.8

• IIS

  • 7.0
  • 8.0
  • 10.0

Windows Server Roles

• Application Server
  • Default Settings
• IIS Features
  • Common HTTP Features:
    • Default Document
    • Directory Browsing
    • HTTP Errors
    • Static Content
    • HTTP Redirection
  • Health and Diagnostics
    • Default Settings
  • Performance:
    • Static Content Compression
    • Dynamic Content Compression
  • Security:
    • Default Setting plus
      • Basic authentication
      • Windows authentication
  • Application development:
    • .NET Extensibility 3.5
    • .NET Extensibility 4.5
    • ASP
    • ASP.NET 3.5
    • ASP.NET 4.5
    • ISAPI Extensions
    • ISAPI Filters

Windows Server Features

• .NET Framework 3.5 Features
  • complete
• .NET Framework 4.5 Features
  • complete
• Windows TIFF IFilter

Database Server

• Supported Products:
  • MS-SQL (Feature: Database Engine Services)
    • 2012, 2014, 2016, 2017, 2019 (use at least Cumulative Update 8)
  • ORACLE 11g, 12c
    • Only Byte Semantics!

Databases

• inPointSRV (Metadata inPoint Archive)
• inPointHS (Metadata inPoint HybridStore)
• User: SQL or Windows Authentication access, owner of the inPoint databases
• Database required user permissions

Service User

inPoint Services user rights:

• Member of the local Administrators group and Distributed COM Users group.
• Assign DCOM Rights on Windows 2012 and above:
• Distributed COM Users -- Local and Remote Access, Launch and Activation

AD synchronization: enable reading the Active Directory deleted objects container when deleting AD users from inPoint

The user who accesses the Active Directory during synchronization is configured in the web.config under the following keys:

web.config:
Path: %installdir%\H&S Heilig und Schubert Software AG\Pam.Storage\Web\web.config

<add key="LDAPAuthenticationDomain" value=""/>
<add key="LDAPAuthenticationUser" value=""/>
<add key="LDAPAuthenticationPassword" value=""/>

For a detailed description please see the LDAP & authentication settings section.

When an Active Directory object is deleted, a small part of the object stays in the deleted objects container for a specified time. By default, only the System account and members of the Administrators group can view the contents of this container. In the case, when the user specified in the LDAPAuthenticationUser web.config key is a non-System account or a non-Administrator account, it's required to modify the permissions on the deleted objects container.

• At the command prompt, type the following command:

dsacls <deleted_object_dn> /takeownership

, where deleted_object_dn is the distinguished name of the deleted objects container of your domain.

Example:

dsacls "CN=Deleted Objects,DC=mydomain,DC=local" /takeownership

• To grant permission to view objects in the Deleted Objects container to a user or a group, type the following command:

dsacls <deleted_object_dn> /G <user_or_group>:<Permissions>

where deleted_object_dn is the distinguished name of the deleted objects container of your domain and user_or_group is the user or group for whom the permission applies, and Permissions is the permission to grant.

Example:

dsacls "CN=Deleted Objects,DC=mydomain,DC=local" /G mydomain\username:LCRP

In this example, the user mydomain\username has been granted List Contents and Read Property permissions for the Deleted Objects container in the mydomain.local domain. These permissions let this user view the contents of the Deleted Objects container, but do not let this user make any changes to objects in this container.

Antivirus

It's required to exclude the following folders from the antivirus scan:

• ElasticSearch
  • Default: C:\ProgramData\Elastic\Elasticsearch (index, data, logs and config folders)
• inPoint.Indexer Temp folder
  • Default: %TEMP%\inPointFT
• inPoint.HybridStore
  • Default: C:\Storage (Storage folder)
  • Default: %TEMP%\hybridStore (Storage temp folder)
• FileConverterPro
  • Default: C:\ProgramData\FileConverterPro
• Axon.ivy
  • Example: C:\Install\AxonIvyEngine8.0.3.2003061030_Windows_x64\logs (Logs)
  • Example: C:\Install\AxonIvyEngine8.0.3.2003061030_Windows_x64\elasticsearch (ElasticSearch)

Other Requirements

• Read/write access to the store location for the configured user accounts
• inPoint Server cannot be installed directly on a "Windows domain controller".
  There is a separate domain controller needed for the user administration.
• Active Directory is required for the inPoint installation
• All of the users should have a UPN which must be unique in the domain. Details

inPoint Search Server

Recommendation is to have an additional (separated) Search Server and not to install it on the same inPoint.Server hardware. This can optionally also run the Indexer Service.

Hardware requirements

Software requirements

inPoint.Web

Please see the inPoint.Web documentation for more details.

inPoint Workflow Engine

System requirements

inPoint.CloudSync

inPoint.CloudSync is based on ".NET Core 3.1" but the setup includes all components.

Software Requirements

• OS:

  • Windows Client: 7, 8.1, 10 (1607) or later
  • Windows Server: 2012 R2 or later

• .NET version:

  • 3.5 or later (required for the setup itself)

inPoint Client

inPoint.Client (Windows)

Optional installation - requires inPoint.Server installation.

inPoint.Client - Windows Standalone, Windows Outlook Add-in, Windows Office Integrations

• OS: Windows 8.1, Windows 10 starting Anniversary Update, any inPoint.Server supported OS
• .NET Framework 4.7.2
• Office 2010, 2013, 2016, 2019 and Office 365 Pro Plus (x86 and x64)
• Visual Studio 2010 Tools for Office Runtime (VSTO 2010)

inPoint.Web (Browser)

Optional installation - requires inPoint.Web.Identity and inPoint.Web.Server installations / configuration.

For security reasons we recommend to use the latest available web browser versions.

Most other web browser that support the latest JavaScript, Html 5 and CSS 3 specifications will work too.

inPoint.Web supports the following Browsers (current stable version and the previous current stable version are supported)

• Google Chrome 36 (Windows, iOS, Android)
• Firefox 29 (Windows, Android)
• MS Edge 13.0 (Windows, Android)
• Safari 9 (iOS)
• Opera 23.0 (Windows)
• Android 4.4
• iOS 7.1
• MS Internet Explorer 11 (Windows)
• Samsung Browser 4
• Blackberry 10

inPoint.Web can also integrate with inPoint.Sync (part of inPoint.Client Windows installation), but only on Windows OS.

inPoint CSE 3.9 Content Server for Exchange

The following prerequisites are needed additional to the general prerequisites if you would like to archive emails with the inPoint CSE Content Server for Exchange.

Software Requirements

• MS Outlook 2013 x64, MS Outlook 2016 x64, MS Outlook 2019 x64

Supported MS Exchange server versions

• MS Exchange 2010, MS Exchange 2013, MS Exchange 2016, MS Exchange 2019
• Exchange Web Services (EWS)
• Exchange Online - Office 365

Note: The EWS user must have at least View-only organization management rights on the Exchange (required by the Email Archive provisioning). Organization management rights are required if Mail app is also used.

Additional Databases

• Databases:

  • inPointcA (Metadata central Administration)
  • inPointcA01 (Metadata inPoint eMail Archive)

Service User

inPoint CSE MS Exchange services user rights

• Read rights over the Configuration Container in Active Directory.

External Accessibility

In case of using OWA/WebAPP or mobile Access also for archived items, it is necessary, the inPoint Content Server Proxy is accessible from external. The Proxy can be installed on an existing server, which is accessible from external, on a separate server (also in DMZ) or on the inPoint Content Server itself.

The communication is secured by SSL; therefore, a valid SSL Certificate is necessary. We recommend also using a DNS alias for the Proxy like inPoint.yourcompany.com.

Outlook Forms Support

The security updates for Outlook released on September 12, 2017 are affecting the inPoint Content Server email archive. The users are no longer able to open the original archived messages from shortcuts, only the shortcut itself. This is caused by the Microsoft's decision to disable Outlook form scripting by default.

After installing the security updates for Outlook, emails that were archived by third-party application are showing an unwanted behavior. All programs and applications using custom Outlook forms are affected.

Detailed Information about this problem.

Download necessary Registry Files.

inPoint CSE 3.9 Content Server for File

The following prerequisites are needed additional to the general prerequisites if you would like to archive the file system with the inPoint CSE Content Server for file.

Supported MS Windows server versions

inPoint CSE services user rights:

• MS Windows 2012 and above, all service packs

Additional Databases

• Databases:

  • inPointcA (Metadata central Administration)
  • inPointcAFile01 (Metadata inPoint File Archive)

Service User

inPoint CSE services user rights:

• Impersonation rights

Other Requirements

• Read/write access to the source file systems for the configured user accounts

inPoint CSD Content Server for Domino

Software Requirements

• Same as inPoint.Server

Supported Domino server versions

• Domino Server 9.0.x, 10.x

Additional Databases

• inPointDO (for Domino metadata)

inPoint CSS Content Server for ERP

This separate product must be installed on the same inPoint.Server instance.

Software/Hardware Requirements

• Same as inPoint.Server