SCCM (Anglais)

How to upgrade ConfigMgr to the latest version along with upgrading OS and SQL

The Official Configuration Manager Support Team Blog -

Here is a step by step upgrade path from System Center Configuration Manager 2012 SP2 hosted on Windows Server 2012 R2 to System Center Configuration Manager 1702 or later hosted on Windows Server 2016.

These steps can be used if you want to upgrade Configuration Manager 2012 R2, R2 SP1 or SP2 version to Configuration Manager 1702, or upgrade your environment to the latest operating system and SQL server.

I strongly recommend you read Upgrade to System Center Configuration Manager before following the upgrade path.

Important points to remember:

  • You can directly upgrade Configuration Manager 2012 R2 ,R2 SP1 or SP2 to 1702, no update installation is required.
  • You will need to run TestDBupgrade before upgrading the Configuration Manager 2012 SP1 environment to Configuration Manager 1702. (If we are using standalone media for 1702)
  • You will need to download Configuration Manager 1702 setup files from your volume licensing website. When you have version 1702 baseline media, you can upgrade the following to a fully licensed version of System Center Configuration Manager version 1702:
    • An evaluation install of System Center Configuration Manager version 1702
    • System Center 2012 Configuration Manager with Service Pack 1
    • System Center 2012 Configuration Manager with Service Pack 2
    • System Center 2012 R2 Configuration Manager
    • System Center 2012 R2 Configuration Manager with Service Pack 1

Let get to it!

In this example we are running a Primary site (Configuration Manager 2012 SP2) on a Windows Server 2012 R2 OS with SQL Server 2014 hosting the Configuration Manager database on the same box. In below steps we are

  • Upgrading Base OS windows Server 2012 R2 to Windows Server 2016
  • Upgrading SQL Server 2014 R2 to SQL server 2016
  • Upgrading Configuration Manager 2012 SP2 to Configuration Manager 1702
Base OS Upgrade

If you plan to upgrade the base OS of the Configuration Manager primary site server, and upgrade SQL then follow these steps:

Take a backup of your existing primary site database, SMS backup, Source directory, SCCMContentLib (All the folders for SCCMContentlib). See  https://technet.microsoft.com/en-in/library/gg712697.aspx#BKMK_SupplementalBackup

  1. Rename your current Configuration Manager primary site server and create a new machine with Windows server 2016 installed.
  2. It should have same name, drive letters and drive structure as your earlier site server.
  3. Install all the pre-requisites for Configuration Manager. See Site and site system prerequisites for System Center Configuration Manager.

 

SQL upgrade

Please refer to this article for SQL upgrade:

https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/support-for-sql-server-versions#upgrade-options-for-sql-server

As we are running SQL on primary site server locally, we need to install the upgraded version of SQL on this newly created server.

  1. In our previous server we were running SQL server 2014 (Microsoft SQL server 2014 (SP2-CU2)- 12.0.5522.0 (X64))

  1. On new Primary site server, we installed Microsoft SQL server 2016 Ent version (Microsoft SQL Server 2016 SP1 -13.0.4001.0 (X64))

3. Copied the smsbackup locally on the new server.

4. Copy CM_<Sitecode>.mdf and CM_<SiteCode>_log.ldf files from smsbackup location to the location on the new server exactly where it was stored in your old Primary (SQL) server. For example, if .mdf and .ldf files on your old server are stored in <G:\MSSQL\11\Data> then it has to be stored in the same location on the new server.

SMSBackup Location:

Copy to below location (As per the previous server database files location):

  1. Now attach the database on the New server (SQL) and then run site recovery.

Click on Add and provide the location for .mdf and .ldf files copied from the backup and click ok.

With this we should see the Primary Site Database visible under Databases in SQL Server Management Studio.

Now we can start the site recovery Process

Primary Site Recovery

6. Run the Configuration Manager setup and recover the site using “Manually recovered DB option”.

https://technet.microsoft.com/en-us/library/gg712697.aspx#Recover

-Please follow below link for the Recovery process.

-General:   System Center 2012 Configuration Manager R2 – Disaster Recovery for Entire Hierarchy and Standalone Primary Site recovery scenarios     http://www.microsoft.com/en-us/download/details.aspx?id=44295

-After waiting for couple of hours, we can start the Upgrade process for Configuration Manager 1702.

-Copy the Configuration Manager 1702 Media locally on the Primary site server.

-Also take the current SMSbackup for the primary site.

-The following is a checklist of required and recommended actions to perform prior to upgrading to System Center Configuration Manager:

https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/upgrade-to-configuration-manager#bkmk_checklist

-Make sure that all the Tasks are verified before we go for the Upgrade.

-Also make sure that TestDbUpgrade is successful before we go for the upgrade.

Note: We need to take the backup of current Database and restore to a separate SQL server (Non- production SQL) and run TestDbUpgrade.

Test upgrade should not be run on production database.

-Now we can run the Configuration Manager 1702 media to start the upgrade process.

https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/upgrade-to-configuration-manager#bkmk_upgrade

NOTE– We can implement all the above steps in case we have multiple sites, to upgrade multiple sites, we need to perform the above steps from Top to bottom (First we need to Upgrade CAS then Primary sites)

–Rajat Choubey

Support Engineer, Microsoft

Update 1710 for Configuration Manger Technical Preview released

The Official Configuration Manager Support Team Blog -

We are happy to let you know that update 1710 for the Technical Preview Branch of 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 about this month’s new preview features, please see the following two posts.

Using ConfigMgr With Windows 10 WUfB Deferral Policies

The Official Configuration Manager Support Team Blog -

Important: Configuration Manager current branch version 1706 is needed for any ConfigMgr environment using WUfB deferral policies. ConfigMgr client version 1702 will periodically delete all WUfB deferral policies, if configured. This could lead to unintended results. 

As you are probably aware, Windows 10 version 1607 introduced new Dual Scan behavior for enterprises that wanted Windows Update (WU) to be their primary update source while Windows Server Update Services (WSUS) provided all other content.  In this scenario, the WU client automatically scans against both WSUS and WU, but it only accepts scan results for Windows content from WU. Stated another way, the Dual Scan enabled client ignores anything on WSUS from the “Windows” product family. If you configure a combination of Windows Update group policies (or their MDM equivalents, or the underlying registry keys corresponding to either set of policies), then Dual Scan will be automatically enabled. These policies are:

  • Specify intranet Microsoft update service location (i.e. WSUS)

and

  • Either of the “deferral” policies belonging to Windows Update for Business
    • Select when Feature Updates are received
    • Select when Quality Updates are received

To defer updates, many enterprise customers used the configuration above prior to 1607. For them, the new Dual Scan behavior was an unwelcomed change as it broke ConfigMgr software update deployments for any updates within the “Windows” product family. Demystifying “Dual Scan” provides details about Dual Scan as well as settings that enterprises can use to work around the new behavior.

The October cumulative update for 1703 includes new functionality and a new policy that allows Dual Scan to be disabled. The new policy, “Do not allow update deferral policies to cause scans against Windows Update”, when enabled, will disable Dual Scan. This allows enterprises that wish to configure deferral policies, the ability to do so without being concerned that Dual Scan will override administrator intent.

NOTE: You can only configure the new policy, “Do not allow update deferral policies to cause scans against Windows Update”, via local group policy for now. Updated administrator template files will be available later this fall that will allow you to configure this policy at a domain level.

It is important to understand the expected behavior as it relates to ConfigMgr.

  • Windows Update for Business deferral policy configured and deployed via ConfigMgr (Windows 10 version 1703 and higher) – If you configure and deploy WUfB deferral policy via ConfigMgr, Dual Scan will be automatically enabled*. That is, “Do not allow update deferral policies to cause scans against Windows Update” will be set to disabled on any ConfigMgr client where the WUfB deferral policy is deployed. Even if you enable “Do not allow update deferral policies to cause scans against Windows Update” at the domain level, that setting will be periodically overwritten by the ConfigMgr client. *Assumes that the “Specify intranet Microsoft update service location” policy is set to Enabled.
  • Windows Update for Business deferral policy and Dual Scan disable policy configured and deployed via GPO – If you configure WUfB deferral policy as well as disable Dual Scan (e.g. enable the new policy) via GPO, those settings will be preserved by the ConfigMgr client.

To summarize:

  1. To use WUfB deferral policies while disabling Dual Scan, use GPO to configure all required settings.
  2. To use Dual Scan with WUfB deferral policies, configure and deploy WUfB policy via ConfigMgr.
  3. And if you’re still managing some Windows 10 version 1607 clients, the August cumulative update for 1607 also includes the new Dual Scan policy. You can use GPO to set deferral polices and disable Dual Scan when running ConfigMgr version 1706.

 

Recently Published KB articles and Support Content 9-15-2017

The Official Configuration Manager Support Team Blog -

We have recently published or updated the following support content for Configuration Manager.

How-To or Troubleshooting

10082 Troubleshooting PXE boot issues in Configuration Manager

  • Online Troubleshooting Guide that helps administrators diagnose and resolve PXE boot failures in System Center 2012 Configuration Manager (ConfigMgr 2012 or ConfigMgr 2012 R2) and later versions. Read More https://support.microsoft.com/help/10082.

4040243 How to enable TLS 1.2 for Configuration Manager

  • This article describes how to enable TLS 1.2 for Microsoft System Center Configuration Manager. This description includes individual components, update requirements for commonly-used Configuration manager features, and high-level troubleshooting information for common problems.  Read More https://support.microsoft.com/help/4040243/.
Issue Resolution

4037828 Summary of changes in System Center Configuration Manager current branch, version 1706

  • Release version 1706 of System Center Configuration Manager Current Branch contains many changes to help you avoid issues and many 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. Read More https://support.microsoft.com/help/4037828.

4036267 Update 2 for System Center Configuration Manager version 1706, first wave

  • An update is available to administrators who opted in through a PowerShell script to the first wave (early update ring) deployment for System Center Configuration Manager current branch, version 1706. You can access the update in the Updates and Servicing node of the Configuration Manager console. This update addresses important late-breaking issues that were resolved after version 1706 became available globally. Read more https://support.microsoft.com/help/4036267.

4039380 Update for System Center Configuration Manager version 1706, first wave

  • This update address important issues in the first wave (early update ring) deployment for Microsoft System Center Configuration Manager current branch, version 1706.This update is no longer available and has been replaced by update KB 4036267. Read more https://support.microsoft.com/help/4039380.

4041012 1702 clients do not get software updates from Configuration Manager

  • After installing Configuration Manager version 1702, newly installed clients are unable to get updates from the Software Update Point. This can also occur if the Software Update Point is moved to a different server after installation of version 1702.  Read More https://support.microsoft.com/help/4041012.

4019125 FIX: System Center Configuration Manager replication process by using BCP APIs fails when there is a large value in an XML column. Read More https://support.microsoft.com/help/4019125.

4038659 Existing computer records are not updated when new information is imported in System Center Configuration Manager version 1702

  • When new information for an existing computer is imported, either through the Configuration Manager console or the ImportMachineEntry method, a new record is created for that computer. This causes changes to the existing collection membership, discovery properties, and task sequence variables for that computer. Read More https://support.microsoft.com/help/4038659.

HOTFIX: Clients cannot download peer cache content in Configuration Manager version 1706

The Official Configuration Manager Support Team Blog -

After you upgrade to Configuration Manager current branch version 1706, clients may not be able to download content from peer cache sources.  We have released a hotfix that resolves this issue.  This is a targeted hotfix and will be available in the Updates and Servicing node of the Configuration Manager console for sites that need it.

For the latest information about the issue and how to install the hotfix, please see the following:

4042345Clients cannot download peer cache content in Configuration Manager version 1706 (https://support.microsoft.com/help/4042345)

Update 2 for Configuration Manager current branch, version 1706 first wave is now available

The Official Configuration Manager Support Team Blog -

Administrators who opted-in to the first (early) wave deployment for System Center Configuration Manager current branch, version 1706, have an update available in the Updates and Servicing node of the Configuration Manager console. This update, made available on August 31, 2017, addresses important late-breaking issues that were discovered during the final release process for version 1706. 

For more information, including the issues fixed and the applicability of the update, please read:

4036267 : Update 2 for System Center Configuration Manager version 1706, first wave – https://support.microsoft.com/help/4036267

High CPU/High Memory in WSUS following Update Tuesdays

The Official Configuration Manager Support Team Blog -

Recently, we’ve seen an increase in the number of high CPU/High Memory usage problems with WSUS, including WSUS in a System Center Configuration Manager environment – these have mostly corresponded with Update Tuesdays.

Microsoft support has determined that the issue is driven primarily by the Windows 10 1607 updates, for example KB4022723, KB4022715, KB4025339, etc. See here for the list of Windows 10 1607 updates.

Microsoft is also aware of a known issue with KB4034658 that will cause Windows 10 1607 clients to run a full scan after install – Microsoft is investigating and the latest information is available here.

These updates have large metadata payloads for the dependent (child) packages because they roll up a large number of binaries. Windows 10, versions 1507 (Windows 10 RTM) and 1511 updates can also cause this, though to a lesser extent.  Windows 10, version 1703 is still recent enough that the metadata is not that large yet (but will continue to grow).

Symptom

The symptoms include

  • High CPU on your WSUS server – 70-100% CPU in w3wp.exe hosting WsusPool
  • High memory in the w3wp.exe process hosting the WsusPool – customers have reported memory usage approach 24GB
  • Constant recycling of the W3wp.exe hosting the WsusPool (identifiable by the PID changing)
  • Clients failing to scan with 8024401c (timeout) errors in the WindowsUpdate.log
  • Mostly 500 errors for the /ClientWebService/Client.asmx requests in the IIS logs
Cause

Microsoft support has determined that the issue is driven primarily by the Windows 10 1607 updates, for example KB4022723, KB4022715, KB4025339, etc. See here for the list of Windows 10 1607 updates.

These updates have large metadata payloads for the dependent (child) packages because they roll up a large number of binaries. Windows 10, versions 1507 (Windows 10 RTM) and 1511 updates can also cause this, though to a lesser extent. Windows 10, version 1703 is still recent enough that the metadata is not that large yet (but will continue to grow).

How to determine if the 1607 Updates are the cause

To determine if WSUS is affected by this problem, decline the Windows 10 updates (including the latest cumulative update). If CPU and memory quickly drop back to normal, then the issue is likely the result of metadata size from the Windows 10 updates. They can be reapproved after you have determined if the updates are causing this issue, assuming you want to deploy them.

If declining the Windows 10 updates does not help, then the problem may be due to too many superseded updates in the WSUS server. Take the steps outlined in The Complete Guide to Microsoft WSUS and Configuration Manager SUP maintenance to decline the superseded updates. If, after doing this you are still having problems, read on.

This blog post may help alleviate some of these problems, but is not a magic bullet. After these changes are made, you will still see high CPU and memory until the system stabilizes as I explain further down.

WSUS Caching

WSUS has a caching mechanism whereby the first time update metadata is requested by any client WSUS will store it in memory. Further requests for the same update revision will retrieve the update metadata from memory instead of reading it from the database. Some of the metadata in the database is compressed, so not only must it be retrieved, it must be decompressed into memory, which is an expensive operation.

You can monitor the current number of updates stored in the cache via Performance Monitor with the counter WSUS: Client Web Service/Cache size and instance spgetcorexml. Keep in mind that this counter provides the number of cached items, not the amount of memory consumed by cached metadata. w3wp.exe process memory can be used as a proxy for the amount of space consumed by the metadata cache.

The Problem

For large metadata packages and many simultaneous requests, it can take longer than ASP.NET’s default timeout of 110 seconds to retrieve all of the metadata the client needs. When the timeout is hit, ASP.NET disconnects the client and aborts the thread doing the metadata retrieval. If you look at Program Files\Update Services\LogFiles\SoftwareDistribution.log, the abort looks like this:

System.Threading.ThreadAbortException: Thread was being aborted.   at System.Buffer.__Memcpy(Byte* dest, Byte* src, Int32 len)    at System.Buffer._Memcpy(Byte* dest, Byte* src, Int32 len)     at System.Buffer.Memcpy(Byte* dest, Byte* src, Int32 len)   at System.String.CtorCharPtrStartLength(Char* ptr, Int32 startIndex, Int32 length)    at Microsoft.UpdateServices.Internal.CabUtilities.ExpandMemoryCabToString(Byte[] src)    at Microsoft.UpdateServices.Internal.DataAccess.ExecuteSpGetCoreUpdateXml(Int32[] revisionIds)    at Microsoft.UpdateServices.Internal.DataAccessCache.GetCoreUpdateXml(Int32[] revisionIds, DataAccess da, Int64 maxXmlPerRequest)    at Microsoft.UpdateServices.Internal.ClientImplementation.GetSyncInfo(Version clientProtocolVersion, DataAccess dataAccess, Hashtable stateTable, Hashtable deploymentTable, Boolean haveGroupsChanged, Boolean driverSyncNeeded, Boolean doChunking)    at Microsoft.UpdateServices.Internal.ClientImplementation.SoftwareSync(DataAccess dataAccess, UnencryptedCookieData cookieData, Int32[] installedNonLeafUpdateIds, Int32[] leafUpdateIds, Boolean haveGroupsChanged, Boolean expressQuery, Guid[] filterCategoryIds, Boolean needTwoGroupOutOfScopeUpdates)    at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)    at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)

Note: What you are looking for is a ThreadAbortException with ExecuteSpGetCoreUpdateXml on the stack (ThreadAbortExceptions could happen for other reasons as well – we are concerned with this specific scenario).

When the thread abort happens, all of the metadata that has been retrieved to that point is discarded and is not cached. As a result, WSUS enters a continuous cycle where the data isn’t cached, the clients can never complete the scan and continue to rescan.

Another issue that can occur is the WSUS application pool keeps recycling because it exceeds the private memory threshold (which it is very likely to do if the limit is still the default of 1843200). This recycles the app pool, and thus the cached updates, and forces WSUS to go back through retrieving updates from the database and caching them.

Solution

Configure IIS to stop recycling the App Pool

The goal is to stop the app pool recycling since a recycle clears the cache. The defaults in IIS for Private Memory limit of 1843200 will cause the pool to constantly recycle. We want to make sure it doesn’t recycle unless we intentionally restart the app pool.

  • Open IIS Manager for the WSUS server
  • Expand <Server name> and click Application Pools.
  • Find WSUSPool > Right-click > Advanced Settings.
  • Find the setting Private Memory Limit (KB) under Recyling and set it to 0.
    • Check and verify Virtual Memory Limit (KB) is set to 0 .
    • This will prevent IIS from recycling due to a memory limit.
  • Find the setting Regular Time Interval (minutes) below the Private Memory limit and set to 0.
  • Find the Ping Enabled setting and set it to False.
    • This will prevent IIS from recycling the pool if it gets too busy and doesn’t respond to the ping.
  • Click OK.
  • From an elevated command prompt, run IISReset to restart IIS.

Limit the number of inbound connections to WSUS

Reducing the number of allowed connections will cause clients to receive 503 errors (service not available), but they will retry. If the performance counter Web Services | Current Connections for the website on which WSUS is hosted has more than 1000 connections, complete this step:

  • Open IIS Manager for the WSUS server.
  • Expand <Server name> and then Sites.
  • Select the site hosting WSUS.
    • If you aren’t sure, expand each site and look for the ClientWebService directory underneath it – that is the WSUS site the clients use.
  • With the site selected, click the Limits link in the toolbar on the right side.
  • Check the option Limit number of connections and change it to 1000 (or even smaller).
  • Click Ok to save the changes.
  • From an elevated command prompt, run IISReset to restart IIS.

Increase the ASP.NET timeout

  • Make a copy of \Program Files\Update Services\WebServices\ClientWebService\Web.Config.
  • Open \Program Files\Update Services\WebServices\ClientWebService\Web.Config.
  • Find the element “<httpRunTime”. It will look like this (in an unmodified web.config):
<httpRuntime maxRequestLength="4096" />
  • Modify httpRunTime by adding an executionTimeout attribute:
<httpRuntime maxRequestLength="4096" executionTimeout="3600" />
  • Save the web.config to a different location and copy the modified one into the directory.
  • From an elevated command prompt, run IISReset to restart IIS.

Monitor

Open Windows Performance monitor and add the following counters

  • WSUS: Client Web Service | Cache Size counter for spgetcorexml instance.
  • Process | Private Memory counters.
    • If there is more than one w3wp.exe, add them all – the one with the highest memory usage is probably the WSUSPool, but you can also add Process | ID Process to determine which worker process should be monitored.

Monitor the cache size counter – it should increase and eventually reach a peak value that does not change. This indicates all metadata that clients need is cached. It can take several hours for this to stabilize, so be patient.

Monitor the IIS logs and filter on ClientWebService/Client.asmx. The majority will be 500s, but as the cache increases, the number of 200s will increase with it. Once the cache is fully built, you should see mostly 200s.

If you see the cache size drop, then one of two things has happened:

  1. The App pool was recycled (or it crashed), or
  2. The cache was purged due to memory pressure

If the app pool process ID didn’t change and you didn’t make any changes to IIS config that would cause the app domain to unload (such as changing IIS connection limit), then you have most likely hit scenario #2. To get around this, you can force the cache to be a certain size before items will be trimmed from it. You can also make this change beforehand if you wish.

  • Make a copy of \Program Files\Update Services\WebServices\ClientWebService\Web.Config.
  • Open \Program Files\Update Services\WebServices\ClientWebService\Web.Config.
  • Find the element <system.web>.
  • Immediately under it add a new element:
<caching> <cache privateBytesLimit = "8000000000"/> </caching>
  • The privateBytesLimit value can be changed to be larger. 8,000,000,000 is usually enough
  • Save the web.config to someplace else, backup the old one, then copy the modified one into the directory.
  • From an elevated command prompt, run IISReset to restart IIS.

Again monitor the cache size – if it continues to bounce around and the PID isn’t changing and memory is high ( > 8GB) then you probably need increase the privateBytesLimit further.

Refresh of Update 1706 for System Center Configuration Manager (Current Branch)

The Official Configuration Manager Support Team Blog -

On July 28th we released version 1706 for the Current Branch of System Center Configuration Manager and made it available for customers to opt-in for early deployments. On August 8th, we updated the 1706 package to address a few issues found during these initial deployments. We quickly noticed that we had a problem with both download and the package. We pulled it and replaced it with a fixed version as fast as we could but a small number of customers still managed to install it during this time window. We have already released a hotfix targeted to those customers to update them to the latest build. This hotfix will be available in the Updates and Servicing node of the Configuration Manager console. For more information, please see:

KB 4039380: Update for System Center Configuration Manager version 1706, first wave

Also, if you have installed the original version of the 1706 update, we will have a hotfix package for you in the coming weeks to bring you up to the latest build.

For assistance with the upgrade process please post your questions in the Site and Client Deployment forum. To provide feedback or report any issues with the functionality included in this release, please use Connect.

Thank you,

The System Center Configuration Manager team

Error: “There are no task sequences available to this computer” during a PXE boot

The Official Configuration Manager Support Team Blog -

Starting with System Center Configuration Manager, version 1702, unknown computers that are started from media or PXE may not find task sequences targeted to them. The SMSTS.log shows:

There are no task sequences available to this computer. Please ensure you have at least one task sequence advertised to this computer" Unspecified error (Error: 80004005; Source: Windows)

This issue may occur if the Previous button on the “Select a task sequence to run” page is selected on the unknown computer.

This is a known issue that is now fixed by applying Update rollup for System Center Configuration Manager current branch, version 1702.

 

 

 

ConfigMgr 1702: Adding a new Secondary Replica to an existing SQL AO AG

The Official Configuration Manager Support Team Blog -

Hello everyone,

Our colleague Umair Kahn has a helpful post on his blog where he and Sean Mahoney walk through adding a new secondary replica node to an existing SQL Server Always On availability group for a primary site server.

This process involves several steps

  • Adding the new server as a secondary replica.
  • Stopping the Configuration Manager site.
  • Backing up and restoring the site database from the primary replica to the new secondary replica.
  • Configuring each secondary replica.

Umair and Sean call out the issues that are specific to primary site servers. You’ll find the complete text for Umair’s post here:

ConfigMgr 1702: Adding a new node (Secondary Replica) to an existing SQL AO AG

Recently Published KB Articles for System Center Configuration Manager

The Official Configuration Manager Support Team Blog -

Hello Everyone, we have recently published the following Knowledge Base (KB) articles.

KB 4034393 Getting network captures from a task sequence in ConfigMgr

This is a how-to article about capturing a network trace in a Windows PE environment. For the step by step see https://support.microsoft.com/en-us/help/4034393.

KB 4035047 Configuration Manager 2007 client operations fail after you install a May 2017 security update for Windows Server 2008 or 2008 R2

This KB article describes client operations failures resulting from problems accessing the ConfigMgr 2007 server locator point after installation of one of the May 2017 security updates for Windows Server 2008 or 2008 R2. For more information and workarounds see http://support.microsoft.com/help/4035047.

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