Summit Tahoe SP3 HF31

Owned by Comala Publishing for Confluence Cloud
Jan 04, 2025

 | Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali HF03 << Denali SP1 << Denali SP1 HF01 << Tahoe << Tahoe SP1 << Tahoe SP3 HF01 << Tahoe SP3 HF01 (V1) << Tahoe SP3 HF02 << Tahoe SP3 HF03 << Tahoe SP3 HF04 << Tahoe SP3 HF05 << Tahoe SP3 HF06 << Tahoe SP3 HF07 << Tahoe SP3 HF08 << Tahoe SP3 HF09 << Tahoe SP3 HF10 << Tahoe SP3 HF11 << Tahoe SP3 HF12  << Tahoe SP3 HF13 << Tahoe SP3 HF14 << Tahoe SP3 HF15  << Tahoe SP3 HF16 << Tahoe SP1 HF17 << Tahoe SP3 HF18 << Tahoe SP3 HF19  << Tahoe SP3 HF20 << Tahoe SP3 HF21 << Tahoe SP3 HF22 << Tahoe SP3 HF23 << Tahoe SP3 HF24 << Tahoe SP3 HF25 << Tahoe SP3 HF26 << Tahoe SP3 HF27 << Tahoe SP3 HF28 << Tahoe SP3 HF29 << Tahoe SP3 HF30 

What's New? | Customer Fixed Issues and Known Issues | Prerequisites | Installation, Configuration, and Upgrade

On this page: 


What's New?

The following section provides a description of new features and improvements introduced in Tahoe SP3 HF31.

New Features and Improvements

Improvement NameImprovement DescriptionImprovement Benefits

Azure AD Import

In the Azure AD Import, a new filter has been introduced to import Active Directory (AD) user data into the Summit User Master table. Based on the locations specified in the Summit Config table (SUMMIT_AppConfigSettings) where the DataKey is 'AD_User_Default_Location'.

The location specified must match the location of the AD user’s data to be imported.

  • Simplified Management
  • Resource Optimization

Enhanced SAM Agent Compatibility

In higher versions of SAM Agents, additional data like MonitorDetails, ChassisTypeID, HDDSize_External, and HDDQty_External etc is retrieved. This additional information caused older version applications like Denali SP3 HF 16 and below to fail.

To address this, a key-value pair has been added to the Summit_ProxyServer.exe.config file, allowing certain fields to be excluded from comparison.

The exclusion list now includes fields such as ScanSource, ScanType, AgentVersion, Description, Organization, CountryCode, etc and is standardized for all future releases starting from Denali SP3 HF 17. In this release, few extra field names are added to this key-value pair. 

  • Prevents application failures by dynamically managing exclusion lists.
  • Increases flexibility and adaptability for future releases without the need for hard-coded exclusions.
  • Provides a consistent method for handling additional data across various SAM Agent versions.

For more information, about customer fixed and known issues, refer Customer Fixed Issues and Known Issues.