<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Cool new Longhorn Server feature is out of the closet&#8230;</title>
	<atom:link href="http://blog.joeware.net/2007/03/18/828/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.joeware.net/2007/03/18/828/</link>
	<description>Information about joeware mixed with wild and crazy opinions...</description>
	<lastBuildDate>Thu, 08 Jul 2010 18:21:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: joe</title>
		<link>http://blog.joeware.net/2007/03/18/828/comment-page-1/#comment-22833</link>
		<dc:creator>joe</dc:creator>
		<pubDate>Tue, 20 Mar 2007 03:46:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.joeware.net/2007/03/18/828/#comment-22833</guid>
		<description>The idea, or at least as I see it, would be to create groups to match each policy and place the users into them directly when you set them up. Not sure why being in multiple groups would come into play here unless you were just linking the PSO&#039;s to random groups. If you do that, then yes you will be falling back on your PSO Precedence.

I completely disagree on the being useless in large orgs comment. I do most of my work in 100k+ seats and see this as massively useful in those environments and honestly, not that difficult to manage. It isn&#039;t something that should be changing all that much.</description>
		<content:encoded><![CDATA[<p>The idea, or at least as I see it, would be to create groups to match each policy and place the users into them directly when you set them up. Not sure why being in multiple groups would come into play here unless you were just linking the PSO&#8217;s to random groups. If you do that, then yes you will be falling back on your PSO Precedence.</p>
<p>I completely disagree on the being useless in large orgs comment. I do most of my work in 100k+ seats and see this as massively useful in those environments and honestly, not that difficult to manage. It isn&#8217;t something that should be changing all that much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Kelly</title>
		<link>http://blog.joeware.net/2007/03/18/828/comment-page-1/#comment-22803</link>
		<dc:creator>Steve Kelly</dc:creator>
		<pubDate>Tue, 20 Mar 2007 02:09:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.joeware.net/2007/03/18/828/#comment-22803</guid>
		<description>Although, this is better than nothing, it will be almost useless in large organizations unless MS decides to make dynamic group membership a reality. Then I could see the real potential. The fact that users could be a member of multiple groups makes this almost pointless unless, the group were automatically based on some other factor such as another attribute or object creation.</description>
		<content:encoded><![CDATA[<p>Although, this is better than nothing, it will be almost useless in large organizations unless MS decides to make dynamic group membership a reality. Then I could see the real potential. The fact that users could be a member of multiple groups makes this almost pointless unless, the group were automatically based on some other factor such as another attribute or object creation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
