Walk-through Guide – Installing EdgeSight 5.4 with SQL 2008 R2
Citrix have created this great walk-through guide Howto install Citrix EdgeSight 5.4 with SQL 2008 R2.
Background
- Machine name is Windows-YC5LBMH.
- The SQL Server 2008 R2 is already installed, and Report Server is local.
- All accounts used are local not domain because it is in a lab environment. Normal installation utilizes Domain Accounts instead.
Installation of EdgeSight
After setting up a brand new virtual machine on Windows 2008 R2 64-bit:
- Install the IIS and Message Queue
- Install the SQL Server 2008 R2 (with Reporting Services)
Complete the following steps to install EdgeSight:
- Start the EdgeSight Installation. The account Windows-YC5LBMH\rsno that belongs to User and Administrators group is used, and is logged on for using the Windows Integrated Authentication during the installation.
- Select English.
- Click Continue.
- You will get an option to select either Web Server and Database or Database only. For a new installation select the Web Server and Database option, as shown in the following screen shot:
- Click Next.
- Ignore the following SSL warning because you do not intend to use SSL for the lab session. Click OK.
%temp% now contains the msibootstrapper2CSM_MSI_Install.log. After the Preparing to Install dialog box, there is the Citrix License Agreement dialog box.
- Click Next.
- Select Typical, if you wish to use the default settings and the allocated database space requirement is 500MB * (8+1) which is 4.5 GB.
- For the test environment select Custom to specify the size of the EdgeSight database filegroups.
- Create a user Credential 1 rsno before continuing with the Installation of EdgeSight:
- Create this user account as a system administrator role account.
You must create a user rsno as a administrator account that is registered with SQL Server with the minimum SQL Server roles.Note: At the end of the install, you must remove the DBCreator and SecurityAdmin from“rsno user and all the reports continues to generate correctly.
- Select dbcreator and securityadmin for the rsno account.
- Log on as Windows-YC5LBMH\rsno that has permissions in SQL and Windows-YC5LBMH computer as shown in the preceding screen shot. Because you have logged in as rsno to utilize the integrated Windows authentication in SQL, you have to be an administrator to execute the EdgeSight installation.
Note: The SQL server is local and is on the same server.
- Click Test Connect, and verify if the connection to the SQL database is successful.
Note the Temp folder has the MSI log (msibootstrapper2CSM_MSI_Install.txt), the size is dependent on the amount of text generated with your installation (i.e. yours will not be exactly at 500KB).
- 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, you can change the database name to ES54, as shown in the following screenshot:
- Click Next.
- Enter the credential 2 esno, and click Validate.The second credential esno is used to run the RSSH services the script host of the EdgeSight Web Server. It is also used to grant access to the EdgeSight database. All access by the EdgeSight Web Server except for Reporting Services uses esno credentials to access and write to the SQL database.
Note: The esno user is setup as shown in the following screen shot:
The DEFAULT size for database file is 500 MB. There are 8 filegroup files with one transaction log (4.5 GB total).
- Change the values to 20 MB and 50 MB arbitraryly to save space.
- Select the Server installation location. The default path is selected in the following screen shot:
- Click Next.
- Click Install.
Note: You might receive many entries in the installation log before clicking Install:
Note: After clicking on Install, the following entries are logged in the installation log:
Progress check (random) 1
Progress check (random) 2
Progress check (random) 3
The following screen shot indicates that the SQL database is created:
Progress check (random) 4
The following screen shot indicates that the Web server pages are copied to the installation location:
The EdgeSight Server 5.4 installation is complete.
- Click Finish.
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 esno granted access to the ES54 database and therefor the Database role membership is [db_datareader; db_datawriter; db_owner; ztmanager; ztoperator; ztpublic].
Note: zt* roles are created by EdgeSight, and is used for reports.
The other Database role membership for esno are shown in the following screen shot:
Post Installation Setup Wizard
Complete the following steps after installation:
Note: You must be able to configure the email settings and use it if you are using an administrator’s email account. The user name is stored as a credential to the EdgeSight database.
- 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 SuperUser Account.
Note: All information here are fictional; the Email/Login is stored as a user account on the EdgeSight database.
- Configure the Email Settings.
- Configure Agent Support and Licensing.
Final Validation Screen of the Post-Installation Setup Wizard
- Use the superuer account and logon to the EdgeSight server:
Report Server is currently empty and does not contain any EdgeSight reports and schedules.
- 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. 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.
After the SQL Server Agent is started, the Reporting Services Web page displays the EdgeSight Reports.
- 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.
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.
You can run a report from Reporting Services report page.
Note: 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 Setup 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:
Sherri Hansen
just got my ES 5.4 server up and running .. .thanks!
David
This is a very well done and comprehensive EdgeSight article.. its my go-to guide for all things ES.. Working on the third 2008R2 install and most of the settings are appropriate for 2012.
Thomas Poppelgaard
Good to hear Sherri =) Hope things are great in US.
I am happy David you could use it ;o) i have updated the pictures so the article is more friendly to read.
Cheers
Danny de Wolf
Hey Thomas,
Great work, thanks. I’m still running into an issue that I cannot seem to resolve. I was hoping you might have an idea where I should look ?
I’ve got an application server with ES5.4, and a separate SQL server with the Reporting installed. I can get to the Reporting websites /reports and /reportserver, but when configuring Reporting within ES, it keeps saying “The report server credentials used to communicate with Reporting Services are invalid”. I tried pretty much everything I think, and cannot get my head around this.
The account that I’m using at the “Report Server Credentials” page, is a domain account, and has admin rights on the application server (for now, local admin) as well as on the Report and ES databases.
I’m a bit lost what else I can check to make this work… Any advise you can give me would be greatly appreciated 🙂
Thanks.
Anonymous
None of the images on this site show. It would be great if the images could be re-uploaded! 🙂