Search This Blog

Monday 19 May 2014

PowerShell & System Center 2012


As of 01/05/2017, this blog will not be updated or maintained

A few days ago Microsoft published a cmdlet reference for System Center 2012, containing many documents about all available PowerShell cmdlets for the System Center 2012 family.

These 37 references can be downloaded from here:

  1. SC2012_AppController_Cmdlets.pdf
  2. SC2012_DPM_Cmdlets.doc
  3. SC2012_DPM_Cmdlets.pdf
  4. SC2012_OpsMgr_Cmdlets.doc
  5. SC2012_OpsMgr_Cmdlets.pdf
  6. SC2012_VMM_Cmdlets.doc
  7. SC2012_VMM_Cmdlets.pdf
  8. SC2012R2_AppController_Cmdlets.doc
  9. SC2012R2_AppController_Cmdlets.pdf

SCOM 2012 R2: FINALLY The Collation Settings Issue Is Addressed!


As of 01/05/2017, this blog will not be updated or maintained

The past
As we all know up to SCOM 2012 R2 the Collation Settings of the SCOM SQL databases was crucial and ONLY SQL_Latin1_General_CP1_CI_AS worked, even though Microsoft stated differently.
Main reason here was that the installer of SCOM installed the Data Warehouse database with this SQL Collation setting (SQL_Latin1_General_CP1_CI_AS) no matter what (SQL) Collation Setting the SQL instance itself was running.

And when there is a mismatch between the (SQL) Collation settings of both SCOM SQL databases (OperationsManager & Data Warehouse) you could end up in situations like these. Only a reinstall would solve that issue OR – when being blessed with really power SQL DBAs – the databases could be preserved while modifying the SQL Collation Settings.