have you checked the client is not stuck in provisioning mode<http://blogs.technet.com/b/configurationmgr/archive/2010/09/13/solution-after-a-configmgr-2007-osd-task-sequence-completes-the-client-may-not-automatically-pull-down-policy.aspx>? and have you tried installing the client without the CU2 patch to see if theres any difference ?
On Fri, Sep 13, 2013 at 8:15 PM, Fritzroy Guillot <[email protected]>wrote: > We have a strange issue that I was hoping someone could help us with. We > are currently using MDT 2012 Integrated in CM12 for our OSD deployments. > Here is the process: > We run our OSD build which completes without any issues, Once the machine > is on the network it then should talk to the CM12 server to pull down the > policies and find the additional applications that should be installed > through software center. > > Problem that we are seeing is that once the builds complete, it seems like > the CM12 client is never fully installed. Some times we are seeing over a > couple of hours before the CM12 client shows fully installed and is > communicating with the CM12 server. That is when applications are showing > up in the software center. > > We are concerned that we have a broken client because the OSD process. > > Couple of things to note, as part of our Task Sequence we are pushing out > the CU2 patch. > > > PATCH="%_SMSTSMDataPath%\OSD\CMP00257\CU2Patch\x64\configmgr2012ac-sp1-kb2854009-x64.msp" > > > -Fritzroy > >
