SCCM (Anglais)

Reminder: Latest Improvements to the Simplified Servicing for Windows 7 and Windows 8.1

The Official Configuration Manager Support Team Blog -

Applies to: System Center Configuration Manager (all supported versions)

As previously announced, the Windows team has made some modifications to the servicing model for Windows 7 SP1, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 to further simplify update deployment. Beginning with March 2017, the Security Only Quality Update will no longer include updates for Internet Explorer. The cumulative Internet Explorer update will again be available as a separate update.

With this separation, the Security Only Quality Update package size will be significantly reduced, but you will need to deploy and install the Cumulative Security Update for Internet Explorer to remain secure for the latest supported version of the browser if you elect not to deploy the Security Monthly Quality Rollup for Windows. The Monthly Rollup will continue to include updates for Internet Explorer, as a single additive update that provides all security and reliability fixes since the beginning of the new servicing model in October 2016.

If you’re currently deploying the Security Only Quality Updates with Configuration Manager, please make the necessary deployment process changes to also deploy the Cumulative Security Update for Internet Explorer to remain secure.

Please see the Reducing the package size of the Security Only update section for full details.

Anti-malware Platform Support

The Official Configuration Manager Support Team Blog -

Applies to: System Center Endpoint Protection (All Versions), Forefront Endpoint Protection 2010

Microsoft plans to release anti-malware platform updates once or twice per year through Microsoft Update (MU) to down-level operating systems (e.g. Windows 8.1 and below) running SCEP or FEP. Customers must stay current with the latest anti-malware platform update to be fully supported. Our support structure is now dynamic, evolving into two phases depending on the availability of the latest platform version.

  • Security and Critical Updates servicing phase – When running the latest anti-malware version, you will be eligible to receive both Security and Critical updates to the anti-malware platform.
  • Technical Support (Only) phase – After a new platform version is released, support for older versions (N-2) will reduce to technical support only. Platform versions older than N-2 will no longer be supported.*

*Technical support will continue to be provided for upgrades from the baseline version to the latest platform version.

NOTE: The platform updates for SCEP and FEP are published as follows: Category: Critical Updates, Product: Forefront Endpoint Protection 2010. Version 4.7 is the current baseline version for SCEP and FEP. Special MU detection logic and applicability rules are used to upgrade the baseline version directly to the latest platform version.

During the technical support (only) phase, commercially reasonable support incidents will be provided through Microsoft Customer Service & Support and Microsoft’s managed support offerings (such as Premier Support). If a support incident requires escalation to development for further guidance, requires a non-security update, or requires a security update, customers will be asked to upgrade to the latest platform version.

The version history table below will be updated as new platform updates are released.

(Platform versions older than N-2 are no longer supported.)

Version Availability Date Support Phase 4.7 (baseline) February, 2015 Technical Support (Only) for upgrades to the latest platform version 4.8 May, 2015 Technical Support (Only) 4.9 April, 2016 Technical Support (Only) 4.10 October, 2016 Security and Critical Updates

Configuration Manager 2007 and Windows Enforcement of SHA1 Certs

The Official Configuration Manager Support Team Blog -

Effective February 14, 2017, Windows no longer trusts certain certificates signed with SHA-1.  System Center Configuration Manager 2007 supports SHA-1 but does not support SHA-2 certificates. If you use SHA-2 certificates with Configuration Manager 2007, Configuration Manager continues to operate as expected using SHA-1 fallback.   

For more information, see Windows Enforcement of SHA1 certificates.

For later versions of Configuration Manager see,

ConfigMgr (current branch): Support Removal Reminder

The Official Configuration Manager Support Team Blog -

Applies to: System Center Configuration Manager (current branch)

We announced back on July 10th, 2015 that support for Windows Server 2008 R2 as a site server or most site system roles as well as SQL Server 2008 R2 for the site server database role would be removed in the first update version for ConfigMgr (current branch) released in 2017. Please see Deprecated operating systems and Deprecated support for SQL Server versions as a site database for more information.

As we approach the release of this update version, we wanted to publish this reminder. Please plan accordingly, as updating to future update versions may be blocked.

Additional Resources:

Device fails to join domain during a ConfigMgr OSD Task Sequence due to DC time synchronization issues

The Official Configuration Manager Support Team Blog -

We have all dealt with mysterious task sequence failures while imaging. Owing to the number and types of issues we run into, I decided to put together a series of posts that discuss the unexpected and undocumented task sequence failures that are triggered by environmental issues and configurations. This is Post 1 of the series, and it concerns an interesting issue I worked recently. This will help in troubleshooting domain join scenarios during operating system deployment.

The core issue is that a task sequence fails to join the machine to the domain during the Windows imaging process via Configuration Manager.

Assessment:

===========

We looked at the task sequence, made sure that the user name and password were typed correctly, and then we looked at the log files:

netsetup.log (c:\windows\debug)

12/20/2016 17:51:07:055 NetpValidateName: name ‘Polyone.com’ is valid for type 3

12/20/2016 17:51:07:086 NetUseAdd to \\machine1.contoso.com\IPC$ returned 2457

12/20/2016 17:51:07:086 NetpJoinDomain: status of connecting to dc ‘\\ DC1.contoso.com: 0x999

12/20/2016 17:51:07:086 NetpJoinDomainOnDs: Function exits with status of: 0x999

 

Seuperr.log

This server’s clock is not synchronized with the primary domain controller’s clock.

Seupact.log

2017-01-06 10:18:51, Error                        [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [2457]

2017-01-06 10:18:51, Error                        [DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x999

 

Error 2457 translated to:-

NERR_TimeDiffAtDC /* This server’s clock is not synchronized with the primary domain controller’s clock. */

Error 0x999 also translated to:-

NERR_TimeDiffAtDC /* This server’s clock is not synchronized with the primary domain controller’s clock. */

We tried a manual domain join with the logged-on user, and it was successfully joined to the domain. That tells us that the issue is specific to the domain join process during OS deployment only.

We checked on the domain controllers and found that the domain time was in sync. For that matter, if we joined the machine using the same service account that was used in the task sequence, we noticed the same error:

We tried another account and it went just as expected, so now it was clear that the issue was with the service account being used in the task sequence. We then took an ldifde dump of working users (successful domain joined accounts) and non-working users (failing accounts):

Non-Working user

ldifde -f test.ldf -d “CN=svc_SCCM,OU=Service,OU=Restricted Accounts,DC=Contoso,DC=com” -p subtree -s “DC1.Contoso.com”

Working user

ldifde -f test2.ldf -d “CN=Admin, ,OU=Users,DC=Contoso,DC=com” -p subtree -s “DC1.Contoso.com”

Upon comparison of these dumps, we determined that the UserAccountControl value for the bad account was 4260352, and for the good account it was set to 66048. We changed the UserAccountControl value of the failing account to 66048 and could now join the machine successfully through the task sequence.

Hope this helps! Do keep working and sharing! More on task sequence failures coming soon!

Anil Sood

Technical Advisor | Microsoft System Center Configuration Manager 

Disclaimer: This posting is provided “AS IS” with no warranties and confers no rights.

 

Update Rollup for System Center Configuration Manager current branch, version 1610, is now available

The Official Configuration Manager Support Team Blog -

An update rollup for System Center Configuration Manager current branch, version 1610, is now available. This update is available for installation in the Updates and Servicing node of the Configuration Manager console. Please note that if the Service Connection Point is in offline mode, you must re-import the update so that it is listed in the Configuration Manager console. Refer to Install Updates for System Center Configuration Manager for details.

For complete details regarding the update rollup for ConfigMgr current branch v1610, including the list of issues that are fixed, please see the following:

4010155Update rollup for System Center Configuration Manager current branch, version 1610 (https://support.microsoft.com/help/4010155)

ConfigMgr 2012 SP1/R2 RTM: Support for Hybrid Mobile Device Management Ending Soon

The Official Configuration Manager Support Team Blog -

Applies to: Microsoft Intune, System Center 2012 Configuration Manager SP1, System Center 2012 R2 Configuration Manager

Support for System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager RTM ended on July 12th, 2016. Subsequently, support for these releases connecting to the Microsoft Intune service via hybrid MDM (e.g. managing mobile devices with Configuration Manager and Microsoft Intune) will end on April 10th, 2017. After this date, hybrid MDM will stop functioning with these releases. Managed devices will essentially become unmanaged as the Intune Connector will no longer connect to the Intune service. No ConfigMgr data (policies, applications, etc.) will flow up to Intune and no managed device data will flow down to ConfigMgr until an upgrade takes place.

To avoid an interruption in service, customers currently using hybrid MDM with ConfigMgr 2012 SP1 or R2 RTM should upgrade to the Current Branch of ConfigMgr (recommended) or the latest supported service pack (R2 SP1 or 2012 SP2) for ConfigMgr 2012 prior to April 10th, 2017.

Additional resources:

ConfigMgr 2012 R2

Microsoft System Center Configuration Manager now supports macOS Sierra (version 10.12)

The Official Configuration Manager Support Team Blog -

We are proud to announce that the current branch of Microsoft System Center Configuration Manager (version 1610) now supports macOS Sierra (version 10.12) with version 5.0.8466.1 or later of the Configuration Manager Mac client. You can download the latest Mac client for Configuration Manager here. For details on how to upgrade the Configuration Manager Mac client, see How to upgrade clients on Mac computers in System Center Configuration Manager. Please be aware that the version of the Mac client displayed in the Mac preference pane might be different than the version collected by hardware inventory and displayed in the Configuration Manager admin console.

In addition to the Mac client update, we have an update to System Center Endpoint Protection (SCEP) for Mac that includes support for macOS Sierra as well. It is available on the Volume Licensing Service Center (VLSC) at https://www.microsoft.com/Licensing/servicecenter.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Support Tip: Running TestDBUpgrade does not complete and logs “Failed to create process of SetupWpf.exe” error

The Official Configuration Manager Support Team Blog -

~ Rafid Ali

Hello Everyone, Rafid Ali here with another Configuration Manager support tip for you. I recently came across a scenario where a TestDbUpgrade was failing due to a custom database table which was created after adding custom hardware inventory classes in Configuration Manager 2012 R2 Service Pack 1. It was failing to execute Upgrade/TestDBupgrade to newer version 1606, and if you happen to run across this problem then hopefully this post will help.

Below are the error messages that were seen in ConfigMgrSetup.log when running the TestDBUpgrade:

12-08-2016 13:57:48.541    Configuration Manager Setup    4308 (0x10d4)    sql object tel_sum_scansourcewufb is not found. It will be created.
ERROR: SQL Server error: [42S22][207][Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘UseWUServer00’. : TEL_SUM_ScanSourceWufB   Configuration Manager Setup
Failed to execute sql command — Name         : TEL_SUM_ScanSourceWufB ~– Version      : 5.0.8412.1313 ~– Definition   : SqlObjs  ~– Scope        : CAS_OR_PRIMARY  ~– Object       : P  ~– Dependencies : <Detect>  ~– Description : SUM telemetry : Information of client Scan sources to know the usage of Windows Update for Business ~ ~ ~CREATE PROCEDURE TEL_SUM_ScanSourceWufB @Input NVARCHAR(MAX) = NULL  ~AS  ~BEGIN  ~ ~SET NOCOUNT ON ~If exists (Select ID from sysobjects where Name=‘WINDOWSUPDATE_DATA’ ) ~SELECT Count(InstanceKey) as MachineCounts ~      ,AUOptions00 ~      ,InstanceKey00 ~      ,NoAutoUpdate00 ~      ,UseWUServer00 ~  FROM WINDOWSUPDATE_DATA with (NOLOCK) ~  GROUP BY UseWUServer00 ,InstanceKey00, AUOptions00, NoAutoUpdate00 ~End             Configuration Manager Setup
ERROR: Failed to execute SQL Server script: Create SQL object tel_sum_scansourcewufb Configuration Manager Setup
Failed to create process of SetupWpf.exe. return value 1                   1/1/1601 12:00:00 AM           1992642571 (0x76C5500B)

There were similar errors for other columns as well for the same table.

Reason for the failure

ConfigMgr 1606 contains the table ‘WindowsUpdate_DATA’ in its database by default, as the Inventory Class ‘Windows Update’ is included as a default inventory class from version 1606 onwards. However, in ConfigMgr 2012 this was not a default inventory class. Because of this, many ConfigMgr 2012 users manually added this class from WMI (Win32Reg_SMSWindowsUpdate or Win32Reg_WindowsUpdate as per the requirement) to get the required data through Hardware Inventory. When this Hardware Inventory Class was added, it created the same table (WindowsUpdate_DATA) with the same columns names, such as ‘AUOptions00’, ‘InstanceKey00’, ‘NoAutoUpdate00’, ‘UseWUServer00’, etc.

Starting with version 1606, Upgrade Task automatically creates all the required objects which are not there by default in the older versions. We can see this by examining the ConfigMgrSetup.log file:

sql object tel_sum_products is not found. It will be created.
Saved hash for SQLText for SQL object tel_sum_products (SHA256:1C87D231C46ECCC0D559F1AA5B83A1A54FA4C445072285D17CBB84B4DA3BCE29)
INFO: SQL Server script: Create object tel_sum_products
sql object tel_sum_scansourcewufb is not found. It will be created.
*** [42S22][207][Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘UseWUServer00‘. : TEL_SUM_ScanSourceWufB
*** [42S22][207][Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘InstanceKey00. : TEL_SUM_ScanSourceWufB
*** [42S22][207][Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘AUOptions00‘. : TEL_SUM_ScanSourceWufB
*** [42S22][207][Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘NoAutoUpdate00‘. : TEL_SUM_ScanSourceWufB
Failed to execute sql command — Name         : TEL_SUM_ScanSourceWufB ~– Version      : 5.0.8412.1313 ~– Definition   : SqlObjs  ~– Scope        : CAS_OR_PRIMARY  ~– Object       : P  ~– Dependencies : <Detect>  ~– Description : SUM telemetry : Information of client Scan sources to know the usage of Windows Update for Business ~ ~ ~CREATE PROCEDURE TEL_SUM_ScanSourceWufB @Input NVARCHAR(MAX) = NULL  ~AS  ~BEGIN  ~ ~SET NOCOUNT ON ~If exists (Select ID from sysobjects where Name=’WINDOWSUPDATE_DATA’ ) ~SELECT Count(InstanceKey) as MachineCounts ~      ,AUOptions00 ~      ,InstanceKey00 ~      ,NoAutoUpdate00 ~      ,UseWUServer00 ~  FROM WINDOWSUPDATE_DATA with (NOLOCK) ~  GROUP BY UseWUServer00 ,InstanceKey00, AUOptions00, NoAutoUpdate00 ~End  ~~

In this case, Upgrade Task was able to create all of the above objects, like Stored Procedures ‘tel_sum_products’ and its corresponding tables and columns, however when it tried to create and execute object ‘tel_sum_scansourcewufb’, it failed because the same column names (‘AUOptions00’, ‘InstanceKey00’, ‘NoAutoUpdate00’, ‘UseWUServer00’, etc) already existed in the same table (WindowsUpdate_DATA).

You can verify this in your ConfigMgr 2012 R2 SP1 database as shown below.

If this table already exists in the ConfigMgr 2012 database, then it’s been created by custom hardware inventory classes as it’s not a part of the default database for ConfigMgr 2012 R2.

Resolution

In the ConfigMgr 2012 R2 SP1 console, go to Administration:

Next, go to Client Settings:

Select the Client Setting that you are using for Hardware Inventory. In my case it was ‘Default Client Settings’:

Click on ‘Set Classes’:

Select the Custom Inventory Class causing issues and delete it, as shown below.

After a short period of time, you will notice that the table corresponding to that class is deleted in the database. Once the table is deleted, make a healthy backup of Configuration Manager and proceed with the TestDBupgrade. At this point it should complete successfully. Once TestDBUpgrade is successful, you can then proceed with Configuration Manager site upgrade.

NOTE This issue is fixed in Configuration Manager version 1610 and up. Any future baseline builds after 1610 will not encounter this problem.

Rafid Ali, Support Engineer
Microsoft Enterprise Cloud Group

Troubleshooting Configuration Manager and WSUS software update synchronization issues

The Official Configuration Manager Support Team Blog -

If you’re having synchronization problems with either WSUS or System Center Configuration Manager, here’s a friendly reminder that we have a great troubleshooter that will walk you through diagnosing and fixing some of the more common issues that may be encountered when sync fails. If you ever have these kinds of issues, there’s a good chance that this guide will show you how to fix them, and even if you don’t find the resolution to you exact problem, it offers some great resources and tips that will help get you pointed in the right direction. You can find this troubleshooter here.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Microsoft ConfigMgr 2012 R2 ConfigMgr current branch Windows Server software update point software update synchronization Microsoft update windows update

Support Tip: The Apply Driver Package task fails when the ADK is upgraded to ADK 10 1607

The Official Configuration Manager Support Team Blog -

You may find that after installing the Microsoft ADK 10 1607 on System Center Configuration Manager Current Branch 1602 (or later), the Apply Driver Package task will start failing when installing one of the drivers in the Driver Package. The failure is random and may not occur on the same driver every time, and occasionally the Apply Driver Package task may succeed.

If you encounter this problem, Microsoft Senior Support Escalation Engineer Frank Rojas has a great article that describes a few of the workarounds available. You can find Frank’s article here.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

ConfigMgr CB ConfigMgr 1602

Now Available: Interoperability update for Microsoft System Center Configuration Manager version 1610

The Official Configuration Manager Support Team Blog -

An update is available to address important upgrade-related issues for System Center Configuration Manager current branch, version 1610. The issues described in the article below apply only to sites that were upgraded to version 1610 before December 20, 2016. The fixes for these issues are incorporated into the builds of version 1610 that are available from December 20, 2016 onward.

3124042Interoperability update for System Center Configuration Manager version 1610 (https://support.microsoft.com/en-us/kb/3124042)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

KB: Software Metering Agent fails with "Software Metering failed to start PrepDriver" in mtrmgr.log

The Official Configuration Manager Support Team Blog -

After you install the Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1 (3125574) and the System Center Configuration Manager client, the Software Metering Agent fails, and the following error message is recorded in the mtrmgr.log file:

Software Metering failed to start PrepDriver

This error can occur if you install rollup 3125574 before you install the System Center Configuration Manager client software. In that scenario, PrepDrv is not installed during the System Center Configuration Manager client setup process.

For a couple options on how to resolve this issue, please see the following:

3213242Software Metering Agent fails with “Software Metering failed to start PrepDriver” in mtrmgr.log (https://support.microsoft.com/en-us/kb/3213242)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Summary of changes in Microsoft System Center Configuration Manager current branch, version 1610

The Official Configuration Manager Support Team Blog -

Version 1610 of System Center Configuration Manager Current Branch (ConfigMgr 1610) contains many changes that are intended to prevent issues and improve features. A list of these changes and fixes is available in the KB article below, Keep in mind that this list is not comprehensive, however it does include the items that the product development team believes are the most relevant to most customers. Many of these changes are in response to customer feedback about product issues and ideas for product improvement. For more information regarding what’s been fixed and/or updated, please see the following:

3213269Summary of changes in System Center Configuration Manager current branch, version 1610 (https://support.microsoft.com/en-us/kb/3213269)

Please note that version 1610 is available as an in-console update to be installed at the top-most site in a hierarchy. For more information on installing the 1610 update, see Checklist for installing update 1610 for System Center Configuration Manager.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Update 1612 for the Tech Preview Branch of Microsoft System Center Configuration Manager released

The Official Configuration Manager Support Team Blog -

We are happy to announce that that update 1612 for the Technical Preview Branch of Microsoft System Center Configuration Manager has been released. Technical Preview Branch releases give you an opportunity to try out new Configuration Manager features in a test environment before they are made generally available. For information on this month’s new preview features, please see the following:

Update 1612 for Configuration Manager Technical Preview Branch – Available Now!


J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

KB: Client piloting package fails after site expansion in Configuration Manager

The Official Configuration Manager Support Team Blog -

Consider the following scenario:

  • You’re running Configuration Manager current branch, version 1511 through 1606, or version 1610 LTSB.
  • Your old primary site was being used for client piloting.
  • You perform site expansion.

In this scenario, the Configuration Manager Client Piloting Package fails. When this occurs, you receive a status message stating that Distribution Manager failed to access the source directory for Configuration Manager Client Piloting Package content. Additionally, the Distmgr.log file contains errors indicating that Distribution Manager cannot locate the source for PilotUpgrade and cannot process the snapshot of the package.

We have a new KB article that describes this issue as well as how to work around it. For more information please see the following:

3205797Client piloting package fails after site expansion in Configuration Manager (https://support.microsoft.com/en-us/kb/3205797)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Update 2 for System Center Configuration Manager version 1610, early wave is now available

The Official Configuration Manager Support Team Blog -

Administrators who opted in to the early wave deployment for System Center Configuration Manager current branch, version 1610, have an update available in the Updates and Servicing node of the Configuration Manager console. This update, made available on December 12, 2016, addresses important late-breaking issues that were discovered during the final release process for version 1610. This update does not apply to sites that update or install a copy of version 1610 that was downloaded before December 1, 2016.

For more information, including the issues fixed, please see the following:

3211925Update 2 for System Center Configuration Manager version 1610, early wave (https://support.microsoft.com/en-us/kb/3211925)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

ConfigMgr 1610

Important note on Deploying Down Level Windows Updates with Microsoft Configuration Manager 2007

The Official Configuration Manager Support Team Blog -

As you’re probably already aware, in October we announced a new simplified servicing model, where on the 2ndTuesday of each month you will see a new Security Monthly Quality Rollup as well as a new Security Only Quality Update. Because the Security Monthly Quality Rollup contains the same security fixes as the Security Only Quality Update, as well as all fixes from previous monthly rollups and Security Only Quality Updates, there is a supersedence relationship between these updates, and this relationship was described in this post.

However, please note that for December, the Monthly Rollup will not supersede the Security Only update of the same month, nor will it supersede the Security Only update of previous months. Customers using Configuration Manager 2007 will see both updates available to them for deployment (as seen in October), and can deploy the update of their choice using the Software Update Management functionality. In the absence of supersedence, the December Security Only update has installation applicability logic to not install if the Monthly Rollup is installed. This alleviates the impact Monthly Rollup customers observed in October, when the Security Only update would still be installable and show as missing or required in certain compliance tools. Now, customers of the December Monthly Rollup will not see the December Security Only update as missing or required.

Also, with the release of the December updates on Patch Tuesday (12/13), we also revised the following updates:

  • The November Security Only Quality Update
  • The November Security Monthly Quality Rollup
  • The October Security Only Quality Update.

These updates have been rereleased to leverage the same new logic as in the December updates, without supersedence between the Monthly Rollups and the Security Only updates. With this rerelease, customers who have yet to deploy an earlier Security Only update will gain the benefit of it not being superseded.  Additionally, customers of the Monthly Rollups will continue to benefit from the Security Only updates not being installable or flagged as missing.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Update for authentication certificate in System Center Configuration Manager Asset Intelligence is now available

The Official Configuration Manager Support Team Blog -

A new update is available for the Asset Intelligence (AI) authentication certificate in Microsoft System Center Configuration Manager 2007 Service Pack 2, System Center 2012 Configuration Manager Service Pack 2, System Center 2012 R2 Configuration Manager Service Pack 1, and the current branch of System Center Configuration Manager versions 1606 and earlier. Note that System Center Configuration Manager current branch version 1610 and later versions are pre-provisioned with this version of the Asset Intelligence (AI) authentication certificate so you do not have to apply this update to those versions.

For all the details please see the following:

3207852Update for authentication certificate in System Center Configuration Manager Asset Intelligence is available (https://support.microsoft.com/en-us/kb/3207852)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

ConfigMgr 2007 SP2 ConfigMgr 2012 R2 SP2 ConfigMgr 1511 ConfigMgr 1602 ConfigMgr CB

S'abonner à Philippe BARTH agrégateur - SCCM (Anglais)