Please refer to the Support Portal knowledge base article 4377889 for additional information and instructions on implementing.
다운로드의 무결성을 보장하려면 체크섬 값을 확인하십시오.
SHA256: dddc0c813252e8d027169a8d832745589a7f313cf8637160dffeec5cded7d172
Enhancements:
Azure Active Directory renamed to Microsoft Entra ID including the following:
• Azure Active Directory discovery type is now Microsoft Entra ID.
• The tenant application Quest Enterprise Reporter Azure Discovery has been renamed to Quest Enterprise Reporter Microsoft Entra Discovery.
▪ After upgrading to Quest Enterprise Reporter 3.5.1.11000, all cloud discoveries will be displayed with a warning and will require configuration before running the discovery. To reconfigure the tenant application, open the Tenant Application Manager and click Configure. Once the new application has been registered and consent provided to permissions, you will then need to authenticate the discovery credentials. For each cloud discovery, edit the discovery and click the cloud icon to authenticate the credentials. See the “Tenant Applications for Cloud Discoveries” and “Creating Discoveries” topics in the Quest Enterprise Configuration Manager User Guide for details.
• The report library category previously named Azure | Active Directory is now Microsoft Entra | Entra ID.
• All related report types, library report titles and descriptions have been updated
NOTE: Any previously published reports from the Azure | Active Directory report library will not be automatically upgraded and will need to be published again.
Office 365 renamed to Microsoft 365 including the following:
• The report library category previously named Office 365 is now Microsoft 365.
• Some report types, library report titles and descriptions have been updated
Resolved issues
Active Directory discovery domain controller cache refactored to improve performance. #482105
Multi-task Active Directory discovery is collecting data multiple times. #483365
Microsoft Entra ID discovery, with multiple credentials, is unable to authenticate second credential. Workaround: Create another Microsoft Entra credential, using the second credential that you tried to authenticate. When added first, it will authenticate. Go to the original discovery and the second credential will now be authenticated. #483539
Microsoft Entra ID discovery has errors when FIDO2 certificate field is populated. #485385
SQL Server installation is missing VC++ redistributables. #487121
Microsoft Entra ID discovery fails when collecting deleted users MFA authentication methods. #488145
Unable to deploy nodes with alternate credentials from a different domain. #502922
Active Directory group membership information is not being collected. #504669
Memory leak when running computer discoveries. #505983
Incorrect byte array data in database for extended attribute. #513338
Computer ObjectSID extended attribute is not collected. #522099
© ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center