Page History

...

• Anchor
  SQLCM-5989 SQLCM-5989

  When users add a GMSA account as part of a group, SQL CM does not recognize it as a Trusted User. As a workaround, users need to specify the account and the group when configuring Trusted Users and update the audit settings each time a new GMSA account is added to the group.

• Anchor
  SQLCM-6230 SQLCM-6230

  When performing a migration of the Collection Server, while installing the new Collection Server components, the installer raises an error message that prompts for the removal of the newly restored SQLcompliance and SQLcomplianceProcessing databases. The installer locates these databases which have been restored for the purpose of the migration, on the server instance which has been designated as the new repository database server during the installation process. Do not proceed with the removal of these databases, instead contact

  Newtablink
  alias Support url https://www.idera.com/support/supportplans

   for further assistance with installation or look up the KB Article #00012649 for further instructions, in the Solutions section for the SQL Compliance Manager product in the IDERA Customer Portal. 

• Anchor
  SQLCM-6058 SQLCM-6058

  When users run the SQLcomplianceClusterSetup.exe to upgrade agent service deployment to 5.6.1, the cluster setup installation does not prompt user to agree to upgrade and instead it performs a fresh installation.

• Anchor
  SQLCM-6128 SQLCM-6128

  When registering databases to the Primary node of an audited Availability Group, SQL Compliance Manager is not able to establish a connection with the AG databases on the Secondary nodes. Therefore, these databases do not get automatically register on the Secondary nodes.

...