We recently announced that Windows PowerShell 2.0 is being deprecated in the Windows 10 Fall Creators Update. Deprecation is a process whereby technologies or applications are marked as legacy, signalling to users that they may be removed in the future, and that should move away from them and towards newer alternatives.
Source : PowerShell Team Blog
Microsoft is pleased to announce the final release of the recommended security configuration baseline settings for Windows 10 “Creators Update,” also known as version 1703, “Redstone 2,” or RS2. The downloadable attachment to this blog post includes importable GPOs, tools for applying the GPOs, custom ADMX files for Group Policy settings, and all the settings in spreadsheet form.
Source : Microsoft Security Guidance blog
Security Compliance Manager (SCM) is dead. To replace it, Microsoft has released the Security Compliance Toolkit (SCT). In this Ask the Admin, I’ll explain why SCM was killed off and how the new toolkit stacks up in comparison.
Source : Petri Reference : Security Compliance Manager (SCM) retired; new tools and procedures
As we’ve made progress on open-source PowerShell, it’s time to start talking more in-depth about:
different editions of PowerShell PowerShell’s relationship to .NET Core and .NET Standard the future of PowerShell when you might expect to start taking a dependency on PowerShell Core 6.0 in production
Source : PowerShell Team Blog
You should also read : No future for Windows PowerShell—change to PowerShell Core
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.
Source : Ask the Core Team
In IIS 10.0, we introduced the IISAdministration PowerShell module which was a new way to manage IIS. This module included numerous improvements over the existing WebAdministration cmdlets. Unfortunately, folks who hadn’t updated to Windows Server 2016 weren’t able to take advantage of the new management cmdlets until now. I’m pleased to announce that we’ve now released this module to the PowerShell Gallery and is available for use on Windows Server 2012 and above.
Source : IIS Team Blog
Very interesting readings from the WSUS Product Team Blog :
Demystifying “Dual Scan” Improving Dual Scan on 1607
If you still rely on PowerShell 2.0, you should think about updating your code to work with PowerShell 5.0. Starting in the Windows 10 Fall Creators Update, Microsoft will no longer support PowerShell 2.0. In this Ask the Admin, I’ll discuss why PowerShell 2.0 poses a security risk and how to remove it from Windows 10.
Source : Petri
