none
SCCM SP2 Windows 7 OSD + USMT Headache RRS feed

  • Question

  • I am beginning experimenting with Windows 7 Deployment. I have a base image, can deply this, have an answer file, all that is good.

    But the main thing i want to get working is USMT.

    So the scenario would be.

    XP Machine (32 bit)

    Backup the user profiles to a State Migration Point ( created on the SCCM server)

    Wipe the machine install Windows 7

    Then pull the profiles back down again and hey preseto.


    Yesterday morning the majority of this worked, I mean it failed when trying to pull the profiles down, but I felt like i was making progress.

    However as of yesterday afternoon and this morning When i fire off the task sequence from within XP, it begins to run REQUEST STATE STORE.........


    Then immediatly fails......


    I have looked in the SMSTS.log on the machine, and to save putting the whole lot up, I believe I have located the issue, but am unable to fathom out how to resolve it.

    Below is a snippet of the log


    ****

    <![LOG[The execution of the group (Capture User Files and Settings) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="10:43:55.649+000" date="11-04-2009" component="TSManager" context="" type="3" thread="2968" file="instruction.cxx:2424">
    <![LOG[Failed to run the last action: Request State Store. Execution of task sequence failed.
    The administrative limit for this request was exceeded. (Error: 00002024; Source: Windows)]LOG]!><time="10:43:55.649+000" date="11-04-2009" component="TSManager"
    context="" type="3" thread="2968" file="engine.cxx:214">
    <![LOG[Sending status message . . .]LOG]!><time="10:43:55.649+000" date="11-04-2009" component="TSManager" context="" type="1" thread="2968" file="utility.cxx:292">
    <![LOG[Send a task execution status message SMS_TSExecution_TaskSequenceFailError]LOG]!><time="10:43:55.649+000" date="11-04-2009" component="TSManager" context="" type="1" thread="2968" file="utility.cxx:314">
    <![LOG[MP server LONSCM002.LAW.FIRM.PRIV and port 80. SSL=false. CRL=false.]LOG]!><time="10:43:55.649+000" date="11-04-2009" component="TSManager" context="" type="1" thread="2968" file="utility.cxx:458">
    <![LOG[Site code: LON]LOG]!><time="10:43:55.649+000" date="11-04-2009" component="TSManager" context="" type="1" thread="2968" file="utility.cxx:489">
    <![LOG[Client machine name: TAYLOR-A522A656]LOG]!><time="10:43:55.649+000" date="11-04-2009" component="TSManager" context="" type="1" thread="2968" file="utility.cxx:494">
    <![LOG[Client Identity: GUID:b56d702e-7022-43c3-8a3c-582e9e525c85]LOG]!><time="10:43:55.664+000" date="11-04-2009" component="TSManager" context="" type="1" thread="2968" file="utility.cxx:496">
    <![LOG[Advertisement ID: LON201AD]LOG]!><time="10:43:55.664+000" date="11-04-2009" component="TSManager" context="" type="1" thread="2968" file="utility.cxx:505">
    <![LOG[Package ID: LON00176]LOG]!><time="10:43:55.664+000" date="11-04-2009" component="TSManager" context="" type="1" thread="2968" file="utility.cxx:507">
    <![LOG[Sending StatusMessage]LOG]!><time="10:43:55.664+000" date="11-04-2009" component="TSManager" context="" type="1" thread="2968" file="libsmsmessaging.cpp:3806">
    <![LOG[Formatted header:]LOG]!><time="10:43:55.680+000" date="11-04-2009" component="TSManager" context="" type="1" thread="2968" file="libsmsmessaging.cpp:1500">
    <![LOG[<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:b56d702e-7022-43c3-8a3c-582e9e525c85</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2009-11-04T10:43:55Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="2116"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
    ]LOG]!><time="10:43:55.680+000" date="11-04-2009" component="TSManager" context="" type="1" thread="2968" file="libsmsmessaging.cpp:1501">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: LONSCM002.LAW.FIRM.PRIV:80  CCM_POST /ccm_system/request]LOG]!><time="10:43:55.680+000" date="11-04-2009" component="TSManager" context="" type="1" thread="2968" file="libsmsmessaging.cpp:7446">
    <![LOG[The request has succeeded. 200 OK]LOG]!><time="10:43:55.711+000" date="11-04-2009" component="TSManager" context="" type="0" thread="2968" file="libsmsmessaging.cpp:7734">



    Now on the machine, the error box with the 15 minute counter, has the same error code 00002024


    I have tried to google this with not much luck, somewhere suggested a windows update notably KB974571 could cause this problem, now although I have tried this,


    In writing this post, I had a brain wave, on hte lines of updates, I have a couple of machines still hanging around that are on SP2, hence had none of these latest updates (SP3 etc)

    HAve just tried this sequence again, and as we speak it is capturing the USMT settings.

    so my worst fears have come true, clearly an update on my new XP builds is possible causing this administrative limit error!

    I am not sure if it is all going to complete but I would be extremely appreciative of any help.


    Thanks

    Lee
    Wednesday, November 4, 2009 11:10 AM

Answers

  • THIS PROBLEM is directly related to KB 947571.. A side effect of this patch is it causes failures at the "Request State Store" step... Uninstall this patch, and restart the computer.  In some instances you may need to reinstall the SCCM client..
    I've had this problem during our migration and it started right when this patch was released a couple weeks ago...  Its main problem is breaking OCS Front End servers.... Way to go MSFT..

    Fixed all of our problems (just make sure things like WSUS don't reinstall it right back)
    Thursday, November 5, 2009 12:14 AM

All replies

  • AS AN UPDATE.

    Even with SP2 instead of SP2, I get quite a long way, after it has re-installed Windows 7, it goes to the 'Request State Store' Hangs there for quite a long time 'As i think it is trying 30 times as i set it to this' and eventually errors out.

    I have captured the log and and enclose a snipit of where this error is......


    ****

    <![LOG[Let the parent group (Restore User Files and Settings) decides whether to continue execution]LOG]!><time="11:40:52.094+000" date="11-04-2009" component="TSManager" context="" type="0" thread="2300" file="instruction.cxx:3210">
    <![LOG[The execution of the group (Restore User Files and Settings) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="11:40:52.110+000" date="11-04-2009" component="TSManager" context="" type="3" thread="2300" file="instruction.cxx:2424">
    <![LOG[Failed to run the last action: Request State Store. Execution of task sequence failed.
    Unknown error (Error: 00004005;
    Source: Unknown)]LOG]!><time="11:40:52.110+000" date="11-04-2009" component="TSManager" context="" type="3" thread="2300" file="engine.cxx:214">
    <![LOG[Sending status message . . .]LOG]!><time="11:40:52.110+000" date="11-04-2009" component="TSManager" context="" type="1" thread="2300" file="utility.cxx:292">

    My next attempt would be the file permissions on that share, however Administrators have full access to that area. and Domain admin is member of this and my network account is a member of that so cant see why it would be that :S


    Thanks

    Lee
    Wednesday, November 4, 2009 11:49 AM
  • I just posted earlier today the same issue.  Any luck getting this resolved?
    Terry
    Wednesday, November 4, 2009 9:46 PM
  • THIS PROBLEM is directly related to KB 947571.. A side effect of this patch is it causes failures at the "Request State Store" step... Uninstall this patch, and restart the computer.  In some instances you may need to reinstall the SCCM client..
    I've had this problem during our migration and it started right when this patch was released a couple weeks ago...  Its main problem is breaking OCS Front End servers.... Way to go MSFT..

    Fixed all of our problems (just make sure things like WSUS don't reinstall it right back)
    Thursday, November 5, 2009 12:14 AM
  • Yep you are right.  During my reference machien build I am installing updates and sure enough that patch was in there.  I removed it, rebuild my gold image and redeployed and everything works fine now.  Microsoft should put something in the KB article about known side effects besides just breaking OCS it breaks this too.

    Terry
    Thursday, November 5, 2009 4:25 AM
  • I had this same issue and found uninstalling patch KB974571 resolved the issue. Does Microsoft plan on releasing a hotfix for this?
    • Proposed as answer by NealT Wednesday, January 20, 2010 6:02 PM
    Monday, November 23, 2009 3:03 AM
  • there is a fix coming, but in the meantime take a look at Eric's workaround in this post.
    my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
    Thursday, December 3, 2009 10:30 AM
    Moderator
  • Cool thanks Niall
    Tuesday, December 8, 2009 10:16 PM
  • Has a fixed been released yet?  I know there was a fix for OCS.
    BR
    Monday, December 21, 2009 5:16 PM