ConfigMgr 2007 PXE Password ist not geting set

So you have ConfigMgr 2007 and some remote PXE. You want to set  PXE password and for some reason on some reason on one particular PXE it does not stick.

The first thing to check is that for this site de Serial number in the database  is the same with the one in the site control file.

You can run this query in SQL (using the SMS_XYZ database-XYZ is the sitecode e.g. CM7)

select * from SiteControl

and then check in the sitectrl.ct0 file (more info about site control file here). You can also dump the Site Control file from the database and compare it to the sitectrl.ct0 (more info on preinst /dump are found here)

site ctrl number

If numbers match than you can proceed to check if the password is stored in the site control file. Search for PXEPassword and make sure it matches the PXE site system:

Here is a sample where we have a password

pxe in site control file

And here we do not have a password:

no pxe pass

During troubleshooting I found out  is that  the …\Microsoft Configuration Manager\inboxes\\sitectrl.ct0 is either setting or clearing the 2nd instance of:
–  when setting  –  <PXEPassword><{{STRING_OF_HEX_CHARACTERS}}><><0>
–  when clearing  –  <PXEPassword><><><0>

Site Reset did not help.

Verbos logging in for AdminUI.log might show the following:

[3][23/7/2015 11:22:07 PM] :Found Site code ‘KP1’ for RefreshScf
[3][23/7/2015 11:22:07 PM] :Executing static method SMS_SiteControlFile.RefreshScf()
[3][23/7/2015 11:24:07 PM] :Refresh of SCF successful
[3][23/7/2017 11:24:07 PM] :Get()
[3][23/7/2015 11:24:07 PM] :
instance of SMS_SCI_SysResUse

instance of SMS_EmbeddedProperty
PropertyName = “PXEPassword”;
Value = 0;
Value1 = “”;
Value2 = “”;},

So if you see only GET calls but no PUT or SET might be an indication.

We should also check in the WMI :
Wbemtest – Connect to root\sms\site_XYZ

SELECT * FROM SMS_SCI_SysResUse WHERE SiteCode=’XYZ’ AND FileType=2 AND RoleName=’SMS PXE Service Point’

Double click on problematic server
– Double click on Props
– View Embedded
– Find the property with PropertyName = PXEPassword
– Double click on Value1 and Copy Value
– Exit the  problematic server



If the password is not there and Value 1 is empty but you have another PXE that works when setting the password than we can  use this value to configure it dor the bad PXE .

Here are the steps:

Wbemtest – Connect to root\sms\site_y=XYZ


SELECT * FROM SMS_SCI_SysResUse WHERE SiteCode=’XYZ’ AND FileType=2 AND RoleName=’SMS PXE Service Point’


Double click on Good Server

  – Double click on Props

  – View Embedded

  – Find the property with PropertyName = PXEPassword

  – Double click on Value1 and Copy Value

  – Exit the Good Server


Double click on Bad Server

  – Double click on Props

  – View Embedded

  – Find the property with PropertyName = PXEPassword

  – Double click on Value1 and Paste Value copied from the Good Server

  – Save Property and then Save object

  – Close then Save Property & Save Object again.


Click on Execute Method

  – Specify SMS_SiteControlFile under Object Path and click Ok

  – Select CommitSCF Method 

  – Click Edit In Parameters

  – Double click on SiteCode

  – Click on “Not NULL” and specify XYZ as value

  – Save Property & Save Object

  – Execute Method


Look at SMSProv.log for this line to ensure it worked:

CSspSiteControl::CommitSCF – Delta was created


Win 7 32 Bit Clients fails to do a WUA scan with error : WARNING: ISusInternal::GetUpdateMetadata2 failed, hr=8007000E



It seems there have been still issues with out of memory errors with CONFIGMGR initiated scans even after applying KB3050265. The problem seems to be only related to 32-bit SCCM client systems.
Yesterday, Microsoft released a new fix for Windows Update Agent that should address this variation of out of memory errors. Please see for the full information.




Original post:

System Center 2012 R2 Configuration Manager update scan is sometimes  failing with this error hr=8007000E  . Typically the scenario is that a ConfigMgr 2012 R2 client is requesting an update scan but the Windows Update Agent on 32-bit Windows 7 computers fails to return the scan results to Configuration Manager. This causes the Configuration Manager client to report incorrect compliance status as a result. It is further evident that the updates fail to install on the Windows 7 32-bit clients when ConfigMgr requests the update cycle, however if you use the Windows Update control panel applet the updates will usually install.

You will also notice a message similar to the following in WindowsUpdate.log:WARNING: ISusInternal::GetUpdateMetadata2 failed, hr=8007000E

At its core this is a memory allocation issue, thus 64-bit Windows 7 computers will not see this error because the address space is effectively unlimited. They will, however, exhibit high memory and high CPU usage, possibly affecting performance. Note that x86 clients will also exhibit high memory usage (around 1.2-1.4GB).

Issue is addressed in this BLog

Later Edit

Microsoft released Windows Update Agent fix under the following:
3050265, Windows Update Client for Windows 7: June 2015,


Enable SQL Tracing for ConfigMgr

Allows logging of SQL statements being executed for components interacting with the Site Database
• Set SQLEnabled to 1 to enable SQL Tracing, 0 to disable


You can enable SQL tracing by setting the following value:
On 64-bit systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SMS\Tracing\SQLEnabled = 1
On 32-bit systems: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing\SQLEnabled = 1

From <>

In the logs you will be able to see following type of entires: SQL>>>

sql tracing enabled

Full and Clean reinstall of a ConfigMgr Client + script

Check to see if ccmexec is running in the Task list. If it is, stop it.

Deinstallation of Clients:  Ccmsetup.exe /uninstall

Run CCMSETUP.exe /Uninstall

Via Task Manager wait until CCMsetup is done. Check Task manger and see that the process finishes.

Use WBEMTEST and try to connect to namespace root\ccm. Namespace should be unavailable

  • Check to see if SMSCFG.INI  was deleted.
  •  Check to see if REG Keys were deleted (e.g HKLM\Software\Wow6432Node\Microsoft\SMS, or HKLM\Software\Microsoft\SMS etc.)
  • Check if the folders were deleted(e.g. C:\Windows\SysWOW64\CCM or C:\Windows\System32\CCM or C:\Windows\CCMetc.)
  • Check and confirm that the following registry entries and folder structure does not exist, delete if exists(Not to implement if this is a ConfigMgr Site Server).


               – HKLM\System\CurrentControlSet\Services\clisvcl

               – HKLM\System\CurrentControlSet\Services\ccmexec

               – HKLM\Software\Microsoft\CCM

               – HKLM\Software\Microsoft\NAL

               – HKLM\Software\Microsoft\SMS

               Folder Structure:


              – Windows\ccm

               – Windows\ccmsetup  

              For ConfigMgr 2007:

              – Windows\System32\ccm

               – Windows\System32\ccmsetup  


You can also use CCMClean and CCMDelCert:

Download – CCMClean.exe (Download SMS 2003 toolkit and run it to install all the files – go to the installation directory, it includes CCMClean.exe )

Ccmdelcert.exe wasn’t included in the System Center Configuration Manager 2007 Toolkit, but you can still use the version in the SMS2003 Toolkit 2.

You can download that here:



Here is also a scripted version

net stop ccmexec
net stop ccmsetup
C:\Windows\ccmsetup\ccmsetup.exe /uninstall
timeout /T 180 >nul
rd c:\windows\ccm  /S /Q
rd c:\windows\ccmcache /S /Q
rd c:\windows\ccmsetup  /S /Q
del c:\windows\smscfg.ini
reg delete HKLM\software\Microsoft\ccm  /f
reg delete HKLM\System\CurrentControlSet\Services\clisvcl   /f
reg delete HKLM\System\CurrentControlSet\Services\ccmexec   /f
reg delete HKLM\Software\Microsoft\NAL   /f
reg delete HKLM\software\Microsoft\CCMSETUP /f
reg delete HKLM\software\Microsoft\SMS /f
reg delete HKLM\software\Microsoft\Systemcertificates\SMS\Certificates /f
timeout /T 180 >nul
rd c:\windows\ccm  /S /Q
shutdown /r /t 300

Client Verbose and Debug Logging

Verbose und Debug Logging on clients (MP as well)  :

Enable Debug Logging

 1.      Stop the SMS Agent Host service:

           a.       Click Start, point to Programs, point to Administrative Tools, and then click Services.

           b.      In the Services screen, locate the SMS Agent Host service.

           c.       Right-click the SMS Agent Host serxvice, and then click Stop.

2.      Click Start, click Run, type regedit in the Open box, and then click OK.

3.      In Registry Editor, add the following key:


4.      Add a new value under this key::

                    ·         Value name: Enabled

                    ·         Value: True

                    ·         DataType: REG_SZ

5.      Restart the SMS Agent Host service.


Enable Verbose Logging

For verbose logging change the value of Loglevel to 0 at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\@Global\Loglevel

You need to configure  Permissions with Full Control on this Reg Key.


         Data type: UInt32

The level of detail that the log will capture. Possible values are shown below. The default value is 1.


Verbose logging


Normal logging


No logging

Client side reference registry(For ConfigMgr 2007)

For X86 systems

–          HKLM\Software\Microsoft\CCM\Logging\@GLOBAL

For X64 systems

–          HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\CCM\Logging\@GLOBAL


Configuration Manager 2012 SP2 and R2 SP1 is out

Configuration Manager 2012 SP2 and R2 SP1 is out

Announcing the availability of System Center 2012 R2 Configuration Manager SP1 and System Center 2012 Configuration Manager SP2

System Center 2012 R2 Configuration Manager SP1 and System Center 2012 Configuration Manager SP2 are now generally available and can be downloaded on the Microsoft Evaluation Center. These service packs deliver full compatibility with existing features for Windows 10 deployment, upgrade, and management.

System Center Configuration Manager