locked
Capture error GetCurrentManagementPointEx() failed. 0x80004005 RRS feed

  • Question

  • Hey everyone

    I dont know if it's the right place to post this, but now it's here and i need a fix to this problem soon as possible. I created a USB capture media with sccm 2012, i run it on the client that i need to capture the image from, i filled every critica such as network location and user/password, Soon as i click next, im getting the "task sequence: image capture wizard has failed with the error code (0x80004005)". Here is some of my smslog. Will post a image and log file when my account got verified.....

    GetCurrentManagementPointEx() failed. 0x80004005. PrepareSMSClient 6/28/2018 4:00:50 PM 6624 (0x19E0)
    GetMPInformation() failed. 0x80004005. PrepareSMSClient 6/28/2018 4:00:50 PM 6624 (0x19E0)
    Failed to wait for Ccmexec service to be fully operational (0x80004005) PrepareSMSClient 6/28/2018 4:00:50 PM 6624 (0x19E0)
    Failed waiting for client agent service to initialize. Code 0x80004005 PrepareSMSClient 6/28/2018 4:00:50 PM 6624 (0x19E0)
    Failed to prepare SMS Client for capture, hr=80004005 PrepareSMSClient 6/28/2018 4:00:50 PM 6624 (0x19E0)
    Failed to prepare SMS Client for capture, hr=80004005 PrepareSMSClient 6/28/2018 4:00:50 PM 6624 (0x19E0)
    Process completed with exit code 2147500037 TSManager 6/28/2018 4:00:50 PM 3668 (0x0E54)
    Failed to run the action: Prepare Configuration Manager Client. 
    Unspecified error (Error: 80004005; Source: Windows) TSManager 6/28/2018 4:00:50 PM 3668 (0x0E54)

    As you can see it keeps telling me that "GetCurrentManagementPointEx() failed" but it doesn't tell me why it failed....my client can reach out to sccm server just fine. So i really dont know where do i get started to fix this error. I've tryed reboot the client, create a new capture media, Search for help in google, but apperently there's no one who got  solution for this error yet... PLZ Any SCCM geniue help plz, i've been stucked with this project in 3 month now.......


    Thursday, June 28, 2018 2:29 PM

Answers

  • I solved halv of the problem by having a clean image without domain join just as mentioned, the other halv is some buildin apps from microsoft that preventing sysprep step, i looked into sysprep log and found which app was the problem and removed them 1 by 1 .PS DO NOT REMOVE ALL BUILDIN APPS!! or else, even if you successfull capture the image after u deploying it you will get boot loop error.
    • Marked as answer by Enduva Molrich Wednesday, September 19, 2018 7:56 AM
    Wednesday, September 19, 2018 7:55 AM

All replies

  • Please check the CcmExec.log and the LocationServices.log files on the client. Those should give you a hint on why the client is unable to get the MP information.

    Thursday, June 28, 2018 8:53 PM
  • Hey, thank for you reply. I have looked into these logs, nothing helpful in there. But i did find out what's the cause of this problem. It seems like the sccm client was not installede correctly first time on the capture client, andi didnt noticed it and took it off the domain. When i resign the client back in domain and reinstalled the sccm client, the error was fixed.

    Then.... i ran into another problem. this is my smts.log.

    Timed out waiting for ccmexec service to be fully operational PrepareSMSClient 6/29/2018 2:32:26 PM 7676 (0x1DFC)
    Failed to wait for Ccmexec service to be fully operational (0x80004005) PrepareSMSClient 6/29/2018 2:32:26 PM 7676 (0x1DFC)
    Failed waiting for client agent service to initialize. Code 0x80004005 PrepareSMSClient 6/29/2018 2:32:26 PM 7676 (0x1DFC)
    Failed to prepare SMS Client for capture, hr=80004005 PrepareSMSClient 6/29/2018 2:32:26 PM 7676 (0x1DFC)
    Failed to prepare SMS Client for capture, hr=80004005 PrepareSMSClient 6/29/2018 2:32:26 PM 7676 (0x1DFC)
    Failed to run the action: Prepare Configuration Manager Client. 
    Unspecified error (Error: 80004005; Source: Windows) TSManager 6/29/2018 2:32:26 PM 7588 (0x1DA4)
    The execution of the group (Capture the Reference Machine) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows) TSManager 6/29/2018 2:32:26 PM 7588 (0x1DA4)
    Failed to run the last action: Prepare Configuration Manager Client. Execution of task sequence failed.
    Unspecified error (Error: 80004005; Source: Windows) TSManager 6/29/2018 2:32:26 PM 7588 (0x1DA4)
    Task Sequence Engine failed! Code: enExecutionFail TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    Task sequence execution failed with error code 80004005 TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    Failed to delete directory 'C:\_SMSTaskSequence' TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    DeleteFile(B) failed for C:\_SMSTaskSequence\sms\bin\x64\CcmCore.dll TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    RemoveFile() failed for C:\_SMSTaskSequence\sms\bin\x64\CcmCore.dll. 0x80070005. TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    DeleteFile(B) failed for C:\_SMSTaskSequence\sms\bin\x64\CcmUtilLib.dll TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    RemoveFile() failed for C:\_SMSTaskSequence\sms\bin\x64\CcmUtilLib.dll. 0x80070005. TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    DeleteFile(B) failed for C:\_SMSTaskSequence\sms\bin\x64\msvcp120.dll TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    RemoveFile() failed for C:\_SMSTaskSequence\sms\bin\x64\msvcp120.dll. 0x80070005. TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    DeleteFile(B) failed for C:\_SMSTaskSequence\sms\bin\x64\msvcr120.dll TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    RemoveFile() failed for C:\_SMSTaskSequence\sms\bin\x64\msvcr120.dll. 0x80070005. TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    DeleteFile(B) failed for C:\_SMSTaskSequence\sms\bin\x64\TsCore.dll TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    RemoveFile() failed for C:\_SMSTaskSequence\sms\bin\x64\TsCore.dll. 0x80070005. TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    DeleteFile(B) failed for C:\_SMSTaskSequence\sms\bin\x64\TsManager.exe TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    RemoveFile() failed for C:\_SMSTaskSequence\sms\bin\x64\TsManager.exe. 0x80070005. TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    DeleteFile(B) failed for C:\_SMSTaskSequence\sms\bin\x64\TsMessaging.dll TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    RemoveFile() failed for C:\_SMSTaskSequence\sms\bin\x64\TsMessaging.dll. 0x80070005. TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence\sms\bin\x64 TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence\sms\bin TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence\sms TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    SetNamedSecurityInfo() failed. TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    SetObjectOwner() failed. 0x80070005. TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005. TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    Missing TS Progress UI executable C:\_SMSTaskSequence\sms\bin\x64\TsProgressUI.exe. TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    GetTsRegValue() is unsuccessful. 0x80070002. TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)
    Error executing Task Sequence Manager service. Code 0x80004005 TSManager 6/29/2018 2:44:14 PM 7588 (0x1DA4)

    any idea, how i fix these?

    Friday, June 29, 2018 12:53 PM
  • Maybe i am misinterpreting what you said but just to confirm, you are not joining your reference machine to the domain are you? 


    Dan Padgett | Blog: http://execmgr.net | Twitter: @danjpadgett

    Friday, June 29, 2018 2:35 PM
  • nope. i took it off domain befor i start to capture. As i mention ,the error was fixed after i reinstalling the ccm client from fresh, then i ran into some sysprep error, that got fixed by removing the win 10 building appstore apps. And now the image is capture and uploaded to the server. But... now i have another error, the client pc after capture cannot boot, it stuck with "windows could not complete the installation to install windows on this computer restart installation" and it goes in a loop. I've been looking into the sysprep logs to see what's going on, it clearly have something to do with OOBE, as well is there the error message pops up. So now im trying to some how disable the welcome to windows 10 screen or get pass that point. I've been searching for solution online have looked into http://troubleshooter.xyz/wiki/fix-windows-could-not-complete-the-installation/ it doesn't seems to work, and the scenario in the topic isn't quite the samme as mine....

    Setuppac error log

    2018-07-02 09:35:19, Error                 SYSPRP RenewLocalSIDs for  RDP-Tcp FAILED: 1332
    2018-07-02 09:35:19, Warning               SYSPRP RestoreTSCustomSecurity() FAILED: 1332. To see if this is an error, please see message(s) above.
    2018-07-02 09:35:19, Info                  SYSPRP ResetTSRDSAppXKeys on AUINSTALLAGENT_REG_STAGINGINPROGRESS FAILED: 2
    2018-07-02 09:35:19, Error      [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'LSMSysPrepRestore' from C:\Windows\System32\setup\tssysprep.dll; dwRet = 0x534[gle=0x00000534]
    2018-07-02 09:35:19, Error                 SYSPRP ActionPlatform::ExecuteAction: Error in executing action; dwRet = 0x534[gle=0x00000534]
    2018-07-02 09:35:19, Error                 SYSPRP ActionPlatform::ExecuteActionList: Error in execute actions; dwRet = 0x534[gle=0x00000534]
    2018-07-02 09:35:19, Error                 SYSPRP SysprepSession::Execute: Error in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Specialize.xml; dwRet = 0x534
    2018-07-02 09:35:19, Error                 SYSPRP RunPlatformActions:Failed while executing SysprepSession actions; dwRet = 0x534
    2018-07-02 09:35:19, Info                  IBS    Callback_Specialize: Internal Providers Specialized Failed. System can't proceed to handle Internal Providers
    2018-07-02 09:35:19, Error      [0x060435] IBS    Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x534
    2018-07-02 09:35:56, Info       [0x070042] DIAG   CallBack_DiagnosticDataSend: Called with notification for Error published by ErrorHandler
    2018-07-02 09:35:56, Info       [0x0601d7] IBS    InstallWindows:Error Type = 3211266
     

    Monday, July 2, 2018 10:40 AM
  • > "i took it off domain befor i start to capture"

    For best results, reference systems should never be joined to a domain at any point.

    What OS are you trying to capture?

    Why aren't you using an automated image build and capture process?


    Jason | https://home.configmgrftw.com | @jasonsandys


    Tuesday, July 10, 2018 4:49 PM
  • because the reference machine have some program that's very complex, and some of them are not installede as exe or msi. example we have some indusoft symbol components to read our plcs, they are very complex to install because it need some binary file copied to the right dirctory etc, and we also have some software that cannot run with the latest java version 1.8, so we have different version of java running on the reference machine, and edit it in the windows path that refers to the software so they using the right java version.

    And you mention the reference machine should never be joined to a domain at start? can it really lead to the problem that i have now?

    thank for you reply

    Thursday, September 6, 2018 1:42 PM
  • > "because the reference machine have some program that's very complex"

    If you can manually do it, you can script it. Automation is what IT should be good at.

    For Java, same answer, script it.

    For the domain join, yes, absolutely. Many things happen to a system when joined to a domain including (but not necessarily limited to) group policies being applied that are not fully reversed when unjoined from the domain. The whole point of a reference image is to be as clean and generic as possible. There are certainly trade-offs and grey area here based on the scenario, but there are some fairly concrete things, like joining the domain, that are best avoided at all costs because they will have negative impacts.


    Jason | https://home.configmgrftw.com | @jasonsandys

    • Proposed as answer by Dan Padgett Sunday, September 9, 2018 4:20 PM
    Thursday, September 6, 2018 1:53 PM
  • I solved halv of the problem by having a clean image without domain join just as mentioned, the other halv is some buildin apps from microsoft that preventing sysprep step, i looked into sysprep log and found which app was the problem and removed them 1 by 1 .PS DO NOT REMOVE ALL BUILDIN APPS!! or else, even if you successfull capture the image after u deploying it you will get boot loop error.
    • Marked as answer by Enduva Molrich Wednesday, September 19, 2018 7:56 AM
    Wednesday, September 19, 2018 7:55 AM
  • Ran into the same issue. Machine not in the domain and stil trying to connect to MP due to ConfigMgr client being installed. Try uninstalling the ConfigMgr client. Runs fine after this.
    Thursday, January 16, 2020 10:55 AM