Setup on new iMac, asking for a Keychain Password for com.apple.smig

Can't answer the smig thing, but suggest that you peruse Pondini's Setup New Mac guide and ensure you're doing it properly.

This does not provide an answer.

What's your question? The OP hasn't come back. All i can offer is peruse the google search results for com.apple.smig and be enlightened.

Has anyone else figured this out? I'm getting it on every machine I upgrade and I have about 18 more to go and would like to fix it.

These are brand new iMac's shipped with Mountain Lion. I turn them on and the third screen asks if you want to transfer items from a backup or another Mac. I choose another Mac. Then use Migration Assistant on the users old machine (running Snow Leopard 10.6.8) and then let it transfer all of their files.

At just about the end of the transfer the new Mac pops up this error and waits until an action is taken. I've tried every password it could have been on the previous users machine to no avial. The only option appears to be hitting cancel and movi ng on but I'd like to know what is breaking when this happens becase the machines exhibit a strange spinning wheel hang when logging in afterwards?

Here's a screen shot of the new iMac and the problem:

Thanks!

Since these are new machines, contact Apple's Express Lane and let them sort this out for you.

Could it be that you are transferring from a machine running Snow Leopard to a machine running Mountain Lion?

I cannot remember exactly what but there were big changes when the operating system changed to Lion let alone Mountain Lion.

Just a thought.

I'd rather it get sorted here so when someone else has this problem and types these search terms into Google (like I was for a few hours) they can find an answer.

There were many changes. Which is why I'm asking if anyone has run into this problem and figured out what exactly is going on.

Is this related to iCloud? Root certificates? OS X server credentials? Self-signed certificates? iChat/Messages?

If this just happened on one machine I'd have ignored it but it's happening on all of them (3 so far) and I'm curious what is breaking so I can go back and fix or eliminate it after I get it up and running (for now I'm just hitting cancel on the request and it continues and finishes).

Thanks for the reply though.

Adam T wrote:

I'd rather it get sorted here so when someone else has this problem and types these search terms into Google (like I was for a few hours) they can find an answer.

Suit yourself. But, IMO, if anyone had any ideas, they'd answered already. It's been almost two months since the OP inquired.