Jump to content


radish

Usmt capture user status failed 0x00004005 ,usmt捕获用户状态失败

Recommended Posts

测试环境,测试环境

Win2016

SCCM1706  

ADK1709

测试客户端系统,测试客户端系统

Win10和Win7的

 

Usmt捕获用户状态失败0x00004005,请解决,谢谢

出现捕获用户状态失败
这怎么一回事?

无法捕获用户状态,因此无法捕获用户状态
,发生了什么?

 

smsts.log

1112.png

5555.png

3334444.png

55444.png

20180522_100750.jpg

 

 

已解决,通过网络保存用户状态迁移,不能用中文文件夹,改成英文 就可以正常通过网络捕获状态转移了。

Has been resolved, through the network to save the user state migration, can not use the Chinese folder, change to English can be normally transferred through the network capture state.

Edited by radish

Share this post


Link to post
Share on other sites

it's failing to talk to the USMT State Migration Point, is that configured ?

 

<![LOG[Error. Status code 500 returned]LOG]!><time="07:22:00.631-480" date="05-21-2018" component="OSDSMPClient" context="" type="0" thread="4276" file="libsmsmessaging.cpp:9551">
<![LOG[Received 1164 byte response.]LOG]!><time="07:22:00.631-480" date="05-21-2018" component="OSDSMPClient" context="" type="0" thread="4276" file="smpclient.cpp:2376">
<![LOG[pReply != NULL, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2391)]LOG]!><time="07:22:00.631-480" date="05-21-2018" component="OSDSMPClient" context="" type="0" thread="4276" file="smpclient.cpp:2391">
<![LOG[SMP Root share info response is empty]LOG]!><time="07:22:00.631-480" date="05-21-2018" component="OSDSMPClient" context="" type="3" thread="4276" file="smpclient.cpp:2391">
<![LOG[ClientRequestToSMP::ClientRootShareRequestToSMP failed. error = (0x80004005).]LOG]!><time="07:22:00.631-480" date="05-21-2018" component="OSDSMPClient" context="" type="3" thread="4276" file="smpclient.cpp:2442">
<![LOG[ExecuteRootShareInfoRequest(sRootShareList), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1717)]LOG]!><time="07:22:00.631-480" date="05-21-2018" component="OSDSMPClient" context="" type="0" thread="4276" file="smpclient.cpp:1717">
<![LOG[ClientRequestToSMP::DoRequest failed. error = (0x80004005).

Share this post


Link to post
Share on other sites

2 hours ago, anyweb said:

它没有与USMT国家移民点交谈,是否配置?

 

<![LOG [错误。状态码500返回] LOG]!> <time =“07:22:00.631-480”date =“05-21-2018”component =“OSDSMPClient”context =“”type =“0”thread =“4276”file =“libsmsmessaging.cpp:9551”>
<![LOG [Received [1164 byte response。] LOG]!> <time =“07:22:00.631-480”date =“05-21-2018”component =“OSDSMPClient” context =“”type =“0”thread =“4276”file =“smpclient.cpp:2376”>
<![LOG [pReply!= NULL,HRESULT = 80004005(e:\ nts_sccm_release \ sms \ client \ osdeployment \ osdsmpclient \ smpclient.cpp,2391)] LOG]!> <time =“07:22:00.631-480”date =“05-21-2018”component =“OSDSMPClient”context =“”type =“0”thread =“ 4276“file =”

<![LOG [ClientRequestToSMP :: ClientRootShareRequestToSMP失败。error =(0x80004005)。] LOG]!> <time =“07:22:00.631-480”date =“05-21-2018”component =“OSDSMPClient”context =“”type =“3”thread =“4276 “file =”smpclient.cpp:2442“>
<![LOG [ExecuteRootShareInfoRequest(sRootShareList),HRESULT = 80004005(e:\ nts_sccm_release \ sms \ client \ osdeployment \ osdsmpclient \ smpclient.cpp,1717)] LOG]!> time =“07:22:00.631-480”date =“05-21-2018”component =“OSDSMPClient”context =“”type =“0”thread =“4276”file =“smpclient.cpp:1717”>
< ![LOG [ClientRequestToSMP :: DoRequest失败。错误=(0x80004005)。

 

 

Hello, state migration point configuration, ah, Is dns problem?

2 hours ago, anyweb said:

 

 

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.