Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Today’s post falls into the category of things I feel a little guilty about posting, but I will anyway. I’m not saying anything new here, just trying to spread the knowledge because I keep seeing customers hit the same problem, which has a simple solution. If you want to skip reading my blog you can go to https://blogs.technet.com/b/configurationmgr/archive/2008/11/12/configmgr-2007-osd-task-sequence-fails-with-unspecified-error-80004005-and-setupact-log-indicates-invalid-product-key.aspx and get the details.
What I see with customers is that they are building a new OSD task sequence and they enter their company product key into the task sequence only to have it fail, usually with a 80004005 error code. This is occurring because the product key they entered was a a MAK (Multiple Activation Key) and not a standard product key, which ConfigMgr just doesn’t know how to handle. The solution is easy for newer (vista and higher) OS. Leave the key blank and add a step to your task sequence, after OS install, to run the following command line and set the product key:
SLMGR.VBS -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
I had one customer encounter this with older OS, WinXp. We didn’t actually get into the issue so if that is your situation I can only offer you the advice I offered them (and if it works or not, please let us all know in the comments below) but I have not yet had validated. Add the key to a custom unattend.txt file and then add that text file to your task sequence, in the “Apply Operating system”. This might pass it along correctly.