SSL certificate installation

make sure you use the certificates snap-in and make sure it uses the "Computer Account".

awesome ssl tool for windows - http://www.microsoft.com/downloads/details.aspx?familyid=cabea1d0-5a10-41bc-83d4-06c814265282&displaylang=en

Welll, I have downloaded and run the diagnostics. It comes back with an error reading the metabase, "cannot read metabase". The suggestion is then to download and install the IIS 6 resource kit. I have downloaded, installed and run the Metabase Explorer. When running this application it comes back with an error, "Failed to connect to the local metabase", "Failed to open metabase key, Reason, access is denied". I'm stuck here. Any ideas?

oooh very nice.  you're logged in as admin right?

Yes, I'm logged in as admin

in metabase explorer - does it open at all?  do you see the root node?  if so right click on it and check the permissions.  make sure administrator is listed.  if not go to the owner take ownership as admin

it opens to a blank grid and the only choices I have are to "connect" or "import key".

ok thats pretty nasty.  i'd guess that your metabase is corrupt.  im no expert when it comes to the metabase - but that stuff definitely should not be happening.

you might want to try restoring a backup of your metabase.  luckily iis6 creates a revision backup each time its edited.  This article outlines some things you might want to try.

Might be a good idea to do this after hours in case something gets truly messed up.  also have a credit card available in case you need to call MS for support :)
http://www.windowsitpro.com/Articles/ArticleID/22281/22281.html?Ad=1

Alright, i coughed up the $200+ and had Jaskirat of MS show me the errors of my ways. The problem was that someone prior to me had changed the Dcom properties and by going into Adminsitrative Tools --> Component Services and under Computers selecting the properties of my computer I was navigated to the default properties. Those properties had been set to anonymous under the impersonation level. Once the settings of the Default Authentication Level was set back to "Connect" and the Default Impersonation level was set back "Iddentify (the MS defaults), the certificate installed fine. I appreciate everyone's help on this but it took a level 2 engineer with remote control of my system to figure this one out.
Henry