<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>wmi</title><link>https://evotec.xyz/es/tags/wmi</link><description>Evotec Main Website</description><atom:link href="https://evotec.xyz/es/tags/wmi/index.xml" rel="self" type="application/rss+xml" /><item><title>Using Win32_UserAccount WMI filter in PowerShell/Group Policies and what to avoid</title><link>https://evotec.xyz/es/blog/using-win32_useraccount-wmi-filter-in-powershell-group-policies-and-what-to-avoid</link><description>Some months ago, I created PowerShell Script to create local administrative users on workstations – Create a local user or administrator account in Windows using PowerShell. It’s a bit overcomplicated, but the goal was it should work for Windows 7 and up, and that means supporting PowerShell 2.0. As part of that exercise, I’ve been using Win32_UserAccount WMI based query to find local users and manage them to an extent. While Get-LocalUser exists, it’s not suitable for the PowerShell 2.0 scenario. I also use the same query in GPO for WMI filtering. You can say it’s been a good friend of mine.</description><pubDate>Tue, 02 Jun 2020 15:45:54 GMT</pubDate><guid>https://evotec.xyz/es/blog/using-win32_useraccount-wmi-filter-in-powershell-group-policies-and-what-to-avoid</guid><category>active directory</category><category>ad</category><category>gpo</category><category>powershell</category><category>wmi</category></item></channel></rss>