Like I said I haven’t tried the hot fix yet, we did the workaround of replacing 
the bootsect.exe file with an older version, and that has been working 100% for 
us.  The version of bootsect from the previous ADK works, you just have to 
replace the file in the install directory for ADK on your primary, and then 
update your PE 3.1 boot image (update DP)

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Brian McDonald
Sent: Friday, May 9, 2014 9:55 AM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] Fwd: [MDT-OSD] XP-Win7 migration with CM12r2

Yes sir I have installed CU1 on the XP clients.

Thanks!

Rich

Sent from my iPhone

On May 9, 2014, at 8:47 AM, "Jason Sandys" 
<ja...@sandys.us<mailto:ja...@sandys.us>> wrote:
Yes, CU1 includes that hotfix. I see sporadic reports of it not working though 
and am not sure of the commonality. Did you apply CU1 to the XP system begin 
reimaged?

J

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Brian McDonald
Sent: Friday, May 9, 2014 7:48 AM
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: Re: [mssms] Fwd: [MDT-OSD] XP-Win7 migration with CM12r2

Doesn't CU1 take care of this particular hot fix though? I have CU1 applied in 
my environment.

Sent from my iPhone

On May 9, 2014, at 1:06 AM, "Michael Niehaus" 
<michael.nieh...@microsoft.com<mailto:michael.nieh...@microsoft.com>> wrote:
Sounds like this:

http://support.microsoft.com/kb/2910552<https://urldefense.proofpoint.com/v1/url?u=http://support.microsoft.com/kb/2910552&k=DRaZFQufJSh%2Bz2CJu01vGA%3D%3D%0A&r=G7Rp%2FyVEkz9AB1xRQWzmh1E0dbzzZxlFIY6QTWSRqzc%3D%0A&m=3QD7Rgkaitp%2B202%2BC8M7WEstB19qPq0ifsLKJhLYw%2Fo%3D%0A&s=5de50467ff4fea7c658fd2d86c59d9f103a60d0f79c275d2dc22f83736354b55>
You cannot stage a Windows PE 3.1 boot image to a Windows XP-based computer in 
System Center 2012 R2 Configuration Manager

Thanks,
-Michael

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Brian McDonald
Sent: Thursday, May 8, 2014 7:45 PM
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: RE: [mssms] Fwd: [MDT-OSD] XP-Win7 migration with CM12r2

I did go with WAIK from Win7 as Jason Sandy's mentioned, but even with WinPE 
3.1 the staging of the WinPE fails in my task sequence.
________________________________
From: jaso...@outlook.com<mailto:jaso...@outlook.com>
Subject: Re: [mssms] Fwd: [MDT-OSD] XP-Win7 migration with CM12r2
Date: Thu, 8 May 2014 19:28:34 +0100
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
You'll need to go back to WAIK for the boot image

On 8 May 2014, at 13:33, "Brian McDonald" 
<mcdonald...@hotmail.com<mailto:mcdonald...@hotmail.com>> wrote:
Trying my luck here! :)

Brian

Sent from my iPhone

Begin forwarded message:
From: Brian McDonald <mcdonald...@hotmail.com<mailto:mcdonald...@hotmail.com>>
Date: May 8, 2014 at 5:09:35 AM CDT
To: <mdt...@lists.myitforum.com<mailto:mdt...@lists.myitforum.com>>
Subject: [MDT-OSD] XP-Win7 migration with CM12r2
Reply-To: <mdt...@lists.myitforum.com<mailto:mdt...@lists.myitforum.com>>
Hey all,

I have an SCCM 2012 R2 environment and have a couple hundred XP devices that 
need to be refreshed to Win7.

I have ADK 8.1 installed, but it appears the requirements to perform an 
in-place migration would include USMT 4.0 and the WinPE version from the ADK 
8.0. Can someone please confirm this and are there any other requirements 
needed to use USMT with hardlinks in this scenario?

Thanks,

Brian

Sent from my iPhone








________________________________

CONFIDENTIALITY NOTICE: This email contains information from the sender that 
may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected 
from disclosure. This email is intended for use only by the person or entity to 
whom it is addressed. If you are not the intended recipient, any use, 
disclosure, copying, distribution, printing, or any action taken in reliance on 
the contents of this email, is strictly prohibited. If you received this email 
in error, please contact the sending party by reply email, delete the email 
from your computer system and shred any paper copies.

Note to Patients: There are a number of risks you should consider before using 
e-mail to communicate with us. See our Privacy & Security page on 
www.henryford.com for more detailed information as well as information 
concerning MyChart, our new patient portal. If you do not believe that our 
policy gives you the privacy and security protection you need, do not send 
e-mail or Internet communications to us.

Reply via email to