Back to ConfigMgr main menu
This was tricky to solve. Everything looked correct. ConfigMgr 2007 and 1E Branch Nomad clients had been installed on several computers. The ConfigMgr clients were upgraded to 2012. Boundaries and boundary groups were correct. Yet, in Software Center, all content was stuck on Downloading (0% complete) (updates, packages etc.)
In normal ConfigMgr 2012 operation, content is downloaded directly to the cache (C:\Windows\ccmcache) and executed from there. In testing, I uninstalled the Nomad Branch client and the process worked perfectly. However, when the Nomad client was installed again the problem re-occurred.
In a correctly operating "ConfigMgr + Nomad Branch" client the content should be downloaded to the ConfigMgr cache and transferred immediately to the Nomad Cache (ProgramData\1E\NomadBranch). At this point execution takes place. Strangely enough, the content was being transferred to the Nomad cache but never installed. Also, ConfigMgr did not know that the content had been downloaded and the Software Center did not report correctly.
Nomad uses CcmCTMNotification.dll to provide status updates to the ConfigMgr client. A review of the Nomad log files revealed that version 4.0.xx of this file was reporting on the effected clients. This is a 2007 file. The 2012 version should read 5.0.x.x. It seems that the file was locked by Nomad during the ConfigMgr client upgrade process and could not be deleted.
The issue was resolved by deleting the C:\Windows\System32\CCM folder and rebooting the computer (note that this is the 2007 location, the 2012 client uses C:\Windows\CCM). All content could then be downloaded and installed.
Note that this issue only occurred on 60 of 1000 computers.