<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>/ M@ / &#187; Group Policy</title>
	<atom:link href="http://matthewsnell.com/blog/tag/group-policy/feed/" rel="self" type="application/rss+xml" />
	<link>http://matthewsnell.com/blog</link>
	<description>Random things and geekery</description>
	<lastBuildDate>Wed, 06 May 2009 18:59:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>The Borked WSUS GPO Mystery</title>
		<link>http://matthewsnell.com/blog/2007/08/03/the-borked-wsus-gpo-mystery/</link>
		<comments>http://matthewsnell.com/blog/2007/08/03/the-borked-wsus-gpo-mystery/#comments</comments>
		<pubDate>Fri, 03 Aug 2007 14:45:10 +0000</pubDate>
		<dc:creator>M@</dc:creator>
				<category><![CDATA[Geekery]]></category>
		<category><![CDATA[Group Policy]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[WSUS]]></category>

		<guid isPermaLink="false">http://matthewsnell.com/blog/2007/08/03/the-borked-wsus-gpo-mystery/</guid>
		<description><![CDATA[So here&#8217;s a story, a crappy story.  There&#8217;s no real explanation (at this time anyway) but the issue is resolved..
I was @ work yesterday, updating some software on some client machines.  I started noticing that Windows Update wasn&#8217;t enabled on these boxes and I was damn sure that I had a GPO set [...]]]></description>
			<content:encoded><![CDATA[<p>So here&#8217;s a story, a crappy story.  There&#8217;s no real explanation (at this time anyway) but the issue is resolved..</p>
<p>I was @ work yesterday, updating some software on some client machines.  I started noticing that Windows Update wasn&#8217;t enabled on these boxes and I was damn sure that I had a <a href="http://en.wikipedia.org/wiki/Group_Policy_Object" target="_blank">GPO</a> set up for turning it on.  As a matter of fact, it was a fairly new policy (about a month old?) that was pointing the machines to a WSUS server on campus.  I know little about WSUS and what it does in the background, I just know it&#8217;s a handy way to report on and approve updates for machines and not have to install whatever MS says you have to install.  We have a very capable gentleman keeping his eyes on the updates and the vulnerability notices.  Glad to have him dealing with this for us.</p>
<p>Anyway..  My machines just weren&#8217;t picking up the policy that enables Automatic Updates and points the client to the WSUS server.  Whats funny is that when it was initially set up, it was working fine!  I have no idea when it decided to jump the track, I just know that it did.  I did everything I could think of, forcing group policy updates, googling, talking to other admins on campus, all of us stumped.  We finally decided that somebody would come down and be a second pair of eyes on the clients in my area the next day.  I still continued poking and prodding my boxes for the remainder of the afternoon.</p>
<p>Eventually the day ended, I was p*ssed about this problem and late leaving the office.  I HATE knowing something is wrong and being unable to fix it.  So I stomped about and sulked all night, wondering what other steps I could perform.  I ended up just going to bed really early and hoping that some sleep would help.  Riiiiiiiight.</p>
<p>So there I was, 3:45 in the morning, working out and cursing the millipedes trying to invade my house (another story).  Still CRaZy angry and annoyed..  I just couldn&#8217;t figure out WTF was wrong..  I finished the workout, got ready and headed into work bright and early.   I attempted all of the things I had done before, and got the same result.</p>
<p>I finally just decided to unlink the GPO, create a new one, mirror the settings and then force an update on the client machine.  All the while my toes were crossed (fingers were busy).</p>
<p>Wouldn&#8217;t ya know it.  It worked.  No idea why, it just did.  There aren&#8217;t any glaring diffs between the policies.  One works, the other doesn&#8217;t.  pffft.  Hate crap like that.. I wouldn&#8217;t have minded (as much) if there was some freaking reason for problem..</p>
<p>So, it&#8217;s Friday, I don&#8217;t have to spend the weekend worrying about this and I&#8217;m leaving at noon (just over an hour from now).  At least it ended well.</p>
<p>Ahhh, let the weekend begin.</p>
]]></content:encoded>
			<wfw:commentRss>http://matthewsnell.com/blog/2007/08/03/the-borked-wsus-gpo-mystery/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
