{
  "version": "https://jsonfeed.org/version/1.1",
  "title": "GPO",
  "home_page_url": "https://evotec.xyz/de/categories/gpo",
  "feed_url": "https://evotec.xyz/de/categories/gpo/index.feed.json",
  "description": "Evotec Main Website",
  "items": [
    {
      "id": "https://evotec.xyz/de/blog/the-only-command-you-will-ever-need-to-understand-and-fix-your-group-policies-gpo",
      "url": "https://evotec.xyz/de/blog/the-only-command-you-will-ever-need-to-understand-and-fix-your-group-policies-gpo",
      "title": "The only command you will ever need to understand and fix your Group Policies (GPO)",
      "summary": "I\u2019ve been working on cleaning up Group Policies for a couple of months. While it may seem trivial, things get complicated when you\u2019re tasked with managing 5000 GPOs created over 15 years by multiple teams without any best practices in mind. While working on GPOZaurr (my new PowerShell module), I\u2019ve noticed that the more code I wrote to manage those GPOs, the more I knew passing this knowledge to admins who will be executing this on a weekly/monthly basis is going to be a challenge. That\u2019s why I\u2019ve decided to follow a similar approach as my other Active Directory testing module called Testimo. I\u2019ve created a single command that analyses Group Policies using different methods and shows views from different angles to deliver the full picture. On top of that, it provides a solution (or it tries to) so that it\u2019s fairly easy to fix \u2013 as long as you agree with what it proposes.",
      "date_published": "2021-01-24T17:15:04.0000000Z",
      "tags": [
        "active directory",
        "gpo",
        "group policy",
        "powershell"
      ]
    },
    {
      "id": "https://evotec.xyz/de/blog/using-win32_useraccount-wmi-filter-in-powershell-group-policies-and-what-to-avoid",
      "url": "https://evotec.xyz/de/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"
      ]
    }
  ]
}