Edgesight 5.4 installation

Dowload Edgesight 5.x (myCitrix login)
https://www.citrix.com/English/ss/downloads/details.asp?downloadId=1681164&productId=25119#top

Edgesight installation Windows 2008 R2 server

Installation ofEdgeSight (CTX130967)

After setting up a new Windows 2008 R2 64-bit:

Install IIS and Message Queue.

• IIS 7.0 Components Required on Windows Server 2008 SystemsSpecific IIS 7.0 components are required on a Windows Server 2008 or later system which will be hosting an EdgeSight Server. These components are checked by the bootstrapper program. When configuring IIS 7.0, ensure that the following role services are selected under the Web Server role:
• Static Content
• Default Document
• ASP.NET
• ISAPI Extensions
• ISAPI Filters
• Windows Authentication
• Request Filtering
• The following Management Tools:
• IIS 6 Management Compatibility
• IIS 6 Metabase Compatibility
• IIS 6 WMI Compatibility
• IIS 6 Scripting
• IIS 6 Management Console

• Install Message Queuing 4.0 on Windows Server 2008 or Windows Server 2008 R2
  1. In Server Manager, click Features.
  2. In the right-hand pane under Features Summary, click Add Features.
  3. In the resulting window, expand Message Queuing.
  4. Expand Message Queuing Services.
  5. Click Directory Services Integration (for computers joined to a Domain), then click HTTP Support.
  6. Click Next, then click Install.

• Install SQL Server 2008 R2 (with Reporting Services).

Complete the following steps to install EdgeSight Server:

Start the EdgeSight Installation.
The user DOMAIN\USER (currently member of User and Administrators group) is logged on for using the Windows Integrated Authentication during the installation.
Select English.
Click Continue.

Welcome to the EdgeSight Server 5.4 Installer.
Click Next.

For a new installation select the Web Server and Database option, as shown in the preceding screen shot:
Click Next.

If the SSL Warning message appears, then click OK and ignore the SSL warning because this installation does not use SSL.
Click OK.

After the Preparing to install dialog box closes you must accept the Citrix License Agreement.
Note: %temp% folder now contains the MSI installation log, msibootstrapper2CSM_MSI_Install.log.

After reading the End-User License Agreement or the Citrix License Agreement and accepting the terms of the license, Click Next.

Select Custom to customize the EdgeSight database filegroups.
Note: Select Typical, if you choose to use the default settings and the allocated database space requirement is 500MB * (8+1) which is 4.5 GB. Some of the following steps are not applicable if you have selected a Typical installation.

If the Database User is not created, create a Database User DOMAIN\USER in SQL Management Studio. You can also choose to create the database user before installing the EdgeSight Server. You can install the EdgeSight server using any SA equivalent or a database user account with the minimal Server Roles, DBCreator and SecurityAdmin. After installing the EdgeSight server the two minimal Server Roles can be removed from DOMAIN\USER user account.

The prececding screen shots shows the Server Role settings of the database user DOMAIN\USER used for this installation. The SQL server is local and is on the same server.

The local user account Windows-YC5LBMH\rsno is currently a member of Administrators and Users as shown in the preceding screen shot. The Administrators membership is required to complete the EdgeSight installation. At the end of the installation, the user account can be removed from the Administrators group.
The local user account Windows-YC5LBMH\esno is used as Credential 2 (the EdgeSight service account). This user belongs to the Users group with no special privileges. This user is used later on in the installation.

Click Test Connect, and verify if the connection to the SQL database is successful.
Note: The location of the MSI installation log, msibootstrapper2CSM_MSI_Install.log, is shown in the background as a reference. The size is dependent on the amount of text generated by the installation.
Click Next.

Check the msibootstrapper2CSM_MSI_Install.txt for the following entries before you click Next in the SQL Server Database Selection dialog box.

For this installation, the database name is changed from default EdgeSight to ES54, as shown in the preceding screen shot.
Click Next.

Enter the User Name (Credential 2, the EdgeSight service account), Windows-YC5LBMH\rsno, along with the password.
Note: This user account is used to run the Citrix RSSH services. This account is granted access to the EdgeSight 5.4 database by the database user (Credential 1). This user name is usually an Active Directory account with similar rights that is no special privileges.
Click Validate.

The local user account, Windows-YC5LBMH\esno is currently a member of Users.

The DEFAULT size for database file is 500 MB. There are eight filegroup files with one transaction log (4.5 GB total).

Change the values from 500 MB to 20 MB and 50 MB arbitrarily to save space.

Click Next.

Select the Server location of the installation. The default path is selected in the preceding screen shot.
Click Next.

Click Install.

Note: There are many Note: 1: entries in the installation log, as shown in the preceding screen shot before you click Install.

Note: After clicking Install, the entries as shown in the preceding screenshot are logged in the installation log:

Progress check (Random) 1

Progress check (Random) 2

Progress check (Random) 3. The preceding screen shot indicates that the SQL database is created.

Progress check (Random) 4. The preceding screen shot indicates that the Web server pages are copied.

Click Finish. The EdgeSight Server 5.4 installation is complete.

SQL Database

Note the size of the ES54 database which contains the static data in the various tables, it is approximately 256 MB.

Credential 1 rsno created the database and therefore the owner of ES54 database is rsno.

Credential 2 Windows-YC5LBMH\esno granted access to the ES54 database and therefore the Database role membership is [db_datareader; db_datawriter; db_owner; ztmanager; ztoperator; ztpublic].

Note: The zt* roles are created by EdgeSight, and is used for reports.
Post Installation Setup Wizard
Complete the following steps after installation:

Create an Initial Company.
Every device that reports to the EdgeSight server must identify the company name else the device is reported as another company. When you access the EdgeSight Web Server, the TimeZone specified is used that is if you want historical data for computer X, from 3 a.m. to 6 a.m.then it is relative to the EdgeSight Web Server time.

Create the company name and configure the Time Zone.
The company name must be consistently used for all EdgeSight agent devices reporting to the EdgeSight Web server. In customer sites, only one company name must be used unless you intend to completely separate the data and EdgeSight administrator across multiple companies. There is no useful use-case for separating into multiple companies in an EdgeSight deployment.

The Time Zone drives the time data on the EdgeSight reports. All agent data in other time zones are normalized to UTC, and the EdgeSight Web server drives the display of data relative to the Time Zone setting in the EdgeSight Web server. For example, when EdgeSight server is configured for EST, agent data from 11 p.m. PST on 12/01/2011 is presented as report data from 2 a.m. EST on 12/02/2011.

Create the SuperUser Account. The account is used for the first logon to EdgeSight Web Console.

Configure the Email Settings.

Configure Agent Support and Licensing.

Final Validation Screen of the Post-Installation Setup Wizard. Click Finish.

Note: Report Server is currently empty and does not contain any EdgeSight reports and schedules.

Use the superuser account and logon to the EdgeSight server.

Specify the rsno credentials for Report Server Credentials and esno credentials for Data Source Credentials.
Note: Most customers choose to use one account for both credentials.

Clear the User Report Server Credentials option to allow two credentials.
Click Save Changes.
The “Reporting Services is not configured or is configured incorrectly” message appears, as shown in the preceding screen shot. The “Reporting Services Configuration Status – Webpage Dialog” Window appears. If the Windows does not appear and times out after 20 minutes, then there is a delay in the communication from the EdgeSight Web server to SQL Server Reporting Services.
Note: Ensure that the SQL Server Agent is started. This is required for publishing the schedules.

Double-click and open the Citrix folder. The string that appears, is the computer GUID.

If you share the Reporting Services Web site and Web service with multiple Edgesight Web servers, then more than one entry appears on this screen.

Note: The Reporting Services Web page displays the EdgeSight Reports.

Note: The Reporting Services data source to the EdgeSight database is stored here. You need not change this information because the EdgeSight Web Console Reporting Services configuration updates the required information.

Note: You can run a report from Reporting Services report page. This is useful if there is a problem with reports and you want to know if EdgeSight or the Reporting Services is having a problem.
Example
Run the alert report with the following values:

-5 and -4 represents relatives days back from the execution date
Filter as 1
FilterName as Departments “All”
There is only one company “es,” thus the CompId is always 1.
DrillQSItems can be any text. Run the same report from EdgeSight Web Console.

IIS Settings after EdgeSight is Installed
The following screen shot shows the /edgesight Home page:


The following screen shot shows the .NET Authorization Rules page:

The following screen shot shows the .NET Compilation page:

The following screen shot shows the .NET Globalization page:

The following screen shot shows the .NET Profile page:

The following screen shot shows the .NET Trust Levels page:

The .NET Users information was not available.
The following screen shot shows the Application Settings page:

The following screen shot shows the Connection Strings page:

The following screen shot shows the Machine Key page:

The following screen shot shows the Pages and Controls page:

The following screen shot shows the Providers page:

The following screen shot shows the Session State page:

The following screen shot shows the SMTP E-mail page:

The following screen shot shows the Authentication page:

The following screen shot shows the Compression page:

The following screen shot shows the Default Document page:

The following screen shot shows the Directory Browsing page:

The following screen shot shows the Error Pages:

The following screen shot shows the Handler Mappings page:

The following screen shot shows the HTTP Response Headers page:

The following screen shot shows the Logging page:

The following screen shot shows the Mime Types page:
The following screen shot shows the Modules page:

The following screen shot shows the Request Filtering page:

The following screen shot shows the SSL Settings page:

The following screen shot shows the Session State for the default Web site:
Note that the value for timeout on session cookies is set as 20 minutes.

The following screen shot shows the Authentication for the default Web site:

The following screen shot shows the Compression page:

The following screen shot shows the Default Document page:

The following screen shot shows the Handler Mappings for the default Web site:

The following screen shot shows the HTTP Response Headers page:

The following screen shot shows the ISAPI Filters page:

The following screen shot shows the Logging page:

The following screen shot shows the Modules page:

The following screen shot shows the Request Filtering page:

The following screen shot shows the Application Pools page:

Doubles-click on EdgeSight to view the details:



Component Service (DCOM) Settings after EdgeSight is Installed

The RSSH is running with a non-Administrator user account on the local system. EdgeSight installation usually uses an Active Directory account. The EdgeSight User account (credential 2) Windows-YC5LBMH\esno is used in this article.
DCOM Configuration for Citrix RSSH Administrator Service










DCOM Configuration for Citrix RSSH Application [es_zqueue] Properties
Note: This procedure does not have similar screen shots that are present in the previous section.





DCOM Configuration for Citrix RSSH Application Object Properties
Note: This procedure does not have similar screen shots that are present in the previous sections.






Message Queue
Not all installed Features are required by EdgeSight. Message Queue is used for agent alerts that are defined by EdgeSight Web Console alert rules.




Note: Ensure that you configure the required antivirus exclusion for the EdgeSight server using the Knowledge Center article CTX114906 - Required Antivirus Software Configuration for the EdgeSight Server.

http://support.citrix.com/article/CTX130967/