CU1 has been installed on my site server and XP clients. I mean, this should be working. Does it make sense to install KB2910552? Not really since CU1 has already been applied.
I have ADK 8.1 installed. Are you saying replacing the bcdboot.exe file from ADK 8.0 is also a possible workaround? Thanks, Brian Sent from my iPhone > On May 8, 2014, at 12:37 PM, "Krueger, Jeff" <[email protected]> wrote: > > Interesting, that’s how it should work. But I haven’t tried the CU1 for R2 > yet, I used the previous workaround of replacing the bcdboot.exe file in the > 8.1 ADK with the one from the older ADK. > > From: [email protected] [mailto:[email protected]] > On Behalf Of Brian McDonald > Sent: Thursday, May 8, 2014 1:27 PM > To: [email protected] > Subject: Re: [mssms] Fwd: [MDT-OSD] XP-Win7 migration with CM12r2 > > Hmmmm... > > I don't see how this could be the problem though. CU1 was applied to my CM > 2012 R2 server last night. > > I just created my WinPE 3.1 boot image today. When I updated the distribution > point with the new package, it should've already received the new bits. > > Ideas? > > Brian > > Sent from my iPhone > > On May 8, 2014, at 12:14 PM, "Krueger, Jeff" <[email protected]> wrote: > > Yeah, when you update the boot image it will mount the PE wim and inject the > updated SCCM bits into the boot image. > > From: [email protected] [mailto:[email protected]] > On Behalf Of Brian McDonald > Sent: Thursday, May 8, 2014 1:06 PM > To: [email protected] > Subject: Re: [mssms] Fwd: [MDT-OSD] XP-Win7 migration with CM12r2 > > But my boot image is WinPE 3.1 in this case, how do I update it? Just update > DP? > > Brian > > Sent from my iPhone > > On May 8, 2014, at 11:59 AM, "Jason Sandys" <[email protected]> wrote: > > This is a known issue fixed by CU1 (and updating your boot images afterwards). > > > > J > > From: [email protected] <[email protected]> on > behalf of Brian McDonald <[email protected]> > Sent: Thursday, May 8, 2014 11:37 AM > To: [email protected] > Subject: Re: [mssms] Fwd: [MDT-OSD] XP-Win7 migration with CM12r2 > > I followed these steps and created a WinPE 3.1 boot image and USMT 4 pkg, > updated my TS. USMT completes with no errors, however, when it goes to stage > the boot image it fails. The Restart to Windows PE fails. > > "Failed to install boot image. Is not a valid Win32 application." Code: > 800700C1 > > Is this a known issue? How do I get around this? > > Thanks, > > Brian > > Sent from my iPhone > > On May 8, 2014, at 7:44 AM, "Jason Sandys" <[email protected]> wrote: > > Actually, you need to use WinPE 3.1 as WinPE 4.0 is not supported by > ConfigMgr 2012 R2. Thus, you need to load the AIK for Win 7 and AIK For Win 7 > SP1 supplement on another system (not your primary site server) and manually > create the WinPE images there. These can then be imported into ConfigMgr. As > for USMT, you can just grab the files from the same AIK installation and > create a new package for them and reference that in your TS. > > > > A couple of quick web searches and you'll find detailed step by steps for all > of the above. > > > > J > > From: [email protected] <[email protected]> on > behalf of Brian McDonald <[email protected]> > Sent: Thursday, May 8, 2014 7:33 AM > To: [email protected] > Subject: [mssms] Fwd: [MDT-OSD] XP-Win7 migration with CM12r2 > > Trying my luck here! :) > > Brian > > Sent from my iPhone > > Begin forwarded message: > > From: Brian McDonald <[email protected]> > Date: May 8, 2014 at 5:09:35 AM CDT > To: <[email protected]> > Subject: [MDT-OSD] XP-Win7 migration with CM12r2 > Reply-To: <[email protected]> > > 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. > >
