Microsoft Endpoint Manager is an integrated solution for managing all
of your devices. Microsoft brings together Configuration Manager and Intune
with simplified licensing. Continue to make use of your existing Configuration
Manager investments while you take advantage of the power of the Microsoft
cloud at your own pace.
Update 1910 for Configuration Manager current branch is available as an
in-console update. Apply this update on sites that run version 1806 or later.
This article summarizes the changes and new features in Configuration Manager,
version 1910.
In version 1910, aside from the name change, Configuration Manager still
functions the same. Some of the name changes might impact your use of the
following components:
- Configuration Manager console: Find shortcuts to the console and the Remote Control Viewer under the Windows Start menu in the Microsoft Endpoint Manager folder.
- Software Center: Find the Software Center shortcut under the Windows Start menu in the Microsoft Endpoint Manager folder.
Starting in current branch version 1906, you could clear your lock on a
task sequence. Now you can clear your lock on any object in the Configuration
Manager console.
ExtendMigrateToAzure.exe
This new tool helps you to programmatically create Azure virtual machines
(VMs) for Configuration Manager. It can install with default settings site
roles like a passive site server, management points, and distribution points.
After you validate the new roles, use them as additional site systems for high
availability. You can also remove the on-premises site system role and only
keep the Azure VM role.
For more information on the monthly changes to the Desktop Analytics
cloud service, see What's new in Desktop
Analytics.
You can now add evaluation of custom configuration baselines as a
compliance policy assessment rule. When you create or edit a configuration
baseline, you can now use the Evaluate this baseline as part of compliance
policy assessment option. When you add or edit a compliance policy rule,
you have a condition called Include configured baselines in compliance
policy assessment.
For co-managed devices, and when you configure Intune to take Configuration
Manager compliance assessment results as part of the overall compliance status,
this information is sent to Azure Active Directory. You can then use it for
conditional access to your Office 365 resources.
Configuration Manager current branch version 1906 introduced support for Windows Virtual Desktop. This Microsoft Azure environment supports several OS versions, some of
which allow multiple concurrent active user sessions. For example, Windows 10
Enterprise multi-session is one of these OS versions.
If you require user policy on these multi-session devices and accept any
potential performance impact, you can now configure a client setting to enable
user policy. In the Client Policy group, configure the Enable user
policy for multiple user sessions setting.
We've added some significant optimizations to the CMPivot engine. Now you
can push more of the processing to the ConfigMgr client. The optimizations
drastically reduce the network and server CPU load needed to run CMPivot
queries. With these optimizations, you can now sift through gigabytes of client
data in real time.
We've added a number of new CMPivot entities and entity enhancements to aid
in troubleshooting and hunting. We've included the following entities to query:
- Windows event logs (WinEvent)
- File content (FileContent)
- DLLs loaded by processes (ProcessModule)
- Azure Active Directory information (AADStatus)
- Endpoint protection status (EPStatus)
This release also includes several other enhancements to CMPivot.
When you enable Microsoft Connected Cache on your Configuration Manager
distribution points, they can now serve Microsoft Intune Win32 apps to
co-managed clients.
The all-new Microsoft Edge is ready for business. You can now deploy
Microsoft Edge, version 77 and later, to your users. Admins can pick the Beta,
Dev, or Stable channel, along with a version of the Microsoft Edge client to
deploy.
Starting in current branch version 1906, you can create a group of
applications to send to a device collection as a single deployment. This release improves upon this
feature:
- Users can select Uninstall for the app group in Software Center.
- You can deploy an app group to a user collection.
You now have more granular controls over synchronization of third-party
updates catalogs. Starting in Configuration Manager version 1910, you can
configure the synchronization schedule for each catalog independently. When you
use catalogs that include categorized updates, you can configure
synchronization to include only specific categories of updates to avoid
synchronizing the entire catalog. With categorized catalogs, when you're
confident you'll deploy a category, you can configure it to automatically
download and publish to Windows Server Update Services (WSUS).
Previously, you could use Delivery Optimization only for express updates.
With Configuration Manager version 1910, it's now possible to use Delivery
Optimization for the distribution of all Windows Update content for clients
running Windows 10 version 1709 or later.
You can now use Deployed as an update filter for your automatic
deployment rules (ADRs). This filter helps identify new updates that might need
to be deployed to your pilot or test collections.
The task sequence editor includes the following improvements:
- Search the task sequence editor: If you have a large task sequence with many groups and steps, it can be difficult to find specific steps. You can now search in the task sequence editor. This action lets you more quickly locate steps in the task sequence.
- Copy and paste task sequence conditions: If you want to reuse the conditions from one task sequence step to another, you can now copy and paste conditions in the task sequence editor.
You can now run a task sequence with the high-performance power plan. This
option improves the overall speed of the task sequence. It configures Windows
to use its built-in high-performance power plan, which delivers maximum
performance at the expense of higher power consumption.
You can use the task sequence to deploy a Windows 10 in-place upgrade via
the cloud management gateway (CMG). However, it requires the deployment to
download all content locally before starting the task sequence.
Starting in this release, the task sequence engine can download packages
on-demand from a content-enabled CMG or a cloud distribution point. This change
provides additional flexibility with your Windows 10 in-place upgrade
deployments to internet-based devices.
This release includes the following improvements to OS deployment.
Boot image
keyboard layout
Configure the default keyboard layout for a boot image. On the Customization
tab of a boot image, use the new Set default keyboard layout in WinPE
option. If you select a language other than en-us, Configuration Manager still
includes en-us in the available input locales. On the device, the initial
keyboard layout is the selected locale, but the user can switch the device to
en-us if needed.
Import a single
index of an OS upgrade package
When you import an OS upgrade package, you can use the Extract a
specific image index from install.wim file of selected upgrade package
option. This behavior is similar as with OS images, except that it overwrites the existing install.wim in the OS upgrade
package. It extracts the image index to a temporary location and then moves it
into the original source directory.
Output the
results of a Run Command Line step to a variable during a task sequence
The Run Command Line step now includes an Output to task sequence
variable option. When you enable this option, the task sequence saves the
output from the command to a custom task sequence variable that you specify.
Improvements to
task sequence debugger
This release includes the following improvements to the task sequence
debugger:
- Use the new task sequence variable TSDebugOnError to automatically start the debugger when the task sequence returns an error.
- If you create a breakpoint in the debugger and then the task sequence restarts the computer, the debugger keeps the breakpoints after restart.
Improved
language support in task sequence
This release adds control over language configuration during OS deployment.
If you're already applying these language settings, this change can help you
simplify your OS deployment task sequence. Instead of using multiple steps per
language or separate scripts, use one instance per language of the built-in Apply
Windows Settings step with a condition for that language.
Use the Apply Windows Settings task sequence step to configure the
following new settings:
- Input locale (default keyboard layout)
- System locale
- UI language
- UI language fallback
- User locale
New variable for
Windows 10 in-place upgrade
To address timing issues with the Window 10 in-place upgrade task sequence
on high-performance devices when Windows setup is complete, you can now set a
new task sequence variable, SetupCompletePause. When you assign a value
in seconds to this variable, the Windows setup process delays that amount of
time before it starts the task sequence. This timeout provides the
Configuration Manager client additional time to initialize.
The Office 365 ProPlus Pilot and Health Dashboard helps you plan, pilot,
and deploy Office 365 ProPlus. The dashboard provides health insights for
devices with Office 365 ProPlus to help identify possible issues that might
affect your deployment plans. The Office 365 ProPlus Pilot and Health Dashboard
provides a recommendation for pilot devices based on add-in inventory.
Configuration Manager now provides the following management capabilities
for BitLocker Drive Encryption:
- Deploy the BitLocker client to managed Windows devices.
- Manage device encryption policies.
- Generate compliance reports.
- Use an administration and monitoring website for key recovery.
- Access a user self-service portal.
We've made the following improvements to Console Connections:
- The ability to message other Configuration Manager administrators through Microsoft Teams.
- The Last Console Heartbeat column has replaced the Last Connected Time column.
- An open console in the foreground sends a heartbeat every 10 minutes to help determine which console connections are currently active.
There are new device actions for Client Diagnostics in the
Configuration Manager console:
- Enable verbose logging: Change the global log level for the CCM component to verbose, and enable debug logging.
- Disable verbose logging: Change the global log level to default, and disable debug logging.
This release includes the following improvements to search in the
Configuration Manager console:
- You can now use the All Subfolders search option from the Driver Packages and Queries nodes.
- When a search returns more than 1,000 results, select OK on the notice bar to view more results.
Aucun commentaire:
Enregistrer un commentaire