We have a SCCM R3 SP2 installation with Client Push Installation configured. We also use OSD. On occasion, the “Setup Windows and ConfigMgr” step in a Task Sequence fails with error code 16389. It seems that when ccmsetup is being executed as part of the task sequence, the SCCM server recognizes the PC and pushes the client to it. The new ccmsetup process kills the ccmsetup process being run from the Task Sequence. From the ccm.log on the server (filtered to rows which contain the client name): C:\WICM\16389>find /i "PCNAME" ccm.log ---------- CCM.LOG ======>Begin Processing request: "PCNAME_DOMAINNAME.DOMAINNAME", machine name: "PCNAME" $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:14:38.162 2011 Eastern Daylight Time><thread=12936 (0x3288)> ---> Attempting to connect to administrative share '\\PCNAME.DOMAINNAME\admin$' using account 'DOMAINNAME\_SCCMComputer'~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:14:38.163 2011 Eastern Daylight Time><thread=12936 (0x3288)> ---> Connected to administrative share on machine PCNAME.DOMAINNAME using account 'DOMAINNAME\_SCCMComputer'~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:14:46.929 2011 Eastern Daylight Time><thread=12936 (0x3288)> ---> Attempting to make IPC connection to share <\\PCNAME.DOMAINNAME\IPC$> ~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:14:46.929 2011 Eastern Daylight Time><thread=12936 (0x3288)> ---> Searching for SMSClientInstall.* under '\\PCNAME.DOMAINNAME\admin$\'~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:14:46.930 2011 Eastern Daylight Time><thread=12936 (0x3288)> ---> Service Pack version from machine "PCNAME" is 3 $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:14:47.481 2011 Eastern Daylight Time><thread=12936 (0x3288)> ---> Unable to connect to WMI (r) on remote machine "PCNAME", error = 0x8004100e. $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:14:47.681 2011 Eastern Daylight Time><thread=12936 (0x3288)> ---> Creating \ VerifyingCopying exsistance of destination directory \\PCNAME\admin$\system32\ccmsetup.~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:14:47.682 2011 Eastern Daylight Time><thread=12936 (0x3288)> ---> Copying client files to \\PCNAME\admin$\system32\ccmsetup.~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:14:48.839 2011 Eastern Daylight Time><thread=12936 (0x3288)> ---> Copying file "E:\SMS\bin\I386\MobileClient.tcf" to "\\PCNAME\admin$\system32\ccmsetup\MobileClient.tcf" $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:14:48.887 2011 Eastern Daylight Time><thread=12936 (0x3288)> ---> Created service "ccmsetup" on machine "PCNAME". $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:14:50.417 2011 Eastern Daylight Time><thread=12936 (0x3288)> ---> Started service "ccmsetup" on machine "PCNAME". $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:15:11.532 2011 Eastern Daylight Time><thread=12936 (0x3288)> ---> Deleting SMS Client Install Lock File '\\PCNAME.DOMAINNAME\admin$\SMSClientInstall.0A1'~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:15:11.572 2011 Eastern Daylight Time><thread=12936 (0x3288)> ---> Completed request "PCNAME_DOMAINNAME.DOMAINNAME", machine name "PCNAME". $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:15:11.624 2011 Eastern Daylight Time><thread=12936 (0x3288)> Deleted request "PCNAME_DOMAINNAME.DOMAINNAME", machine name "PCNAME" $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:15:11.624 2011 Eastern Daylight Time><thread=12936 (0x3288)> <======End request: "PCNAME_DOMAINNAME.DOMAINNAME", machine name: "PCNAME". $$<SMS_CLIENT_CONFIG_MANAGER><Thu May 05 10:15:11.625 2011 Eastern Daylight Time><thread=12936 (0x3288)> C:\WICM\16389> From the ccmsetup.log on the client (showing the rows around Thu May 05 10:14:48.887 2011, the time when the server pushed the client): <![LOG[File download 99% complete (17760256 of 17847296 bytes).]LOG]!><time="10:14:28.350+240" date="05-05-2011" component="ccmsetup" context="" type="0" thread="2372" file="ccmsetup.cpp:8694"> <![LOG[File download 99% complete (17825792 of 17847296 bytes).]LOG]!><time="10:14:28.350+240" date="05-05-2011" component="ccmsetup" context="" type="0" thread="2372" file="ccmsetup.cpp:8694"> <![LOG[File download 100% complete (17847296 of 17847296 bytes).]LOG]!><time="10:14:28.350+240" date="05-05-2011" component="ccmsetup" context="" type="0" thread="2372" file="ccmsetup.cpp:8694"> <![LOG[Download complete.]LOG]!><time="10:14:29.835+240" date="05-05-2011" component="ccmsetup" context="" type="1" thread="2372" file="ccmsetup.cpp:5337"> <![LOG[Successfully downloaded client files.]LOG]!><time="10:14:29.835+240" date="05-05-2011" component="ccmsetup" context="" type="1" thread="2372" file="ccmsetup.cpp:2539"> <![LOG[Searching for available transform]LOG]!><time="10:14:29.835+240" date="05-05-2011" component="ccmsetup" context="" type="1" thread="2372" file="ccmsetup.cpp:8873"> <![LOG[Failed to find resource file client.mst for locale 1033]LOG]!><time="10:14:29.835+240" date="05-05-2011" component="ccmsetup" context="" type="1" thread="2372" file="util.cpp:578"> <![LOG[Not trying base path for resource file]LOG]!><time="10:14:29.835+240" date="05-05-2011" component="ccmsetup" context="" type="1" thread="2372" file="util.cpp:712"> <![LOG[Failed to find resource file 'client.mst']LOG]!><time="10:14:29.835+240" date="05-05-2011" component="ccmsetup" context="" type="3" thread="2372" file="util.cpp:718"> <![LOG[0, HRESULT=80070002 (e:\nts_sms_fre\sms\framework\core\ccmcore\util.cpp,719)]LOG]!><time="10:14:29.835+240" date="05-05-2011" component="ccmsetup" context="" type="0" thread="2372" file="util.cpp:719"> <![LOG[No transform available for this locale. Installation will proceed with no transformation.]LOG]!><time="10:14:29.835+240" date="05-05-2011" component="ccmsetup" context="" type="1" thread="2372" file="ccmsetup.cpp:8912"> <![LOG[Updated security on object C:\WINDOWS\system32\ccmsetup\.]LOG]!><time="10:14:29.850+240" date="05-05-2011" component="ccmsetup" context="" type="0" thread="2372" file="ccmsetup.cpp:8849"> <![LOG[==========[ ccmsetup started in process 3320 ]==========]LOG]!><time="10:14:50.647+240" date="05-05-2011" component="ccmsetup" context="" type="1" thread="3324" file="ccmsetup.cpp:9010"> <![LOG[Version: 4.0.6487.2000]LOG]!><time="10:14:50.647+240" date="05-05-2011" component="ccmsetup" context="" type="1" thread="3324" file="ccmsetup.cpp:2068"> <![LOG[Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required.]LOG]!><time="10:14:50.647+240" date="05-05-2011" component="ccmsetup" context="" type="1" thread="3324" file="ccmsetup.cpp:4093"> <![LOG[Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="10:14:50.647+240" date="05-05-2011" component="ccmsetup" context="" type="1" thread="3324" file="ccmsetup.cpp:4102"> What is the best way to prevent this behavior? Thanks, Terence

How often are your discoveries running?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Hi Jason, We have Active Directory System Discovery running daily at 8:00 PM, with delta discovery running every 5 minutes, but these are existing computer accounts in AD; the PC is just getting reimaged. The way we advertise the Task Sequences: we have a pre-execution hook that removes the system from SCCM, and then adds it back in to a collection that gets the Task Sequence advertisement. Thanks, Terence

we have a pre-execution hook that removes the system from SCCM, and then adds it back in to a collection That might cause the client push installation.Torsten Meringer | http://www.mssccmfaq.de

I concur with Torsten. Why remove it only to add it back? Why not just add it to the appropriate collection without deleting it from ConfigMgr?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

We have been using the UnknownComputer.asmx web service since September 2008. At the time, to reimage an existing computer, having the hook remove the record and then use the web service to add it back to a collection seemed like the way to go. We have about 35,000 clients spread across 230 secondary sites, 30 Task Sequences targeted to 10 different collections, and average 40-50 reimages a day. Since 2008, we've reimaged roughly 7,000 computers using Task Sequences. The weird thing is, this issue has cropped up only recently. It started in September 2010 and happened three times total in the last 4 months of the year. Since 2011, it has happened with more frequency (48 times); in the last 3 months it has happened 4 times in March, 3 times in April, and now 10 times in May (out of approximately 1,800 Task Sequences run in those 2 1/2 months). Our MS consultant gave us a new UnknownComputer.asmx web service that adds existing clients to collections without having to remove it first; I will modify our boot CD to use that, but since we just had the Secondary Site LAN admins burn new CDs in March (we went to Native mode) I was hoping for something I could put in the task sequences to alleviate this issue.