MSExchange.org Monthly Newsletter of April 2007 Sponsored by: EqualLogicWelcome to the MSExchange.org newsletter by Henrik Walther, Exchange MVP, Exchange 2007 MCTS, MCSE 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 1. Outlook 2007 Performance Issues Finally ResolvedHello everyone and welcome to the April 2007 edition of the MSExchange.org newsletter! I hope all of you had a great Easter In the previous newsletter I quickly went through some of the new features and improvements that we can expect to see in Exchange Server 2007 Service Pack 1. Guess what? The first beta version of Exchange 2007 SP1 was released to MSDN and TechNet Plus subscribers last week! Bear in mind though that only the x64 version can be downloaded from the MSDN site, but both the x86 and x64 versions can be downloaded from the TechNet site. I've already tested many of the features in the service pack intensively, and by the time you read this newsletter, my first Exchange 2007 SP1 article, which uncovers the new Public Folder Management console, should already have been published here on MSExchange.org. The download file for the x64 version is a whopping 734MB! What? I hear some of you scream. Yes that's correct, but the reason behind this craziness is that the SP1 updates have been rolled directly into the bits of the original Exchange 2007 RTM version, so you can both upgrade an existing Exchange 2007 RTM installation or perform a clean installation of Exchange 2007 SP1 (that is install Exchange 2007 SP1 in the same manner you would perform an installation of Exchange 2007 RTM). For more information about Exchange 2007 SP1 beta and how you install it, see the Exchange 2007 SP1 Release Notes. Other noticeable things that have happened in the Exchange 2007 update arena lately is that a hotfix for Outlook 2007, which resolved the performance issue you experienced with large PST or OST files, has finally been RTWed. This hotfix can be downloaded here. Additionally, the first update rollup for Exchange 2007 has RTWed. This update can be downloaded here. The issues fixed are listed in this MS KB article. That's all for this time! Should you have any ideas for content in future editions of the MSExchange.org newsletter, you're more than welcome to shoot me an e-mail at Henrik@msexchange.org. 2. Order Henrik Walther's Exchange Server 2007 book
3. MSExchange.org Learning Zone Articles of InterestWe 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 MonthHere are some interesting and useful MSExchange related articles posted by Microsoft in the last month:
5. Tip of the MonthYou want to be an Exchange 2007 Management Shell guru but are primarily a GUI admin, and therefore have a steep learning curve in front of you? Fear not. This is where Quest's PowerGUI tool comes into the picture. PowerGUI is a freeware tool with an extensible graphical administrative console for managing systems based on Windows PowerShell. These include Windows OS (XP, 2003, Vista), Exchange 2007, Operations Manager 2007 and other new systems from Microsoft. The tool allows you to use the rich capabilities of Windows PowerShell in a familiar and intuitive GUI console.
You can read more about PowerGUI as well as download the tool and available snap-ins here. There's even a demo which shows you just how efficient this tool is. Check out the demo here. 6. MSExchange Links of the Month
7. Ask Henrik Walther a questionQUESTION: I'm of the understanding that since an Edge Transport server (which I know should be deployed in the perimeter network) uses a local ADAM store to replicate configuration and recipient data with the Active Directory domain on the internal network, using the EdgeSync service, this also means that the Edge Transport server cannot be a domain-member server, but must be a stand-alone box? ANSWER: Although it's generally recommended to deploy an Edge Transport server as a stand-alone box, this isn't correct. Let's imagine we have a perimeter network consisting of 10 Edge Transport servers. Because these 10 Edge Transport servers in most situations should be configured identically, it would make sense to add all of them to an Active Directory forest dedicated to the perimeter network. This way it's much easier to apply the same security settings, etc, to the servers. Actually Microsoft's own IT group, which currently has 6 Edge Transport servers deployed in the perimeter network, uses this approach. TechGenix Sites
|