<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sysvol on Anything About IT</title><link>https://www.verboon.info/tags/sysvol/</link><description>Recent content in Sysvol on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 19 Nov 2019 22:22:16 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/sysvol/index.xml" rel="self" type="application/rss+xml"/><item><title>How to identify orphan Group Policy content within the Sysvol folder</title><link>https://www.verboon.info/2019/11/how-to-identify-orphan-group-policy-content-within-the-sysvol-folder/</link><pubDate>Tue, 19 Nov 2019 22:22:16 +0000</pubDate><guid>https://www.verboon.info/2019/11/how-to-identify-orphan-group-policy-content-within-the-sysvol-folder/</guid><description>&lt;p&gt;G&amp;rsquo;day everyone. Today I was working on a Microsoft Security Configuration baseline implementation and while browsing through the Sysvol folder I got the impression that there are less GPO objects stored within AD compared to the number of GPO content folders located within the Sysvol\Policies folder. As we speak about several hundred folders here, too many to count manually, and so another PowerShell script was born.&lt;/p&gt;
&lt;p&gt;Now if the terms SYSVOL, policies folder doesn&amp;rsquo;t mean anything to you, I suggest you first read this article from Darren (@grouppolicyguy) &lt;a href="https://sdmsoftware.com/gpoguy/whitepapers/understanding-group-policy-storage/"&gt;Understanding Group Policy Storage&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>