CERTIFICATE SERVICES

Written by Sam McGeown on 25/6/2010
Published under Microsoft
This is a pretty specific set of instructions for a specific environment: If you are using Microsoft System Center Operations Manager 2007 and you have a Microsoft Certificate Services 2003 Certificate Authority on your domain and you have non-domain Windows Server 2008 servers you wish to monitor or set up as a gateway server.   Getting a certificate for either a Gateway Server or remotely monitored Server can be a touch vexing.
Written by Sam McGeown on 25/6/2010
Published under Microsoft
This is a pretty specific set of instructions for a specific environment: If you are using Microsoft System Center Operations Manager 2007 and you have a Microsoft Certificate Services 2003 Certificate Authority on your domain and you have non-domain Windows Server 2008 servers you wish to monitor or set up as a gateway server.   Getting a certificate for either a Gateway Server or remotely monitored Server can be a touch vexing.
Written by Sam McGeown on 7/5/2010
Published under Microsoft
This was a bit of an odd one. I was adding a Gateway Server to a newly rebuilt SCOM 2007 R2 Root Management Server when I kept encountering this error: The certificate specified in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Machine Settings cannot be used for authentication.  The error is The credentials supplied to the package were not recognized(0x8009030D). I followed the Microsoft install and setup guides exactly, and it’s not my first time either – but I’d never seen that one before.
Written by Sam McGeown on 7/5/2010
Published under Microsoft
This was a bit of an odd one. I was adding a Gateway Server to a newly rebuilt SCOM 2007 R2 Root Management Server when I kept encountering this error: The certificate specified in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Machine Settings cannot be used for authentication.  The error is The credentials supplied to the package were not recognized(0x8009030D). I followed the Microsoft install and setup guides exactly, and it’s not my first time either – but I’d never seen that one before.