<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Creating a List of OWA Exchange Users</title>
	<link>http://kerpau.net/creating-a-list-of-owa-exchange-users/</link>
	<description>Practical system administration...</description>
	<pubDate>Wed, 07 Jan 2009 10:56:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Carl</title>
		<link>http://kerpau.net/creating-a-list-of-owa-exchange-users/#comment-2</link>
		<pubDate>Tue, 02 Jan 2007 17:30:23 +0000</pubDate>
		<guid>http://kerpau.net/creating-a-list-of-owa-exchange-users/#comment-2</guid>
					<description>Tom,

Thanks for the comment on my blog.  I actually had problems with a similar script a couple years ago on Exchange 2000.  The script SHOULD have worked, but it didn't return all OWA-enabled accounts on Exchange 2000 at the time.  

The accounts in question had the HTTP protocol enabled in AD Users and Computers, but they didn't show up in the list generated by this query.  I looked at the AD attributes using ADSIEdit - (or it could have been LDP) and the "HTTP" attribute actually didn't exist, even though the option was definitely checked in AD Users and Computers.  Anyway, I'd suggest spot checking a half dozen accounts that you know are enabled, just to make sure the script is giving you all the users.

My script use the Advanced Find feature in AD Users and Computers rather than dsquery, but as I said, the attributes were actually missing in AD.</description>
		<content:encoded><![CDATA[<p>Tom,</p>
<p>Thanks for the comment on my blog.  I actually had problems with a similar script a couple years ago on Exchange 2000.  The script SHOULD have worked, but it didn&#8217;t return all OWA-enabled accounts on Exchange 2000 at the time.  </p>
<p>The accounts in question had the HTTP protocol enabled in AD Users and Computers, but they didn&#8217;t show up in the list generated by this query.  I looked at the AD attributes using ADSIEdit - (or it could have been LDP) and the &#8220;HTTP&#8221; attribute actually didn&#8217;t exist, even though the option was definitely checked in AD Users and Computers.  Anyway, I&#8217;d suggest spot checking a half dozen accounts that you know are enabled, just to make sure the script is giving you all the users.</p>
<p>My script use the Advanced Find feature in AD Users and Computers rather than dsquery, but as I said, the attributes were actually missing in AD.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
