ConfigMgr 2012 SP1 client will not communicate with MP

by Thomas Forsmark Sørensen 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.log
RegTask: Failed to get certificate. Error: 0x80004005
CertificateMaintenance.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.

Problem solved......

I

SCCM 2007 backup fails with "Error: SMS Writer not found."

by Thomas Forsmark Sørensen 21. December 2012 15:00

Today I had a ConfigMgr 2007 server where the ConfigMgr backup was failing.

When I looked in the smsbkup.log log file I could see that the backup was complaining "Error: SMS Writer  not found"

I checked the registered VSS writers by runining the following command:

VSSAdmin list writers

No "SMS Writer" showed up in the list.

It turned out that the fix to the problem was to add the "sysadmin" rights to the ConfigMgr computer account defined on the SQL server.

After adding this right to the computer account the "SMS Writer" was added to the list of VSS writers and the backup worked as it should.

Thanks, thats all for now.

DELL DCIP v3.0 cannot create ConfigMgr driver package

by Thomas Forsmark Sørensen 7. November 2012 12:11

Hi,

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.

 More...

Windows 8 RTM ready for download

by Thomas Forsmark Sørensen 15. August 2012 21:55

Windows 8 RTM is now ready for download for MSDN subscribers.

I am downloading it while I write this... Looking forward to install it.

More to follow.....

ConfigMgr 2007 MP will not install after a reinstallation of WSUS

by Thomas Forsmark Sørensen 21. June 2012 14:42

After a reinstallation of WSUS on a ConfigMgr 2007 server the MP was not working anymore.

I looked in the mpcontrol.log and should see that the MP was not working. I could see no "Call to HttpSendRequestSync succeeded for port 80 with status code 200, text: OK" lines. Those lines will be there if the MP is working as it should.
I could see in the mpsetup.log that it was trying to install the MP again and again but it kept failing.

In the MPMSI.logfile I found the following line:
“Product: SMS Management Point -- Error 25006. Setup was unable to create the Internet virtual directory CCM_Incoming”

After googling the problem I found the solution here.
The Bits service had to be reinstalled. After doing that the MP installed successfully Laughing

System Center 2012 Service Pack 1 CTP2 has been released

by Thomas Forsmark Sørensen 18. June 2012 15:28

Last friday Microsoft released System Center 2012 Service Pack 1 Community Technology Preview (CTP2).

Included in the CTP2 is CTP2 SP1 for ConfigMgr 2012 that Kent Agerlund described here.

You can download the CTP2 here.

Installing ConfigMgr 2007 Secondary Site keeps having status "Install Pending"

by Thomas Forsmark Sørensen 16. May 2012 23:29

When installing a ConfigMgr 2007 secondary site I have seen several times that it keeps showing "Install Pending" in the ConfigMgr console.

There are several problems that can lead to this. I will try to mention the problems here and how I have solved them.

Problem

Descrption

 Solution

The secondary sit server is not added to the SMS_SiteToSiteConnection_XXX group on the primary ConfigMgr server.

During the installation of the secondary site the installation program should add the secondary site server to the local group SMS_SiteToSiteConnection_XXX (where XXX is the site code of the primary server) on the primary site server.

Add the secondary site server to the group SMS_SiteToSiteConnection_XXX.

More...

ConfigMgr 2007 backup will not connect to SQL cluser registry

by Thomas Forsmark Sørensen 16. May 2012 23:09

I had a ConfigMgr 2007 installation where the DB was placed on a SQL cluster.

 

ConfigMgr was configured to do a backup every night but it failed every time.

A look in the backup log showed the following error:

 

Info: Sending message to start the SQL Backup…
Couldn’t connect to \\SQLcluster registry
STATMSG: ID=5049 SEV=E LEV=M SOURCE=”SMS Server” COMP=”SMS_SITE_BACKUP” SYS=SCCMserver SITE=LHT PID=3400 TID=924 GMTDATE=Wed Jan 23 19:21:16.539 2008 ISTR0=”" ISTR1=”" ISTR2=”" ISTR3=”" ISTR4=”" ISTR5=”" ISTR6=”" ISTR7=”" ISTR8=”" ISTR9=”" NUMATTRS=0
Error: Failed to send start message to the SqlBackup.

More...

ConfigMgr 2012 Management Point will not install

by Thomas Forsmark Sørensen 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 problem:

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...

Windows Server 2012

by Thomas Forsmark Sørensen 17. April 2012 23:46
Today in the key note "Windows Server er 8" was official named "Windows Server 2012". So Brad promised that it will be released later this year.

Powered by BlogEngine.NET 1.6.1.0
Theme by Mads Kristensen | Modified by Mooglegiant

About Me

  

My name is Thomas Forsmark Sørensen.

I live in Odense in Denmark and work for Globeteam in Virum.

I am working as a Microsoft Infrastructure consultant with main focus on application and Operating System Deployment.

I work mostly with Microsoft System Center Configuration Manager 2012 R2 and MDT 2013, but I also work with other of Microsofts products. 

Calendar

<<  March 2017  >>
MoTuWeThFrSaSu
272812345
6789101112
13141516171819
20212223242526
272829303112
3456789

View posts in large calendar

Blogs that I read

Download OPML file OPML