Did your SMS_OBJECT_REPLICATION_MANAGER component shows a lot or 6004 MessageIDs with the following description: “Object Replication Manager failed to process Object changes. These changes will be retried on next processing cycle.?


By design, maybe.


Run the following query in SQL Management Studio (Warning! modifying the database directly may not be supported by Microsoft. Do this on your own risk.):

SELECT ca.UniqueID,c.CollectionName
FROM vClientSettingsAssignments as ca LEFT JOIN collections AS c ON ca.CollectionID=c.SiteID
WHERE CollectionName = NULL

This will show collection name/s for all active assignments to collection/s that do not exist anymore.

If you have any, copy the UniqueID and run the following query:

DELETE FROM vClientSettingsAssignments
WHERE UniqueID = ‘{UniqueId here}’

Credit goes to:


You make changes to a package and update your distribution points. Shortly you receive error messages in Component Status for SMS_DESPOOLER component.

Status message details is similar to the following:


The destination drive where site server is uncompressing the package is full.


If you don’t know the drive where the package is uncompressing to, open the despool.log file from the site server system where this error occurs. In the log file look for the following lines:

Received package PackageID version 12. Compressed file –  F:SMSPKGPackageID.DLT.11.12 as F:Program FilesMicrosoft Configuration Managerinboxesdespoolr.boxreceivePKG8l1ab.TRY
Old package storedUNC path is \SiteServerFQDNF$SMSPKGPackageID.PCK.
Use drive F for storing the compressed package.
No branch cache registry entries found.
Uncompressing F:SMSPKGPackageID.PCK to F:SMSPKGPackageID.PCK.temp
WriteFile failed, 0 bytes written
FileWrite failed; 0x80070070
decompression failed for F:SMSPKGPackageID.PCK to F:SMSPKGPackageID.PCK.temp
CContentBundle::ExtractContentBundle failed; 0x80070070
Failed to extract contents to the content library. 0x80070070

So, looks like we have a low disk space problem on disk F:. Clean it up to create more space and monitor Component Status again. Shortly, you should see the following:

Received package PackageID version 12. Compressed file –  F:SMSPKGPackageID.DLT.11.12 as F:Program FilesMicrosoft Configuration Managerinboxesdespoolr.boxreceivePKG0auju.TRY
Waiting for ready instruction file….
Old package storedUNC path is \SiteServerFQDNF$SMSPKGPackageID.PCK.
Use drive F for storing the compressed package.
No branch cache registry entries found.
Uncompressing F:SMSPKGPackageID.PCK to F:SMSPKGPackageID.PCK.temp
Content Library: G:SCCMContentLib
Extracting from F:SMSPKGPackageID.PCK.temp
Extracting package PackageID

Extracting content 1c4c0f71-e7a3-4cda-813f-dc7baff8d6a7
Extracting content 93f2ea53-fbf5-4082-98c3-a2b3887dd658
Extracting content 73a4fc00-02da-4e32-824d-957053338834
Extracting content 79267f60-69a5-465c-8a40-a6a8db8b1416
Extracting content 1181a482-c797-451c-9468-e2bf1bc8d68d
Package PackageID (version 11) exists in the distribution source, save the newer version (version 12).
Stored Package PackageID. Stored Package Version = 12

This time, our package uncompressed fine and it was stored successfully in the content library.

Status message details will now show this message:

IF you during deployment you want to easily uncheck “Install new versions automatically” feature, there is a registry setting you can configure prior to actual IE setup.exe or msi, whatever you use.


Copy the following text to a notepad and save it as a REG file. Then use REG IMPORT “Disable_AutoUpdate.reg” before you deploy your IE and that’s all.

Windows Registry Editor Version 5.00
HKEY_LOCAL_MACHINESOFTWAREMicrosoftInternet ExplorerMain]

For example, here’s our script to deploy IE and disable auto update:

: - - - - - - Uncheck "Install new versions automatically" - - - - - - -
REG IMPORT "Disable_AutoUpdate.reg"
: - - - - - - Install Application - - - - - - -
MSIExec /i "IE10-Setup-Full.msi" /qn /norestart /l*v C:WindowsTempMicrosoft_IE10_x64_ENG_R1_Install.log

  1. Create a CMD file with the following content
    @echo off

    :: - - - - - Check if KB is installed - - - - - - - -

    systeminfo | findstr 2823324

    :: - - - - - If not installed (1), exit - - - - - - -

    IF %errorlevel% EQU 1 GOTO NOTFOUND



    Echo %date% - %time% KB 2823324 was not found. Exit. >> C:WindowsTempMicrosoft_Uninstall_Patch_KB2823324.log


    :: - - - - - If installed (0), uninstall - - - - - - -


    Echo %date% - %time% KB 2823324 was found. Attempt uninstall. >> C:WindowsTempMicrosoft_Uninstall_Patch_KB2823324.log

    wusa.exe /uninstall /kb:2823324 /quiet /norestart /log:C:WindowsTempMicrosoft_Uninstall_Patch_KB2823324_WUSA.log

    Echo %date% - %time% KB 2823324 uninstall complete. Restart might be needed for operation to complete successfully. >> C:WindowsTempMicrosoft_Uninstall_Patch_KB2823324.log


  2. Deploy this CMD file by creating a new package and program. Keep in mind that a restart is required to fully uninstall this patch.

Let’s say you know the IP address of a computer but you don’t know the hostname. Seems to be an easy task with ping –a, if you have a working DNS Smile

If not, you can try the following approach:

  1. Create a cmd on client’s computer. Say in \IPC$WindowsTempFindHostname.cmd
  2. Edit FindHostname.cmd. Type in: echo %computername% >> C:WindowsTempHostname.log
  3. Run PSExec: C:PSToolsPsExec.exe \IP C:WindowsTempFindHostname.cmd
  4. Look into \IPC$WindowsTempHostname.log, you will have the computer’s name.

From Run or Command Prompt window: gpedit.msc /gpcomputer: Computername

select SMS_R_SYSTEM.ResourceID, SMS_R_SYSTEM.ResourceType, SMS_R_SYSTEM.Name, SMS_R_SYSTEM.SMSUniqueIdentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup, SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_CH_ClientSummary on SMS_G_System_CH_ClientSummary.ResourceId = SMS_R_System.ResourceId where SMS_R_System.Client = "1" and SMS_R_System.OperatingSystemNameandVersion = "Microsoft Windows NT Workstation 6.1" and SMS_G_System_CH_ClientSummary.ClientActiveStatus = 1 and DATEDIFF(dd,SMS_R_System.CreationDate,getdate()) < 10

Just paste the query in Query Statement window and press OK, do not use Query Design.

Run it with whatever tool you have. I’m using PsExec.

consolesetup.exe /q TargetDir="C:Program FilesConfigMgr" EnableSQM=1 DefaultSiteServerName=SiteServer.Something.Anything

Having an internal app that uses VSFLEX7.OCX file and that works fine on a Windows XP system but not on a Windows 7 one, might require a Win7 hotfix.
To install the file, register it and install the hotfix for Win7 systems, I’ve created a ConfigMgr package that runs the following bat file:

:: – – – – – – – – Copy the source from DP to the local drive – – – – – – – –

XCopy "%~dp0*.*" "C:WindowsPackages%~n0" /cherky
Cd /d "C:WindowsPackages%~n0"

:: – – – – – – – – Copy required file to System32 folder – – – – – – – –

XCopy "vsflex7.ocx" "C:WindowsSystem32" /cherky

:: – – – – – – – – Registering OCX file – – – – – – – –

regsvr32 /s"C:WINDOWSsystem32vsflex7.ocx"

:: – – – – – – – – Install Windows 7 hotfix – – – – – – – –

If EXIST "C:Program Files (x86)" goto X64
wusa.exe Windows6.1-KB2734642-v2-x86.msu /quiet /norestart

If NOT EXIST "C:Program Files (x86)" goto END
wusa.exe Windows6.1-KB2734642-v2-x64.msu /quiet /norestart


Looking for a place where you can find links to all Microsoft Office updates? Try this website and read it’s RSS feed to be aware of new additions

This is a good place to start if you want to make your Office packages updated right after installation, avoiding being not healthy until all the updates will be installed.