This 5.7.2.5 release of Foglight for Office 365 accompanies the release of Foglight Evolve 9.1 and Foglight for Virtualization, Enterprise Edition 8.9.1. This release does not include any resolved issues and enhancements.
The latest version of Foglight for Office 365 is 5.7.2.5. You can upgrade to version 5.7.2.5 of Foglight for Office 365 from Foglight for Exchange 5.7.2.2 or Foglight for Office 365 5.7.2.3 and later.
Note: When upgrading a stand-alone Foglight for Office 365 from a version earlier than 5.7.2.3, the license must be updated. Contact your Quest Account Manager for your new license.
To upgrade the Foglight for Office 365 to the latest version:
The following is a list of product versions and platforms compatible with this release.
Product Name |
Product Version |
Platform |
Foglight Management Server |
5.9.6 |
All platforms supported by this version of the Foglight Management Server |
Foglight Agent Manager |
5.9.6 |
All platforms supported by this version of the Foglight Agent Manager |
Foglight Evolve |
9.1 |
All platforms supported by these versions of the Foglight Evolve |
Foglight for Virtualization, Enterprise Edition |
8.9.1 |
All platforms supported by this version of the Foglight for Virtualization, Enterprise Edition |
Before installing Foglight for Office365, ensure your system meets the following minimum hardware and software requirements:
Platform |
Any supported Foglight, Foglight Evolve, or Foglight for Virtualization, Enterprise Edition platform. For complete information, see the System Requirements and Platform Support Guide. |
Memory |
As specified in Foglight, Foglight Evolve, or Foglight for Virtualization, Enterprise Edition documentation. |
Hard Disk Space |
As specified in Foglight, Foglight Evolve, or Foglight for Virtualization, Enterprise Edition documentation. |
Operating System |
As specified in Foglight, Foglight Evolve, or Foglight for Virtualization, Enterprise Edition documentation. |
Monitored Servers |
Foglight for Office 365 support Microsoft Active Directory Federation Service 2.0, 2.1, 3.0, 4.0, and 5.0. Active Directory Federation Service 2.0 and 5.0 can only be monitored via WinRm at this release, while other ADFS version can be monitored via both Dcom and WinRm. For ADFS agents: If the monitored host is a physical machine, it requires a host agent for host information collection. If the monitored host is a virtual machine, it requires a VMware/Hyper-V agent to collect host information collection. |
The following prerequisite conditions must be in place in order to successfully initialize an Office 365 agent. Failure to meet these prerequisites may result in missing metrics in Foglight for Office 365 dashboards.
Important: All prerequisite steps must be completed on the ADFS server as well as the Active Directory® server because the Office365 agent collects information from the Active Directory server and requires access permissions.
Note: The Remote Access Diagnostics utility, provided with this cartridge, checks the connectivity between the Foglight Agent Manager (FglAM) and Active Directory and ADFS servers that are being monitored. It also tests for the prerequisite conditions that must be met in order to initialize an Office 365 agent. This utility requires .NET® 2.0 libraries to run. For more information on running the Remote Access Diagnostics utility, see the Remote Access Diagnostics User Guide.
Office 365 account privileges:
Note: Make sure to give minimum required privilege to your agent; otherwise this agent cannot start data collection.
ADFS account privileges:
Office 365® account privileges:
To grant permissions on the registry keys:
ADFS servers that have to be accessed by clients not supporting GSS authentication must have SmbServerNameHardeningLevel set to 0 (the default). For more information, see http://support.microsoft.com/kb/2345886.
Rule #1: need local ports 135, 139, 389 (or 636) and 445 opened.
Rule #2: need "Dynamic RPC" local ports opened.
For more information, see the following article: https://support.quest.com/kb/SOL85903.
For details about this topic, refer to the "Configuring Windows Remote Management (WinRM)" section in the Foglight Agent Manager Guide.
The Kerberos configuration file specifies the KDC from which tickets are obtained. Operating systems sometimes have their own Kerberos configuration files. If present, the Agent Manager uses them by default. They can be found in the following locations:
If none of these files are found, the Agent Manager attempts to create its own kerberos configuration file, based on the detected settings. The detection can only be done on Windows, so on Unix, the file is not generated. On Unix platforms, you need to create your own Kerberos configuration files to establish WinRM connections using Negotiate authentication.
The krb5.ini or krb5.conf file should contain the realm info and hostname of the KDC for this realm. For example:
[libdefaults]
default_realm = <REALM_NAME_IN_CAPS>
[realms]
<REALM_NAME_IN_CAPS> = {
kdc = <fully_qualified_kdc_name>
}
[domain_realm]
.<domain_in_lower_case> = <REALM_NAME_IN_CAPS>
Important: Starting with version 5.7.1, Foglight for Exchange trusts (by default) any certificates for secure LDAP connections, and does not require users to import the SSL certificate any longer. The only case when users need to import the certificate is when they set the vm parameter "quest.ldap.ssl.trustAnyCert" as False to disable any certificate trust.
When collecting data using LDAP through SSL communication, a new Certificate Authority must be added to the Agent Manager’s Java® Runtime Environment (JRE). The JRE includes a command-line tool keytool which can be used to add the new Certificate Authority.
keytool -import -file <importCertPath> -alias <someName> -keystore <cacertsPath> -storepass <changeit>
keytool -list -alias <someName> -keystore <cacertsPath> -storepass <changeit>
Here are example commands that import and list a new root certificate:
<FMS_HOME>\jre\bin\keytool -import -file MySSL.cer –alias MySecuryLDAP.ca -keystore <FMS_HOME>\jre\lib\security\cacerts -storepass changeit
<FMS_HOME>\jre\bin\keytool -list -alias MySecuryLDAP.ca -keystore <FMS_HOME>\jre\lib\security\cacerts -storepass changeit
The initial password of the cacerts keystore file is changeit. System administrators should change this password and the default access permissions of this file when installing the SDK. The file can be found in the directory <FMS_HOME>\jre\lib\security\cacerts (embedded Agent Manager) or <FglAM_HOME>\jre\<JRE_VERSION>\jre\lib\security\cacerts (external Agent Manager).
Note: The certificate file that you want to import should be the public certificate for the Certificate Authority that signed the server's SSL certificate, not the SSL certificate itself. The Agent Manager must be restarted for the certificate to take effect. If security LDAP is enabled when creating the Exchange agent via the Agent Setup wizard, the root certificate also needs to be added to the Foglight Management Server’s Java Runtime Environment (JRE).
Server objects do not appear until at least one piece of data has been collected and recorded. If communication fails completely, you will not see objects.
Configuration steps:
ADFS agents delegate Windows agents, VMware agents, or Hyper-V agents to collect host data. ADFS agents collect host details to decide whether it is a VMware Virtual machine or a Hyper-V Virtual machine. By default, the host type is a physical machine.
For VMware virtual machine, agents delegate VMware agents to collect host data.
For Hyper-V virtual machine, agents delegate Hyper-V agents to collect host data.
For physical machine, agents delegate IC agents to collect host data.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center