<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Obscurum per Obscurius : GPO</title><link>http://blogs.msdn.com/muaddib/archive/tags/GPO/default.aspx</link><description>Tags: GPO</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Group Policy Resources</title><link>http://blogs.msdn.com/muaddib/archive/2009/04/30/group-policy-resources.aspx</link><pubDate>Thu, 30 Apr 2009 22:04:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9581145</guid><dc:creator>MuadDib</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/muaddib/comments/9581145.aspx</comments><wfw:commentRss>http://blogs.msdn.com/muaddib/commentrss.aspx?PostID=9581145</wfw:commentRss><description>In the last couple of weeks I have been working with customers on GPO implementations. One of the first things I show them are the Excel spreadsheets that contain all the settings in a search able format. These spreadsheets are useful when you don't know...(&lt;a href="http://blogs.msdn.com/muaddib/archive/2009/04/30/group-policy-resources.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9581145" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/muaddib/archive/tags/Group+Policy/default.aspx">Group Policy</category><category domain="http://blogs.msdn.com/muaddib/archive/tags/GPO/default.aspx">GPO</category></item><item><title>Unlocking the Local Security Policy on a Computer</title><link>http://blogs.msdn.com/muaddib/archive/2006/11/04/unlocking-a-local-security-policy-on-a-computer.aspx</link><pubDate>Sun, 05 Nov 2006 04:51:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:966830</guid><dc:creator>MuadDib</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/muaddib/comments/966830.aspx</comments><wfw:commentRss>http://blogs.msdn.com/muaddib/commentrss.aspx?PostID=966830</wfw:commentRss><description>&lt;P&gt;There are times when you are doing troubleshooting or testing when you need to work on a production computer&amp;nbsp;in a lab environment.&amp;nbsp; In these cases you capture an image of the computer in question and restore it on lab hardware.&amp;nbsp; Many times&amp;nbsp;the local security policy has been set by a GPO and cannot be modified by using the &lt;STRONG&gt;Local Security Settings&lt;/STRONG&gt; MMC.&amp;nbsp;&amp;nbsp;When the computer is removed from the network (and domain)&amp;nbsp;the local security policy remains unchanged.&amp;nbsp; The procedure below will enable you to modify the local security policy on a computer where this has occured.&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Log onto the&amp;nbsp;computer with an Administrator account.&lt;/LI&gt;
&lt;LI&gt;Start the &lt;STRONG&gt;Local Security Settings&lt;/STRONG&gt;&amp;nbsp;MMC (SECPOL.MSC)&lt;/LI&gt;
&lt;LI&gt;Export the current security settings to&amp;nbsp;an INF file by right clicking the top node in the MMC and selecting Export from the context menu. (for Windows XP see additional information below) and name the file "current.inf" (name is not important)&lt;/LI&gt;
&lt;LI&gt;Open a blank MMC (Start &amp;gt; Run MMC)&lt;/LI&gt;
&lt;LI&gt;Add the &lt;STRONG&gt;Security&amp;nbsp;Configuration and Analysis&lt;/STRONG&gt;&amp;nbsp;snap-in.&lt;/LI&gt;
&lt;LI&gt;Right-click the top node in&amp;nbsp;&lt;STRONG&gt;Security&amp;nbsp;Configuration and Analysis&lt;/STRONG&gt; and select "New Database" and then save the database.&lt;/LI&gt;
&lt;LI&gt;When prompted to import a security template use the one exported in step 3 above (current.inf)&lt;/LI&gt;
&lt;LI&gt;Now right click &lt;STRONG&gt;Security&amp;nbsp;Configuration and Analysis&lt;/STRONG&gt; and select "Analyze Computer Now".&lt;/LI&gt;
&lt;LI&gt;Now browse to the setting you want to modify.&amp;nbsp; You will notice the database setting and computer settings are the same in all cases.&amp;nbsp; Double-click the setting and make changes.&amp;nbsp; Repeat for each setting you want to modify.&lt;/LI&gt;
&lt;LI&gt;When you are finished making changes, right-click top node and select "Configure Computer Now" and you changes will be applied.&lt;/LI&gt;&lt;/OL&gt;
&lt;P mce_keep="true"&gt;In Windows XP the SECPOL.MSC does not support the exporting of the security configuration to a template.&amp;nbsp; The SECEDIT.EXE command-line utility does not support exporting the configuration either.&amp;nbsp; There is an updated version of SECEDIT.EXE available from Microsoft as described int he KB article below that does enable you to export the security configuration to an inf file.&lt;/P&gt;
&lt;P mce_keep="true"&gt;&lt;STRONG&gt;You cannot use the Secedit.exe command-line tool to export the local security policy settings on a stand-alone workstation that is running Microsoft Windows XP&lt;/STRONG&gt;&lt;BR&gt;&lt;STRONG&gt;&lt;A href="http://support.microsoft.com/default.aspx/kb/897327/" mce_href="http://support.microsoft.com/default.aspx/kb/897327/"&gt;http://support.microsoft.com/default.aspx/kb/897327/&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=966830" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/muaddib/archive/tags/Group+Policy/default.aspx">Group Policy</category><category domain="http://blogs.msdn.com/muaddib/archive/tags/GPO/default.aspx">GPO</category></item></channel></rss>