jaskelly3578 Posted January 16, 2014 Report post Posted January 16, 2014 Hi Rocket Man, I have sorted the issue. The client upgrade that came with the one of the hotfix's was not being installed during the OSD. The was the smallest of errors in the PATCH=.................. command that i was using. Now this has been sorted the task sequence components have been upgraded and the error has disappeared. Thanks for you help. Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted January 16, 2014 Report post Posted January 16, 2014 Good stuff Quote Share this post Link to post Share on other sites More sharing options...
joec212000 Posted February 5, 2014 Report post Posted February 5, 2014 I'm having the same exact issue. in my MDT TS. The drivers apply just fine. Immediately after the Setup and Configure Windows Action starts. The machine quickly reboots and comes back into the TS to install the config mgr client. Once the client install completes the machine goes to the logon screen and will not complete the TS. This only started after I upgraded to R2. My TS hasn't changed. Any takers? Quote Share this post Link to post Share on other sites More sharing options...
jaskelly3578 Posted February 5, 2014 Report post Posted February 5, 2014 Have you made sure that you are installing the correct client hotfix? Make sure you are using the right type ie x86 or x64 in the PATCH command of the Setup and Configure Windows step. This will require changing the TS. See my TS for example. This is installing the x86 patch to a x86 deployment. 1 Quote Share this post Link to post Share on other sites More sharing options...
kdevries Posted April 22, 2014 Report post Posted April 22, 2014 I am having this same issue. I have SCCM 2012 R2 CU1 installed and I cannot get the applications to deploy during an install of a OSD. Can anyone give me any directions? Thanks Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted April 22, 2014 Report post Posted April 22, 2014 Depends on the issues you're having. An often seen problem is a combination of SSD drives with application installations. A solution (workaround) for that is SMSTSMPListRequestTimeout, see also: http://technet.microsoft.com/en-us/library/hh273375.aspx Quote Share this post Link to post Share on other sites More sharing options...
