Beginning Installation (Part I)
The Ivanti Endpoint Security administrator performs the first portion of the install procedure. At the end of this portion, the installer creates a script that is delivered to the SQL Server administrator.
Prerequisites:
- Complete Downloading Ivanti Endpoint Security.
- As applicable to your network environment, you have gathered the information and completed the tasks itemized in the Appendix D: Installation Checklist.
- Complete Configuring SQL Server to Accept Remote Connections.
- If installing using SSL, complete the first portion of Appendix B: Configuring Your Server to use SSL.
This first portion of this installation procedure is performed by the Ivanti Endpoint Security (Ivanti Endpoint Security) administrator on the target Ivanti Endpoint Security server.
- Using either a local or domain account with system administrator privileges, log in to the server on which you will install Ivanti Endpoint Security.
- Stop or disable any AntiVirus products (such as McAfee, Trend-micro, Symantec, and so on) running on your server.
- Double-click the Ivanti Endpoint Security installer at the location defined during the download.
The Ivanti Endpoint Security InstallShield Wizard opens and begins extracting files. This process may take several minutes. - If prompted, install prerequisites and reboot your server.
The installer reopens by itself after the reboot. - Click Next.
The License Agreement page opens.Tip: Click Print for a hard copy of the license agreement.
- Review the License Agreement and select the I accept the terms of the license agreement option.
- Click Next.
The Customer Information page opens. - Type the applicable information in the following fields:
- Click Next.
A new page or dialog opens. - DNS Client
- Function Discovery Resource Location
- SSDP Discover
- UPnP Device Host
- Static Content
- Default Document
- HTTP Errors
- ASP.NET
- .NET Extensibility
- ASP
- ISAPI Extensions
- ISAPI Filters
- Basic Authentication
- Windows Authentication
- Static Content Compression
- Dynamic Content Compression
-
If you receive only system requirement warnings, you may proceed with installation by clicking Next. Ivanti recommends resolving warnings before proceeding with installation.
-
If you receive any system requirement failures, you must cancel the installation, resolve these failures, and then restart installation.
- Create the Web client account and server accounts that Ivanti Endpoint Security will use.
Important: Preexisting accounts or domain accounts cannot be used for this installation procedure.
- [Optional] Edit the Web Client Account Username field.
- In the Web Client Account Password field, type the desired password.
- In the Web Client Account Confirm password field, retype the password.
- [Optional] Edit the Service Account Username field.
- In the Service Account Password field, type the desired password.
- In the Service Account Confirm password field, retype the password.
Ivanti recommends using the default account user names created by the installation.
- Click Next.
If required, acknowledge the creation of new accounts by clicking OK.
The SQL Server Instance Page opens. - Ensure the Connect to an existing SQL Server instance option is selected.
- Click Next.
The SQL Server and Instance page opens. - Type the name (not the IP address) of the server hosting the remote SQL Server instance in the Server name field.
- Based on the SQL Server instance you are using, select a SQL Server Instance option.
Select one of the following options. - Select the Named instance option.
- Type the instance name in the Named instance field.
- Click Next.
The SQL Server Authentication page opens. - Click Next.
The credentials provided do not have sufficient privileges to continue dialog opens. - Note where the script is located and click Close.
- Leave the installer open on its current page.
You will continue from this point during the last portion of the procedure. - Deliver the script to your SQL Server administrator.
An AntiVirus product can prevent processes from running correctly during the installation. Therefore, to ensure a successful installation, all AntiVirus services must be stopped or disabled prior to running the Ivanti Endpoint Security installer.
Field |
Description |
---|---|
Company Name |
Your company name. |
Serial Number |
Your Ivanti Endpoint Security serial number. Your serial number is two groups of eight alphanumeric characters. Letters are not case sensitive. If you cannot locate your serial number, obtain it by contacting the Ivanti Sales Support. |
Tip: Retain your serial number following installation, as it is necessary if a reinstall of the Ivanti Endpoint Security server is needed.
Page/Dialog |
Step |
---|---|
If the Question dialog opens: |
Click Yes to start network discovery services. The following services are necessary to use discovery features within Ivanti Endpoint Security: |
If the Required IIS Features page opens: |
Your server does not have the required IIS features installed. Click Install Features to install the features and proceed. On Windows Server 2008, the default installation of IIS lacks components necessary for Ivanti Endpoint Security. The Ivanti Endpoint Security installer installs the following IIS components if not present: |
If the System Requirements page opens: |
Your server does not meet the minimum installation requirements. When installing on a virtual platform you will likely receive a warning about the CPU requirements since the installer is unable to identify the processor in a virtual environment. Click View all Failures/Warnings for detailed information about prerequisite status deficiencies. |
If the Service Accounts page opens: |
Proceed to the next step. |
Important: If Server Location options are available from this page, you are performing the wrong procedure. Instead, perform Installing Using an Existing SQL Server Instance (either locally or remotely).
Option |
Steps |
---|---|
To use a default SQL Server instance: |
Select the Default instance option. |
To use a named SQL Server instance: |
|
After Completing This Task:
Have your SQL Server administrator complete Creating Components on SQL Server (Part II).