That checklist you were looking for: http://deploymentresearch.com/Research/Post/422/A-Geeks-Guide-for-upgrading-to-ConfigMgr-2012-R2-and-MDT-2013
Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Scott Kenyon Sent: Wednesday, June 03, 2015 11:12 AM To: [email protected] Subject: RE: [mssms] OSD Problems after Upgrading SCCM 2012 SP1 to SCCM 2012R2 What solved this for me, was to re-create the boot images, ensure I was using the correct system center client agent (in the task sequence) and then re-deploy to our OSD collection. Thanks for all the responses….. Scott Kenyon Technical Lead, Service Desk Dean of Medicine Information Technology UW School of Medicine 850 Republican Street, Box 358047 Seattle, WA 98109 Phone: 206.685.2825 Helpdesk: 206.221-2459 | [email protected]<mailto:[email protected]> [email protected]<mailto:[email protected]> uwmedicine.org<http://www.uwmedicine.org/> [Visit UW Medicine on.line]<http://uwmedicine.org/> The above email may contain patient identifiable or confidential information. Because email is not secure, please be aware of associated risks of email transmission. If you are communicating with a UW Medicine Provider or Researcher via email, your acceptance of the risk and agreement to the conditions for email communications is implied. (See http://www.uwmedicine.org/Global/Compliance/EmailRisk.htm.) The information is intended for the individual named above. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please notify the sender by reply email, and then destroy all copies of the message and any attachments. See our Notice of Privacy Practices at http://uwmedicine.washington.edu/. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mawdsley R. Sent: Wednesday, June 03, 2015 2:32 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OSD Problems after Upgrading SCCM 2012 SP1 to SCCM 2012R2 I think I had this issue a year or so ago.. and I think the solution was to recreate the Boot Images and decommission the old ones. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Scott Kenyon Sent: 02 June 2015 23:13 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] OSD Problems after Upgrading SCCM 2012 SP1 to SCCM 2012R2 Hello Ryan, Let me get the log file. And yes this is after a the Upgrade from SCCM 2012 SP1 CU5 to SCCM R2 Funny thing the stand alone task sequence media works just. Thanks for the assistance. Scott Kenyon Technical Lead, Service Desk Dean of Medicine Information Technology UW School of Medicine 850 Republican Street, Box 358047 Seattle, WA 98109 Phone: 206.685.2825 ServiceDesk: 206.221-2459 | [email protected]<mailto:[email protected]> [email protected]<mailto:[email protected]> uwmedicine.org<http://www.uwmedicine.org/> [Visit UW Medicine on.line]<http://uwmedicine.org/> The above email may contain patient identifiable or confidential information. Because email is not secure, please be aware of associated risks of email transmission. If you are communicating with a UW Medicine Provider or Researcher via email, your acceptance of the risk and agreement to the conditions for email communications is implied. (See http://www.uwmedicine.org/Global/Compliance/EmailRisk.htm.) The information is intended for the individual named above. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please notify the sender by reply email, and then destroy all copies of the message and any attachments. See our Notice of Privacy Practices at http://uwmedicine.washington.edu. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ryan Sent: Tuesday, June 02, 2015 9:18 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] OSD Problems after Upgrading SCCM 2012 SP1 to SCCM 2012R2 What do the logs say? The SMSTS log file will tell you if the device was found and why it does or doesn't show you task sequences. On Tue, Jun 2, 2015 at 10:34 AM, Scott Kenyon <[email protected]<mailto:[email protected]>> wrote: Is there an OSD check list after upgrading to SCCM 2012 R2? Applied all the necessary Hotfixes, but still receiving the same error message. OSD Task Sequence fails with "There are no task sequences available for this computer" I’ve updated the Boot Images and re-deployed the task sequence. Not sure if it will be necessary to re-create the MDT package, but this is going to be my next step. Then I’ll try re-creating the task sequence if the previous step fails. Any advice would be appreciated. Thank you, Scott Kenyon Technical Lead, Service Desk Dean of Medicine Information Technology UW School of Medicine 850 Republican Street, Box 358047 Seattle, WA 98109 Phone: 206.685.2825<tel:206.685.2825> ServiceDesk: 206.221-2459<tel:206.221-2459> | [email protected]<mailto:[email protected]> [email protected]<mailto:[email protected]> uwmedicine.org<http://www.uwmedicine.org/> [Visit UW Medicine on.line]<http://uwmedicine.org/> The above email may contain patient identifiable or confidential information. Because email is not secure, please be aware of associated risks of email transmission. If you are communicating with a UW Medicine Provider or Researcher via email, your acceptance of the risk and agreement to the conditions for email communications is implied. (See http://www.uwmedicine.org/Global/Compliance/EmailRisk.htm.) The information is intended for the individual named above. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please notify the sender by reply email, and then destroy all copies of the message and any attachments. See our Notice of Privacy Practices at http://uwmedicine.washington.edu. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
