What is the difference between Exchange 2010 SP1 in Small Business Server (SBS) 2011 and the “normal“ version

I often see or been asked the question what is the difference between the Exchange 2010 SP1 version available as part of Small Business Server (SBS) 2011 and the normal Exchange 2010 SP1 Standard.

The answer to the question is relatively easy, there isn’t.

Alright there is one little difference, if you have configured your Small Business Server with predefined wizards, there are automatically created 3 receive connectors (with 1 that accepts anonymous email from the outside) and 1 send connector. With a normal Exchange 2010 server installation you need to allow anonymous access and create a send connector manually.

Small Business Server 2011 includes the Exchange 2010 SP1 standard version without any limitation. And the Small Business Server Client Access License (CAL) covers the Exchange 2010 CAL.

If you would like to use the so called enterprise functionality like: Custom Retention Policies, Personal Archive, Voicemail, Information Protection and Compliance, Cross Mailbox Search, Legal Hold, Advance Mobile Policies, and Per User/Distribution List Journaling, you need to buy additional the Exchange 2010 Enterprise CAL.

Q. May I use the SBS 2011 CAL Suite to access the Enterprise functionality of Microsoft Exchange Server Enterprise server software?

 A. You may use SBS 2011 CAL Suite instead of Exchange Server 2010 Standard CALs to access base functionalities in instances of Exchange Server 2010 Standard or Enterprise in the Windows Small Business 2011 domain. In addition to SBS 2011 CAL Suite, you must acquire Exchange Server 2010 Enterprise CALs to access the following Exchange Server Enterprise functionalities in the Windows Small Business 2011 domain: Custom Retention Policies; Personal Archive; Voicemail; Information Protection and Compliance; Cross Mailbox Search; Legal Hold; Advance Mobile Policies, and Per User/Distribution List Journaling.

Taken from the Small Business Server 2011 Licensing FAQ.

Is there than nothing that cannot be done with Exchange Server in Small Business Server. Because Small Business Server is based on Windows server 2008 R2 standard, you cannot add the Exchange server to a Database Availability Group (DAG) this feature requires that your operating system is Windows Server 2008 (R2) Enterprise.

Posted in Blog, Exchange 2010, SBS 2011 at March 21st, 2011. 9 Comments.

Reply or forward via OWA gives “An unexpected error occurred and your request couldn’t be handled.”

When you try to reply or forward an e-mail via outlook web app (OWA) in exchange 2010 (in this case small business server 2011 exchange 2010 SP1) you get this error “An unexpected error occurred and your request couldn’t be handled.”

Url: https://remote.domain.com:443/owa/?ae=PreFormAction&a=Reply&t=IPM.Note&id=RgAAAACGrFxHc9ijR44U4ykKtU4LBwAeKagN6lmQSpA1lJbfKp7EAAAALJcxAAAeKagN6lmQSpA1lJbfKp7EAAAcI3ykAAAJ&pspid=_1300011623710_69458484
User host address: ::1
User: User A
EX Address: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=User A
SMTP Address: email@domain.com
OWA version:
Mailbox server: servername.domain.local

Exception type: System.ArgumentException
Exception message: imceaDomain must be a valid domain name.

Call stack

Microsoft.Exchange.Data.Storage.InboundConversionOptions.CheckImceaDomain(String imceaDomain)
Microsoft.Exchange.Data.Storage.InboundConversionOptions..ctor(String imceaDomain)
Microsoft.Exchange.Clients.Owa.Core.Utilities.CreateInboundConversionOptions(UserContext userContext)
Microsoft.Exchange.Clients.Owa.Core.ReplyForwardUtilities.CreateReplyOrReplyAllItem(BodyFormat bodyFormat, Item item, ReplyForwardFlags flags, Boolean replyAll, UserContext userContext, StoreObjectId parentFolderId)
Microsoft.Exchange.Clients.Owa.Core.ReplyForwardUtilities.CreateReplyItem(BodyFormat bodyFormat, Item item, ReplyForwardFlags flags, UserContext userContext, StoreObjectId parentFolderId)
Microsoft.Exchange.Clients.Owa.Premium.Controls.ItemReplyPreFormAction.Execute(OwaContext owaContext, ApplicationElement& applicationElement, String& type, String& state, String& action)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DoFinalDispatch(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.OwaRequestEventInspector.OnPostAuthorizeRequest(Object sender, EventArgs e)
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Solution: The problem was caused with one of the accepted domains, probably a space or other illegal character at the end of the domain name. After reading this article and set the domain name again with the following command in the exchange management shell:

Set-AcceptedDomain -Identity “accepted domain name” -Name “domain.com”

Did this for the last added domain name, because that was when the problem started. After completing this and restarted the server, the problem was solved.

Posted in Blog, Exchange 2010, SBS 2011 at March 13th, 2011. 14 Comments.

Remove http redirect for exchange virtual directories, public, exchange, exadmin and exchweb error

When accidentally set a http redirect for your OWA on your Exchange 2007 / 2010 and SBS 2008 via IIS7 and inherited to all virtual sub directories and then try to remove it for the virtual directories public, exchange, exadmin and exchweb you get an error like this one:

HTTP Redirect:
There was an error while performing this operation.
Filename: \\?BackOfficeStorage\yourdomain.extension\Public Folders\web.config
Error: Cannot write configuration file

Solution: This error is generated because these virtual directories don’t have a physical path.
You can solve this issue by opening a command prompt window. Change directory to Windows\system32\Inetsrv. Then run this command: appcmd set config “/” /section:httpredirect /enabled:false -commit:apphost. Change and for your specific environment.

More information about this topic and setting http redirect for owa can be found here: Simplify the Outlook Web App URL

Posted in Blog, Exchange 2007, Exchange 2010, SBS 2008 at December 21st, 2010. No Comments.

Howto: Configure Send and Receive limits for Exchange 2007 and 2010

There are 3 levels to control the message size limits for sending and receiving emails through a Exchange 2007 or 2010 mail server. Mail transport is controlled by the hub transport role so settings are made on the hub transport role.

Global settings: In Exchange Management Console, on Organization level, Hub Transport, Global Settings tab, select Transport settings properties you can set the Maximum receive size (KB) and Maximum send size (KB) at Transport limits for the whole Organization.

Connector settings, Receive connector: In Exchange Management Console, on Server Configuration level, Hub Transport, select the server and receive connector you want to set the Maximum message size (KB) for. You can set different values for all servers and receive connectors, so be sure you change the settings for the right Hub Transport server and the right receive connector.

Connector settings, Send connector: In Exchange Management Console, on Organization level, Hub Transport, Send Connector tab, you can set the Maximum message size (KB) for your Send connector(s). The setting is organization wide so for all servers if you have multiple send connectors you can make differences for the specific send connectors.

Last possibility is to set it on a User Mailbox: In Exchange Management Console, on Recipient Configuration level, Mailbox, select a User you want to set the limit for, properties, on the tab Mail Flow Settings select Message size restrictions

Posted in Exchange 2007, Exchange 2010, Howto at November 11th, 2010. 7 Comments.

MSExchangeTransport error, EventID: 12014 on a Exchange 2010 server

On the Exchange 2010 with the Hub Transport role installed you get several EventID 12014 errors on the MSExchangeTransport source.
“Microsoft Exchange could not find a certificate that contains the domain name mail.domain.com in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector “your send or receive Connector” with a FQDN parameter of mail.domain.com. If the connector’s FQDN is not specified, the computer’s FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.”

Solution: This error will occur when the FQDN you have entered in the send or receive connector doesn’t match with the FQDN names used at your exchange certificates.

You can change the FQDN at the connector to a name available on you certificate or install a new certificate with the right FQDN name.
It can also be that the SMTP service is not bind to the right certificate, in this case you can bind the SMTP service to the certificate using this FQDN.

Posted in Blog, Exchange 2010 at October 14th, 2010. 2 Comments.

Exchange 2010 SP1 mailbox move errors

When moving mailbox from a exchange 2003 server to a exchange 2010 server I ran into some warnings and errors.

When you try to move a mailbox via the wizard and choose “Skip the corrupted messsages.” and select to skip more then 50 messages you get the following error:
“Large BadItemLimit (50+) is specified. Please confirm your intention to accept a large amount of data loss by specifying AcceptLargeDataLoss.”

Solution: Use the Exchange Management Shell and use “New-MoveRequest -Identity “Mailboxname” -BadItemLimit 50+ -AcceptLargeDataLoss”
You can use other options if you like, but the -AcceptLargeDataLoss resolves this issue. More option on the New-MoveRequest cmdlet are available here.

Another error I ran into was, “Active Directory operation failed on Servername. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150A45, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], ADOperationException
+ FullyQualifiedErrorId : D6EC1D97,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest”

Solution: Go to the Active Directory user account witch you are trying to move. Select properties, security tab and then Advanced. Make sure the “Allow inheritable permissions from the parent to propagate to this object and all child objects. Include these with the entries explicity defined here.” is checked. If not enable it and then apply the setting.

Posted in Blog, Exchange 2010 at September 24th, 2010. No Comments.

Outlook: The following message had an error and synchronization of it was skipped (0x00050b)

After migrating out Exchange 2007 server to Exchange 2010 I got on several outlook clients Sync Issues. When you look at the log it says: The following message had an error and synchronization of it was skipped (0x00050b).

Solution: Just before the error it gives Synchronizing server changes in folder ‘foldername’. When looking in the folder via Outlook no strange items were seen in this folder. When logging on to OWA and browsing to the folder I found an item witch was corrupted. Looking back in outlook the item wasn’t visable so it looks like outlook removes corrupted mails. So You have to remove the corrupted item via OWA.

Posted in Blog, Exchange 2010 at September 20th, 2010. No Comments.

Exchange 2007 or 2010 migration fails with: Access control list (ACL) inheritance is blocked

The setup of Exchange 2007, Exchange 2010 or even SBS 2008 stops with the error “Access control list (ACL) inheritance is blocked”

Solution: Exchange setup requires that permission inheritance is enabled for the following objects:
Exchange Organization object, Exchange Administrative Group object, Exchange Servers container object, Exchange Address List object, Exchange Public Folder object and Exchange Public Folder tree object.

For Exchange 2003 start Exchange system manager and goto the objects and right click and choose properties, then on the security tab choose advanced and make sure “Allow inheritable permissions from the parent to propagate to this object and all child objects” is enabled. After that restart the Exchange server.

If security tab isn’t available you have to create the following registry value:
Value Name: ShowSecurityPage, Data Type: REG_DWORD, Radix: Binary, Value: 1 At the HKEY_CURRENT_USER\Software\Microsoft\Exchange\EXAdmin key.

For Exchange 2007 and 2010 use adsiedit, and browse to the object you want to change. Right click and choose properties, then on the security tab choose advanced and make sure “Allow inheritable permissions from the parent to propagate to this object and all child objects” is enabled. Wait till Active Directory replication has replicated the changes.

Posted in Blog, Exchange 2007, Exchange 2010, SBS 2008 at September 17th, 2010. No Comments.

Upgrading Exchange 2010 RTM to Exchange 2010 SP1

When upgrading your Exchange 2010 RTM server to Exchange 2010 SP1 you need to install a set of pre-required hotfixes. These hotfixes depent on with Operating System you run and witch Exchange roles you have installed on the server.

When you start the Exchange 2010 SP1 setup, you first can choose Exchange language option for upgrade. If you run multiple servers you can download the language bundle file from microsoft. So you can point to this file every installation and don’t have to download it multiple times.

After you choose the language option you can choose Install Microsoft Exchange Server upgrade. This starts a wizard and after the introduction and license agreement, the readiness checks are performed. This is where setup tells you witch pre-requirements are needed.

In my case all servers are running windows server 2008 R2. I have 2 load balanced Client Access / Hub Transport servers and 2 Mailbox servers configured with a DAG.

For the Client Access role the following updates are needed: KB 982867, 979744, 983440 and 977020.

For the Hub Transport and the Mailbox role only the Microsoft Office 2010 Filter Pack is needed.

In my case KB 979099 was already installed by windows updates so wasn’t needed.

When upgrading keep the following Exchange roles upgrade order in mind:
Client Access server
Hub Transport server
Unified Messaging server
Mailbox server

More information about upgrading, pre-requirements and known issues can be found:
by the Exchange team: Exchange 2010 SP1 FAQ and Known Issues
by Microsoft Technet: Upgrade from Exchange 2010 RTM to Exchange 2010 SP1

Posted in Blog, Exchange 2010 at September 15th, 2010. No Comments.

Error updating public folder with free/busy information.

On a exchange server you notice the following error in the application event log.
Event id 8207, MSExchangeFBPublish
Error updating public folder with free/busy information on virtual machine servername. The error number is 0x80004005.

Start a elevated Exchange management shell and run the following command:
set-publicfolder -identity “\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY\EX:/o=orgnizationname/ou=First Administrative Group” -replicas “public folder database”

Posted in Blog, Exchange 2007, Exchange 2010 at September 11th, 2010. No Comments.
Sharing Buttons by Linksku