# Advanced Install The advanced install option will allow you to customize the installation options for OneSite Platform, including using an existing SQL Server instance. {% hint style="warning" %} Do not install Adaptiva Server on the Operating System (OS) C: drive. The OneSite product log files and the Adaptiva Content Library installed with the Adaptiva Server grow over time, which impacts storage and performance on the OS C: drive. The installer will prompt you to change the destination drive if you continue to install on the boot drive. This also applies to the SQL Server 2022 Express Edition installation. {% endhint %} ## Configure Installation settings Configure your installation settings and add your license key to begin the Adaptiva Server setup process. 1. Right click `adaptiva-server--windows.exe`, and then select **Run as administrator**. ![Server Install](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-ae4f54d7f8a466097b9e668981a658ee0037b745%2Fimage6.png?alt=media) 2. Click **Browse** to navigate to and select the installation folder to a drive other than the C drive. * If you continue with installation on the C: drive, you will see a warning dialog. Click **Yes** to ignore this warning if you still want to install on the C drive. ![Target Disk Warning](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-be88ea4ef81616034f0a75bfac2a87b06235ccb5%2Fimage7.png?alt=media) 3. Configure your **Superadmin Login ID and Password**. * **Use Windows Login**: This option will use either your current logged in account or one that you specify with your Windows credentials. * **Use Custom Login**: This option allows you to supply an email address and password to create a server login. The email address is a username and does not need to be a valid email address. 4. Enter one or more license keys, separated by semicolons. 5. The following items are checked by default: * **Create an Add/Remove Programs Entry**: The Adaptiva Server Installer will create an entry for OneSite Platform in **Windows Settings > Apps & Features**. ![](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-f87d4ec7eb87f3e1331a1866f380b8fce359929b%2Fapps-features.png?alt=media) * **Add a Windows Firewall Exception for Server Application**: The Adaptiva Server Installer will add local exceptions in the Windows firewall for the default server ports (See [Communication Ports](https://adaptiva.com/hubfs/Docs/OneSite-Port-Detail.pdf)). * **IMPORTANT**: Review any existing domain-based group policies (GPO) that configure or restrict Windows firewall rules or rule creation as they can prevent or override these Adaptiva-created firewall exceptions. 6. Click **Advanced Install**. ### Configure TLS Security Settings TLS Security Settings will be used to secure the Admin Portal. The [Deployment Planning Installation Guide](https://docs.adaptiva.com/platform-install/planning-guides/onesite-platform-planning#security-certificate-options) provides details about Certificates. ![TLS Security Settings](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-70acafc9bfd96a1efd3c60112d150bb70bc4bb0e%2Fimage8.png?alt=media) 1. Select one of the following **TLS security Settings**: * **TLS Using A Certificate Authority (CA)**: use a certificate you exported from a Certificate Authority: 1. Click to select **Install A CA-Issued X.509 Certificate**. 2. Click **Browse** and navigate to the location of the exported **Certificate PEM File**. 3. Click **Browse** and navigate to the location of the exported **Private Key PEM File**. * **TLS Using Self-signed Certificate** (default): use a self-signed certificate. 1. Click to select **Create A Self-signed X.509 Certificate**. 2. Enter the **names or IP address** associated with the Adaptiva server that will host the Adaptiva Admin Portal. Include any server details for NETBIOS, FQDN, DNS Alias or IP Address. Separate each entry with a comma. 2. Set the **Web UI Port** used by the Admin Portal. This defaults to port *443*, but if other services are using that port, we suggest that you use port **9678**. * **IMPORTANT**: Be sure to share this port with all OneSite Administrators. It is required to access the Admin Portal. #### Optional: Configure HTTP Proxy Configuration If you are using an HTTP Proxy to route internet traffic, click **HTTP Proxy Configuration**. 1. Select your proxy configuration. ![HTTP Proxy Configuration](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-c362355b4c8fa66cc8e29842df7ebbadbf0a8908%2Fimage9.png?alt=media) * **Don't Use an HTTP Proxy**: no proxy settings will be configured. * **Prefer User Proxy Configured on the System**: a locally configured proxy will be configured. * **User a Proxy Auto-Configuration (PAC) File**: supply the URL to your PAC file. * **Use an HTTP Proxy Server**: supply the protocol, FQDN/IP of the proxy server, the port configured and a bypass list of semi-colon separated host names or IP addresses. 2. Click **OK**. ### Expected Client Count 1. Set the expected Adaptiva Client Count. Use the number determined from the Design Planning. The **Expected Total Number Of Adaptiva Clients** defaults to **5000**, which automatically sets the **Maximum Data Memory Buffer Size** to **2048 MB**. 2. Click **Next**. ### (Optional) Integrate 3rd party products This installation dialog box provides third-party integration options for Microsoft ConfigMgr and Omnissa Workspace ONE. * If you select **Integrate an Existing Microsoft ConfigMgr Site**, continue with [Integrate with ConfigMgr](https://docs.adaptiva.com/platform-install/server-install/install-platform/install-platform-advanced-install/install-platform-advanced-integrate-configmgr). * If you select **Integrate With Workspace One**, continue with [Integrate with Workspace ONE](https://docs.adaptiva.com/platform-install/server-install/install-platform/install-platform-advanced-install/install-platform-advanced-integrate-workspaceone). If you do **NOT** select an integration, continue with the Configure the SQL Database steps below. ### Configure the SQL Database You can choose to install the SQL database on a new instance of SQL Express or an existing instance on a SQL 2017 or later server. * If you select **Download and install free Microsoft SQL Express and auto-create database**, continue with [Option 1: SQL Express Installation](#option-1-sql-express-installation). * If you select either **Create the database in ana existing SQL Server Instance** or **Create the database in the same SQL instance as ConfigMgr Site Database**, click [Option 2: Existing SQL Instance](#option-2-existing-sql-instance). #### Option 1: SQL Express Installation 1. Select **Download And Install Free Microsoft SQL Express And Auto-create Database** and click **Next**. ![SQL Database Options](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-7f4f04278e2d2f540b31a527a614c7ad7480a630%2Fimage16.png?alt=media) 2. Click **Next**. 3. At the SQL Express Settings screen enter where the SQL Server Express installer should be downloaded to and where SQL Server Express will be installed ![SQL Express Settings](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-98c14c1264b20cb2abdb8bcaeabb85d0d81095f5%2Fimage17.png?alt=media) * **Download Folder:** the folder where the SQLExpr\_x64\_ENU.exe will be downloaded. * You can pre-download SQLExpr\_x64\_ENU.exe. Click Browse and navigate to the executable. * **Installation Folder:** the folder where SQL Server 2022 Express Edition will be installed. Change the drive letter of the **Installation Folder** to a drive other than C. 4. Click **Next**. 5. Continue with [**Read-Only SQL Login For Reporting**](#read-only-sql-login-for-adaptiva-reporting). #### Option 2: Existing SQL Instance 1. Select either **Create The Adaptiva Database In An Existing SQL Server Instance** or **Create the Database in the same SQL Instance as ConfigMgr Site Database** and click **Next**. ![SQL Database Options](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-43d021f0065ab98ef6c5257041f1d1bf98847723%2Fimage18.png?alt=media) 2. You will be prompted to confirm that your system meets the SQL Server pre-requisites: ![SQL Prerequisites](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-2be88328e55429b381a19b2a4f16f8deaed6a4b1%2Fimage19.png?alt=media) 3. Click **Continue**. 4. On the **Database Information** page, enter your SQL Server information. ![Database Information](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-0b9e069d1385fc53707868b043f5665c980aa098%2Fimage20.png?alt=media) #### Database Information 1. Select **SQL Instance Is Encrypted** if the SQL Server Instance is using encryption s. 2. If the **Default SQL Instance** is not used, uncheck the box and enter the **SQL Instance name**. 3. If the **Default SQL Port** is not used, uncheck the box and enter the **SQL Port**. #### SQL Login 1. Enter the **SQL Server Machine Name** FQDN. 2. Select or enter a SQL account. * (Recommended) Select **Use Adaptiva Server's Local System Account**. * If you choose not to use the Local System Account, enter the NETBIOS Domain name, User Name and Password of the account with sysadmin permission in the SQL Server that will host the Adaptiva database. * If the account specified is a SQL account, uncheck **Use Windows Authentication**. 3. Click **Next**. 4. If the account specified is different from the login account used for the service SQL Server (*MSSQLSERVER | InstanceName*) a dialog box will prompt you to verify the account used by the SQL Service. ![Account Warning](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-24db279cefea768b56ccd3042df522e3429f9812%2Fimage21.png?alt=media) 5. Click **Yes** if the settings are correct, otherwise, click **No** and update the settings. 6. At the Windows Authentication Protocol for SQL dialog, select the authentication method that will be used to connect to the SQL database. ![SQL Authentication Protocol](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-2f9e9e3967f27ca42c717d3309484394a6ac0693%2Fimage22.png?alt=media) * **NTLM v2** is selected by default. * If you require extended protection with SQL, you can select **Kerberos (Requires SQL SPN)**. To support Kerberos authentication, Service Principal Names (SPNs) must be created and delegated properly in Active Directory. For more information, please see our [SPNs and delegation](https://docs.adaptiva.com/platform-install/additional-configuration/platform-spns-delegation) page on how to create SPNs and delegate Kerberos authentication. 7. Click **OK**. 8. When the SQL Server hosting the Adaptiva database is different from the SQL Server hosting the ConfigMgr database, a message will be displayed. ![Linked SQL Servers](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-4dbd7b7f8733e2478fd306e2f9b7382e2f0e583e%2Fimage23.png?alt=media) * Be sure the Linked Servers are created before continuing and then click **OK**. For more information see [Create the Linked Servers](https://docs.adaptiva.com/platform-install/additional-configuration/platform-spns-delegation#create-the-linked-servers). ### Read-Only SQL Login For Adaptiva Reporting Provide a SQL login for reporting. ![SQL Reporting Login](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-24e836c97fb9f2e60348da38352bada6d5521ec8%2Fimage24.png?alt=media) 1. Enter the account information to be used for reporting: * **Use Windows Authentication** -- This box will be checked and greyed out Windows Authentication mode has been specified in the local SQL Server. * **Domain Name** -- Enter the NETBIOS domain name used for the reporting account. Leave blank if *Use Windows Authentication* is unchecked and a SQL Login account is to be used. * **User Name** -- Enter the account name created for use as the reporting account. * **Password** -- Enter the password for the reporting account. * **Confirm Password** -- Confirm the password that you entered above. * **IMPORTANT**: When SQL Server is remote from the Adaptiva Server, the installation will only be able to use Windows authentication. New Installations using SQL Express that did not use Quick Install will also be required to create an account and use Windows Authentication. 2. Click **Next**. ### Completing the Installation 1. The installation will begin. ![Install Success](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-12eda470de34870b620e2fc8f32212412afae75e%2Fimage25.png?alt=media) 2. When the installation is complete, click **Next**. ![Post-Install Verification](https://1238239958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcNZqjCKqgdpA83eD4o%2Fuploads%2Fgit-blob-d069511d00cfdb5b6f6852e780b3b5b4afff297d%2Fserver-installer-verification.png?alt=media) * The wizard performs a series of Post-Installation Verifications to validate the installation. The installation will skip some checks when not integrated with Microsoft Configuration Manager. * **NOTE:** There is a known issue when the Kerberos authentication protocol is selected for the Adaptiva database: The **Read-Only Account Write Access Denied** will report **Failed**. This can be ignored. 3. Click **Done**. After the installation of the OneSite Platform server, you must also install the Adaptiva client agent onto this machine. For instructions on how to install the client on the sever machine, please see our [Client Installation on the Server](https://docs.adaptiva.com/platform-install/server-install/install-platform/install-platform-server-client-install) page. ### Server Installation Logs In the case where an administrator needs to troubleshoot an Adaptiva Server installation, the following table contains the installation log locations. Other logs exist in the installation folder. | Function | Log Location and Name | | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------- | | Server Installation Logs |

%windir%\AdaptivaSetupLogs\Server\AdaptivaServerSetup.log
%install\_path%:\Adaptiva\AdaptivaServer\logs\Adaptiva\*.log

| | Client Installation Log |

%windir%\AdaptivaSetupLogs\Client\AdaptivaClientSetup.log
%install\_path%:\Adaptiva\AdaptivaClient\logs\*.log

| Access Server logs by navigating to **Settings** > **Logs** in the Admin Portal, or by navigating to the following location: `\Adaptiva\Adaptiva Server\Logs` {% hint style="info" %} OneSite Patch SaaS tenant logs can only be accessed by navigating to **Settings** > **Logs** in the Admin Portal. {% endhint %} The following options are available on the **Logs** page: * **Download All Server Logs:** Downloads all Server logs, including component and workflow logs. * **Download Server Error Logs:** Downloads Adaptiva Server error logs. * **Clear Web Logs:** Clears all Admin Portal runtime information and errors recorded by the browser session. * **Download Web Logs:** Downloads all Admin Portal runtime information and errors recorded by the browser session.