Smartdoc makes use of many standard Microsoft® technologies already in place in many offices. These requirements are only a guideline. Please contact our support desk.
The minimum hardware requirements to run Smartdoc Server on a dedicated machine in a production environment are:
The system running Smartdoc Server can be used for other applications (this includes SQL Server), either presently or in the future, but the hardware requirements have to account for all software running on that same machine.
When no dedicated system is available to run Smartdoc Server, Smartdoc cannot be held responsible for any 3rd party conflicts which may occur during install or operation.
These editions of Windows® Server are supported:
Smartdoc Server listens for incoming connections on a particular port. The default port used for Smartdoc Server is TCP 4000.
Support for Server 2008 ended in July 2019.
There should be at least double the space of the current document or file collection on your file server and/or network drive. More space may be required depending on the number and size of documents to be managed by the document software.
Recommended hardware requirements for MS SQL Server.
Windows® Active Directory Integration
For user authentication and security a system with Microsoft® Active Directory is required.
Smartdoc application – supported Operating Systems
Smartdoc Office Connector
You are solely responsible for backing up any content or data entered into Smartdoc Server. We recommend that you regularly and completely backup all of your content and data on the server.
Comprehensive recovery requires more than just data backup. Your SQL Server® database contains tables, logs, and other components that structure the data. Using a specific backup solution for SQL Server®, a unified and intuitive backup solution, is critical to create a secure live database backup that can be recovered successfully.
Proven database backup technology can significantly reduce disaster recovery time, so organizations can be up and running again in minutes instead of hours. One-step recovery and automated recovery to pointof- failure reduces downtime in order to meet Recovery Time Objectives (RTO). A rolling snapshot feature enables near-instantaneous recovery in cases where a database is damaged due to human error or logical data corruption.
Last update: 18/01/2022