<?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>Federated Infrastructure</title><link>http://blogs.msdn.com/anthonw/default.aspx</link><description>A discussion on how politics influence technical design, how scripts and code can overcome politics, and random experiences or thoughts from the Microsoft field.  </description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Where can I get Single Instance Store (SIS) for Windows File Servers?</title><link>http://blogs.msdn.com/anthonw/archive/2009/01/23/where-can-i-get-single-instance-store-sis-for-windows-file-servers.aspx</link><pubDate>Fri, 23 Jan 2009 23:24:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9373134</guid><dc:creator>anthonw</dc:creator><slash:comments>3</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/9373134.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=9373134</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=9373134</wfw:comment><description>The answer, it seems, is only from Windows Unified Data Storage Server 2003, which goes by so many other names, it can be challenging to understand sometimes. However, the Single Instance Store, which is based on the Exchange and WDS technologies, detects...(&lt;a href="http://blogs.msdn.com/anthonw/archive/2009/01/23/where-can-i-get-single-instance-store-sis-for-windows-file-servers.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9373134" width="1" height="1"&gt;</description></item><item><title>When Legacies Are Baggage (Resolving the #550 5.1.1 RESOLVER.ADR.ExRecipNotFound error during Migration)</title><link>http://blogs.msdn.com/anthonw/archive/2008/11/07/when-legacies-are-baggage-resolving-the-550-5-1-1-resolver-adr-exrecipnotfound-error-during-migration.aspx</link><pubDate>Sat, 08 Nov 2008 03:21:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9053368</guid><dc:creator>anthonw</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/9053368.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=9053368</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=9053368</wfw:comment><description>I was working with an education customer this week when I came upon an interesting problem related to mail routing for a specific user. This user was migrated from one domain to another and mailbox-enabled for the new Exchange 2007 environment after their...(&lt;a href="http://blogs.msdn.com/anthonw/archive/2008/11/07/when-legacies-are-baggage-resolving-the-550-5-1-1-resolver-adr-exrecipnotfound-error-during-migration.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9053368" width="1" height="1"&gt;</description></item><item><title>Windows Server 2008, IIS 7.0, Exchange 2007 and the Offline Address Book</title><link>http://blogs.msdn.com/anthonw/archive/2008/10/24/windows-server-2008-iis-7-0-exchange-2007-and-the-offline-address-book.aspx</link><pubDate>Fri, 24 Oct 2008 23:20:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9015222</guid><dc:creator>anthonw</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/9015222.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=9015222</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=9015222</wfw:comment><description>I've been working through an interesting situation with one of my customers during the past couple of weeks. For some reason, everytime Outlook 2007 clients attempted to download the offline address book (OAB), they would error out. We found a lead at...(&lt;a href="http://blogs.msdn.com/anthonw/archive/2008/10/24/windows-server-2008-iis-7-0-exchange-2007-and-the-offline-address-book.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9015222" width="1" height="1"&gt;</description></item><item><title>Putting the F in FERPA (Building Distribution Groups for Class Schedules in Exchange)</title><link>http://blogs.msdn.com/anthonw/archive/2008/08/08/putting-the-f-in-ferpa-building-distribution-groups-for-class-schedules-in-exchange.aspx</link><pubDate>Sat, 09 Aug 2008 00:35:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8844397</guid><dc:creator>anthonw</dc:creator><slash:comments>3</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/8844397.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=8844397</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=8844397</wfw:comment><description>One goal at many universities has been to provide a collaboration solution for students, based on email. To do this in Exchange, an administrator needs to create a distribution list to represent the class and populate it with the user accounts. Each distribution...(&lt;a href="http://blogs.msdn.com/anthonw/archive/2008/08/08/putting-the-f-in-ferpa-building-distribution-groups-for-class-schedules-in-exchange.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8844397" width="1" height="1"&gt;</description></item><item><title>NoMAS and Other Solutions to 9548 and 9551 Events (Exchange Server 2003)</title><link>http://blogs.msdn.com/anthonw/archive/2008/07/17/nomas-and-other-solutions-to-9548-and-9551-events-exchange-server-2003.aspx</link><pubDate>Thu, 17 Jul 2008 21:59:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8744756</guid><dc:creator>anthonw</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/8744756.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=8744756</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=8744756</wfw:comment><description>I thought I had posted this information several years ago, but a customer recently contacted me seeking it and I realized it never left the publishing stage. Please note that this post is more specific to 5.5 to 2003 migrations, but may still be relevant...(&lt;a href="http://blogs.msdn.com/anthonw/archive/2008/07/17/nomas-and-other-solutions-to-9548-and-9551-events-exchange-server-2003.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8744756" width="1" height="1"&gt;</description></item><item><title>Installing Exchange 2007 SP1 onto Windows Server 2008 with a WS2008 Active Directory</title><link>http://blogs.msdn.com/anthonw/archive/2008/01/29/installing-exchange-2007-sp1-into-windows-server-2008-active-directory.aspx</link><pubDate>Tue, 29 Jan 2008 21:32:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7310773</guid><dc:creator>anthonw</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/7310773.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=7310773</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=7310773</wfw:comment><description>This post consists of some notes that I took during the installation of Exchange Server 2007 SP1 (Integrated) into a Windows Server 2008 Active Directory Environment (green field, clean installation of everything). The AD environment was created on RC1...(&lt;a href="http://blogs.msdn.com/anthonw/archive/2008/01/29/installing-exchange-2007-sp1-into-windows-server-2008-active-directory.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=7310773" width="1" height="1"&gt;</description></item><item><title>The procedure entry point_except_handler4_common could not be located in the dynamic link library msvcrt.dll</title><link>http://blogs.msdn.com/anthonw/archive/2007/12/06/the-procedure-entry-point-except-handler4-common-could-not-be-located-in-the-dynamic-link-library-msvcrt-dll.aspx</link><pubDate>Thu, 06 Dec 2007 23:48:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6684635</guid><dc:creator>anthonw</dc:creator><slash:comments>6</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/6684635.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=6684635</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=6684635</wfw:comment><description>Every now and then, I take a break from federated infrastructure to post something that is likely only relevant to me. I recently purchased a new sound card (Creative Soundblaster X-Fi Extreme Audio) for a machine that is still running Windows XP. I allowed...(&lt;a href="http://blogs.msdn.com/anthonw/archive/2007/12/06/the-procedure-entry-point-except-handler4-common-could-not-be-located-in-the-dynamic-link-library-msvcrt-dll.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=6684635" width="1" height="1"&gt;</description></item><item><title>Pool Nonpaged memory Leaks on Exchange 2003</title><link>http://blogs.msdn.com/anthonw/archive/2007/11/27/pool-nonpaged-memory-leaks-on-exchange-2003.aspx</link><pubDate>Wed, 28 Nov 2007 03:10:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6563917</guid><dc:creator>anthonw</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/6563917.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=6563917</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=6563917</wfw:comment><description>I am working with two independent customers. Each of these customers is running Exchange 2003 on the backend, but have been working over the last several months to upgrade their clients to Office 2007, including Outlook 2007. In most cases, desktops were...(&lt;a href="http://blogs.msdn.com/anthonw/archive/2007/11/27/pool-nonpaged-memory-leaks-on-exchange-2003.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=6563917" width="1" height="1"&gt;</description></item><item><title>Using Powershell to Correct  9325 Events in Exchange 2007</title><link>http://blogs.msdn.com/anthonw/archive/2007/08/23/using-powershell-to-correct-9325-events-in-exchange-2007.aspx</link><pubDate>Thu, 23 Aug 2007 21:58:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4530108</guid><dc:creator>anthonw</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/4530108.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=4530108</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=4530108</wfw:comment><description>Per knowledge base article 936197 , Exchange 2007 may be dropping recipients from the Offline Address book and generating any of the following errors in the event log (note that diagnostic logging on the Exchange server needs to be set to High or Expert...(&lt;a href="http://blogs.msdn.com/anthonw/archive/2007/08/23/using-powershell-to-correct-9325-events-in-exchange-2007.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=4530108" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/anthonw/archive/tags/Exchange/default.aspx">Exchange</category><category domain="http://blogs.msdn.com/anthonw/archive/tags/Code/default.aspx">Code</category><category domain="http://blogs.msdn.com/anthonw/archive/tags/Management+Tools/default.aspx">Management Tools</category></item><item><title>Mailbox Cleanup After Cross Organizational Moves</title><link>http://blogs.msdn.com/anthonw/archive/2007/08/08/mailbox-cleanup-after-cross-organizational-moves.aspx</link><pubDate>Wed, 08 Aug 2007 21:51:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4296396</guid><dc:creator>anthonw</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/4296396.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=4296396</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=4296396</wfw:comment><description>I thought I would share some code I wrote for doing bulk mailbox cleanups on Exchange 2003 for cross-organizational mailbox moves. This code is nearly identical to that in my previous post , but this one takes an input file to process several mailboxes...(&lt;a href="http://blogs.msdn.com/anthonw/archive/2007/08/08/mailbox-cleanup-after-cross-organizational-moves.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=4296396" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/anthonw/archive/tags/Exchange/default.aspx">Exchange</category><category domain="http://blogs.msdn.com/anthonw/archive/tags/Code/default.aspx">Code</category></item><item><title>There is no primary SMTP address</title><link>http://blogs.msdn.com/anthonw/archive/2007/07/31/there-is-no-primary-smtp-address.aspx</link><pubDate>Tue, 31 Jul 2007 22:17:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4151939</guid><dc:creator>anthonw</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/4151939.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=4151939</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=4151939</wfw:comment><description>Although the mailbox was moved to the target Microsoft Exchange server, an error occurred while the policies were being applied.  Proxy address policies, Unified Messaging settings, managed content settings, and Exchange ActiveSync settings may not be set correctly.  There is no primary SMTP address....(&lt;a href="http://blogs.msdn.com/anthonw/archive/2007/07/31/there-is-no-primary-smtp-address.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=4151939" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/anthonw/archive/tags/Exchange/default.aspx">Exchange</category></item><item><title>Having ZUNE Shuffle Issues?</title><link>http://blogs.msdn.com/anthonw/archive/2007/07/13/having-zune-shuffle-issues.aspx</link><pubDate>Fri, 13 Jul 2007 18:33:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3849733</guid><dc:creator>anthonw</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/3849733.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=3849733</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=3849733</wfw:comment><description>Okay, so this has nothing to do with federated infrastructure, except that many of my customers have or are considering Zunes. I have one and I have what I believe to be a common problem. My music collection contains some content that may be inappropriate...(&lt;a href="http://blogs.msdn.com/anthonw/archive/2007/07/13/having-zune-shuffle-issues.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=3849733" width="1" height="1"&gt;</description></item><item><title>Moving Mailboxes Cross Organizations in Exchange 2007</title><link>http://blogs.msdn.com/anthonw/archive/2007/07/05/moving-mailboxes-cross-organizations-in-exchange-2007.aspx</link><pubDate>Thu, 05 Jul 2007 19:45:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3709201</guid><dc:creator>anthonw</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/3709201.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=3709201</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=3709201</wfw:comment><description>I've seen a number of posts on other blogs talking about the new features of Exchange 2007 and the ability now to move mailboxes across organizations. I currently have a customer engaged in a major consolidation of multiple Exchange 2003 organizations...(&lt;a href="http://blogs.msdn.com/anthonw/archive/2007/07/05/moving-mailboxes-cross-organizations-in-exchange-2007.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=3709201" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/anthonw/archive/tags/Exchange/default.aspx">Exchange</category><category domain="http://blogs.msdn.com/anthonw/archive/tags/Code/default.aspx">Code</category><category domain="http://blogs.msdn.com/anthonw/archive/tags/Management+Tools/default.aspx">Management Tools</category></item><item><title>Improving the Exchange Availability Report</title><link>http://blogs.msdn.com/anthonw/archive/2006/09/29/777391.aspx</link><pubDate>Sat, 30 Sep 2006 00:01:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:777391</guid><dc:creator>anthonw</dc:creator><slash:comments>3</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/777391.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=777391</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=777391</wfw:comment><description>So, maybe it's not a total improvement, but I thought it would be worth sharing. The following SQL commands are designed to create a new, indexed table, and populate that database with Exchange Availability reporting data from the MOM System Center Reporting...(&lt;a href="http://blogs.msdn.com/anthonw/archive/2006/09/29/777391.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=777391" width="1" height="1"&gt;</description></item><item><title>What exactly is "No Measurement %" in the MOM 2005 Exchange Availability Report?</title><link>http://blogs.msdn.com/anthonw/archive/2006/09/26/773001.aspx</link><pubDate>Wed, 27 Sep 2006 03:01:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:773001</guid><dc:creator>anthonw</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/anthonw/comments/773001.aspx</comments><wfw:commentRss>http://blogs.msdn.com/anthonw/commentrss.aspx?PostID=773001</wfw:commentRss><wfw:comment>http://blogs.msdn.com/anthonw/rsscomments.aspx?PostID=773001</wfw:comment><description>If you've used the MOM 2005 Exchange availability report, you probably accepted the default parameters (which are exactly one week from the current time) and got a report that looked something like the following: Server Database Availability % Success/...(&lt;a href="http://blogs.msdn.com/anthonw/archive/2006/09/26/773001.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=773001" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/anthonw/archive/tags/Management+Tools/default.aspx">Management Tools</category></item></channel></rss>