Summary
Release version 1902 of Microsoft System Center Configuration Manager current branch contains fixes and feature improvements.
The "Issues that are fixed" list is not inclusive of all changes. Instead, it highlights the changes that the product development team believes are the most relevant to the broad customer base for Configuration Manager. Many of these changes were made in response to customer feedback about product issues and product improvement.
Notes
-
Version 1902 is available as an in-console update that can be installed at the top-tier site in a hierarchy.
-
For installation information, see Checklist for installing update 1902 for System Center Configuration Manager.
-
For more information about the changes that are included in version 1902, see What’s new in version 1902 of System Center Configuration Manager.
Issues that are fixed and improvements
Configuration Manager console
-
Multiple areas of the Configuration Manager console are updated to allow the correct sorting of content by different fields. For example, updates are made to the Number in Progress column in the Deployments node and the Expiration Date column in the Certificates node.
-
Administrators may not be able to open the Configuration Manager console after they promote a passive site server to active mode. This occurs if they were not previously a member of the SMS Admins group on the passive site server.
-
Administrators cannot delete a custom third-party software updates catalog if the feature is not enabled.
-
Co-management workload transition reports that have a count of zero are not displayed as expected in the co-management dashboard.
-
The Approve button in the Devices node of the Configuration Manager console is incorrectly enabled for clients that are installed through Azure Active Directory.
Software Updates Management
-
Synchronization of Microsoft Surface driver and firmware updates may fail on a site server that has a remote Software Update Point. Error entries that resemble the following are recorded in the WsyncMgr.log file:
Generic exception : ImportUpdateFromCatalogSite failed. Arg = {guid}. Error =The request failed with HTTP status 401: Unauthorized.
Client
-
Clients try to download content from a cloud distribution point by using a cloudapp.net DNS suffix when a custom domain name is provided. Error entries that resemble the following are recorded in the DataTransferService.log file:
Target URL scheme is HTTPS: https://ServerName.cloudapp.net:443/downloadrestservice.svc/getcontentxmlsecure....
AsyncCallback(): WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered WINHTTP_CALLBACK_STATUS_FLAG_CERT_CN_INVALID is set-
Software Center may display a failure and an “Error 0x0(0)” entry message after Windows Feature updates are successfully installed. Subsequent software update scans will return the correct successful installation status.
-
Client computers may still receive a pre-production (pilot) version of the client software even after they are removed from the pre-production collection.
-
An internet-only client that is collocated with an HTTPS distribution point cannot download content. An error entry that resembles the following is recorded in the ContentTransferManager.log file:
CCTMJob::UpdateLocations - locality does not match for CTM Job {job_id}, suspending download
-
The client cache size is incorrectly limited to 99,999 MB if the maximum cache size client setting is defined as having a larger value.
Inventory
-
The IsVirtualMachine property of the CCM_VirtualMachineInfo hardware inventory class returns a value of FALSE for some VMware virtual machines.
-
The IsHyperthreadEnabled hardware inventory property is still set to True even if HyperThreading is disabled in the BIOS of a client computer.
Site Systems
-
An administrator-defined Trusted Root Certification Authority certificate may be overwritten when updating certificates on the Client Computer Communication tab of Site Properties.
-
The Azure Active Directory (AAD) discovery process incorrectly creates a data record for users that are blocked in AAD.
-
KB 4498264: Duplicate rows in DistributionContentVersion table after you reassign a DP in Configuration Manager
-
The database replication link between a Central Administration Site and a primary site may show degraded status. This can occur if state messages are present from a client that has migrated from one site to another. Error entries that resemble the following are recorded in the RCMCtrl.log file:
CSqlBCP::BCPIN: bcp_exec failed.
*** DRS_Init_BCPIN() failed *** BCP fails due to internal sql error. Check if this table has a trigger failed to execute. BulkInsert::DRS_Init_BCPIN : Failed to BCP in BCP in result is 2147500037. ERROR: Failed to BCP in for table CI_CurrentComplianceStatus with error code 2147500037. ERROR: Failed to apply BCP for all articles in publication General_Site_Data.Software Distribution and Content Management
-
Applications may fail to install through a task sequence if the “Allow clients to use distribution points from the default site boundary group" option is enabled, and the relevant distribution points have no other boundary groups defined.
Operating System Deployment
-
Retry download attempts for the PXE variable file (variables.dat) are increased to six retries that are delayed 15 seconds apart.
-
The Create Task Sequence Media wizard now allows the specification of a temporary media folder.
-
The Import New Driver Wizard may fail when it imports more than 100 drivers if the “Import the driver and append a new category to the existing categories” duplicate driver option is selected.
PowerShell
-
The Add-CMDeviceCollectionDirectMembershipRule cmdlet does not correctly display a warning when you add a duplicate device to an existing collection.
Hotfixes that are included in this update
-
KB 4488598: Update Rollup 2 for System Center Configuration Manager current branch, version 1810
Dependency changes
The following dependent components that are included with Configuration Manager version 1902 are updated to the specified versions:
-
Microsoft.Graph.dll to version 1.12.0
-
Microsoft.Graph.Core.dll to version 1.12.0
-
Microsoft.identity.client.dll to version 1.1.4.2
References
Learn about the terminology Microsoft uses to describe software updates.