To successfully install OfficeMaps as a self-hosted solution, a number of requirements must be met.
You will need a server with the following:
(Note: due to the .Net Framework version changing from 4.6.1 to 4.8, Windows Server 2008 will no longer be supported from OfficeMaps version 2.3 or higher.
Two sites are created during installation. These sites require separate DNS host names, one for web and one for the API.
Any host names can be used, below are example host names for a domain iconico.com:
Intranet (embedded search,etc)
Kiosk / Guest Access
If you are planning to use SSL/https for your on premise installation, one or more certificates will be required for the host names that will be used.
If you are planning to use Active Directory for authentication, then the web server will need to be on a machine connected to the Active Directory domain.
Hardware requirements are contingent on the number of OfficeMaps users, how busy the server is and whether the server is virtualised. For example, if the server is Hyper-V, it is recommended to allocate at least two processors and 8GB of RAM.
Some Frequently Asked Questions:
What authentication schemes need to be installed with IIS (e.g. Basic, Digest, Integrated Windows)?
Only the default (Anonymous) is required.
Is there a base database that is attached to the SQL Server or is it created with a program?
The current practice is for the client to create an empty database (with any name) in SQL Server. It is important that full permission to this database be available during the installation process.
What permission does the SQL account used by the OfficeMaps site require?
Full dbo permission is required to the OfficeMaps database only which is required to add and modify the database schema during updates.
Do you need to know the name of the security group that is allowed to access OfficeMaps?
Yes, AD Sync requires the domain name and group name that users are to be synchronised from. This security group is configured after installation. Once this is done, the default logon type for this group can be changed to Active Directory.