Install of SCOM F5 Man Pack 1.6.2.311 fails

John,

I am starting to suspect something strange is going on. The way we get the Ahsl20 server is by directly querying this information from the SCOM administration. If this is returning the wrong SQL server, then I think there might be something wrong with SCOM or your deployment. We can verify this a couple of ways:

PowerShell way:

1. Open up an Operations Manager PowerShell console.

2. Enter the following commands:

$mgc = Get-ManagementGroupConnection;  
  $mg = $mgc.ManagementGroup;  
  $mga = $mg.GetAdministration();  
  $dwsn = [Microsoft.EnterpriseManagement.Administration.Settings+ManagementGroup+DataWarehouse]::DataWarehouseServerName;  
  $mga.Settings.GetDefaultValue($dwsn); 

3. Report back value returned by last statement in the script above.

Registry way:

1. Start RegEdit

2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Reporting

3. Report back value of DWDBInstance and DWDBName

Also, during our Setup program, the SQL server it wants you to specify is where the F5 DB will live, not necessarily where the OpsMgr DBs are. It finds the OpsMgr SQL Server and uses that as the default value since we know there is a ‘related’ database at that location.

If these 2 values do not match, we have a problem, or if they are not what you expect them to be. But let us know and we'll help you figure out how to resolve it.

Thanks,

-Dave