#systemcenterconfigurationmanager

Microsoft Endpoint Configuration Manager version 2006 KB4575786. After installing the following update rollup, the Configuration Manager console terminates unexpectedly.KB 4578605 Update Rollup for Microsoft Endpoint Configuration Manager version 2006 This occurs if the user is not a member of the Full Administrator security role and switches between different nodes of the console. For example, a user that is a member of the Remote Tools Operator security role, and selects the Devices node in the console will encounter this issue.Event ID 1026 is recorded in the Application Event log with details resembling the following. Application: Microsoft.ConfigurationManagement.exeFramework Version: v4.0.30319Description: The process was terminated due to an unhandled exception.Exception Info: System.Collections.Generic.KeyNotFoundException   at System.Collections.Generic.Dictionary`2,].get_Item(System.__Canon)... Read the full article

SCCM OSD Error Sending with Winhttp failed 80072f8f. In the smsts.log file using CMTrace you can see next error: Sending with winhttp failed; 80072f8f. retrying Retrying and Ignoring date security failures. AsyncCallback() WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered dwstatusinformationlength is 4 WINHTTP_CALLBACK_STATUS_FLAG_INVALID_CA is set sending with winhttp failed; 80072f8f If your SMSTS.log file contains: WINHTTP_CALLBACK_STATUS_FLAG_INVALID_CA This means problems with SCCM certificate. Without a certificate, the PXE and media boot clients won’t trust the CA that issued the certs which is your issue. Under the Site Properties (SCCM ConsoleAdministrationSite ConfigurationSites) open Properties of the site.Navigate to the Communication Security tab, select the Root CA and restart the WDS service. Read the full article

ConfigMgr Content Transfer Error 0x80070003. You can see next error in distmgr.log file: Package Transfer Manager failed to update the package " ", Version 2 on distribution point MP server. Review PkgXferMgr.log for more information about this failure. In addition to the previous error, in the Monitoring/Overview/System Status/Component Status SMS_DISTRIBUTION_MANAGER and SMS_PACKAGE_TRANSFER_MANAGER weren’t healthy. Distribution Manager failed to process package "Configuration Manager Client Package" (package ID = ).Possible cause: Distribution Manager does not have access to either the package source directory or the distribution point.Solution: Verify that distribution manager can access the package source directory/distribution point. Things to try to remove this error: Remove the distributed content from the distribution point and re-distribute it.Check if there are any WAN or network problems. Usually, these interfere with network traffic and cause issues while distributing content.In most cases, antivirus software is the main cause for content distribution failures. If you use AV on the SCCM server, don't forget to add to exclusions ConfigMgr folders. Read the full article

SCCM client failed with error code 0x80080005. Ccmsetup error code 0x80080005 occurs because Microsoft Background Intelligent Transfer Service (BITS) version 2.5 or a later version must be installed before you can install the SCCM client. As per Microsoft, BITS version 2.5 is required to enable throttled data transfers between the client computer and Configuration Manager site systems. During client installation, BITS isn’t downloaded automatically (because Microsoft operating systems include BITS). However, if your operating system does not include BITS (maybe you remove it or disable), you must install BITS before you install the SCCM client agent. If BITS is installed - check BITS Windows services, it may be stopped. Start BITS service, the SCCM client installation must worked fine now. Read the full article

SCCM Update Stuck in Downloading State. When upgrading Configuration Manager to the next build for a long time you may see that the status show as downloading but the update was never downloaded. In the SCCM console, find and remember (notate) Package GUID of the update. 2. If you go to the EasySetupPayload folder, you will find a folder with a name that matches the Package GUID from previous step. If you check the folder properties it must show 0 bytes. 3. With SCCM update reset tool you can either reset an update or force delete. Run the command prompt as administrator (you can use windows search to achieve this). 4. Change the path to CMUpdateReset folder (C:Program FilesMicrosoft Configuration Managercd.latestSMSSETUPTOOLSCMUpdateReset). NOTE: Path for CMUpdateReset folder is valid only for SCCM server. 5. In the command prompt run the CMUpdateReset.exe and that will show you the tool usage options or examples. Out from the above screenshot is listed below. Microsoft (R) Microsoft Endpoint Configuration Manager Update Reset Tool Copyright (C) 2020 Microsoft. All rights reserved. Usage: Run CMUpdateReset.exe on any server. The User that runs the tool must have administrator rights on all site servers and on the service connection point server. Example to run the default CMUpdateReset.exe: CMUpdateReset.exe -S server1.contoso.com -D CM_XYZ -P 61F16B3C-F1F6-4F9F-8647-2A524B0C802C CMUpdateReset.exe -S server1.contoso.com Read the full article

SQL Server Configuration for site upgrade :Checks if the specified SQL Server meets the minimum requirments for site upgrade The log files (CMUpdate.log) say it kicking on with the SQL Service Broker on the Database. Run the following SQL query to check it out: SELECT is_broker_enabled FROM sys.databases WHERE name = ''; Then to enable it, run the following: ALTER DATABASE SET ENABLE_BROKER WITH ROLLBACK IMMEDIATE; Run the first SQL query again to confirm that the SQL Service Broker was enabled: SELECT is_broker_enabled FROM sys.databases WHERE name = ''; After that KB installation prerequisite checks completed successfully. Read the full article

3. After removing TCP Dynamic Ports restart SQL Server Instance Service. 4. Try the installation again. Read the full article

Configuration Manager Task Sequence failed with the error code (0x800705AA). At deployment process you can encounter next error: Task Sequence: Deploy Windows 10 has failed with the error code (0x800705AA) This error may occur when the minimum requirements do not match the current system specs. In most cases it's about HyperV Virtual Machine configured with: Startup memory: 512 MB Minimum memory: 512 MB Maximum memory: 4096MB Configuration Manager Task Sequence requires more memory to install the WIM-file to the drive. To solve this issue you must increase Minimum and Startup memory to 2048 MB or use fixed memory size, also 2048. After increasing Virtual Machine memory the Task Sequence will run successfully. Read the full article