More in Exchange Server 2010

  • Jul 8, 2013

    Rapid evolution in Exchange compliance features causes some problems 4

    Microsoft has poured huge amounts of engineering effort into Exchange to produce the array of compliance features available in Exchange 2013. As is often the case with software, backward compatibility poses a problem in some areas. It's worth keeping an eye on the detail....More
  • Jun 10, 2013

    Fantastic session line-up selected for Exchange Connections

    Receiving 85 session proposals for Exchange Connections was a simply great outcome. The variety available created terrific pressure for selection as only 16 agenda were slots assigned originally for Exchange-related content....More
  • Jun 4, 2013

    Comparing results from different calculators is a fool's game (and Exchange 2010 SP3 RU1) 2

      I guess that it was inevitable that people would rush to use the Exchange 2013 server role requirements calculator and compare its output to the results generated by the Exchange 2010 mailbox server calculator. And of course, the results do not match. Not by a long way, because Exchange 2013 uses a different architecture than its predecessor and because server hardware has different capabilities than it had when Exchange 2010 was designed....More
  • May 2, 2013

    Exchange Connections - Calling all speakers

    Las Vegas in October - conference time again. But with a difference - Exchange Connections is back and it's going to be packed with insightful and practical information about Exchange and its surrounding ecosystem. Opportunities exist for speakers and you can submit session ideas until May 14. It should be great fun!...More
  • Apr 25, 2013

    MRMAPI, the Little Brother of MFCMAPI 2

    You've probably heard of MFCMAPI, a very useful program in the hands of any administrator who wants to learn just what's stored in an Exchange mailbox. MRMAPI is less well known, but it is also pretty useful for other reasons....More
  • technology collage for Microsoft Exchange Server migration
    Apr 23, 2013

    Binary Tree Acquires Server Migration Vendor ManageRED

    Exchange Server migration experts Binary Tree announced the acquisition of ManageRED Software, a company with a range of Active Directory (AD) and Microsoft server migration products....More
  • Apr 18, 2013

    Microsoft and Google War Over First Ajax Webmail

    Google claims they were the first webmail client based on Ajax but Microsoft's Outlook Web Access was Ajax-based in Exchange 2003. But the competition has moved the state of email far in a short time....More
  • Apr 11, 2013

    Individual fix for Exchange soft delete problem proves worth of support contracts 4

    Microsoft now has individual fixes for the soft-delete bug that affects Outlook clients configured in online mode for certain items that contain voicemail or PDF attachments. The fixes are only available to customers who have support contracts, proving once again that support contracts are a necessity for most companies that use Exchange....More
  • Exchange Server email management with PST files: yield sign
    Mar 28, 2013

    What's to Be Done with PSTs: Capture, Migrate, Eliminate?

    Microsoft's free PST Capture tool has been updated to work with Exchange Server 2013, but a tool such as Sherpa Software's Mail Attender provides more features for PST management....More
  • Mar 26, 2013

    Preserving mailboxes when employees leave

    If employees leave your company, you should think about preserving the content held in their mailboxes. You might just be glad that you do this if your company becomes liable to legal discovery. Then again, it can be argued that deleting mailboxes immediately solves the problem... until you're forced to restore the mailboxes from backup by the legal department. So here's a discussion about some practical steps to help with the problem of what to do with those pesky mailboxes....More
  • Mar 19, 2013

    Exchange 2010 Discovery Searches: What about users who leave?

    As you probably know, Microsoft has made quite a big fuss about the compliance features that they have incorporated into Exchange 2010 and extended further in Exchange 2013. It’s fair to acknowledge the progress that has been made in this area through the addition of features such as archive mailboxes, retention policies and tags, litigation and retention hold, enhancements to the “dumpster”, and the provision of a discovery search capability....More
  • Feb 19, 2013

    Exchange 2010 Datacenter switchover tool

    I must have been asleep when Microsoft published the Exchange 2010 datacenter switchover tool last October as I have utterly failed to acknowledge its existence until now. Some have noted that this is not really a tool at all, largely because it has not been created by coding the steps necessary to switchover a Database Availability Group (DAG) across datacenters in some form of computer code and presenting the resulting knowledge as an executable program. The assertion is true, but only if you regard a tool as something that absolutely has to be an executable. I guess this is true, if you assume that tool in this context means a computer utility, but it’s not in the wider context if you regard a tool as something that helps you to do a job more effectively, which is what this tool does. Of course, you might regard PowerPoint as a language. Certainly, there are people who can make PowerPoint do things that I would never dream of, such as the PowerPoint MVPs. So perhaps the datacenter switchover tool, which is provided in the form of a PowerPoint presentation, really is a tool after all. Now that we have battered the semantics of the situation to death, the tool is the result of some pretty impressive work by Tim McMichael, someone who is well known as a true expert in the arcane art of the lesser-known corners of DAGs. Tim has presented at many conferences and his sessions are always content-rich and full of practical knowledge......More
  • Feb 12, 2013

    Exchange 2010 SP3 is released - almost ready for Exchange 2013 deployments

    At last, the chocks have been released and the runway is almost clear for Exchange 2013 deployment. The missing places that have stopped existing customers introducing Exchange 2013 into their environment have been provided with the release of: Exchange 2010 SP3 Exchange 2007 SP3 RU10...More
  • Feb 7, 2013

    Touchdown—a solution for BYOD email?

    Loss of control over the software run to connect to corporate services is just one of the issues for companies that’s exposed by the BYOD craze. Given the range of devices that people use, it’s practically impossible for administrators and help desk personnel to know the details of the applications that connect....More
  • Feb 5, 2013

    Performance Monitor and Exchange DAG replication queues

    When I wrote about how the Exchange 2013 Administration Center (EAC) simplifies the management of Database Availability Groups (DAGs), Scott Schnoll, that well-known and much-travelled evangelist of Exchange high availability, pointed out quite correctly that none of Exchange’s management tools include any business logic whatsoever as all depend on calling whatever Exchange Management Shell (EMS) cmdlet is appropriate to manipulate information an object. This has been the case since Exchange 2007 embraced PowerShell and launched Exchange on the path that it has since followed. Not being picky at all, my sources within the EAC team tell me that they run EMS in a slightly different manner than an administrator does through an EMS window. It’s all to do with the way that browsers send commands to servers. At least, that’s what I remember from a lunch-time conversation at MEC in Orlando. Or maybe I was too concerned with eating to remember accurately. In any case, Scott’s point is well made....More
  • Jan 8, 2013

    Exchange 2010 SP1 reaches end of support

    It might have escaped your attention or maybe you aren’t concerned, but Microsoft’s formal support for Exchange 2010 SP1 expires today. Ongoing support activities were proceeding until quite recently, with Exchange 2010 SP1 RU8 released on December 11, 2012. But now it’s time to move on and get servers upgraded to Exchange 2010 SP2, preferably applying the latest roll-up update (RU5) for that service pack, making sure that you test everything thoroughly first. Exchange 2010 SP1 completed the development process for Exchange 2010. I know that’s not the official story because Microsoft always holds that development is complete when they ship the RTM version for a product, but in reality this isn’t so as there’s invariably a rush to get software out the door to meet arbitrary dates and usually there are some gaps remaining that have to be close post-RTM, usually delivered in the first service pack. Exchange 2010 SP1 appeared with a completely rewritten version of Outlook Web App, for instance, and it included lots of new UI in the Exchange Management Console to help administrators cope with retention policies and tags. It also introduced some very interesting technology in the Store, including block-mode replication. Of course, we’re still waiting for news about Exchange 2010 SP3, a release announced by Microsoft in October 2012 with a delivery date in “early 2013”. This is an important release because SP3 is needed to allow Exchange 2010 to co-exist alongside the brand-new Exchange 2013. The word is that work is progressing and that SP3 will appear soon. I hope so as its lack is preventing any sort of activity around Exchange 2013. Another item that we’re still awaiting news of is what Microsoft intends to do to address the issue that they caused when the decision was made to move Exchange 2013 into prime position for TechNet searches. I don’t think anyone would quibble with the notion that it is a good idea to keep TechNet refreshed in such a way that the lates...More
  • Jan 3, 2013

    Downgrading an Exchange 2010 Server 2

    Microsoft doesn't support the use of license keys to downgrade an Exchange server from enterprise to standard edition--but it seems like it should be possible....More
  • Jan 1, 2013

    Exchange searches limited to specific item types

    It’s always good to get questions and comments after an article appears, if only to prove that someone’s reading the material out there on the InterWeb. I was happy to receive some comments after my “Search and Destroy” article that covers the basics of Exchange 2010’s ability to search for and (optionally) remove messages in user mailboxes. Hopefully you won’t have to remove messages too often because users don’t typically respond too well to this kind of administrative intervention. That is, of course, if they notice that anything has been deleted! But if you do, it’s good to have solid tools to interrogate mailboxes for offending content and then purge it from the server. I presume the content to be offending in some respect as otherwise it would seem strange to search Exchange for it. One question that came up is about the AQS syntax used by Exchange to frame search queries. Microsoft documents the AQS syntax in MSDN and a couple of examples to help start the ball rolling can be found in the help for the Search-Mailbox cmdlet. The examples are intended to get your creative juices going and it will probably take some trial and error before you settle on the best query for your purposes. But sometimes you run into a limitation that isn’t covered too well in product documentation. Reading about Search-Mailbox, we find that “The SearchQuery parameter specifies a search string or a query formatted using Advanced Query Syntax (AQS).”...More
  • Dec 27, 2012

    How to Fix an Unbalanced DAG

    It is an undeniable fact of system administration that programs and data operate well, most neatly, just after they have been first deployed. Over time components have a nasty habit of degrading, of transforming themselves into non-optimum configurations, or simply not working as well as they might. And so it is with Database Availability Groups (DAGs), which brings us nicely to RedistributeActiveDatabases.ps1, a script that’s provided for your use with the Exchange 2010 kit. DAGs have proven to be the big success story for Exchange 2010 and are a major motivating factor in the decision that many companies have made to upgrade from previous releases. For the first time, Exchange includes native high availability features that scale past two nodes, a limitation that’s been in place ever since the introduction of the original “Wolfpack” clusters on Windows NT 4.0 with Exchange 5.5 in late 1997. DAGs scale to sixteen nodes, a limitation imposed by the underlying Windows Failover Clustering technology, and can accommodate hundreds of active databases if you run the enterprise edition of Exchange 2010. The standard edition supports DAGs too, but a server can only mount up to five databases at a time rather than the hundred supported by the enterprise edition. So good so far. To get back to the point in hand, DAGs operate spiffingly well when they are first deployed and the active databases all run on their preferred server....More
Upcoming Conferences

Register now to get the best rates available!

Windows Forums

The Windows IT Pro forums are moving to! Get answers to questions, share tips, and engage with the IT professional community.

Sponsored Introduction Continue on to (or wait seconds) ×