System requirements and step-by-step instructions for the installation of OneOffixx Server components can be found here.

System requirements

Operating system & components

OneOffixx Server can be installed on the following operating systems:

  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Server 2008 R2
  • Windows Server 2008

The following components are required for running OneOffixx Server applications:

  • Internet Information Server Version 7 or higher
  • SQL Server from Version 2008 (Express or higher). In case of a large number of users it is not recommended to use Express.
  • Microsoft .NET Framework 4.5.2 or higher

A PowerShell Script is included in the product package to ease installation on the Server. Windows PowerShell 2.0 has to be installed (automatically included on Windows Server 2008 R2 and higher) to run the Script correctly.

The PowerShell “ExecutionPolicy” has to be set to allow the execution of PowerShell scripts. Please execute the command “Set-ExecutionPolicy Unrestricted” in PowerShell if the script is not loaded properly.

Memory & CPU Cores

OneOffixx Server is operated within the Internet Information Server. We recommend meeting the requirements of Microsoft.

Advisable are at least 4 GB memory and 2 cores. More advanced CPUs and larger memory are recommended if additional software is running on the web server.

Hard disk space

The software requires about 100 MB of hard drive space. The software requires about 100 MB of hard drive space. All OneOffixx Server applications are set in their standard configuration to log in their respective application directory.

Log files are created every day and can reach a size of several hundred Mb. Log files are stored for maximum 7 preceding days.

Active Directory

The server hosting OneOffixx must be part of the Active Directory. Permissions for the organizational units are set in the Active Directory.

Ensure that the company network is integrated in the Active Directory.

DNS

OneOffixx clients communicate through HTTP/HTTPS with the OneOffixx Server. It is recommended to assign a designated CNAME to the OneOffixx server in the local DNS server. This is employed multiple times in the client configuration and the server.

The following exemplary DNS CNAME is used from here on:

oneoffixx.company.com

Usage of antivirus programs on the Windows Server

If a virus scanner is employed on the same system that is used to execute OneOffixx server applications, it should be configured to avoid restrictions in their functionality.

The following is recommended:

  • The virus scanner should not analyze the installation directory of OneOffixx (standard “C:\inetpub\wwwroot\OneOffixx”) on the server. Log files are frequently written in this directory if set in standard configuration.
  • The directory IIS Logs should also not be analyzed (“C:\inetpub\logs”).
  • Exceptions should be added for OneOffixx if the virus scanner is analyzing HTTP/HTTPS connections.

Operating OneOffixx and a virus scanner on the server at the same time may lead to performance issues without application of the aforementioned changes.

Installation Scenarios

Installing a OneOffixx Server & Database on new servers

x

  Installation and configuration step
1. Supply Microsoft Windows Server
2. Install SQL Server
3. Create a SQL Server OneOffixx user
4. Execute basic installation with PowerShell and follow instructions
5. Follow the configuration wizard on the administrator page
6. Functional test

Installing an OneOffixx Server on a new server. The database is installed on an already existing server.

x

  Installation and configuration step
1. Supply Microsoft Windows Servern
2. Create a SQL Server OneOffixx user
3. Execute basic installation with PowerShell and follow instructions
4. Follow the configuration wizard on the administrator page
5. Functional test

IIS and SQL Server already exist. Installing OneOffixx Server and database.

x

  Installation and configuration step
1. Create a SQL Server OneOffixx user
2. Execute basic installation with PowerShell and follow instructions
3. Follow the configuration wizard on the administrator page
4. Functional test

Server Application Updates

NEU ab 3.0

The PowerShell installation script can be called up again for an update. It is recommended to make a backup beforehand. You should make sure that the already existent files “OneOffixx.config” are kept during the installation. The script will take care of that for you.

Please note with Version 2.x: The admin application has it’s own configuration file called “OneOffixxAdmin.config”.

Exception: We will supply you with separate instructions if changes affect the structure of “web.config”.

Whether the update requires changes in the database will be displayed in the OneOffixx Admin and you will be able to implement these changes directly in the Admin web application.