<?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: The sky is falling&#8230;</title>
	<atom:link href="http://blog.joeware.net/2006/03/23/268/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.joeware.net/2006/03/23/268/</link>
	<description>Information about joeware mixed with wild and crazy opinions...</description>
	<lastBuildDate>Wed, 01 Sep 2010 22:02:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Lee Flight</title>
		<link>http://blog.joeware.net/2006/03/23/268/comment-page-1/#comment-754</link>
		<dc:creator>Lee Flight</dc:creator>
		<pubDate>Fri, 24 Mar 2006 00:20:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.joeware.net/2006/03/23/268/#comment-754</guid>
		<description>If I dig through my mailbox archive I could probably find
the e-mail chain where I reported this issue in the
Exchange beta program. Being in the UK it was hard to 
get a response but we were eventually told this was 
expected behavior and would be in the gold product
which of course it was :( So we wrote our deprovisioning
around this and updated the masterAccountSID on the 
(pending-delete) users. I was amazed that, seemimgly no 
upgrade testing against a real, dirty AD had been done
and disappointed that the feedback was not (IMO) taken.
We since updated our deprovisioning to dump the AD
user object, take a final back up of filestore and profile 
and exmerge dump the exchange mailbox before delete 
to aid recovery.

I am amazed this has finally been fixed.</description>
		<content:encoded><![CDATA[<p>If I dig through my mailbox archive I could probably find<br />
the e-mail chain where I reported this issue in the<br />
Exchange beta program. Being in the UK it was hard to<br />
get a response but we were eventually told this was<br />
expected behavior and would be in the gold product<br />
which of course it was <img src='http://blog.joeware.net/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  So we wrote our deprovisioning<br />
around this and updated the masterAccountSID on the<br />
(pending-delete) users. I was amazed that, seemimgly no<br />
upgrade testing against a real, dirty AD had been done<br />
and disappointed that the feedback was not (IMO) taken.<br />
We since updated our deprovisioning to dump the AD<br />
user object, take a final back up of filestore and profile<br />
and exmerge dump the exchange mailbox before delete<br />
to aid recovery.</p>
<p>I am amazed this has finally been fixed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: /var/log  &#187; Exchange hotfix: finally!</title>
		<link>http://blog.joeware.net/2006/03/23/268/comment-page-1/#comment-753</link>
		<dc:creator>/var/log  &#187; Exchange hotfix: finally!</dc:creator>
		<pubDate>Thu, 23 Mar 2006 17:43:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.joeware.net/2006/03/23/268/#comment-753</guid>
		<description>[...]   Exchange hotfix: finally! Posted at March 23, 2006 by fred   	  Via joe, and the MS Exchange team blog, it seems us poor Exchange shlobs admins will finally be able to get r [...]</description>
		<content:encoded><![CDATA[<p>[...] </p>
<p> Exchange hotfix: finally!<br />
 Posted at March 23, 2006 by fred</p>
<p>  Via joe, and the MS Exchange team blog, it seems us poor Exchange shlobs admins will finally be able to get r [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
