Blog Post

Configuration Manager Blog
2 MIN READ

Configuration Manager technical preview version 2405

Bala_Delli's avatar
Bala_Delli
Icon for Microsoft rankMicrosoft
Jun 07, 2024

 

Configuration Manager now supports SQL Extended Protection for Authentication

 

Configuration Manager now supports SQL Extended Protection for Authentication. It's a security feature that enhances protection against MITM attacks, making SQL Server more secure when connections are made using Extended Protection. These enhancements collectively reduce the risk of unauthorized access and protect sensitive data managed by the SQL Server Database Engine.

 

For more information, see Connect to the Database Engine Using Extended Protection

 

BitLocker support in Arm devices

 

Configuration Manager now supports BitLocker Task Sequence steps for Arm devices. In BitLocker Management, policies that include OS Drive encryption with a TPM protector and Fixed Drive encryption with the Auto-Unlock option are supported on Arm devices.

 

 

Introducing Centralized Search - Desired Workspace Selection

 

The centralized search box now enables the option to select the desired workspace for searching. Users can easily refine their search results by selecting the desired workspace from the dropdown menu.

 

 

Fixes

 

Performance Enhancement of policy processing and collection evaluation

 

The performance of policy processing and collection evaluation has been enhanced. Previously, blocking chains from sp_ProcessPolicyChanges, called by PolicyPv, would run for hours, disrupting multiple workloads including collection management and policy processing.

Known issues

 

Unable to import or connect to Powershell Configuration Manager module via console

 

While importing or connecting to Configuration manager Powershell module via CM console users get the following error message : PS C:\Build\AdminConsole\bin> Import-Module .\ConfigurationManager.psd1 Import-Module : The module manifest 'C:\Build\AdminConsole\bin\ConfigurationManager.psd1' could not be processed because it is not a valid Windows PowerShell restricted language file. Remove the elements that are not permitted by the restricted language

Configuration Manager console won't automatically update

 

If you update a technical preview site from version 2401 to a later version, the Configuration Manager console fails to update. This problem is because of a known issue in the extension installer.

 

Mitigation: To work around this issue, after you update the site from version 2401 to a later version, manually uninstall the previous console and run ConsoleSetup.exe.

 

For more information, see Install the Configuration Manager console

 

Update 2405 for Technical Preview Branch is available in the Microsoft Configuration Manager Technical Preview console. For new installations, the 2405 baseline version of Microsoft Configuration Manager Technical Preview Branch is available on the link:  CM2405TP-Baseline or from Eval center

 

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.

 

We would love to hear your thoughts about the latest Technical Preview! Send us feedback directly from the console.

 

Thanks,

The Configuration Manager team

 

Configuration Manager Resources:

Documentation for Configuration Manager Technical Previews

Try the Configuration Manager Technical Preview Branch

Documentation for Configuration Manager

Configuration Manager Forums

Configuration Manager Support

Updated Jun 26, 2024
Version 2.0
  • PiotrBrz - This is TP, if it is for production please track the CB releases and upgrade from console. We release two TP every CB release

     

    ms_edrusi - Sure, feedback noted.

  • PiotrBrz's avatar
    PiotrBrz
    Copper Contributor

    Hi, we use older version of SCCM, is there any roadmap how long SCCM will be developed/continued.

    Technical preview is 2405 will there be new versions too?

  • ms_edrusi's avatar
    ms_edrusi
    Brass Contributor

    Hello Bala and SCCM Team.

    I have an ask and I hope you see fit to include at some point in the near future. Can you please add a link to see machines with the patch installed like we are able to see the required list?

     

    Thank you,

    Ed

  • ggaston's avatar
    ggaston
    Copper Contributor

    I'm seeing delays on policy processing including Intune registration due the impact of sp_ProcessPolicyChanges merge in SQL. There's any way to get this fix out of this TP? I do see the policy module msi and exe in the installer. Is any supported way to apply this without installing TP?

  • Joseph_Smith290's avatar
    Joseph_Smith290
    Copper Contributor

    Bala_Delli  PalikaSingh 
    This post states that "SQL Extended Protection for Authentication" is a feature that is available starting in Configuration Manager 2405. I am running Configuration Manager 2303 with a database server (Windows Server 2019 V. 1809 Build 17763.6189) Running SQL Server 2022. On the database server (through SQL Server Configuration Manager) I was able to enable Extended Protection (set to "Required"). I subsequently was able to confirm that this effectively mitigated NTLM relay attacks against the Database server. 

    What exactly is the difference between what I did, and what is stated to be supported here? What benefit would I derive from upgrading to Configuration Manager 2405, that I don't already have with enabling Extended Protection via SQL Server Configuration Manager on my SQL Server as is (what is the distinction between the two)?

  • Joseph_Smith290 - There is no difference, only thing is we have not tested and certified. With 2409 we are testing E2E with scenarios and if anything is breaking, we are fixing. If you are not seen any issues you can enable and use, once we release 2409 you can upgrade the infra. Thanks for your feedback that even with 2303 SQL extended protection is intact which is good to know.