Tuesday, 30 October 2012

vpx.fault.SecurityConfigFault when trying to replace center certificate

The problem is due to the certificate "Issued To" field not being the fqdn of the server. The fqdn being in the subject alternative is not enough. I guess this rules out wildcard certs too.

An addition to this, all vSphere 5.1 certs need a different subject name, you need 1 certificate for each of the following services:


SSO
Inventory Service
vCenter
Update Manager
Web Client
Log Browser


This blog is pretty complete about certificate replacement:

http://derek858.blogspot.co.uk/2012/09/vmware-vcenter-51-installation-part-1.html

Sunday, 27 April 2008

Intel Active Monitor

I've been cleaning up my Exchange Server 2003 VM... I found a service which was installed when it was a physical machine... Intel Active Monitor...

It won't uninstall from add/remove programs and makes the machine give the "service / driver failed to load" message at startup, so I've made it a mission to get rid of it!

the eventvwr message i get is:

"The SIODRV service failed to start due to the following error: 
The system cannot find the device specified. "

problem is I can't find which windows service that relates to... From reading around it appears to be the Intel Active Monitor....

First thing I thought was to try re-downloading the monitor, Installing, then UnInstalling. I got bored looking on the intel site so decided to dig a bit further...

The only Intel service on the machine is the Active monitor and that's disabled, so what next?

I found this bad boy! So, I deleted the following Key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SIODRV

this didn't remove the Intel Active Monitor service, but has sorted the problem!

edit: intel key is here:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\imonNT
deleted this and intel active monitor is gone!!

In doing this i found this... I can now shut my exchange box down in less than 10 minutes!!! The script doesn't work, but if i manually stop the services the box shuts down MUCH quicker!
This article explains the shutdown issue much better...