#configurationmanager

Configuration Manager Current Branch 2010. In this release we continue to build on the tenant attach and work from anywhere themes from earlier releases, making cloud attach and management from the cloud easier and applicable for all. Cloud attach is using any combination of the “Big 3”: cloud management gateway (CMG), tenant attach and co-management. Administrators now have more control over use of the cloud, enhancements to tenant attach and additional functionality when managing clients over cloud management gateway.  Additionally, we have introduced CMG support for Azure Cloud Solution Provider (CSP) subscriptions. Microsoft Endpoint Manager tenant attach Troubleshooting portal lists a user’s devices based on usage - The troubleshooting portal in Microsoft Endpoint Manager admin center allows you to search for a user and view their associated devices. Starting in this release, tenant attached devices that are assigned user device affinity automatically based on usage will now be returned when searching for a user. Enhancements to applications in Microsoft Endpoint Manager admin center We've made improvements to applications for tenant attached devices. Administrators can now do the following actions for applications in the Microsoft Endpoint Manager admin center: Uninstall an applicationRepair installation of an applicationRe-evaluate the application installation statusReinstall an application has replaced Retry installation Cloud-attached management Cloud manage Read the full article

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

Configuration Manager Technical Preview 2011. Categorize Community hub content Community hub content is grouped into a Microsoft, curated, or unreviewed category to allow admins to choose the types of content their environment displays. Admins can choose from the different categories of content that are provided in the Community hub to match their risk profile and their willingness to share and use content from those outside Microsoft and outside their own company. Community hub content has three categories for content sources: Microsoft curated: Content provided by MicrosoftCommunity curated: Content provided by the community that gets reviewed by MicrosoftCommunity unreviewed: General content from the community that doesn't get reviewed by Microsoft Admins can choose the types of content their environment displays from the following options: Display Microsoft content: Selecting this option means that only content created by Microsoft will be shown in the Community hub. This content has had some basic testing and scanning validation to confirm no malware and inappropriate text.Display Microsoft and curated community content: Show curated content from both Microsoft and community partners with basic level of review. Selecting this option means that only content that has been curated will be shown. The curation process includes basic review to confirm that the content doesn’t have malware and inappropriate text, but hasn’t necessarily been tested. Read the full article

UR for Microsoft Endpoint Configuration Manager version 2006 KB4578605. Issues that are fixed During client policy download, the execmgr.log repeats the following log entry multiple times every minute. Device is not MDM enrolled yet. All workloads are managed by SCCM This results in potentially valuable troubleshooting information being overwritten. Client computers that are performing a PXE boot to install a new operating system are unable to find the boot WIM file. This occurs when the WIM file is stored in a content library split across multiple drives. Errors resembling the following are recorded in the SMSPXE.log file. CContentDefinition::GetFileProperties failed; 0x80070003CContentDefinition::TotalFileSizes failed; 0x80070003   Computers are unexpectedly removed from orchestration groups. This occurs if the site has the option Use this boundary group for site assignment enabled, but the target computers are not in that boundary group. Clients are unable to communicate over a custom port for a management point when other communications changes are made to the site. For example, enabling HTTPS communication for a site causes previously defined custom HTTP ports to stop working. State messages from clients may not be properly recorded if the client computer restarts within 10 seconds of state message generation. This results in inconsistent or unexpected state message values, affecting the accuracy of task sequence and software deployment reporting. Read the full article

Configuration Manager Technical Preview 2010.2. Tenant attach: Troubleshooting portal lists a user’s devices based on usage The troubleshooting portal in Microsoft Endpoint Manager admin center allows you to search for a user and view their associated devices. Starting in this release, tenant attached devices that are assigned user device affinity automatically based on usage will now be returned when searching for a user. Prerequisites An environment that's tenant attached with uploaded devicesInstall the latest version of the Configuration Manager client.Target clients with User and Device Affinity client settings to automatically create the affinities. Tenant attach: Create and deploy firewall policies You can now configure and deploy settings for Windows Defender Firewall with Advanced Security to tenant attached Windows 10 devices. Prerequisites An environment that's tenant attached with uploaded devicesWindows 10 or later clients Enhancements to applications in Microsoft Endpoint Manager admin center We've made improvements to applications for tenant attached devices. 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