Microsoft released a standalone version of Microsoft Exchange Server 2010 SP2 Help.
Download HERE
Microsoft released a standalone version of Microsoft Exchange Server 2010 SP2 Help.
Download HERE
Exchange Server 2010 Service Pack 2 (SP2) has been released, raising the Exchange version number to 14.2.247.5. You can download Exchange 2010 SP2 here.
For those still unaware, the 530Mb+ file (1,4 GB extracted) contains the full set of binaries; you can use it to upgrade existing RTM or SP1 installations or deploy new Exchange 2010 SP2 installations.
Besides the usual set of hotfixes, SP2 introduces the following features:
Address Book Policies
Address Book Policies, also known as GAL segmentation, ABPs are meant to segmentize the address book, giving users a certain view of the address book like Address List Segregation did for Exchange 2003/2007.
OWA mini
This will be a lightweight browser like OMA in the past, meant for simple browsers.
Hybrid Configuration
This wizard is to make the configuration of an on-premise Exchange and Office 365/Exchange Online more simple, reducing the steps required from 49 to 6.
OWA Cross-Site redirection
This will allow clients to be silently redirected to the proper site if they log on to a CAS server located in a site different than the site where their mailbox is hosted and externalURL has been specified there.
After preparing your forest for Exchange 2010 SP2, the schema version number will have changed. Check the Schema Versions page for information on the new ObjectVersion and RangeUpper values for Exchange 2010 SP2.
Note that SP2 introduces an additional requirement, which is the IIS 6 WMI Compatibility feature; you can add this feature using the GUI or by using the Powershell cmdlets Import-Module ServerManager followed by Add-WindowsFeature Web-WMI.
The proper method to upgrade mailbox servers that are a member of a Database Availability Group is described here.
The releases notes are not available at time of writing; we’ll update this post when they become available.
The Exchange CXP team released Update Rollup 6 for Exchange Server 2010 SP1 to the Download Center.
This update contains a number of customer-reported and internally found issues since the release of SP1. See ‘KB 2608646: Description of Update Rollup 6 for Exchange Server 2010 Service Pack 1’ for more details.
This update contains a number of customer reported and internally found issues since the release of RU5.
The most Important Fixes:
Other Fixes:
General Notes
An issue with management of RBAC roles when RU6 is partially deployed in the organization: Due to changes shipped in this update, certain warnings can be displayed when managing RBAC roles, if RU6 is not yet deployed to all servers in the organization. Please see the following KB article for more information:
Managing RBAC roles might display warnings or errors if Exchange 2010 SP1 RU6 is partially deployed in the organization
http://support.microsoft.com/kb/2638351
Note for Forefront users: For those of you running Forefront Protection for Exchange, before installing the update, stop all Forefront services.
The Exchange team made a fix available a fix to solve the issues when using the Management Console of Exchange 2007 or 2010 in conjunction with Internet Explorer 9.
As you probably know, when using Internet Explorer 9 you can’t close the Exchange Management Console properly as it gives you the error “You must close all dialog boxes before you can close Exchange Management Console” having no dialogs open.
To solve this issue, you had to use the Task Manager to force closing the EMC process using
To properly install the hotfix:
Microsoft states it expects to incorporate this fix in a future update of Internet Explorer 9.
While releasing a fix for the IE9 issue is great after all these month, I can’t help but wonder why the fix has not been made public.
Today the Exchange Team released Rollup 5 for Exchange Server 2007 Service Pack 3 (KB2602324). This update raises Exchange 2007 version number to 8.3.213.1.
Here’s the list of changes included in this rollup:
981820 New X-headers of a message item do not appear when the message item is retrieved by IMAP4 or by POP3 in an Exchange Server 2007 SP2 environment
2292150 A deleted hyperlink remains in the HTML source of an email message if you create the email message by using OWA in an Exchange Server 2007 environment
2411423 The Msftefd.exe process constantly consumes up to 100 percent of CPU resources when your mailbox language is set to German on an Exchange Server 2007 server
2450078 The sent time in an email message body is incorrect when you reply or forward the email message by using an EWS application in an Exchange Server 2007 environment
2451415 “There was a problem logging onto your mail server” error message when you use a POP3 client to access a mailbox in an Exchange Server 2007 SP3 environment
2536652 EdgeTransport.exe randomly stops responding on a Hub Transport server after you configure public folder replication in Exchange Server 2007
2536695 “Some items cannot be deleted” error message when you try to delete or modify an email message in a public folder in an Exchange Server 2007 environment
2536697 DBCS characters in a rule name are converted to question marks after you move a mailbox from Exchange Server 2003 to Exchange Server 2007
2537783 The EdgeTransport.exe process crashes occasionally after you install Update Rollup 2 for Exchange Server 2007 SP3
2538958 Extended Protection Warning Displayed in Exchange Management Console and Exchange Management Shell After Installing RU2 for Exchange 2007 SP3
2554575 Items accumulate in the MRM submission folder when managed folder assistant journal items in an Exchange Server 2007 environment
2556751 The EdgeTransport.exe process crashes when processing certain email messages on an Exchange Server 2007 Hub Transport server
2557304 The Store.exe process may consume excessive CPU resources and memory resources intermittently when a user opens a calendar item by using OWA in an Exchange Server 2007 SP3 environment
When running ForeFront Protection for Exchange, make sure you disable ForeFront before installing the rollup and re-enable it afterwards, otherwise the Information Store and Transport services may not start. You can disable ForeFront using fscutility /disable and enable it using the fscutility /enable command.
Note that update rollups are cumulative, i.e. they contain fixes released in earlier update rollups for the same product level (RTM, SPx). This means you don’t need to install previous update rollups during a fresh installation but can start with the latest rollup available right away.
You can download Exchange 2007 SP3 Rollup 5 here.
A white paper has been published that examines how Microsoft Exchange Server 2010 performs on vSphere 5 in terms of scaling up (adding more virtual CPUs) and scaling out (adding more VMs). Having the choice to scale up or out while maintaining a positive user experience gives IT more flexibility to right-size system deployments and maximize total cost of ownership with respect to licensing and hardware purchases.
Testing shows the effectiveness of vSphere 5 to add compute power by scaling up Exchange Server VMs, in increments, from 2 to 12 virtual CPUs. This allowed the total number of very heavy Exchange users to increase from 2,000 to 12,000 while sendmail latency remained well within the range of acceptable user responsiveness. Processor utilization remained low, at about 15% of the total host processing capacity for 12,000 very heavy Exchange users.
Testing also shows that scaling out to eight Exchange Server VMs supports a workload of up to 16,000 very heavy users, with the load consuming only 32% of the ESXi host processing capacity.
Additional tests were undertaken to show the performance improvements of vMotion and Storage vMotion in vSphere 5. vMotion migration time for a 4-vCPU Exchange mailbox server VM showed a 34% reduction in vSphere 5 over vSphere 4.1. Storage vMotion migration time for a 350GB database VMDK showed an 11% reduction in vSphere 5 over vSphere 4.1.
For the full paper, see Microsoft Exchange Server 2010 Performance on vSphere 5.
At the moment I am busy to design a Exchange 2010 environment.
The customer where I going to implement Exchange 2010 use only HP equipment.
A great tool is the HP sizer for Exchange 2010.
About the HP Sizer tool:
Microsoft® Exchange Server 2010 is a complex application that requires intensive knowledge of deployment strategies, interdependencies, server and storage performance related issues.HP has developed the HP Sizer for Microsoft Exchange Server 2010 to assist customers with proper server and storage sizing for their Exchange Server 2010 deployments. The algorithms developed and implemented in this tool are based upon extensive testing of Exchange Server 2010 server roles and technologies, HP’s deep experience with Microsoft Exchange, and intricate knowledge of server CPU, memory, and I/O subsystems. This tool is free to download and use, and is designed to simplify configuration across a broad range of deployments. This newest Microsoft Exchange Server Sizer provides support for multiple site deployments, varied client types and access methods, all Exchange Server 2010 server roles, Database Availability Group (DAG) high availability options, choice of tower, rack mounted, or HP BladeSystem server platforms, and either direct attached or SAN-based storage solutions. Based on your input, the tool provides a comprehensive bill of materials along with a deployment overview of the Exchange Server 2010 server roles and storage configurations. Once this Sizer is installed, updates can be downloaded automatically to the underlying software engines that are necessary to provide support for HP server and storage product information details.
Please see the ‘What’s new” link on the home page of the Sizer (when installed on your system) for the most recent information.
![]()
This update contains a number of customer-reported and internally found issues since the release of SP1. See ‘KB 2582113: Description of Update Rollup 5 for Exchange Server 2010 Service Pack 1′ for more details.
We want to let you know this rollup contains the Exchange 2010 SP1 version of the change described in this KB article:
2543879 PDF attachment from a Mac Mail client is not displayed when you use Outlook 2010 to open the email message in an Exchange Server 2007 SP3 environment
Most important fixes:
2556352 "ChangeKey is required for this operation" error message in Outlook for Mac 2011 in an Exchange Server 2010 environment
2555850 You cannot delete a mailbox folder that starts with a special character in its name by using Outlook in an Exchange Server 2010 environment
2499044 You cannot save attachments in an email message by using OWA if the subject line contains special characters in an Exchange Server 2010 environment
Other Fixes:
2275156 The inline contents disposition is removed when you send a "Content-Disposition: inline" email message by using EWS in an Exchange Server 2010 environment
2509306 Journal reports are expired or lost when the Microsoft Exchange Transport service is restarted in an Exchange Server 2010 environment
2514766 A RBAC role assignee can unexpectedly run the Add-ADPermission command on an Exchange Server 2010 server that is outside the role assignment scope
2529715 Slow network or replication issues after you change the number of virus scanning API threads in Microsoft Exchange Server 2010
2536704 Mailbox users who are migrated by using ILM 2007 cannot use the Options menu in OWA in an Exchange Server 2010 environment
2537094 French translation errors occur when you edit a response to a meeting request by using OWA in an Exchange Server 2010 SP1 environment
2554604 A RBAC role assignee can unexpectedly manage certificates that are outside the role assignment scope in an Exchange Server 2010 environment
2555800 You cannot use the GetItem operation in EWS to retrieve properties of an email message in an Exchange Server 2010 environment
2556096 The columns in the .csv logging file are not lined up correctly when you perform a discovery search on a mailbox in an Exchange Server 2010 environment
2556107 The columns in the .csv logging file are not lined up correctly when you perform a discovery search on a mailbox in an Exchange Server 2010 environment
2556133 A device that uses Exchange ActiveSync cannot access mailboxes in an Exchange Server 2010 environment
2556156 Extra.exe crashes when it performs RPC activity checks against an Exchange Server 2010 server
2556407 Certain client-only message rules do not take effect on email messages that are saved as drafts in an Exchange Server 2010 environment
2559926 "There are no items to show in this view." error message when you try to view a folder by using Outlook in an Exchange Server 2010 environment
2572958 The "Test-OutlookConnectivity -Protocol HTTP" command fails with an HTTP 401 error in an Exchange Server 2010 environment
Download: Rollup 5 for Exchange 2010 SP1 Here
Important Note for Forefront users:
For those of you running Forefront Security for Exchange, be sure you perform these important steps from the command line in the Forefront directory before and after this rollup’s installation process. Without these steps, Exchange services for Information Store and Transport will not start after you apply this update. Before installing the update, disable ForeFront by using this command: fscutility /disable. After installing the update, re-enable ForeFront by running fscutility /enable.
In Outlook 2007, when a user does a reply to some emails the E-mail Type: changes from the normal SMTP to MAILTO and then when the user sends the email it is rejected because either Outlook or our Exchange server is adding @domain.nl to the end of the recipient’s email address.
This also happens with emails where the senders address is shown as a clickable option [mailto:persons.name@domain.co.uk].
Email address has been changed to Persons.name@domain.co.uk for confidentiality reasons.
Delivery has failed to these recipients or distribution lists:
‘Persons.name@wardvissers.nl’
A problem occurred during the delivery of this message. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message later, or provide the following diagnostic text to your system administrator.
_____
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: ward-ex01.wardvissers.nl
IMCEAMAILTO-Persons+2Ename+40domain+2Eco+2Euk@wardvissers.nl
#550 5.4.4 ROUTING.NoNextHop; unable to route ##
Original message headers:
Received: from ward-ex01.wardvissers.nl ([fe80::d597:2413:93ab:cf17]) by ward-ex01.wardvissers.nl ([fe80::d597:2413:93ab:cf17%13]) with mapi; Thu, 14 Oct 2010 13:58:28 +0100
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Internal User <Internal@wardvissers.nl>
To: "’Persons.Name@domain.co.uk’"
<IMCEAMAILTO-Persons+2Ename+40domain+2Eco+2Euk@wardvissers.nl>
Date: Thu, 14 Oct 2010 13:58:27 +0100
Subject: email
Thread-Topic: email
Thread-Index: Actrn34QI8tEGRBCR/qQGIH5MxGgyA==
Message-ID: <DC037DCA5E8D0F4585E53F80A5599ADC02339D6B5325@ward-ex01.wardvissers.nl>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <DC037DCA5E8D0F4585E53F80A5599ADC02339D6B5325@ward-ex01.wardvissers.nl>
MIME-Version: 1.0
Solution:
Removing Microsft Office Word 2007 (KB2344993) update from the computer did the trick