| Welcome to the MSExchange.org newsletter by Henrik Walther, Exchange MVP, MCA: Messaging (Exchange Ranger) Apprentice, MCTS/MCITP Exchange 2007, MCSE 2003 Messaging/Security. Each month we will bring you interesting and helpful information on Exchange Server. We want to know what all *you* are interested in hearing about. Please send your suggestions for future newsletter content to: henrik@msexchange.org A Better Way to Migrate: The Case for Archiving Before Migrating to Exchange 2007 Migrating e-mail is difficult, risky and time consuming. The new white paper, "The Case for Archiving Before Migrating to Exchange 2007," explains the challenges of an Exchange migration and the importance of proper planning and execution. It discusses an alternative strategy: implementing an e-mail archiving system such as Quest Archive Manager before beginning your migration. Read the white paper and migrate to Exchange quickly, easily and with minimal user impact. 1. Exchange 2007 Edge Transport Server Gotcha of the Month Welcome to the February 2008 edition of the MSExchange.org newsletter! Last month I shared a CCR Cluster gotcha that I dealt with during an Exchange 2007 migration that I had recently performed for a relatively large Enterprise customer with an infrastructure spread out over multiple Active Directory sites (you can read the January version of the MSExchange.org newsletter here). This month I want to share another interesting gotcha with you. A gotcha I also had the pleasure of learning about the hard way during an Exchange 2007 migration that involved deployment of an Exchange 2007 Edge Transport Server in the perimeter network. For those who do not know, the Edge Transport server role is designed to provide improved antivirus and anti-spam protection for the Exchange organization. The Edge Transport server is typically deployed as a standalone server in the perimeter network, but can also be a member of a perimeter Active Directory domain (as long as it is not a member of the internal Active Directory domain things are fine). Since the Edge Transport server role is designed to have a minimal attack surface, it does not have direct access to the Active Directory domain on the internal network, and instead uses an Active Directory Application Mode (ADAM) directory service to store configuration and recipient information synchronized from one or more Hub Transport servers on the internal network via secure LDAP. In order for EdgeSync and mail flow to work properly between the servers, we must make sure the Edge Transport and Hub Transport server(s) can resolve each other. In addition, we must open port 25/SMTP and 50636 on the internal firewall. Note:
Port 50636 is the port assigned for secure LDAP traffic between the Edge Transport and Hub Transport servers. In most deployments this works just fine, but believe it or not I experienced a strange issue during the deployment of an Edge Transport server, where an ISA 2006 server was acting as the internal firewall. I was able to set up the Edge subscription and the EdgeSync process synchronized configuration and recipient settings to the ADAM store on the Edge Transport server properly. Outbound mail flow also worked as expected, but I could not get inbound mail flow to work. All inbound messages queued up on the Edge Transport server with a: 500 5.1.1 Unrecognized Command Error. The odd part was that I was able to telnet from the Edge Transport server to port 25 on the Hub Transport server and a test message sent via telnet arrived to the respective internal recipient. Hmm, time to start looking in the ISA Server log. I could not find any relevant issues here either. Alright then, could the SMTP filer be the sinner? I disabled the SMTP filter on the SMTP publishing rule, and then issued a retry on the inbound message queue on the Edge Transport server, and sure enough, the queue flushed. I researched the issue a little further and found out that SMTP verb commands issued by an Edge Transport server are not understood by an ISA 2006 server, and therefore are filtered. Okay so we can fix this issue by disabling the SMTP filter on the publishing rule, but what if this is not an option in your environment? Well, you can also resolve the issue by adding the required Exchange SMTP verb commands to the SMTP add-in filter on ISA Server 2006. For step by step instructions on how to do this see: How to Add SMTP Verb Commands to ISA Server 2006 For additional information about the SMTP verb issue, also see:
Messages Queue on an Edge Transport Server with 500 5.1.1 Unrecognized Command Error In the near future we will publish an article series covering the Edge Transport server role and all the features included in this server role. Cheers,
Henrik Walther Note:
Should you have any ideas for content in future editions of the MSExchange.org newsletter, you are more than welcome to shoot me an e-mail at Henrik@msexchange.org 2. Order Henrik Walther's Exchange Server 2007 book | Are you among the persons who like the articles I write for MSExchange.org? Then this book is definitely for you. It provides you with step by step instructions on how you get going with Exchange Server 2007, and importantly, how you properly manage it after deployment. The TOC for the book: Table of Contents - Introducing Exchange Server 2007
- Installing Exchange Server 2007
- Managing Recipients in Exchange Server 2007
- Managing the Mailbox Server
- Managing the Client Access Server
- Managing the Hub Transport Server
- Managing the Edge Transport Server
- High Availability for Exchange 2007 Mailbox Servers
- Disaster Recovery with Exchange Server 2007
- Transitioning from Exchange 2000 or 2003 to Exchange 2007
- Introduction to Exchange Server 2007 Unified Messaging
| 
To order the book today
click here
| A Better Way to Migrate: The Case for Archiving Before Migrating to Exchange 2007 Migrating e-mail is difficult, risky and time consuming. The new white paper, "The Case for Archiving Before Migrating to Exchange 2007," explains the challenges of an Exchange migration and the importance of proper planning and execution. It discusses an alternative strategy: implementing an e-mail archiving system such as Quest Archive Manager before beginning your migration. Read the white paper and migrate to Exchange quickly, easily and with minimal user impact. 3. MSExchange.org Learning Zone Articles of Interest We have a great group of articles in the Learning Zone that will help you get a handle on your most difficult configuration issues. Here are just a few of the newer and more interesting articles: 4. KB Articles of the Month Here are some interesting and useful MSExchange related articles posted by Microsoft in the last month: Exchange Server 2007 Exchange Server 2003 A Better Way to Migrate: The Case for Archiving Before Migrating to Exchange 2007 Migrating e-mail is difficult, risky and time consuming. The new white paper, "The Case for Archiving Before Migrating to Exchange 2007," explains the challenges of an Exchange migration and the importance of proper planning and execution. It discusses an alternative strategy: implementing an e-mail archiving system such as Quest Archive Manager before beginning your migration. Read the white paper and migrate to Exchange quickly, easily and with minimal user impact. 5. MSExchange News of the Month 6. Ask Henrik Walther a question QUESTION: Henrik,
I was reading your article "Transitioning from Exchange 2000/2003 to Exchange server 2007 (part 1- part 3)" and thought a few questions. - In part 3 - moving RUS to Exchange 2007 server. You said MS will issue a hotfix to block moving RUS to Exchange 2007. I can't find any MS KB showing me how to remove it before uninstalling Exchange 2003. Do you have the link?
- In part 3 (last page) you mentioned "don't delete the respective legacy AG ..". Where can I find the user's legacyDN is still pointing to the AG? Does that mean that I have to keep the legacy AG forever? Do I need to clean the legacyDN so it won't point to the legacy AG?
- MCS tech worked with another admin installed Exchange 2007 into our Exchange 2003 (sp2) Org, using ISA, Edge, CAS+HT and MBX. What I found that there is no public folder DB on the mailbox server. All our clients are Outlook 2003. What do I lose without PF on Exchange 2007 side? I used be able to view my manager's calendar now can't. We are both on Exchange 2007 server. But I was told by MCS that it's a new permission restriction on Exchange 2007 store not related to missing PF? If I created PF again, will Free+Busy and OAB system folders get replicated automatically or I have to set it up manually?
- Moving mailboxes. With GUI it will move 4 mbx at one time. What's the max. mailboxes I move on a single Exchange 2007 server? In Exchange 2003 I think I can run 4 GUI and each will move 4 so total will be 16 max. With the cmdlet is there a max limit too?
Thanks,
David ANSWER: Hi David,
- I don't think this hot fix ever was released. So you can just use the method I recommend or delete RUS via ADSIEdit as mentioned here:
- Yes it's important you don't touch the legacy admin group. From the same link as I referred to in my answer to your first question above:
The LegacyExchangeDN property on a mailbox from an Exchange 2003 or Exchange 2000 administrative group still references the Exchange 2003 or Exchange 2000 administrative group even after you move the mailbox to a server in the Exchange 2007 administrative group. Office Outlook 2003 and earlier versions use the LegacyExchangeDN property to get free/busy information. If the administrative group that the LegacyExchangeDN property references no longer exists, Outlook will not be able to find free/busy information. In addition, all versions of Outlook use the LegacyExchangeDN property when a user delegates access to folders by using the Outlook client. If you delete the legacy administrative group that the LegacyExchangeDN property references, Outlook will not be able to find the assigned delegated user.
- It's up to you whether you want to have a PF database on the E2K7 server, but it's a good idea to have this in place the day you decommission your E2K3 server (if you do so before upgrading your clients to Outlook 2007 which as you probably know uses Autodiscover and not System folders). See here to manage Mailbox permissions via the Exchange Management Shell
- Yes you have multiple Move Mailboxes instances running at the same time, but you could also use the Move-Mailbox cmdlet and then specify a -maxthreads of 16 or whatever you prefer.
Hope this helps!
Henrik A Better Way to Migrate: The Case for Archiving Before Migrating to Exchange 2007 Migrating e-mail is difficult, risky and time consuming. The new white paper, "The Case for Archiving Before Migrating to Exchange 2007," explains the challenges of an Exchange migration and the importance of proper planning and execution. It discusses an alternative strategy: implementing an e-mail archiving system such as Quest Archive Manager before beginning your migration. Read the white paper and migrate to Exchange quickly, easily and with minimal user impact. | 
No comments:
Post a Comment