February 22nd, 2012 by admin
Is your Exchange 2007 log disk full? Exchange log files aren’t supposed to take up too much space, and when admins were building Exchange 2007 servers, disks were measured in Gigabytes, not Terabytes. Many admins just let the logs go to the default location, which is the same location as the databases, and the binaries, and the rest of the operating system. Others created separate volumes for log files since that’s what best practices suggest, but might not have allocated as much space as they find themselves needing. When your Exchange log disk is full, there’s a fairly easy way to address this. In this post, we’ll discuss the Exchange log files and what to do when your Exchange 2007 log disk is full.
Read more…
February 16th, 2012 by admin
January 25th, 2012 by admin
With Exchange 2010 SP2 released, it’s past time for you to start putting all those old Exchange 2003 servers out to pasture, and any Exchange 2000 servers still hanging on out of their misery. The process to remove Exchange 2003 (or any other version) is not as simple as formatting the drive, but too often that is exactly what people do, and only then realize that to remove Exchange requires a process not too different from retiring a domain controller. In this post we will look at the process to remove Exchange Server from Active Directory and properly retire an old server, including the last legacy Exchange server your environment.
Read more…
December 12th, 2011 by admin
If you have worked with Exchange versions earlier than Exchange 2007, you probably long for the days of the ExMerge utility. That handy tool from the early resource kit days was a great way to import mail into Exchange, whether that was from mailbox to mailbox, or mailbox to PST. You might even remember the “fun” that was introduced in Exchange 2007 with the new PowerShell cmdlet Import-Mailbox, which sounded great when you read the name, but quickly proved to be a big step backwards in both functionality and usability, particularly since you needed a 32 bit client to work with the 64 bit Exchange server using Exchange commands! The improvements to this command in the RTM version of Exchange 2010 helped, but it still depended upon installing a licensed copy of Outlook to do everything you might have need. Fortunately Exchange 2010 Service Pack 1 deprecates the Import-Mailbox command in favor of the new cmdlet named New-MailboxImportRequest. This cmdlet is much more powerful than its predecessors, and can actually perform the work you need, enabling you to do things like import a mailbox into Exchange 2010 and import a PST into Exchange 2010. Using the built-in MAPI provider in Exchange 2010 also means you no longer need Outlook installed to manipulate mail data.
Read more…
November 28th, 2011 by admin
When you want to automate the clearing out of old email, or to ensure that certain messages are held for a period of time, you want to look at Exchange 2010 retention policies. They may also be referred to as Message Retention Manager (MRM Exchange 2010) 2.0 policies. Exchange 2010 can still use the MRM 1.0 policies from Exchange 2007, but they are subtly different and MRM 1.0 has been deprecated. In this article, we’ll simply refer to the new Retention Policies in Exchange 2010 as MRM Exchange 2010.
Read more…