Assumptions

This section describes the assumptions for examples included in the Custom Installation steps.

System Requirement Assumptions

The diagram below shows the system requirements for the Custom Installation that is described in this documentation.

In the Custom Installation examples in the documentation, the following is assumed.

Server Name	Function	Software
SQLSrv	Database server File server	MSSQL Server 2016 Standard Windows Server 2016 Standard SQL Management Studio 17
OITsrv1	ObserveIT Application Server ObserveIT Web Console	Web Console Windows Server 2016 Standard Microsoft IIS 10
OITAgent	ObserveIT Agent	Windows Server 2016 Standard

The diagram below is an example If you use a more complex installation.

The following is assumed:

Server Name	Function	Software
SQLSrv	Database server File server	MSSQL Server 2016 Standard Windows Server 2016 Standard SQL Management Studio 17
OITsrv1	ObserveIT Application Server #1	Windows Server 2016 Standard Standard Microsoft IIS 10
OITsrv2	ObserveIT Application Server #2	Windows Server 2016 Standard Standard Microsoft IIS 10
OITweb	ObserveIT Web Console	Windows Server 2016 Standard Standard Microsoft IIS 10
FILEsrv	File Server	Windows Server 2016 Standard
OITAgent	ObserveIT Agent	Windows Server 2016 Standard

System Prerequisites Assumptions

For the system requirements in a custom installation, the following is required:

• All computers must be members of the same Active Directory domain
• Logon permissions to the computers must be defined with administrative permissions (local administrator)
• Permissions to create a service account user in Active Directory

You must prepare the following in a custom installation:

• Permissions to access the SQL Server database engine (SYSADMIN permissions)
• Permissions to grant the service account DBCREATOR permissions on the SQL Server
• Permissions to create folder(s) and share(s) on the server acting as the file server
• Permissions to grant the service account MODIFY permissions on the file share(s)
• Full network connectivity with no firewall restrictions between the components of the deployment, or permissions to create the appropriate firewall rules to allow the requested traffic type
• For data encryption (data in transit, data at rest, Web Console traffic):
• An internal Certificate Authority (CA) capable of issuing the correct digital certificates (it is possible to use self-signed certificates, however that may add complexity to the deployment)
• For detailed instructions, hardware recommendations and sizing refer to the ObserveIT General Prerequisites and Recommendations document which can be obtained by contacting ObserveIT’s professional Services team at proserv@observeit.com.

Additional Assumptions for Custom Installation

The server hosting the ObserveIT server-side website application is a member of an Active Directory domain, but not a domain controller (DC). Hosting IIS on a domain controller may cause adverse security issues and should be avoided. However, it may be possible when installing in an isolated lab environment. When installing on a DC, you need to use the “Active Directory Users and Computers” MMC snap-in and add the ObserveIT service account to the “Administrators” group found in the “Builtin” container, but this will affect all the DCs in the domain.

The reader has prior knowledge of Public Key Infrastructure (PKI) and its related terminology.

Your organization has an SQL server administrator who follows best practices for deploying and maintaining SQL server.

Your organization has a backup administrator, who follows best practices for backing up databases, Operating Systems, and file shares.