Requirements
System Requirements
inPoint Server & Client
Version 2019.*
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 (Only for inPoint - ElasticSearch is not supported)
-
.NET versions:
- 3.5
- 4.7.2
-
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
- Default Setting plus
-
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 2012, 2014, 2016, 2017 (Feature: Database Engine Services)
-
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
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
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.
inPoint.Identity and inPoint.Web Server
Optional Installation - both those Services can optionally be installed on the same inPoint.Server HW; same requirements apply.
Software Requirements
- .NET 4.7
- A working locally installed inPoint.Client (Windows)
- Two free ports (do not use 443 if already binded to IIS)
SSL Certificate
An SSL Certificate is used to bind to an HTTPS Web Port („Server Authentication") and to sign the Identity Tokens („Code Signing"). There is no way to run only under HTTP, and if you want to access the sites from external browsers (not in the domain) this certificate should be from a valid CA (Certificate Authority) -- either purchased or from free providers (like Let's Encrypt). Otherwise an internal Certificate issued from your local Domain Controller is enough.
The Certificate must:
- Have the correct CN (Common Name) and DNS Name set to the FQDN of machine (in lowercase) which will be used to access inPoint.Web
- Be at least 2048RSA strong
- Have a private key and be exportable
Details and instructions on requesting/creating a local domain Certificate are available in the inPoint.Web Manual.
External access
If you are planning to access the inPoint.Web from external (Internet), you need to:
- Have a valid Certificate from a known CA (otherwise the browsers will complain)
- Setup your firewall to allow access to both ports (Identity and Web)
inPoint Workflow Engine
inPoint Client
inPoint.Client (Windows)
Optional installation - requires inPoint.Server installation.
inPoint.Client - Windows Standalone, Windows Outlook Add-in, Windows Office Integrations
- OS: Windows 7 SP1, Windows 8.1, Windows 10 starting Anniversary Update, any inPoint.Server supported OS
- .NET Framework 4.7
- Office 2010, 2013, 2016, 2019 and Office 365 Pro Plus (x86 and x64)
inPoint.Web (Browser)
Optional installation - requires inPoint.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
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