{
  "version": "https://jsonfeed.org/version/1.1",
  "title": "wmi",
  "home_page_url": "https://evotec.xyz/es/tags/wmi",
  "feed_url": "https://evotec.xyz/es/tags/wmi/index.feed.json",
  "description": "Evotec Main Website",
  "items": [
    {
      "id": "https://evotec.xyz/es/blog/using-win32_useraccount-wmi-filter-in-powershell-group-policies-and-what-to-avoid",
      "url": "https://evotec.xyz/es/blog/using-win32_useraccount-wmi-filter-in-powershell-group-policies-and-what-to-avoid",
      "title": "Using Win32_UserAccount WMI filter in PowerShell/Group Policies and what to avoid",
      "summary": "Some months ago, I created PowerShell Script to create local administrative users on workstations \u2013 Create a local user or administrator account in Windows using PowerShell. It\u2019s 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\u2019ve been using Win32_UserAccount WMI based query to find local users and manage them to an extent. While Get-LocalUser exists, it\u2019s not suitable for the PowerShell 2.0 scenario. I also use the same query in GPO for WMI filtering. You can say it\u2019s been a good friend of mine.",
      "date_published": "2020-06-02T15:45:54.0000000Z",
      "tags": [
        "active directory",
        "ad",
        "gpo",
        "powershell",
        "wmi"
      ]
    }
  ]
}