check before: 2024-01-29
Product:
Windows, Windows Server
Platform:
Windows Desktop, World tenant
Status:
Change type:
Admin impact
Links:

Details:
If you're still using Windows Management Instrumentation Command line (WMIC), you'll start seeing changes this year. While it has been deprecated for a while, you could still use it as a feature on demand (FoD). Starting January 29th, 2024, it will become "disabled by default" in the insider build of Windows 11. It will become part of the next Windows 11 release later in 2024. To find out more, read WMI command-line (WMIC) utility deprecation: Next steps.
When will this happen:
2016: WMIC was deprecated in Windows Server.
2021: WMIC was deprecated in Windows 10, version 21H1.
2022: WMIC was available as a FoD and enabled by default.
January 29, 2024: WMIC FoD will be disabled by default in the insider build of Windows 11.
Later in 2024: WMIC FoD will be disabled by default in the next version of Windows 11.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2024-01-27
updated:
2024-08-10
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
Direct effects for Operations**
- Impact on IT Operations
- Dependency on WMIC for system management tasks may lead to operational disruptions if not migrated to PowerShell or alternative methods.
- Roles impacted: IT Operations Managers, System Administrators
- Reference: [WMIC Deprecation Announcement](https://aka.ms/WMIC-Deprecation)
- Impact on IT Services
- Services relying on WMIC for monitoring and reporting may experience failures or degraded performance, affecting service availability.
- Roles impacted: Service Delivery Managers, Application Support Teams
- Reference: [PowerShell as a WMIC Alternative](https://learn.microsoft.com/powershell/scripting/learn/ps101/07-working-with-wmi?view=powershell-7.2)
- Impact on IT Users
- End-users may face issues with applications that depend on WMIC for functionality, leading to potential downtime or loss of features.
- Roles impacted: End Users, Business Analysts
- Reference: [Using WMI - Win32 apps](https://learn.microsoft.com/windows/win32/wmisdk/using-wmi)
- Impact on IT Administrators
- Administrators will need to invest time in training and transitioning scripts and tools from WMIC to PowerShell, which may lead to temporary productivity loss.
- Roles impacted: IT Administrators, DevOps Engineers
- Reference: [WMIC Command-line Utility Deprecation](https://aka.ms/WMIC-Deprecation)
- Impact on Compliance and Security
- Applications that are not updated to remove WMIC dependencies may pose security risks, as deprecated tools may not receive updates or patches.
- Roles impacted: Compliance Officers, Security Analysts
- Reference: [WMIC Deprecation and Security Risks](https://learn.microsoft.com/windows/win32/wmisdk/using-wmi)
Opportunities**
- Transition to PowerShell for WMI Queries
- Migrate existing scripts and applications that rely on WMIC to PowerShell, which is more efficient and supported.
- Roles benefiting: IT Administrators, System Administrators, DevOps Engineers.
- Reference: [Working with WMI - PowerShell](https://learn.microsoft.com/powershell/scripting/learn/ps101/07-working-with-wmi?view=powershell-7.2)
- Training and Upskilling IT Staff
- Provide training sessions for IT staff on PowerShell and its capabilities to ensure a smooth transition from WMIC.
- Roles benefiting: IT Support Staff, System Administrators, IT Managers.
- Reference: [WMI command-line (WMIC) utility deprecation: Next steps](https://aka.ms/WMIC-Deprecation)
- Review and Optimize Existing Scripts
- Conduct an audit of existing scripts that utilize WMIC and optimize them for performance and maintainability using PowerShell.
- Roles benefiting: IT Administrators, Software Developers, System Analysts.
- Reference: [Using WMI - Win32 apps](https://learn.microsoft.com/windows/win32/wmisdk/using-wmi)
- Implement Monitoring Tools for PowerShell
- Invest in monitoring tools that can track PowerShell script execution and performance, ensuring that any issues can be quickly identified and resolved.
- Roles benefiting: IT Operations, Security Analysts, Compliance Officers.
- Reference: [PowerShell Security Best Practices](https://learn.microsoft.com/powershell/scripting/security/security-best-practices?view=powershell-7.2)
- Develop a Migration Plan with Timelines
- Create a detailed migration plan with timelines for transitioning from WMIC to PowerShell, including milestones and responsible parties.
- Roles benefiting: Project Managers, IT Administrators, IT Managers.
- Reference: [WMIC Deprecation Timeline](https://aka.ms/WMIC-Deprecation)
Potentional Risks**
XXXXXXX ... paid membership only
Data Protection**
XXXXXXX ... paid membership only
Hypothetical Work Council Statement**
XXXXXXX ... paid membership only
DPIA Draft**
XXXXXXX ... paid membership only
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
Last updated 3 weeks ago