Credential created in DB Agent lockbox when new SQL Server agent created with OS credential in different lockbox (4257742)

Credential created in DB Agent lockbox when new SQL Server agent created with OS credential in different lockbox

When adding a new SQL server agent and designating that the OS connection use a credential in a lockbox other than the DB Agent lockbox causes the following three things to occur.  Items 1 and 2 should not occur.

1).  A credential is created in the DB agent lockbox

2).   Resource mappings for "Windows Infrastructure" and "WMI for DB" are both created under the new credential in the DB agent lockbox.

3).   The "Windows Infrastructure" mapping is also added to the intended credential under the designated lockbox.

RESOLUTION 1: Don't enable the OS monitoring when initially adding the new SQL Server agent.  The problem doesn't occur when validating the connectivity and saving the changes for an existing agent.

RESOLUTION 2:   Delete the credential under the DB agent lockbox and then validate the connectivity to add the mappings to the intended credential.

RESOLUTION 3:   Use the CLI (Command Line Installer) to create the agent. The command line installer is discussed in the SQL Server guide.

 

SSFOG-1363