In this post, you will see the list of features released in ConfigMgr 2105.2 Technical Preview. Microsoft has released the third Technical Preview Version, after announcing SCCM 2103 Production Version this year.
The technical preview introduces new functionality that Microsoft is working on and features that aren’t yet included in the current branch of Configuration Manager.
Configuration Manager technical preview version 2105.2 comes with many improvements and new features. Features that were available in a previous version of the technical preview remain available in later versions.
Similarly, features added to the Configuration Manager Production Version 2103 remain available in the technical preview branch.
Let’s try out all the new features in this technical preview version. Help the Configuration Manager product team send your valuable feedback about the new features before the Microsoft product team finalizes the features.
Important ⚠️- The technical preview branch of Configuration Manager is not supported for use in a production environment. The technical preview is licensed for use only in a lab environment.
Download Technical Preview
When you install a new technical preview site, use the latest baseline version. After installing a baseline version, use in-console updates to bring your installation up to date with the most recent Technical preview version 2105.
Let’s check how to build Microsoft Endpoint Configuration Manager aka MECM Technical Preview LAB – How to Build Configuration Manager Technical Preview LAB | SCCM
Upgrade Technical Preview Version
ConfigMgr Technical Preview builds installation is active for 90 days before it becomes inactive. You need to install the available new technical preview updates within 90 days before the technical preview build expires. Typically, new versions of the technical preview are available each month.
To install Configuration Manager Technical Preview 2105.2 update
- In the Configuration Manager console, Navigate to Administration > Updates and Servicing.
- Right-click Configuration Manager Technical Preview 2105.2 and click Install Update Pack.
- Complete all the steps. You are ready to go.
Features in Configuration Manager technical preview version 2105.2, Let’s see what the improvement of ConfigMgr 2105.2 Technical Preview are –
Windows Update native experience for software updates
When installing software updates from Configuration Manager, you can now choose to use the native Windows Update interface and restart the experience. The client’s Windows Update Settings page will display the updates like they appear when using Windows Update for scanning.
To use this feature, client devices must be running Windows Insider build 21277 or later. Let’s check how to enable the Windows Update native experience –
- In the Configuration Manager console, Navigate the Administration workspace, and select Client Settings.
- Select the Computer Restart group in Client Settings
- For the Select the restart experience to be shows to end users setting, choose the Windows option.
- If needed, you can change the number of days the device is allowed to be pending a restart before it’s forced using the following setting: Specify a deadline, the time (in days) from when a device is pending reboot until the device is forced to restart.
Minimum value: 1 day
Maximum value: 30 days
Default value: 2 days
Custom properties for devices
Starting in the Configuration Manager technical preview, you can use the administration service to set this data on devices. You can then use the custom properties in Configuration Manager for reporting or to create collections.
Prerequisites for custom properties
The account that makes the API calls requires the following permissions on a collection that contains the target device:
- To set properties: Modify Resource
- To view properties: Read Resource
- To remove properties: Delete Resource
It’s good to try it out, let’s check more details about creating custom properties!
Hardware inventory for client log settings
You can now inventory client log file settings such as log levels and size. This behavior allows you to track settings that you change by the Client Diagnostics actions. This new inventory class isn’t enabled by default.
- In the Configuration Manager console, edit the default or any custom client settings.
- Enable the new inventory class, Client Diagnostics (CCM_ClientDiagnostics). This class includes the following attributes:
- Debug Logging Enabled
- Logging Enabled
- Log Level
- History File Count
- Max Log File Size
- For a device, download the computer policy and then use the client notification action to Collect hardware inventory.
- After the client completes the inventory cycle, use Resource Explorer to view the hardware inventory.
Improvements to CMPivot
The following improvements were added to CMPivot
Know more about – SCCM CMPivot Architecture Fast Channel | ConfigMgr
- Added a Key value to the Registry entity.
- Added a new RegistryKey entity that returns all registry keys matching the given expression
- Added maxif and minif aggregators that we can use with the summarize operator
- Improvements to query autocomplete suggestions in the query editor
Simplified CMPivot permissions requirements
SCCM 2105.2 technical preview release simplified the CMPivot permissions requirements. The new permissions are applicable for CMPivot standalone and CMPivot in the on-premises console. The following changes have been made:
- CMPivot no longer requires SMS Scripts to read permission
- The SMS Provide still requires this permission if the administration service falls back to it due to a 503 (Service Unavailable) error, as seen in the CMPivot.log.
- The default scope permission isn’t required.
Hierarchy approved console extensions don’t require signing
Starting in the Configuration Manager technical preview, you can choose to allow unsigned hierarchy-approved console extensions. You may need to allow unsigned console extensions due to an unsigned internally developed extension, or for testing your own custom extension in a lab.
To allow unsigned hierarchy approved console extensions –
- In the Configuration Manager console, navigate to the Administration workspace, expand Site Configuration, and select Sites. Select Hierarchy Settings from the ribbon.
- On the General tab, enabling the Hierarchy approved console extensions can be an unsigned option.
- Select Ok when done to close the Hierarchy Settings Properties.
PowerShell New cmdlets release
Here are the latest Configuration Manager PowerShell cmdlets.
This set of new cmdlets was released to manage to install behaviors for application deployment types –
- Add-CMDeploymentTypeInstallBehavior – Use this cmdlet to add to the specified deployment type the executable files that need to close for the app install to succeed.
- Get-CMDeploymentTypeInstallBehavior – Use this cmdlet to get from the specified deployment type the list of executable files that need to close for the app install to succeed.
- Remove-CMDeploymentTypeInstallBehavior – Use this cmdlet to remove from the specified deployment type the executable files that need to close for the app install to succeed.
- Set-CMDeploymentTypeInstallBehavior – Use this cmdlet to modify the executable files that need to close for the app install to succeed.
This set of new cmdlets for application deployment type return codes –
- Add-CMDeploymentTypeReturnCode – Use this cmdlet to add return codes to a supported deployment type.
- Get-CMDeploymentTypeReturnCode – Use this cmdlet to get the list of return codes from the specified deployment type.
- Remove-CMDeploymentTypeReturnCode – Use this cmdlet to delete return codes from the specified deployment type.
- Set-CMDeploymentTypeReturnCode – Use this cmdlet to modify return codes for the specified deployment type.
- Get-CMClientSettingDeployment – Use this cmdlet to get a deployment of a custom client settings object. You can use this object with Remove-CMClientSetting.
- Get-CMDeploymentTypeDetectionClause – You can use this cmdlet to get a detection clause from one app and apply it to another.
Send Product Feedback From Error Windows
Starting in this release, error messages include a link to Report errors to Microsoft. This action opens the standard “send a frown” window to provide feedback. It automatically includes details about the user interface and the error to better help Microsoft engineers diagnose the error.
Aside from making it easier to send a frown, it also lets you include the full context of the error message when you share a screenshot.
Resources
- ConfigMgr 2105 Technical Preview New Features | SCCM
- How to Build Configuration Manager Technical Preview LAB