For the most part these are new builds, the one thing that we do is pre-create the computer account in AD and add them to various AD groups
Sent from my iPhone Fritzroy Guillot On Sep 13, 2013, at 4:18 PM, "Jeff Poling" <[email protected]> wrote: > I am not sure about that error. . .perhaps someone else on the list has seen > it; however, I've seen similar behavior when there are duplicate GUIDs in > ConfigMgr for a PC. Have you validated there are no duplicates? Also, have > you checked to make sure the client in question is Approved? > > Jeff > > > On Fri, Sep 13, 2013 at 2:24 PM, Fritzroy Guillot <[email protected]> wrote: >> The only thing that stands out in those logs is the following line item >> Unable to get SMS_MPInformationEx.MP="<MP Server Name>" of [<MP Server >> Name>] from WMI due to error 0x80041002 >> That was located in the Location Service Log. >> >> We are currently not specifying any custom properties for the client >> installation out side of what I mention about the CU2 updates. >> >> Are Task Sequence we are running a numbers of steps from enabling the TPM >> chip and installing MBAM and installing drivers. Really nothing to fancy. >> >> >> >> -Fritzroy >> >> >> >> Date: Fri, 13 Sep 2013 13:59:42 -0500 >> >> Subject: Re: [MDT-OSD] OSD Breaking CM12 Clients >> From: [email protected] >> To: [email protected] >> >> Is there anything of note in log files such as: >> >> LocationServices.log >> PolicyEvaluator.log >> ClientLocation.log >> ContentTransferManager.log >> DataTransferService.log >> >> Also, are you setting any custom properties for the installation of the >> client? >> >> I guess it might also help to know a bit about the steps in the TS. >> >> Jeff >> >> >> On Fri, Sep 13, 2013 at 1:31 PM, Fritzroy Guillot <[email protected]> wrote: >> We have also tested running the task sequence without the CU2 update and >> seen varying results in regards to the client being fully installed. But for >> the most part the communication to determine what applications should show >> up in software center is taking way to long. >> >> >> >> >> -Fritzroy >> >> >> >> Date: Fri, 13 Sep 2013 13:25:55 -0500 >> Subject: Re: [MDT-OSD] OSD Breaking CM12 Clients >> From: [email protected] >> To: [email protected] >> >> >> I have not seen this specifically, but one thing you could try would be to >> remove the CU2 patch step from the TS. See if the client responds better. >> >> If it does, then deploy the CU2 patch to a collection using the package that >> was installed (if you chose it) during the CU2 update. >> >> Jeff >> >> >> On Fri, Sep 13, 2013 at 1: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 >
