CCM LAB

During the SCCM Management Point installation, you may encounter the error that the SMS Notification Server is not installed. In this scenario, client's status will appear with a question mark. You may also try adding below lines to regsvcs.exe and InstallUtil.exe with their .config files by adding the following: <runtime>     <loadFromRemoteSources enabled="true"/> </runtime> However, this did not resolve the issue.  In the Component Status within the SCCM console, the SMS Notification Server status will appear as Critical and display a message similar to the one below. In the BgbSetup.log, you will see entries similar to the following.  Fatal MSI Error - bgbisapi.msi could not be installed In the BgbisapiMSI.log, you can see the following details. Product: BGB http proxy -- Installation operation failed  Windows Installer installed the product. Product Name: BGB http proxy. Product Version: 5.00.9128.1000. Product Language: 1033. Manufacturer...

When attempting to install Windows 11 feature upgrade via SCCM, you might notice that the update fails quickly, and under the “More Information” section, it shows the error code 0xC1900200 (-1047526912) . Additionally, you may observe that the update content is not downloading properly, and within a few minutes, the installation fails. I encountered this issue on several HP laptops and was able to identify the root cause and solution. The first step in troubleshooting should be reviewing the Panther logs , which can help pinpoint the exact blocker. You can find the Panther logs at the following location: C:\$WINDOWS.~BT\Sources\Panther Next, you need to check the XML files located in the Panther folder, as shown in the screenshot above. Look for the most recently created CompatData.xml file. This file corresponds to the latest SCCM feature update attempt that failed. Open this file using CMTrace , which makes it easier to read and highlight error codes or issues in a structured form...

  Deleting Registry.pol and Forcing Group Policy Update Using a Batch File - Software update cycle scan failures  In some troubleshooting scenarios ( specially software update cycle scanning errors)  , it is necessary to remove the Registry.pol file to reset Group Policy settings and force an immediate update. This guide outlines how to accomplish this using a batch script and deploy it via SCCM.  Step 1: Create a Batch File Script to Delete Registry.pol and Update Group Policy @echo off setlocal :: Define paths set "RegPolPath=C:\Windows\System32\GroupPolicy\Machine\Registry.pol" :: Check if the file exists and delete it if exist "%RegPolPath%" del /f /q "%RegPolPath%" :: Force Group Policy update gpupdate /force :: Notify user echo Group Policy has been updated successfully. pause Open Notepad. Copy and paste the script above. Save the file with a .bat extension (e.g., ResetGPO.bat ). Step 2: Deploy the Batch Script Using SCCM 1. Create an SCCM Packag...

Deploying Software Update Scan Cycle via SCCM using a Batch File If you need to trigger a Software Update Scan Cycle through a batch file in SCCM, follow these steps. Step 1: Create a Batch File Create a new .bat file and add the following lines: @echo off echo Initiating Software Update Scan Cycle... wmic /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000113}" echo Software Update Scan Cycle initiated. timeout /t 10 > nul Save this file with a .bat extension. Copy the batch file to a shared network location that SCCM clients can access. Now we'll create the pacakge SCCM console > Software library > Pacakages > Create Package     Choose a name   Select a souce path Select standard program Browse the command line and select the bat file   Choose other options Hidden or visible to users User login or no   Now distribute the content   After it...