State Migration Point failing to start

One of the many State Migration Points I have failed the install (due to the above certificate error). Also, as part of the initial role assignment, the wrong drive was specified.

The site role was removed, web cert added as per above, then readded with the correct path. As a result, the role installed successfully. However, I was then receiving messages about the State Migration Point starting, then stopping unexpectedly.

Checking the SMPMGR.LOG file, I found the following lines :

Creating directory "D:\USMT\SMPSTORED_378B856C$" SMS_STATE_MIGRATION_POINT 14/05/2010 5:41:31 a.m. 3184 (0x0C70)

Cannot create D:\USMT, Win32 Error = 3 SMS_STATE_MIGRATION_POINT 14/05/2010 5:41:31 a.m. 3184 (0x0C70)

ERROR: Failed to create directory "D:\USMT\SMPSTORED_378B856C$" SMS_STATE_MIGRATION_POINT 14/05/2010 5:41:31 a.m. 3184 (0x0C70)

HandleSMPRegistryChanges failed. error (0x80004005). SMS_STATE_MIGRATION_POINT 14/05/2010 5:41:31 a.m. 3184 (0x0C70)

SMPManager failed to start, Error = (0x80004005). SMS_STATE_MIGRATION_POINT 14/05/2010 5:41:31 a.m. 3184 (0x0C70)

So the SMP was trying to create the folder on the old path, the one specified before I removed and readded the role with the correct part. Damn!

I took a look at the reg key that has the SMP settings (HKLM\Software\Microsoft\SMS\SMP\StateStore) and found TWO subkeys, one for the incorrect path (D:\USMT) and one with the correct path (E:\USMT).
Seems it only reads the first key in here (which makes sense).. Remove the incorrect subkey, and start the SMS_STATE_MIGRATION_POINT component via the service manager.

Check the SMPMGR.LOG file, and bingo! path is created, and component is now ticking along nicely.

Configuration Manager - State Migration Point Install Failure

Just had an issue with the install of a SMP to one of our servers.

I received the below errors in the SMPMSI.LOG :

The state of web site "Default Web Site" is Started.
ERROR: Certificate is not configured on the website for SSL.
ERROR: Validate IIS failed with 0x80004005.
@@ERR:25055
Product: SMS State Migration point -- Internal Error 25055. 80004005

I took a quick look on the server, and lo and behold there was no server cert in IIS under secure communication.

Quick fix (for a change!) - Requested a web server cert, and attached it.
I then removed the State Migration Point role, and readded it.

SMP is now happy, sweet deal!

Inventory Data Loader warnings + more..

This blog is kind of a reference for myself, but if anyone else makes use of the random pieces I put here, then all the better, all about sharing information.

I don't know about anyone else, but now and then I receive warnings in my Inventory Data Loader component. These are normally in the format :

"SMS Inventory Data Loader failed to process the delta MIF file "BLAH" and has moved it to "D:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\BADMIFS\ucq33ee1.MIF."

These only appear to happen for some delta inventory info, and subsequent resynchs will produce the same message.
A full Inventory Resynchronization fixes these clients right up.

The Operations Management team wanted a way they could easily identify which clients were causing these warnings, and a way for our help desk to resolve them.

To do this, I took a two pronged approach.
1) Created a script that parses the computername from the BADMIF files and adds it to a spreadsheet. (you can download this here if you want, all normal disclaimers apply, im not responsible for anything going ka-boom, run at your own risk etc etc)
2) Added a function to the 'Client Management Tool' that I created for the help desk to perform a full HW Inventory.This way, the operations team knew which machines were causing these warnings, they can pass the spreadsheet to the service desk who can then run the full HW inventory to clear these up.