USMT fails at Request User State Storage

[viklc]

Hi everyone,

 

My scenario.

 

We want to upgrade our XP and Vista Clients to Windows 7. In fact we are already a long ways.

However we would like to use USMT to do a PC refresh using the migration store.

Today we manually run a batch-job each time before refreshing/upgrading the PC with a new OS.

 

I have a standard Task Sequence including Capture/Restore user files and settings.

 

Standard_TS_USMT.xml

 

When the TS is executed on a client machine - it almost immediately stumbles upon "Request User State Storage"

 

 

(I have attached 2 different smsts.log files)

 

Virtual_XP_smsts.log

XP_smsts.log

 

KB974571 is NOT installed - neither on the client nor on the SCCM server.

 

As far as I'm concerned sharing and security should be correct on the SMP share.

On the client I can browse to the folder on the server, and manually copy files/folders.

 

 

Seems like the client cannot resolve where to locate the SMP store?

 

What am I missing? IIS settings? WebDAV settings?

 

I have read a ton of threads in various forums - most of them mentioning the dreaded patch KB974571, which apparently breaks the USMT functionality.

However as stated previous - KB974571 isn't present on either server or client.

 

Suggestions anyone?

[viklc]

*BUMP*

 

Anyone?

[anyweb]

hi there,

have you read this post ?

 

http://support.microsoft.com/default.aspx?scid=kb;en-us;959812&sd=rss&spid=12769

 

cheers

niall

 

 

Operating System Deployment (OSD) tasks may fail randomly in System Center Configuration Manager 2007 Service Pack 1-based systems

Hotfix download is available Hotfix Download Available

View and request hotfix downloads

View products that this article applies to.

On This Page

 

* SYMPTOMS

* CAUSE

* RESOLUTION

o Service Pack Information

o Hotfix information

+ Prerequisites

+ Restart requirement

+ Hotfix replacement information

+ File information

* STATUS

* MORE INFORMATION

 

Expand all | Collapse all

SYMPTOMS

Consider the following scenario:You perform an Operating System Deployment (OSD)...

Consider the following scenario:

 

* You perform an Operating System Deployment (OSD) task in Microsoft System Center Configuration Manager 2007 Service Pack 1(SP1)-based systems.

* In this OSD task, you use User State Migration Tool (USMT) to capture user state information and store it on Sate Migration Points (SMP).

 

In this scenario, this OSD task may fail. Additionally, the following log information is logged in the Smsts.log file:

 

<![LOG[signature verification failed]LOG]!><time="" date="" component="OSDSMPClient" context="" type="2" thread="6068" file="libcrypt.cpp:351">

<![LOG[signature check failed: ]LOG]!><time="" date="" component="OSDSMPClient" context="" type="3" thread="6068" file="libsmsmessaging.cpp:2476">

<![LOG[ClientRequestToMP::DoRequest failed (0x80004005).]LOG]!><time="" date="" component="OSDSMPClient" context="" type="3" thread="6068" file="smpclient.cpp:1160">

<![LOG[ExecuteCaptureRequestMP failed (0x80004005).]LOG]!><time="" date="" component="OSDSMPClient" context="" type="3" thread="6068" file="smpclient.cpp:2688">

<![LOG[ExecuteCaptureRequest failed (0x80004005).]LOG]!><time="" date="" component="OSDSMPClient" context="" type="3" thread="6068" file="smpclient.cpp:2762">

<![LOG[OSDSMPClient finished: 0x00004005]LOG]!><time="" date="" component="OSDSMPClient" context="" type="1" thread="6068" file="main.cpp:120">

 

Back to the top

CAUSE

The management point certificate information is not refreshed immediately. There...

The management point certificate information is not refreshed immediately. Therefore, the management point certificate may be missing for some time. If the OSD task starts in this period, the task fails because clients cannot connect to the management point to obtain the SMP list.

Back to the top

RESOLUTION

Service Pack Information To resolve this problem, obtain the latest service pack...

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft System Center Configuration Manager 2007, available from this Microsoft web site: http://www.microsoft.com/downloads/details.aspx?FamilyID=3318741a-c038-4ab1-852a-e9c13f8a8140 (http://www.microsoft.com/downloads/details.aspx?FamilyID=3318741a-c038-4ab1-852a-e9c13f8a8140)

For a list of issues resolved in this service pack, click on the following article number in the Microsoft Knowledgebase:

971348 (http://support.microsoft.com/kb/971348/ ) List of hotfixes and updates that are contained in System Center Configuration Manager 2007 Service Pack 2

Back to the top

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

 

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

 

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have System Center Configuration Manager 2007 Service Pack 1 installed to apply this hotfix.

[viklc]

Hi Niall,

 

Thanx - but as far as I'm concerned - my Configmgr is already at SP2

And therefore I shouldn't be affected by that problem (correct me if I'm wrong)

 

 

Any other suggestions?

[viklc]

Case solved

 

Deleted and re-created the SMP role on my SCCM-server..

 

That fixed the problem

 

Hope someone else finds this useful

[anyweb]

sometimes all you need to do is to delete the obsolete record for the pc that you are migrating, check in Configuration Manager if the computername has a matching computername marked as obsolete, if so, delete it and try again.