Microsoft has released an interesting whitepaper about large mailboxes on Exchange 2010.
Giving your users the ability to store more e-mail has many advantages. Large mailboxes keep e-mail on the Exchange Server instead of allowing it to be scattered in Outlook Data Files (.PST files). That helps reduce the risk of data loss, improve regulatory compliance, and increase productivity among both workers and IT staff. The main barrier to implementing large mailboxes is the perceived cost and complexity of storing large amounts of e-mail data. Microsoft® Exchange Server 2010 is specifically designed to overcome these barriers. This paper discusses how Exchange 2010 enables you to give users large mailboxes without breaking your budget.
Download and read the Whitepaper here.
The Exchange team has released an announcement of the improvements in Exchange 2010 SP1. The headlines of a few of the improvements are the following subjects:
- Archiving and Discovery Enhancements
- Outlook Web App
- Mobility (Exchange ActiveSync)
- Management UI
A full list of what’s coming in SP1 will be on TechNet soon.
One of the mostly awaited improvements is properly the possibility of changing location of the Personal Archive Mailbox to another database. This is great news, now the Personal Archive starts to get interesting.
Read more about the Personal Archive improvements in Henrik’s blog post.
Read the full blog post from the Exchange team about the SP1 improvements.
The Exchange team has released Rollup Update 3 for Exchange 2007 SP2.
More information about the release and download on msexchangeteam.com
The Exchange team has released RU2 for Exchange 2010.
Read more and download here.
Last week Ross Smith once again updated the Exchange Mailbox Server Role Storage Requirements Calculator.
Full post from Ross about the calculator can be read here.
Read more here and download here.
The Exchange team has updated the Exchange 2010 Mailbox Server Role requirements calculator. It’s now in the ver. 3.5.
Read Ross Smith’s latest post about the new version here.
Download the calculator here.
The Exchange CXP team has released Update Rollup 2 for Exchange Server 2007 Service Pack 2.
In addition to bug fixes reported by customers we have added new rules to the Exchange Best Practices Analyzer to check the health of your system. Starting this rollup, customers who wish to deploy the new BPA health rules to a server with no internet connection can do so by downloading the installing the update rollup on the server. Until Exchange Server 2007 Service Pack 2, updates to the BPA rules were available only via the web which meant customers wanting to deploy the new health check rules to servers not connected to the internet would have had to copy over the XML files manually. In Exchange 2007 SP2, we implemented a work item which allows us to ship updates to the BPA health check rules via the rollup and as well as via the traditional web based channel. More on this via a blog post in the near future.
KB972076 lists all the fixes included in this rollup, read more at the Exchange Teams blog and download the update here.
When using Security Configuration Wizard (SCW) on Windows Server 2008 SP2 together with Exchange 2007. You could run into an issue trying to register the Exchange 2007 profile for SCW.
Registering the SCW profile can be done using one of the following:
- - Register-ExchangeSCW.ps1 –register
- - scwcmd register /kbname:Ex2007KB /kbfile:”%programfiles%\Microsoft\Exchange Server\scripts\Exchange2007_WinSrv2008.xml”
The error is logged in the MSSCW log file and states something like:
0×80070057
The specified OS version does not match with the version that is defined in the KBRegistration.xml file.
The parameter is incorrect.
The reason for the above error is that the OS level is hardcoded into the SCW XML files used to register the SCW profile.
To correct the error above, open the SCW XML file, it should look like:
<SCWKBRegistrationInfo OSMajorVersion=”6″ OSMinorVersion=”0″ ServicePackMajorVersion=”1″ ServicePackMinorVersion=”0″>
Change the ServicePackMajorVersion to 2, so it looks like:
<SCWKBRegistrationInfo OSMajorVersion=”6″ OSMinorVersion=”0″ ServicePackMajorVersion=”2” ServicePackMinorVersion=”0″>
