15. September 2015 09:27
Microsoft has just released a number of new KB articles that describes how to maintenance and troubleshoot software updates in Configuration Manager 2012.
How to troubleshoot software update scan failures in System Center 2012 Configuration Manager
How to troubleshoot software update deployments in System Center 2012 Configuration Manager
Using log files to track the software update deployment process in System Center 2012 Configuration Manager
Software update maintenance in System Center 2012 Configuration Manager
Software update troubleshooting and maintenance in System Center 2012 Configuration Manager
11. July 2013 12:43
Today I had a strange problem.
I was testing OS deployment at a customer and had two test PC's that I was testing Windows 7 deployment on.
At first they could PXE boot and start the Windows 7 deployment but then deployment failed with an error.
I corrected the problem in the task Sequence and PXE booted again and this time the Windows 7 deployment was failing with a new error.
I corrected the error but now I could not PXE boot the computers anymore. When they entered the graphical part of WINPE they just rebooted again.
I checked the MSTSC log file that stated that "There is no task sequences available to this computer".
I checked the ConfigMgr console. Both computers (which was failing) was in the correct collection and they had the Deployment for the Windows 7 deployment.
I then google'ed the problem and found this where they have the same problem. More...
4. June 2013 07:26
During a ConfigMgr 2012 SP1 client deployment I had problems with one client on a Windows Server 2003.
It seemed like the client installed correctly but it would not communicate with the management point.
I looked in the log files and found the following:
ClientIDManagerStartup.logRegTask: Failed to get certificate. Error: 0x80004005CertificateMaintenance.log
CryptGenKey failed: 0x80070005
Failed to create certificate 80070005
CCMDOCertificateMaintenance() failed (0x80070005)
I could also notice that there were no SMS certificates in the local computer certificate store.
I asked Google for an answer to the problem and found several posts like this one suggesting to delete all files in the "C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys" folder and then restart the SMS Agent service. This solution had helped several people but in my case it did not work.
Instead the information here guided me to the solution.
When the SMS Agent host service was restarted it recreated a certificate (19c5cf9c7b5dc9de3e548adb70398402_6ee5afbf-3882-4a52-8ad4-1ef3db2563ee) in the above mentioned folder but it turned out that it had the wrong access permissions. I gave "System" full control to the file and restarted the SMS Agent Host service again and now the SMS certificates were created and the ConfigMgr client could communicate with the MP as it should.
7. November 2012 12:11
Today I had a strange problem when I was trying to use DELL Dell Client Integration Pack (DCIP) v3.0 to import DELL driver cab files into ConfigMgr 2012.
No matter which Dell driver CAB i was trying to import as a driver package, they all fail with the message that: 'Failed to create Driver Package in ConfigMgr'. No additional info was shown on the screen.
16. May 2012 22:54
Today I had a strange problem when instaling a Management Point (MP) on a Primary ConfigMgr 2012 site server that is a child of a ConfigMgr 2012 Central Administration Site.
The installation of the MP failed with the well-known 1603 error that is a generic error that can be caused by several things.
A closer look at the mpmsi.log file showed the following cause of the problem:
Action start 11:40:26: CcmMigratePolicySettingsInit.
MSI (s) (80:94) [11:40:26:152]: Note: 1: 2235 2:3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'CcmMigratePolicySettingsInit'
MSI (s) (80:40) [11:40:26:167]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI23B.tmp, Entrypoint: CcmMigratePolicySettingsInit
[11:40:26] Getting settings from WMI and storing in D:\Prog\SMS_CCM\polmig.mof
CustomAction CcmMigratePolicySettingsInit returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 11:40:26: CcmMigratePolicySettingsInit. Return value 3. More...