Why does it take a day or two to re-gen your image? A build and capture should only take a few hours. You are using a build and capture, correct? If not, why not? This is a perfect example of why doing anything else is like banging your head against the wall – it may feel good initially and give you some initial euphoria but it always leads to bad things in the long run.
J From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Berges Sent: Thursday, April 24, 2014 4:34 PM To: SMS Mailing List Subject: Re: [mssms] Upgraded from 2012 RTM to 2012 R2, OSD broke - ccmcore.dll is missing OK, so I think I have figured out the problem. Our reference image(s) were created using a build and capture task sequence in Configuration Manager (yes, yes, I know...), and as such contain the Configuration Manager client. In looking at the failed task sequence on the destination system, ccmcore.dll is nowhere to be found. I checked the boot images, CM client package, etc... it's there. I then started reviewing the ccmsetup.log, which showed that the install completed successfully. But when I reviewed the client.msi.log, I found some interesting entries: File: D:\Windows\system32\ccmcore.dll; Overwrite; Won't patch; Existing file is a lower version PROPERTY CHANGE: Adding CcmDetectFilesInUse property. Its value is 'D:\Windows\system32\ccmcore.dll WARNING: d:\windows\system32\ccmcore.dll is in use by process d:\windows\system32\wbem\wmiprvse.exe WARNING: d:\windows\system32\ccmcore.dll is in use by process d:\windows\system32\msiexec.exe Successfully moved file d:\windows\system32\ccmcore.dll to d:\windows\temp\CCM2646.tmp and marked for deletion on reboot. Then a few minutes later, the ccmsetup.log and client.msi.log report exit code 0 and the task sequence reboots the system to re-(initialize? provision? never was sure what exactly happens here if a CM client is already installed) and the ccmcore.dll error is displayed. It seems that once the image is applied and the task sequence reboots into windows, the installer sees the RTM version of the client and tries to upgrade the bits to R2. Because the msiexec and wmiprvse processes have the ccmcore.dll file locked, it flags it as "in use" and marks the old one for deletion at reboot before terminating the installer. Unfortunately on reboot, the task sequence resumes *AFTER* the dll is deleted, the task sequence tries to load the dll as the msgina to continue the sequence, and dies due to it not being there. Is this a common occurrence? Is the lack of info I can find on this a result of most of the community building the reference with MDT vs CM (show of hands?) and I'm an "edge case"? Could it be that the installer was not built with logic that the task sequence would ever run the "Setup Windows and Configuration Manager" step after applying an RTM reference image in an R2 environment? Anyone see their task sequences break similarly in SP1 / has anyone observed anything similar ever? Really hoping that the workaround isn't breaking OSD for a day or two in order to generate new reference images with the R2 client, so any input is appreciated. Thanks in advance, Andrew On Wed, Apr 23, 2014 at 2:39 PM, Jason Sandys <[email protected]<mailto:[email protected]>> wrote: Yes, I certainly wouldn’t rule it out. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Andrew Berges Sent: Wednesday, April 23, 2014 1:35 PM To: SMS Mailing List Subject: Re: [mssms] Upgraded from 2012 RTM to 2012 R2, OSD broke - ccmcore.dll is missing Thanks for the reply Jason. The sole DP shows as successfully distributed. Client.msi etc shows a date stamp of 9/11/2013 and the client bits on the system indicate a version number of 5.00.7958.1000, so it appears it is installing the R2 agent (although not the CU1, but that's a separate matter to address). Ccmsetup.log and client.msi.log show the installation as completing successfully as well. The image I am trying to deploy contains an RTM version of the Configuration Manager client rather than the SP1 client or R2 client. Could this in any way be responsible for the error? Regards, Andrew On Wed, Apr 23, 2014 at 1:07 PM, Jason Sandys <[email protected]<mailto:[email protected]>> wrote: Make sure the client agent package you are using contains the R2 client agent and is successfully distributed to the DPs. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Andrew Berges Sent: Wednesday, April 23, 2014 11:02 AM To: SMS Mailing List Subject: [mssms] Upgraded from 2012 RTM to 2012 R2, OSD broke - ccmcore.dll is missing I recently upgraded my lab from 2012 RTM to SP1 and then to R2 (including the Cumulative Update 1 for R2), also installing MDT 2013, upgrading the Distribution Share, re-integrated with Configuration Manager, and generated new boot images. I attached the new boot images to my existing deployment task sequence and OSD seemed to be working until I reached the Setup Windows and Configuration Manager step and it rebooted. When the reboot completed into the Windows OS to continue the task sequence, the relevant driver package installed and the Configuration Manager client was downloaded and presumably successfully installed. That's when the Task Sequence progress bar disappears, and I'm left with a dialog window titled TSMBootstrap.exe which states: "The program can't start because ccmcore.dll is missing from your computer. Try reinstalling the program to fix this problem." I saw this post here (http://www.windows-noob.com/forums/index.php?/topic/7418-sccm-2012-sp1-ccmcoredll-missing/), but I've already added the Network Access Account and SCCMSERVER$ to SMS_<site_code> with NTFS Read and Execute permissions as well as Read permissions on the share itself. Anyone seen this before? Am I going about this all wrong? Thanks in Advance, Andrew
