Chatta subito con l'assistenza
Chat con il supporto

Foglight for Exchange 6.0.0 - Foglight for Office 365 Release Notes

Resolved issues and enhancements

Resolved issues and enhancements

This 6.0.0 release of Foglight for Office 365 accompanies the release of Foglight Evolve 6.0.0. This release includes the resolved issues and enhancements listed below:

  • Resolved issue where the Office 365 agent cannot collect service health data due to an expired certificate (FOG-1479)

Back to Top

Known issues

Known issues

The following is a list of issues known to exist at the time of this release.

Defect ID

Known Issues

FOG-621 Office 365 Education domain collections are not supported.
EXC-1628 Office 365 Government domain collections are not supported.

n/a

Microsoft has announced Active Directory LDAP Channel Binding and LDAP signing requirements (https://support.microsoft.com/en-sg/help/4520412/2020-ldap-channel-binding-and-ldap-signing-requirement-for-windows). Below error message will be found in the ADFS agent log, but agent can collect data normally:
Credential LDAP connectivity test failed: UPN: exc@2016dag.fog.local, error message: javax.naming.AuthenticationNotSupportedException: [LDAP: error code 8 - 00002028: LdapErr: DSID-0C090202, comment: The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection, data 0, v2580 ]

 

Back to Top

Upgrade and compatibility

Upgrade and compatibility

The latest version of Foglight for Office 365 is 6.0.0. You can upgrade to version 6.0.0 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 6.0.0, 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:

  1. Deactivate all of the Office 365 agents.
  2. Install version 6.0.0 of Foglight for Office 365. For details, see Installation instructions.
  3. Deploy the agent package to each Foglight Agent Manager that hosts an Office365 agent instance and wait for the version to update.
    Note: This may take two to three refresh cycles.
  4. From the navigation panel, navigate to Dashboards > Office365 > Office365 Environment > Administration tab. In the Agents view select the Office365 agents that you want to upgrade, and click Upgrade Agent.
    Note: You can specify the lockbox when upgrading the agents. The credentials for the existing agents are updated automatically. 
  5. Verify the agent properties and update the properties and collection intervals as required.
  6. Activate the agents and start data collections.

 

The following is a list of product versions and platforms compatible with this release.

Product Name

Product Version

Platform

Foglight Management Server

6.0.0

All platforms supported by this version of the Foglight Management Server

Foglight Agent Manager

6.0.0

All platforms supported by this version of the Foglight Agent Manager

Foglight Evolve

6.0.0

All platforms supported by these versions of the Foglight Evolve

 

Back to Top

System requirements

System requirements

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.

 

Back to Top

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione