Microsoft Exchange Server 2010 SP3 update to Update Rollup 8-v2 for Exchange Server 2010 SP3

i have Microsoft Exchange Server 2010 SP3 and i would like to update to Update Rollup 8-v2 for Exchange Server 2010 SP3.
what is the best way to do so?
my current env:
Name : xxxxxxxx
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : Mailbox, HubTransport
Site : domain/Configuration/Sites/xxx
Name : yyyyyyyy
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : Mailbox, ClientAccess, HubTransport
Site : domain/Configuration/Sites/yyy
Name : cccccccc
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : Mailbox, ClientAccess, HubTransport
Site : domain/Configuration/Sites/ccc
Name : dddddddd
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : ClientAccess
Site : domain/Configuration/Sites/ddd
Name : iiiiiiii
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : Mailbox, ClientAccess, HubTransport
Site : domain/Configuration/Sites/iii
thanks
Mayson

Consider referring to the articles below and that explains it all.
Install the Latest Update Rollup for Exchange 2010 - https://technet.microsoft.com/en-us/library/ff637981.aspx
Applying Service Pack and Rollup Updates on Exchange Server 2010 (Part 1) - http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/applying-service-pack-and-rollup-updates-exchange-server-2010-part1.html
Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

Similar Messages

Update Rollup 6/7 for Exchange Server 2010 SP2

Our config :
Version 14.2 (Build 247.5)
2 Mailbox servers (DAG), 2 CAS/HUB Servers using a NLB, 2 edge
my question is the following:
can i go directly to rullp 7 without installing 2,4, 5, 6 or I have to install all rollup ?
and what's the bests practices for installing rollup ?

Hello,
You can install rollup 7 directly without installing rollup 2,4, 5, 6.
You should install rollup 7 on your Exchange 2010 server roles in the following order: Client Access/ Hub Transport ,Mailbox and Edge Transport.
Please refer to the following article to install rollup 7 on CAS Array Members. (Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does
not guarantee the accuracy of this information.)
http://exchangeserverpro.com/how-to-install-updates-on-exchange-server-2010-cas-arrays/
Please refer to the following steps to install rollup 7 on Database Availability Group Members.
=============================================================
1. Run the StartDagServerMaintenance.ps1 script on the server being updated.
2. Install the update rollup .
3. Run the StopDagServerMaintenance.ps1 script .
4. Re-balance the DAG, as needed .
Here is the article for your reference.
http://technet.microsoft.com/en-us/library/ee861125(v=exchg.141).aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Installing Update Rollup 7 for Exchange Server 2010 SP3

Hi,
I have 4 Exchange servers. Two CAS and two DAG. I am currently on Rollup 2 for Exchange Server 3010 SP 3. Can I install Update Rollup 7 for Exchange Server 2010 SP3 or do I need to install a previous one first?
Thannks!
Wave~Chaser

Hi,
When I try to install Exchange 2010 SP3 roll up 7, am getting the below error:
The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may
be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.
and please find below event log:
Product: Microsoft Exchange Server - Update '{A93DA06F-A5B8-4DF8-8B3F-B285E014C659}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions
on turning on logging support.
Can you please help me with this error.
Thanks

How do I know which update rollup is installed on my exchange 2010 sp3 server ?

how do I know which update rollup version is installed on my exchange 2010 sp3 server ?
Anand_N

And take a peek here:
http://blogs.technet.com/b/rmilne/archive/2013/10/29/how-to-check-exchange-2010-ru-version.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

DPM 2012 R2 Rollup 4, Update Rollup 7 for Exchange Server 2010 SP3 backups with eseutil check fail

Hi,
It could be a coincidence, but ever since installing Update rollup 4 onto DPM 2012 R2, (which was at UR3 I believe) I haven't been able to complete an Exchange express full backup or consistency check with verification using Eseutil checked. If I have the
eseutil check enabled I get the following error:
Type: Consistency check
Status: Failed
Description: Data consistency verification check failed for LOGS of Exchange Mailbox Database Mailbox Database 2011112513 on SERVER.xxx. (ID 30146 Details: The process cannot access the file because it is being used by another process (0x80070020))
Disabling the eseutil verification allows it to succeed, but I'm not happy to continue with that for too long.
I've had this running for many years and this is the first real issue with exchange, its a single stand alone exchange database.
Any ideas?
Thanks,
Andreas

Andreas,
the error is stating that something else has a handle to a file or files during the ESEUtil check. Typically this is AV. I have also seen where the Exchange limits are exceeded and that causes the issue.
Please ensure you have the DPM AV exclusions for the DPM server and I would advise the DPMRA.exe on the PS. You can also trying disabling or removing AV as a test.
DPM AV exclusions -
http://technet.microsoft.com/en-us/library/hh757911.aspx
You may also want to test using eseutil against the logs outside DPM and see if that fails with similar issue. Let us know. Thanks
Regards, A.Nadar, This posting is provided "AS IS" with no warranties, and confers no rights.

Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

What am I trying to do?
I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
error logs at the bottom of the page but the basics are in order it will throw which loop around are:
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
What am I running?
2 X DC on domain and forest functional level 2008R2 both writable
1 X fresh install of Windows 2012 R2 which is domain joined
What have I tried?
Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
Rebooted every server
Run setup as Administrator
My account is part of the domain Enterprise Admin group
Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
Computer Configuration Windows Settings
Security Settings + Local Policies
User Rights Assignment Mange auditing and security log
Turned off firewall on DC and Exchange Server even stopped the service
Turned off all AV on the DC and Exchange Server
Checked I could telnet to global catalog servers on port 3268 which I can
Checked the global catalog records existed in DNS which they all do
Done the obvious ping tests all round which confirms connectivity
Schema has been prepared using appropriate commands before running the setup exe
setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
Making sure the following path has full permissions:
EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
Restarted Microsoft Exchange Active Directory Topology service
DcDiag all looks good
What have I noticed that is suspicious?
Microsoft Exchange Transport service will not start even though both of its dependences services have started:
Microsoft Filtering Management Service
Microsoft Exchange Active Directory Topology Service
It will eventually error with
“Windows could not start the Microsoft Exchange Transport Service on local computer
Error 1053: This Service did not respond to the start of control request in a timely fashion”
This error is from the GUI wizard itself:
Error:
The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
" was run: "System.Exception: Unable to set shared config DC.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Exchange logs which have been written:
**The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
[01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
'{ mydomain.com}'
[01/20/2015 17:13:20.0084] [2] User specified parameters:
-DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[01/20/2015 17:13:50.0288] [1] [ERROR] The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
        " was run: "System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
[01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
[01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
Windows Event Viewer:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
in either the local site 'Default-First-Site' or the following sites:

Hi apl228,
1. Please make sure the IPv6 is enabled.
2. Please make sure the account that install Exchange server has Administrator permission.
3. Please make sure DNS has been configured correctly.
Thanks
Mavis Huang
TechNet Community Support

Exchange 2010 SP3 Update Rollup 6 breaks first OWA login (timezone selection) on SBS 2011

The Exchange 2010 SP3 Update Rollup 6 broke the OWA for Users who access OWA for the first time and have to set a timezone. They get this error:
Request
Url: https://xxxxx:443/owa/languageselection.aspx
User: xxxxxx
EX Address: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=xxxxx
SMTP Address: xxxxxx
OWA version: 14.3.195.1
Exception
Exception type: System.ArgumentNullException
Exception message: Value cannot be null. Parameter name: value
Call stack
Microsoft.Exchange.Clients.Owa.Core.Utilities.RenderDirectionEnhancedValue(TextWriter output, String value, Boolean isRtl)
Microsoft.Exchange.Clients.Owa.Core.LanguageSelection.RenderTimeZoneSelection()
ASP.languageselection_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer)
System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
System.Web.UI.Page.Render(HtmlTextWriter writer)
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
This Server is an SBS2011.
The update broke nothing on a "normal" 2008R2 with exchange 2010.
Uninstalling RU6 helped but thats obviously not the desired way.
Removing the RenderTimeZoneSelection() call from languageselection.aspx obviously helped but then there is no timezone dropdown displayed anymore. The timezone dropdown is working normaly in other places like ecp. Afaik this error occours only in the languageselection.aspx
file which is displayed for "new" OWA users. (Users without a timezone set)
my workaround was to set the language and timezone for these mailboxes via exchange shell.

Hello,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2010 SP1 Update Rollup 6 to Exchange 2010 SP3

Hi there,
I am planning to install Exchange 2010 SP3 next week and after reading some of the related comments on this site I got a little worried.
Our current Exchange environment consists of the following:
1 x CAS/HT Server
2 x Mailbox Server (members of a DAG)
The OS of the 3 servers is Windows Server 2008 R2 SP1. All servers are running Exchange 2010 SP1 Update Rollup 6.
The Execution Policies on our Exchange servers are set as follows:
– CAS/HT Server:
Scope ExecutionPolicy
MachinePolicy Undefined
UserPolicy Undefined
Process Undefined
CurrentUser Undefined
LocalMachine Unrestricted
– Mailbox Servers:
Scope ExecutionPolicy
MachinePolicy Undefined
UserPolicy Undefined
Process Undefined
CurrentUser Undefined
LocalMachine RemoteSigned
Please note that we do not have any Group Policies that defined the PowerShell script execution policy.
I would be very grateful if you (or any of the kind readers) could help me with following questions:
1- Do I have to change the execution policy on our Exchange servers before installing SP3? If I have to change a policy, what should I change? And how would you recommend I should do this?
2- After installing SP3 on a server, can I install the latest rollup update on this server before moving to the next server? For example, can I do the following:
i. Install SP3 followed by RU 5 on the CAS/HT server -> Apply the our custom settings
ii. Install SP3 followed by RU 5 on the first mailbox server
iii. Install SP3 followed by RU 5 on the second mailbox server
Many thanks,
M

Hi Amit,
Many thanks for the swift reply.
That's correct. We didn't set the Powershell execution policy via Group Policy. We only configured the execution policy of "LocalMachine" to "Unrestricted" on the CAS/HT server using the "Set-ExecutionPolicy" command on the server.
The mailbox servers' execution policies have not been changed and are set to those values by default.
I must admit, I go event more confused when I read the "http://support.microsoft.com/kb/2668686" and "http://support.microsoft.com/kb/2810617" articles.
But it looks like I shouldn't worry as our current Powershell execution policies shouldn't affect the upgrade. Right?

Exchange 2010 SP3 Update 7 breaks OWA for some IE11 users

I had issues earlier with OWA on some clients running Internet Explorer 11 (as
documented in this thread), and managed to resolve it by disabling compatiblity mode in IE11.
After SP3 Update Rollup 7 the issue came back, and no tinkering with the compatibility mode will solve it.
Have anyone encountered this issue before? The issue only appears on certain machines in their own AD OU as well as own subnets.

Hi,
I haven't heard that Exchange 2010 SP3 Update Rollup 7 has this issue so far. In your case, I would like to verify if you remove all interim updates for Exchange 2010 SP3 before installing Rollup 7. If no, remove it and check the result.
Here is a kb for your reference.
Update Rollup 7 for Exchange Server 2010 Service Pack 3
http://support.microsoft.com/kb/2961522
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Update Rollup 7 for Exchange Server 2010 Service Pack 3 (KB2961522)

This rollups will not install and has caused multiple issues on the Windows SBS 2011.
The issues are as follows:
All Exchange and related services were stopped and had to be manually restarted.
The update fails for multiple reasons, changes every time.
I am no longer able to perform ANY updates without some sort of error code.
All Domain client computers now report Security Status as Critical, Servers as not available.
DNS does not appear to be properly, many internet requests from domain PC's stop with "Fix connection problems" error page.
Running BPA shows no major issues
I can no longer run the WSUS server cleanup. I get a Connection Error and have to reset the node, but it soon fails again.
Shared folders may take quite a bit of time to open.
Any help would be greatly appreciated. I do have an open ticket with Microsoft and although this is rated critical I am not getting any resolution. The only thing that MS support managed to do was bring the server down for an additional day and corrupt my
EDB files so that they had to be rebuilt.

Hi,
à
All Exchange and related services were stopped and had to be manually restarted.
While the update was installed, it will automatically stop Exchange and IIS services. You may need to restart
manually.
àThe update fails
for multiple reasons, changes every time.
à
I am no longer able to perform ANY updates without some sort of error code.
Would you please let me know any of those
update-failed reasons? Meanwhile, please let me know some error code that you can get when can’t perform updates. Meanwhile, please refer to installation suggestions and tips in following article when install this update rollup.
Exchange
2010 SP3 Update Rollup 7 released and installation tips
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
àAll Domain client
computers now report Security Status as Critical, Servers as not available.
àDNS does not
appear to be properly, many internet requests from domain PC's stop with "Fix connection problems" error page.
Please check if ping the SBS server successfully from the problematic client computer via server name and ip
address. In the SBS 2011, can you access
internet successfully? In addition, please select a client computer as a test machine, re-join it to the SBS network, then check if Security Status still report as Critical. Please also run Fix my network wizard in SBS console. Any find?
Meanwhile, please refer to following article and check if can help you to
repair Windows Server Update Services.
Repair Windows Server Update Services
By the way, did you have a good backup for the server?
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Exchange 2010 SP3 Update Rollup 2 (KB2866475) personal archive issue

I’m wondering if anyone else has run across this issue: We use the Exchange personal online archives, and after installing the rollup, anyone with full access to someone else’s mailbox had all the personal archive names changed to the
same name. As an example, if I had full access to Joe’s mailbox, then the name of Joe’s personal archive, as shown on my Outlook 2010, would display “Archive – Paul@company” rather than “Personal Archive – Joe”. Uninstalling the rollup put
everything back to normal. So, has anyone else seen this?
Thanks.

Hi,
Have you checked it via OWA? Is it the same with Outlook 2010?
If the issue doesn’t occur when you use OWA, I recommend you recreate Outlook profile to check the result.
If OWA also has the issue, please make sure whether all users are impacted by the issue.
Here is a related thread below for your reference, but I cannot find related description for the issue that the Update Rollup 2 for Exchange Server 2010 SP3 resolves.
http://social.msdn.microsoft.com/Forums/exchange/en-US/45814f93-30a7-4cad-ae4d-5c9d1f4d0a08/bug-in-update-rollup-1-for-exchange-server-2010-sp3-breaks-online-archive-names
Description of Update Rollup 2 for Exchange Server 2010 SP3
Best regards,
Belinda

Exchange 2010 SP3 Update Rollups

Hi All,
I have a question about installing Update Rollups for Exchange 2010 SP3. After some organizational changes I have to take care of windows updates and our WSUS server. During the last check I found out that there are:
Update Rollup 5,6,7 listed in WSUS for our Exchange which is (CAS, HUB, MB). I've checked also some information about installing Update Rollup but it's not very clear for me. i saw also a problems after installing Update Rollup 6 and also some info from
blogs.technet.com
The release contains fixes for customer reported issues and previously released security bulletins. Update Rollup 7 is
not considered a security release as it contains no new previously unreleased security bulletins. Customers running
any Service Pack 3 Update Rollup for Exchange Server 2010 can move to Update Rollup 7 directly.
So, what is the best way to do it?
- Decline old Update Rollups, Install all other security and critical updates from WSUS, reboot the server, install Update Rollup 7, reboot the server?
Thanks in advance

Hi kondio
Thank you for your question.
Service packs and update rollups are part of the servicing strategy for Exchange 2010. They provide an effective and easy-to-use method to distribute Exchange 2010 fixes and modifications. We recommend that you install the latest service pack and update
rollup to keep the product up-to-date.
I suggest you update manually instead of WSUS.
You can refer to the following link to read about RU:
http://technet.microsoft.com/en-us/library/ff637981(v=exchg.141).aspx
If there are any questions, please let me know.
Best Regard,
Jim

Issue with Update Rollup 5 for Exchange 2010 SP3 - Mailboxes that were auto mapped not working

Below is my response in another thread but creating a new one in the hopes that someone has the same issue and a solution besides mine below.
Ever since we installed Update Rollup 5 for SP3 Exchange 2010 mailboxes that were auto mapped are not accessible. They all get the same error.
Cannot expand the folder. The set of folders cannot be opened. The attempt to log on to the Microsoft Exchange has failed.
What I have been doing is removing the users permission, then adding them back using the noautomap switch in Powershell. After doing that, the user manually adds the mailbox and all is well.
Just a note here, I suspect it may have something to do with the version of Outlook 2010. We are running an older version here. I think only SP1 with no other incremental updates. Office is up to SP2. Also, one of the users I was working with could not access
the mailbox no matter what we tried but she can walk over to another workstation and open Outlook and access the very same mailbox so that pretty much proves its software related particularly with Outlook.
I cannot reproduce the problem on a workstation (XP) with a newer version of Outlook.
This has been wearing me out and I suspected the Update Rollup all long. Now I am confident as others are having the same problem. If you find out anything on how to fix this other than the steps above, let me know.

Not sure why it was suggested to use the auto mapping feature to grant permissions because that is the component that is causing the issue. Also, there is nothing wrong with the auto configuration because the user can access their own mailbox just fine and
also select mailboxes in their Outlook that were NOT auto mapped.
With that said, here is how I fixed them all.
Remove the permissions using the Exchange Console. Don't forget Send As
Wait about 15 minutes. The mailbox should disappear from the users Outlook
Open an Exchange PowerShell window and run the following command:
.\add-mailboxpermissionsnoautomap.ps1 -Identity mailbox -User user -AccessRights FullAccess
Have the user add the mailbox to their Outlook using the manual process.
All is well....
If you don't have the PS script add-mailboxpermissionsnoautomap.ps1, you can download it. I stumbled across it a few years ago and use it all the time. If you can't find it, just use the Exchange built in command for adding mailbox folder permissions but
specify automap $false.
The idea here is to grant the user access without auto mapping.

Install or not install - exchange 2010 update rollup 4 sp3

Hi guys!
We have Exchange2010 SP3 with update rollup 2.
Users with IE11 are having problems with OWA opening only in light mode. I have read on the internet that CU 4 solves this problem but on the other hand this CU makes additional problems with outlook 2007 clients.
Some of the comments of this issues from other companies are: In Outlook 2007 if you choose to change the current view with Arrange By 'Categories' the following is noticed: - Items that you set unread or read are not changed until you refresh the view
- If you open an unread email by doubleclicking, it's status stays unread until you refresh the view. - New mail items are not automatically seen until refresh. This is a very annoying issue, and our servicedesk already received a lot of calls for this issue
Is there any workaround to fix IE11 OWA light mode and not corrupt Outlook 2007 user clients?
bostjanc

It happens as MSIE token is removed from the user-agent string in IE11. This made the Exchange team provide an update on the Exchange side to fix this issue. The workaround is to use Compatibility Mode in IE11 for OWA. As for the fixes:
2003: Use workaround, no fix will be released
2007: Use workaround until a fix is released, currently a fix is tentatively planned for release in E2007 SP3 RU12
2010: Install
E2010 SP3 RU3 or use workaround
2013: Install
E2013 CU3 or use workaround
O365: Issue is already fixed, no action is required
Thanks,
Jason
Jason Apt, Microsoft Certified Master | Exchange 2010
My Blog

After upgrading Exchange Server 2007 to SP3 with update rollup 13, OWA not working

Hi,
We have just installed Service Pack 3 and update rollup 13 on our Exchange Server 2007, but unfortunately our OWA has gone inaccessible.
PROBLEM- The following error comes up when we try to access OWA :
Exception
Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
Exception message: Object reference not set to an instance
of an object.
Call stack
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
Microsoft.Exchange.Clients.Owa.Core.Globals.InitializeApplication()
Microsoft.Exchange.Clients.Owa.Core.Global.ExecuteApplicationStart(Object sender, EventArgs e)
Inner Exception
Exception type: System.NullReferenceException
Exception message: Object reference not set to an instance
of an object.
Call stack
Microsoft.Exchange.Clients.Owa.Core.Configuration.CheckPublicFolders(ADSystemConfigurationSession session, ADObjectId[] pfdbIds, Boolean& allLegacy, Boolean& allLater)
Microsoft.Exchange.Clients.Owa.Core.Configuration..ctor(ADSystemConfigurationSession session, String virtualDirectory, String webSiteName, ADObjectId distinguishedName, Boolean isPhoneticSupportEnabled)
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.LoadConfiguration()
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
ACTION TAKEN SO FAR :
1. Removed OWA virtual directories and recreated them again.
2. IIS has been reset.
3. Restarted the HUB/CAS server.
4. Created public folder database.
Even after doing all these activities, owa is still inaccessible. Please help.
Regards,
Ankur

Hi Ankur,
From your description, you can't access to OWA after upgrading Exchange server 2007 to SP3 rollup 13. Firstly, please locate to C:\ExchangeSetupLogs and make sure that it is a successful installation. If not, this issue often occurs.
If it is a successful upgrading, please follow the steps below for troubleshooting.
1. Open IIS Manager, click Default Web Site -> Authentication, make sure that Anonymous Authentication and Windows Authentication are enabled.
2. Click Default Web Site -> SSL Settings, check "Require SSL" and click Ignore.
3. Click Default Web Site -> HTTP Redirect, check Redirect (enter your
https://URL), check "Only redirect" box and Status code Found 302.
4. Expand Server Configuration -> Client Access ->double click owa ->Authentication tab. Check the Basic Authentication and check the Use forms-based authentication button Logon Format: Domain\user name.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Microsoft Exchange Server 2010 SP3 update to Update Rollup 8-v2 for Exchange Server 2010 SP3

Similar Messages

Maybe you are looking for