MICHAEL,BERTUIT,PASSION,SYSTEM,CENTER,FR,SCCM2016,SCCM2012,SCCM2007,SCCM2012,SCOM,SCSM,SCVMM,SCDPM,ORCHESTRATOR,MICROSOFT,WINDOWS,SERVER,HOW,TO,CAPTURE,DEPLOY,WIM,SERVICE,MANAGER,2008R2,2010,2012,2013,2016,SYSTEM-CENTER.FR,SP1

SCCM 1806 Hotfix available (KB4462978) !

Commentaires fermés octobre 31st, 2018

Hello,

Just a article for you inform that the SCCM 1806 Hotfix KB4462978 is available on your console.

https://support.microsoft.com/en-us/help/4462978/system-center-configuration-manager-version-1806-update-rollup

PXE crash

No comments octobre 4th, 2018

Hello

A troubleshoot post available under.

Configure IP Helper

Configuration Manager PXE boot causes Windows Deployment Services to crash

Applies to: Microsoft System Center Configuration Manager Current branch

Symptoms


You use a System Center Configuration Manager PXE service point (Configuration Manager 2007) or a Pre-Boot Execution Environment (PXE) distribution point (Configuration Manager 2012) to perform PXE boots. In this situation, the operation first appears to work successfully, but then the process stops running. When you examine the server on which the PXE service point and Windows Deployment Services(WDS) are installed, you discover that WDS has crashed.

When you restart WDS on the server, this does not resolve the issue. When you restart both the Windows Management Instrumentation and WDS, or when you restart the server itself, this may temporarily resolve the problem. However, the issue eventually recurs, and WDS crashes again.

If you try to reproduce this issue by continuing to perform PXE boots, you discover that although the issue may occur frequently, it cannot be reproduced on a consistent basis. The crash behavior occurs randomly.

When you use Event Viewer to examine the WDS server on which the Configuration Manager Current branch PXE service point is installed, you find that the following errors are logged.

System log:

Application log:

Windows Deployment Services log:

You may also receive the following error message:

The Windows Deployment Services (WDS) Server service terminated with service-specific error 16389 (0×4005).

Cause


This issue may occur in environments where there are redundant backup routers. If IP Helpers for PXE (DHCP relays) are positioned on both the primary and backup routers, this may cause a situation where two duplicate PXE request packets are sent to WDS: the original PXE request by the primary router and a duplicate PXE request by the backup, redundant router.

If the timing is just right, the duplicate PXE request may overwrite some of the information in WDS from the original PXE request. This causes information in WDS for the PXE request to become corrupted, and then WDS crashes.

Workaround


To work around this issue, use one of the following methods:

  • Disable the PXE IP Helpers in the backup, redundant router so that duplicate PXE requests are not sent. For more information about PXE IP Helpers, see the following TechNet article:
  • Configure the Configuration Manager WDS provider to be single-threaded instead of multithreaded. This will limit WDS processing of PXE requests to one at a time and will prevent the second, duplicate PXE request from conflicting with the original request. To configure the Configuration Manager WDS provider for single-threading, create the NumberOfThreadsregistry key with a DWORD value of 1 in the following location:Configuration Manager 2007 32bit WDS server:HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\PXEConfiguration Manager 2007 64bit WDS server: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\SMS\PXEConfiguration Manager 2012 DP/WDS server:HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\DPDoing this does not typically affect server performance for PXE requests except in environments where a large number of PXE requests are performed on a consistent basis. In these environments, we recommend that you use the first workaround.

SCCM|What’s new in version 1610 of System Center Configuration Manager

Commentaires fermés octobre 3rd, 2018

Hello All,

Good news !

What’s new in version 1610 of System Center Configuration Manager?

Update 1610 for System Center Configuration Manager current branch is available as an in-console update for previously installed sites that run version 1511, 1602, or 1606.

Tip

To install a new site, you must use a baseline version of Configuration Manager.
Learn more about:

The following sections provide details about changes and new capabilities introduced in version 1610 of Configuration Manager.

In-console monitoring of update installation status

Beginning with version 1610, when you install an update pack and monitor the installation in the console, there is a new phase: Post Installation. This phase includes status for tasks like restarting key services, and initialization of replication monitoring. (This phase is not available in the console until after your site updates to version 1610.) For more information about update installation status, see Install in-console updates.

Exclude clients from automatic upgrade

You can exclude Windows clients from getting upgraded with new versions of the client software. To do this, you include the client computers in a collection that is specified to be excluded from upgrade. Clients in the excluded collection ignore requests to update the client software. For more information, see Exclude Windows clients from upgrades.

Improvements for boundary groups

Version 1610 introduces important changes to boundary groups and how they work with distribution points. These changes can simplify the design of your content infrastructure, while giving you more control over how and when clients fallback to search additional distribution points as content source locations. This includes both on-premises and cloud-based distribution points. These improvements replace concepts and behaviors you might be familiar with (like configuring distribution points to be fast or slow). The new model should be easier to set up and maintain. These changes also lay the groundwork for future changes that will improve other site system roles you associate to boundary groups.

When you update to version 1610, the update converts your current boundary group configurations to fit the new model so that these changes do not disturb your existing content distribution configurations.

For more information, see Boundary groups.

Peer Cache for content distribution to clients

Beginning with version 1610, client Peer Cache helps you manage deployment of content to clients in remote locations. Peer Cache is a built-in Configuration Manager solution for clients to share content with other clients, directly from their local cache.

After you deploy client settings that enable Peer Cache to a collection, members of that collection can act as a peer content source for other clients in the same boundary group.

You can also use the new Client Data Sources dashboard to understand the use of Peer Cache content sources in your environment.

Tip

With version 1610, Peer Cache and the Client Data Sources dashboard are pre-release features. To enable them, see Use pre-release features from updates.

For more information, see Peer Cache for Configuration Manager clients, and Client Data Sources dashboard.

Migrate multiple shared distribution points at the same time

You can now use the option to Reassign Distribution Point to have Configuration Manager process in parallel the reassignment of up to 50 shared distribution points at the same time. Prior to this release, reassigned distribution points were processed one at a time. For more information see, Migrate multiple shared distribution points at the same time.

Cloud management gateway for managing Internet-based clients

Cloud management gateway provides a simple way to manage Configuration Manager clients on the Internet. The cloud management gateway service, which is deployed to Microsoft Azure and requires an Azure subscription, connects to your on-premises Configuration Manager infrastructure using a new role called the cloud management gateway connection point. Once it’s completely deployed and configured, clients can communicate with on-premises Configuration Manager site system roles and cloud-based distribution points regardless of whether they’re connected to the internal private network or on the Internet. For more information and to see how cloud management gateway compares with Internet-based client management, see Manage clients on the Internet.

Improvements to the Windows 10 Edition Upgrade Policy

In this release, the following improvements have been made to this policy type:

  • You can now use the edition upgrade policy with Windows 10 PCs that run the Configuration Manager client in addition to Windows 10 PCs that are enrolled with Microsoft Intune.
  • You can upgrade from Windows 10 Professional to any of the platforms in the wizard that are compatible with your hardware.

Manage hardware identifiers

You can now provide a list of hardware IDs that Configuration Manager should ignore for the purpose of PXE boot and client registration. There are two common issues that this helps to address:

  1. Many devices, like the Surface Pro 3, do not include an onboard Ethernet port. A USB-to-Ethernet adapter is generally used to establish a wired connection for the purpose of deploying an operating system. However, due to cost and general usability, these are often shared adapters. Because the MAC address of this adapter is used to identify the device, reusing the adapter becomes problematic without additional administrator actions between each deployment. Now in Configuration Manager version 1610, you can exclude the MAC address of this adapter so that it can easily be reused in this scenario.
  2. The SMBIOS ID is supposed to be a unique hardware identifier, but some specialty hardware devices are built with duplicate IDs. This issue may not be as common as the USB-to-Ethernet adapter scenario just described, but you can address it by using the list of excluded hardware IDs.

For details, see Manage duplicate hardware identifiers.

Enhancements to Windows Store for Business integration with Configuration Manager

Changes in this release:

  • Previously, you could only deploy free apps from the Windows Store for Business. Configuration Manager now additionally supports deploying paid online licensed apps (for Intune enrolled devices only).
  • You can now initiate an immediate synchronization between the Windows Store for Business and Configuration Manager.
  • You can now modify the client secret key that you obtained from Azure Active Directory.
  • You can delete a subscription to the store.

For details, see Manage apps from the Windows Store for Business with System Center Configuration Manager.

Policy sync for Intune-enrolled devices

You can now request a policy sync for an Intune-enrolled device from the Configuration Manager console, instead of needing to request a sync from the Company Portal app on the device itself. Sync request state information is available as a new column in device views, called Remote Sync State. The information is also available in the discovery data section of the Properties dialog for each device. For details, see Remotely synchronize policy on Intune-enrolled devices from the Configuration Manager console.

Use compliance settings to configure Windows Defender settings

You can now configure Windows Defender client settings on Intune-enrolled Windows 10 computers by using configuration items in the Configuration Manager console. For details, see the Windows Defender section in Create configuration items for Windows 8.1 and Windows 10 devices managed without the System Center Configuration Manager client.

General improvements to Software Center

  • Users can now request apps from Software Center, as well as the Application Catalog.
  • Improvements to help users understand what software is new and relevant.

New columns in device collection views

You can now display columns for IMEI and Serial Number (for iOS devices) in device collection views. For more details, see Predeclare devices with IMEI or iOS serial numbers.

Customizable branding for Software Center dialogs

Custom branding for the Software Center was introduced in Configuration Manager version 1602. In version 1610, that branding is now extended to all associated dialog boxes to provide a more consistent experience to Software Center users.

Custom branding for the Software Center is applied according to the following rules:

  • If the Application Catalog website point site server role is not installed, then Software Center displays the organization name specified in the Computer Agent client setting Organization name displayed in Software Center. For instructions, see How to configure client settings.
  • If the Application Catalog website point site server role is installed, then Software Center displays the organization name and color specified in the Application Catalog website point site server role properties. For more information, see Configuration options for Application Catalog website point.
  • If a Microsoft Intune subscription is configured and connected to the Configuration Manager environment, then Software Center displays the organization name, color, and company logo specified in the Intune subscription properties. For more information, see Configuring the Microsoft Intune subscription.

Enforcement grace period for required application and software update deployments

In some cases, you might want to give users more time to install required application deployments or software updates beyond any deadlines you set up. For example, this might be necessary when a computer has been turned off for an extended period of time and it needs to install a large number of application or update deployments. For example, if an end user has just returned from vacation, they might have to wait for a long while as overdue application deployments are installed. To help solve this problem, you can now define an enforcement grace period by deploying Configuration Manager client settings to a collection.

To configure the grace period, take the following actions:

  1. On the Computer Agent page of client settings, configure the new property Grace period for enforcement after deployment deadline (hours) with a value between 1 and 120 hours.
  2. In a new required application deployment, or in the properties of an existing deployment, on the Schedulingpage, select the check box Delay enforcement of this deployment according to user preferences, up to the grace period defined in client settings. All deployments that have this check box selected, and are targeted to devices to which you also deployed the client setting, will use the enforcement grace period.

If you configure an enforcement grace period and select the checkbox, once the application install deadline is reached, it will be installed in the first non-business window that the user configured up to that grace period. However, the user can still open Software Center and install the application at any time they want. Once the grace period expires, enforcement reverts to normal behavior for overdue deployments. Similar options have been added to the software updates deployment wizard, automatic deployment rules wizard, and properties pages.

Improved functionality in dialog boxes about required software

When a user receives required software, from the Snooze and remind me: setting, they can select from the following drop-down list of values:

  • Later. Specifies that notifications are scheduled based on the notification settings configured in Client Agent settings.
  • Fixed time. Specifies that the notification will be scheduled to display again after the selected time (for example, in 30 minutes).

For read the complete article, click HERE