<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><title type="html">Federated Infrastructure</title><subtitle type="html">A discussion on how politics influence technical design, how scripts and code can overcome politics, and random experiences or thoughts from the Microsoft field.  </subtitle><id>http://blogs.msdn.com/anthonw/atom.xml</id><link rel="alternate" type="text/html" href="http://blogs.msdn.com/anthonw/default.aspx" /><link rel="self" type="application/atom+xml" href="http://blogs.msdn.com/anthonw/atom.xml" /><generator uri="http://communityserver.org" version="2.1.61025.2">Community Server</generator><updated>2006-09-26T20:01:00Z</updated><entry><title>Where can I get Single Instance Store (SIS) for Windows File Servers?</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/anthonw/archive/2009/01/23/where-can-i-get-single-instance-store-sis-for-windows-file-servers.aspx" /><id>http://blogs.msdn.com/anthonw/archive/2009/01/23/where-can-i-get-single-instance-store-sis-for-windows-file-servers.aspx</id><published>2009-01-23T23:24:00Z</published><updated>2009-01-23T23:24:00Z</updated><content type="html">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 multiple copies of the same document and consolidates them to a single document with mulitple pointers. However, this feature is NOT available on any other edition of Windows Server. Of course, this isn't well documented, as I tried to find out...(&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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author></entry><entry><title>When Legacies Are Baggage (Resolving the #550 5.1.1 RESOLVER.ADR.ExRecipNotFound error during Migration)</title><link rel="alternate" type="text/html" 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" /><id>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</id><published>2008-11-08T03:21:00Z</published><updated>2008-11-08T03:21:00Z</updated><content type="html">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 historical information had come over. The user had three different SMTP email addresses, but the primary SMTP address, username@guessme.edu, kept returning mail as undeliverable. The error information looks as follows. Delivery has failed to these...(&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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author></entry><entry><title>Windows Server 2008, IIS 7.0, Exchange 2007 and the Offline Address Book</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/anthonw/archive/2008/10/24/windows-server-2008-iis-7-0-exchange-2007-and-the-offline-address-book.aspx" /><id>http://blogs.msdn.com/anthonw/archive/2008/10/24/windows-server-2008-iis-7-0-exchange-2007-and-the-offline-address-book.aspx</id><published>2008-10-24T23:20:00Z</published><updated>2008-10-24T23:20:00Z</updated><content type="html">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 http://lugies15.blogspot.com/2008/09/offline-address-book-connecting-to.html and noticed that the permission change recommended here fixed the problem. But we couldn't figure out why setting an open read permission to everyone on the c:\program files\microsoft\exchange\client...(&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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author></entry><entry><title>Putting the F in FERPA (Building Distribution Groups for Class Schedules in Exchange)</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/anthonw/archive/2008/08/08/putting-the-f-in-ferpa-building-distribution-groups-for-class-schedules-in-exchange.aspx" /><id>http://blogs.msdn.com/anthonw/archive/2008/08/08/putting-the-f-in-ferpa-building-distribution-groups-for-class-schedules-in-exchange.aspx</id><published>2008-08-09T00:35:00Z</published><updated>2008-08-09T00:35:00Z</updated><content type="html">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 list has a members property and each user has a memberOf property, both of which are multi-valued attributes. This is where the problems begin. The Family Educational Rights and Privacy Act (FERPA) allow directory information on students...(&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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author></entry><entry><title>NoMAS and Other Solutions to 9548 and 9551 Events (Exchange Server 2003)</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/anthonw/archive/2008/07/17/nomas-and-other-solutions-to-9548-and-9551-events-exchange-server-2003.aspx" /><id>http://blogs.msdn.com/anthonw/archive/2008/07/17/nomas-and-other-solutions-to-9548-and-9551-events-exchange-server-2003.aspx</id><published>2008-07-17T21:59:00Z</published><updated>2008-07-17T21:59:00Z</updated><content type="html">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 to many folks out there. After installing Exchange 2003 in your environment, you may see the following types of events in the event log of your Exchange Server 2003 machine. Event Type: Warning Event Source: MSExchangeIS Event Category: General Event...(&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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author></entry><entry><title>Installing Exchange 2007 SP1 onto Windows Server 2008 with a WS2008 Active Directory</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/anthonw/archive/2008/01/29/installing-exchange-2007-sp1-into-windows-server-2008-active-directory.aspx" /><id>http://blogs.msdn.com/anthonw/archive/2008/01/29/installing-exchange-2007-sp1-into-windows-server-2008-active-directory.aspx</id><published>2008-01-29T21:32:00Z</published><updated>2008-01-29T21:32:00Z</updated><content type="html">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 bits of Longhorn with 2008 Forest Functional Level during the DCPromo process. The lab consists of two servers: 1 DC and 1 Exchange Server. Install PowerShell Feature on both DC and Exchange Servers using the Server Manager - "Add Features" tool. ForestPrep...(&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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author></entry><entry><title>The procedure entry point_except_handler4_common could not be located in the dynamic link library msvcrt.dll</title><link rel="alternate" type="text/html" 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" /><id>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</id><published>2007-12-06T23:48:00Z</published><updated>2007-12-06T23:48:00Z</updated><content type="html">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 the hardware wizard to recognize the device and pull the drivers from the CD that came with the card. Some way into the installation, I blue-screened. From that point forward, I could not keep the system up, so I rebooted to safe mode, pull the...(&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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author></entry><entry><title>Pool Nonpaged memory Leaks on Exchange 2003</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/anthonw/archive/2007/11/27/pool-nonpaged-memory-leaks-on-exchange-2003.aspx" /><id>http://blogs.msdn.com/anthonw/archive/2007/11/27/pool-nonpaged-memory-leaks-on-exchange-2003.aspx</id><published>2007-11-28T03:10:00Z</published><updated>2007-11-28T03:10:00Z</updated><content type="html">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 remaining on Windows XP, although some Vista clients were thrown in the mix. In both situations, as the number of Outlook 2007 clients increased against a 2003 backend, the customers have noticed Pool Nonpaged Memory problems. We've considered and...(&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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author></entry><entry><title>Using Powershell to Correct  9325 Events in Exchange 2007</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/anthonw/archive/2007/08/23/using-powershell-to-correct-9325-events-in-exchange-2007.aspx" /><id>http://blogs.msdn.com/anthonw/archive/2007/08/23/using-powershell-to-correct-9325-events-in-exchange-2007.aspx</id><published>2007-08-23T21:58:00Z</published><updated>2007-08-23T21:58:00Z</updated><content type="html">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 to see these events). Event Type: Error Event Source: MSExchangeSA Event Category: OAL Generator Event ID: 9325 Date: 8/23/2007 Time: 9:25:43 AM User: N/A Computer: {Exchange Server where OAB is Generated} Description: OALGen will skip user entry...(&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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author><category term="Exchange" scheme="http://blogs.msdn.com/anthonw/archive/tags/Exchange/default.aspx" /><category term="Code" scheme="http://blogs.msdn.com/anthonw/archive/tags/Code/default.aspx" /><category term="Management Tools" scheme="http://blogs.msdn.com/anthonw/archive/tags/Management+Tools/default.aspx" /></entry><entry><title>Mailbox Cleanup After Cross Organizational Moves</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/anthonw/archive/2007/08/08/mailbox-cleanup-after-cross-organizational-moves.aspx" /><id>http://blogs.msdn.com/anthonw/archive/2007/08/08/mailbox-cleanup-after-cross-organizational-moves.aspx</id><published>2007-08-08T21:51:00Z</published><updated>2007-08-08T21:51:00Z</updated><content type="html">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 at once. The input file must be tab-separated and contain the distinguished name in the first column and the smtp email address in the second. No headers are necessary on the input file. '*******************************************************************************...(&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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author><category term="Exchange" scheme="http://blogs.msdn.com/anthonw/archive/tags/Exchange/default.aspx" /><category term="Code" scheme="http://blogs.msdn.com/anthonw/archive/tags/Code/default.aspx" /></entry><entry><title>There is no primary SMTP address</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/anthonw/archive/2007/07/31/there-is-no-primary-smtp-address.aspx" /><id>http://blogs.msdn.com/anthonw/archive/2007/07/31/there-is-no-primary-smtp-address.aspx</id><published>2007-07-31T22:17:00Z</published><updated>2007-07-31T22:17:00Z</updated><content type="html">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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author><category term="Exchange" scheme="http://blogs.msdn.com/anthonw/archive/tags/Exchange/default.aspx" /></entry><entry><title>Having ZUNE Shuffle Issues?</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/anthonw/archive/2007/07/13/having-zune-shuffle-issues.aspx" /><id>http://blogs.msdn.com/anthonw/archive/2007/07/13/having-zune-shuffle-issues.aspx</id><published>2007-07-13T18:33:00Z</published><updated>2007-07-13T18:33:00Z</updated><content type="html">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 for children under the age of 30. I also like to shuffle the music around. It seems the easiest way to accomplish this is to create a playlist of all age-appropriate music and then shuffle that playlist. So I create a playlist with probably 2,400...(&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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author></entry><entry><title>Moving Mailboxes Cross Organizations in Exchange 2007</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/anthonw/archive/2007/07/05/moving-mailboxes-cross-organizations-in-exchange-2007.aspx" /><id>http://blogs.msdn.com/anthonw/archive/2007/07/05/moving-mailboxes-cross-organizations-in-exchange-2007.aspx</id><published>2007-07-05T19:45:00Z</published><updated>2007-07-05T19:45:00Z</updated><content type="html">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 into a single forest, single Exchange 2007 organization. The design for this customer calls for the following: Users will continue to log onto and operate from their current domains for their primary job functions. Users will all have new accounts in...(&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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author><category term="Exchange" scheme="http://blogs.msdn.com/anthonw/archive/tags/Exchange/default.aspx" /><category term="Code" scheme="http://blogs.msdn.com/anthonw/archive/tags/Code/default.aspx" /><category term="Management Tools" scheme="http://blogs.msdn.com/anthonw/archive/tags/Management+Tools/default.aspx" /></entry><entry><title>Improving the Exchange Availability Report</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/anthonw/archive/2006/09/29/777391.aspx" /><id>http://blogs.msdn.com/anthonw/archive/2006/09/29/777391.aspx</id><published>2006-09-30T00:01:00Z</published><updated>2006-09-30T00:01:00Z</updated><content type="html">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 database in SQL Server (see previous post on the current availability report). Unlike the SQL Reporting Services, this is a Query Analyzer solution. You'll need to wrap the appropriate presentation layer around it. The final step in the code...(&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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author></entry><entry><title>What exactly is "No Measurement %" in the MOM 2005 Exchange Availability Report?</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/anthonw/archive/2006/09/26/773001.aspx" /><id>http://blogs.msdn.com/anthonw/archive/2006/09/26/773001.aspx</id><published>2006-09-27T03:01:00Z</published><updated>2006-09-27T03:01:00Z</updated><content type="html">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/ Expected Exchange Unavailable % DC unavailable for authentication % Other Failures % No Measurements % DOMAIN\SERVER Mailbox Store 89.88 1812/2016 0.00 0.10 0.00 10.02 You're likely to be asking the question, "Why do I have no measurements nearly 10%...(&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;</content><author><name>anthonw</name><uri>http://blogs.msdn.com/members/anthonw.aspx</uri></author><category term="Management Tools" scheme="http://blogs.msdn.com/anthonw/archive/tags/Management+Tools/default.aspx" /></entry></feed>