msdigest.net

Microsoft has announced an update of Mailbox Server Role Storage Requirements Calculator for Exchange Server 2007.

The new version 16.0 is available for download here.

For more information about the enhancements in the new version, check the blogpost at msexchangeteam.com.

As issue that I’ve seen on Exchange 2007 after a migration from Exchange 2003, if you try to remove an accepted domain, but keep getting this error:

Cannot remove the domain ‘<domain name>’ because it is referenced by the proxy address template ‘smtp:@<domain name>’

First off go to the Exchange Management Console – Microsoft Exchange – Organisation configuration – Hub Transport – E-mail Address Policies.

Make sure that the domain is removed from any policies that you have set up, if the problem still persists go to a domain controller that has Windows Server Support Tools installed.

Run: adsiedit.msc from Start – Run

now browse to the following:

• Configuration
• CN=Configuration,DC=<Domain Name>,DC=<Root>
• CN=Services
• CN=Microsoft Exchange
• CN=<Exchange Organization>
• CN=Recipient Policies

Now right click CN=Default Policy and select properties.
Scroll down to the attribute named disabledGatewayProxy, select it and click edit. Remove the offending domain and click ok.
Give it a while for active directory to replicate across all domain controllers.

Go to the Exchange Management Console – Microsoft Exchange – Organisation configuration – Hub Transport – Accepted Domains

You should now be able to remove the offending domain successfully.

Looking for ADSIEdit on a Windows Server 2008 ?

In previous versions of Windows, you installed ADSIedit and the other Windows Support Tools from the server installation media.

The Windows Support Tools are now included in the RSAT (Remote Server Administration Tools) and can be installed as features in Windows Server 2008. 

ADSIedit is part of the Active Directory Domain Controller Tools feature, and can be added by following these steps:

1. In Server Manager, click on Features, then Add Features in the right pane
2. Expand Remote Server Administration Tools –> Role Administration Tools –> Active Directory Domain Services Tools
3. Put a check next to Active Directory Domain Controller Tools
4. Click Next, then Install

There’s an issue with the Exchange 2007 SP1 Rollup 4 patch and it’s confirmed by the Exchange Team on their blog.

Some of the known issues are with the Exchange Web Services (EWS) and failures regarding backup, returning errors in the eventlog regarding “Storage Group Consistency Check”. I’ve seen problems with the last issue.

The patch was originally released to the web, Microsoft Update and WSUS, but was pulled back again. But it’s not completely disappeared, on Sep. 15th I was downloading Rollup 2 and the patch I got was “Rollup 4” ?!

Microsoft recommends uninstalling Rollup 4 and re-installing Rollup 3.

Read more about the issues with Rollup 4 and the pulled back patch on msexchangeteam.com.

Direct download link to: 

• Update Rollup 3 for Exchange Server 2007 Service Pack 1 (KB949870)

The Microsoft IIS Team has released a bunch of new modules for IIS 7.0. Here’s an overview of the newly released modules:

• URLRewrite module
• Web Playlists
• FTP 7 Update (x86) Installation Package 
• FTP 7 Update (x64) Installation Package

• WebDAV Update (x86) Installation Package

• WebDAV Update (x64) Installation Package

Last week Nokia announced that it has expanded it’s support for Microsoft ActiveSync to all Nokia S60 3rd Edition devices, before it was only supported on the E models. This means that 43 different Nokia models now has support for ActiveSync, by installing the Nokia application “Mail for Exchange”.

Nokia plans to make the Mail for Exchange application available out-of-the-box for future releases of the Eseries and Nseries devices. When used with Exchange Server 2007, users will have access to a feature called Autodiscover which allows email to be setup by only requiring the email address, password, domain and username. Users will also be able to access their “Out of Office” messages from their Nokia phone using the application.

Read more from the Nokia Press release.

A new very interesting whitepaper has been release by Microsoft, about the Hosted Exchange Services solution deployed by Microsoft IT.

Microsoft IT deployed the cloud-based Exchange Hosted Services. This solution enables Microsoft IT to implement a messaging environment that processes all messages in a perimeter before unwanted messages reach the corporate firewalls and Exchange Server 2007 Edge Transport servers.

Read the whitepaper here.

Microsoft has announced some news about the upcoming release of Office Communication Server (OCS), the next release will be 64-bit only, the same move with saw with Exchange 2007.

The new version “Office Communication Server 2007 R2” has gone into beta.

Some of the focus for the new version has been:

Consolidate deployments

Based on customer feedback, Microsoft’s goal with the next release of OCS is to simplify deployments by reducing the number of servers needed for deployment. Customers are also telling us they are pushing the limits of existing hardware with their “mission critical” communications solutions.

The x64 Advantage

By leveraging x64 hardware, we are able to use inexpensive memory to support more concurrent processing of real-time media streams (audio, video, conferences) on smaller number of servers. With the change to x64, we can simplify and consolidate OCS deployments while supporting additional capabilities in the 64-bit server hardware is broadly available in the market today and is offered by major hardware vendors. The benefits of adopting 64 bit hardware are not limited to high scale OCS customers.

Guidance for OCS 2007 customers

The majority of server hardware being sold today is x64-based and many businesses are already enjoying its advantages and will not need to purchase new hardware to deploy the next release of OCS. Customers who are using 32-bit hardware systems to run OCS 2007 will need to upgrade to x64 systems to install and run the next release of OCS.

More info from the Communication Server Team blog.