Exchange 2010 SP2, Update Rollup 7

Our setup before we applied Rollup 7:
Exchange 2010, SP2 Update Rollup 6 running on all servers.
2 Mailbox servers w/ DAG
3 CAS/HUB Servers using a hardware load balancer
No problems prior to the Rollup 7 installation.
The Rollup went fine on 4 out of the 5 Exchange Servers. On the 5th server, however, there are problems. The first time I tried to install RU7 it was about 5 hours in when I cancelled it. So I tried again and the install has been running for 13
hours and it appears to be only about 40% complete. The progress bar has been stuck in the same spot for nearly all of that time. Per an article I found on Susan Bradley site (SBS Diva) I had verified that "Check for publisher's certificate revocation"
was disabled in IE prior to the start of the install.
I have seen Service Packs take a long time in the past and I have Rollup Updates take a long time too, but this is taking a very long time.
Anyone else observing this issue with this latest Update Rollup for Exch10, SP2?
Thanks.

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

Similar Messages

Migrating a mailbox cross forest from exchange 2013 Sp1 to exchange 2010 SP2 Update rollup 8

I can migrate a mailbox fine from exchange 2010 sp2 update rollup 8 to exchange 2013 sp1 or Cu2.
I was testing today migrating cross forest from 2010 sp2 udpate rollup 8 back to exchange 2010 sp2 but I get the below error. Is this even possible? I cannot find any documentation on this scenario yet.
VERBOSE: [21:52:47.622 GMT] New-MoveRequest : The remote server doesn't support client 'casservername.domain.com'
version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
VERBOSE: [21:52:47.637 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
The remote server doesn't support client 'casservername.domain.com' version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException
+ FullyQualifiedErrorId : 782D22F0,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

Hi Steve,
I'm a little confused what you are saying. Here is my understanding:
When you migrate mailboxes from Exchange 2013 back to Exchange 2007, the above error occurs.
If I have misunderstood your concern, please let me know.
For migrating mailboxes back to Exchange 2007, there is a simple and straightforward method. Please use the New-MailboxExportRequest cmdlet to convert all mailboxes into pst files. And then use the Import-Mailbox cmdlet to import all pst files into Exchange
2007.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exchange 2010 Sp2 update rollup 7 fails with error code 80070643 on Sbs 2011

Hello Everyone,
When i trie to install rollup 7 voor exchange 2010 sp2 (sbs 2011) it gives me error code 80070643. I cannot find much to solve this problem. Update rollup 8 installs fine. I've read on internet that every rollup must be installed to succesfully install exchange
2010 sp3. Can anyone help me with this error?

I just installed exchange 2010 sp3, but it does not finish. It stops at 'client access role'
This is in the log;
[10-08-2014 21:55:24.0121] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'server.company.com', Preferred Global Catalog: 'server.company.com', Preferred Domain Controllers:
'{ server.company.com }'
[10-08-2014 21:55:24.0121] [2] Beginning processing Start-SetupProcess -Name:'iisreset' -Args:'/noforce /timeout:120'
[10-08-2014 21:55:24.0137] [2] Starting: iisreset with arguments: /noforce /timeout:120
[10-08-2014 21:55:31.0640] [2] Process standard output: Attempting stop...
Internet services successfully stopped
Attempting start...
Restart attempt failed.
The IIS Admin Service or the World Wide Web Publishing Service, or a service dependent on them failed to start. The service, or dependent services, may had an error during its startup or may be disabled.
Process standard error:
[10-08-2014 21:55:31.0640] [2] [ERROR] Unexpected Error
[10-08-2014 21:55:31.0640] [2] [ERROR] Process execution failed with exit code 1062.
[10-08-2014 21:55:31.0640] [2] Ending processing Start-SetupProcess
[10-08-2014 21:55:31.0640] [1] The following 1 error(s) occurred during task execution:
[10-08-2014 21:55:31.0640] [1] 0. ErrorRecord: Process execution failed with exit code 1062.
[10-08-2014 21:55:31.0640] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 1062.
[10-08-2014 21:55:31.0640] [1] [ERROR] The following error was generated when "$error.Clear();
Start-SetupProcess -Name "iisreset" -Args "/noforce /timeout:120"
" was run: "Process execution failed with exit code 1062.".
[10-08-2014 21:55:31.0640] [1] [ERROR] Process execution failed with exit code 1062.
[10-08-2014 21:55:31.0640] [1] [ERROR-REFERENCE] Id=ClientAccessServiceControl___ef7fa14362774cd9af8882d6287b640a Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[10-08-2014 21:55:31.0640] [1] Setup is stopping now because of one or more critical errors.
[10-08-2014 21:55:31.0640] [1] Finished executing component tasks.
[10-08-2014 21:55:31.0672] [1] Ending processing Install-ClientAccessRole
Anyone has any ideas?

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 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

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

Error 1603 when installing Rollup 4 for Exchange 2010 SP2

Hi There,
I have began upgrading our Exchange servers to Rollup 4 for Exchange 2010 SP2 last week and the first 3 servers all successfully installed it without any problems. However I have hit a problem with my 4th server.
I am receiving the 'common' error 1603 in my Application log and I have already ran through many potential fixes to this problem on various posts on this and other forums, but to no avail.
I have tried the following without success:
Turning off UAC
Running from elevated CMD prompt
Running from elevated Powershell command
Removing and re-adding "Exchange Trusted Subsystem" from the Administrators group
Re-downloading the RU4 install package to the local disk on the server
Adding more RAM and CPU resources
I have watched the installation process and it seems to update of the native assembly files and comes to the "Starting Services" process, with which it appears to do fine as I have watched the Services starting within Server Manager while this has been running,
but then all of a sudden just begins "Rolling back actions".
The only difference with this server to the others is the fact that a colleague of mine had to recover this server within the last 6 months and ran the Setup /m:RecoverServer command
to do so, could this have anything to do with it?
I have installed Exchange 2010 Service Pack 2 on this server since the recovery though.
I am running out of ideas so any help would be greatly appreciated.

skippy-85,
Any updates on this Issues?
In case if the issue stands
resolved, Please mark Solution for this Thread and close this.
In case if you still have
the issue with the RU4 installation do let us know!
Thanks
Exchangeexperts.in ~ ( Exchange | 2003/2007/2010/E15(2013)) ~Mark this if Helpful~ This Information is provided "AS IS" and confers no Rights!!

Rollup 8 for Exchange 2010 SP2 causes EWS error with bad parameter for Exchange.MailboxReplicationService.ProxyService

When I installed Rollup 8 for Exchange 2010 SP2 it caused an error in EWS
EWS failed with the error:
exchange web service could not load file or assembly Exchange.MailboxReplicationService.ProxyService bad parameter
When I uninstalled the rollup all worked fine again.
Any ideas, Thanks in advance?

Hi,
To apply this update rollup, you must have Exchange Server 2010 SP2 installed. And remove all interim updates for Exchange Server 2010 SP2 before you apply this update rollup. Please check your installation deployment by the following article:
Install the Latest Update Rollup for Exchange 2010
http://technet.microsoft.com/en-us/library/ff637981.aspx
Description of Update Rollup 8 for Exchange Server 2010 Service Pack 2
http://support.microsoft.com/kb/2903903/en-us
If all requirements and preparations are configured properly, please collect your error logs to check your installation. It would be helpful to post some event logs here for further analysis.
Thanks,
Winnie Liang
TechNet Community Support

Outlook 2010 SP1 Profile Does Not Update After Moving Mailbox Between Exchange 2010 SP2 Sites

I am working on a large mailbox migration from one AD site to another.
Exchange version at both sites:Exchange 2010 SP2
Two Mailbox Servers: MBX01 in site A / MBX02 in site B
(There is a DAG but keeping this simple)
Two CAS Arrays: CASA.domain.com / CASB.domain.com
The RPCClientAccessServer property is set accordingly. Where MBX01 is set to CASA.domain.com and MBX02 is set to CASB.domain.com
Clients:Outlook 2010 SP1
Scenario: I successfully move a mailbox from Site A to Site B. The Outlook client does not automatically update its server settings to point to the new cas array (CASB.domain.com) and continues to connect to the old CAS server (CASA.domain.com).
I have seen a few articles regarding this pointing to workarounds such as:
- repairing the outlook profile on the client
- delete the existing outlook profile
- run a script to update the prf file (re-cache's email at the client)
I am interested in knowing if anyone else has experienced this, what their solution was for a large migration and if any roll-ups or service packs have possibly fixed this problem.
I would also like to know if you have seen this affect ActiveSync devices. I am getting mixed results in my tests and thought it may be contributed toward different device types, mobile os versions, etc...
I have posted this to the Exchange 2010 forum as well, just wasn't sure where to start.
Thanks.
Mike

Hi,
Seems you got several replies in the thread below that you posted in Exchange forum:
http://social.technet.microsoft.com/Forums/exchange/en-US/68ae67c1-59f5-44bb-aadc-0aea3f72ad2d/outlook-profile-not-updated-to-new-cas-array-after-mailbox-move-between-sites?forum=exchange2010#68ae67c1-59f5-44bb-aadc-0aea3f72ad2d
Please come back to the thread above and check if the replies are helpful.
Since this issue is more related to Exchange, we can provide rarely assistance on this problem. If you need any help on Outlook client side, please don't hesitate to let me know.
I would appreciate it if you could post the solution here when you found it, so that other community members who have same question in this forum will benefit from it.
Best Regards,
Steve Fan
TechNet Community Support

Exchange 2010 - Issues after rollup update installation.

Exchange 2010 - Issues after rollup update installation.
We are having issues since we installed SP3 Rollup updates 1, 2, 3, and 4.
Issue1 - People get an error messages constantly popping up when they access our webmail. The error messages are:
An unexpected error occurred and your request couldn't be handled. and
Your network connection is unavailable. Please reconnect and try again.
Issue2 - When I open the Exchange Management Shell I get the following error:
Failed to connect to an Exchange server in the current site. Enter the server FQDN where you want to connect.
Issue3 - We have been using third party software to filter spam email. It is installed on our Exchange server. Since the updates it has not been working and we have tons of spam coming through. I dont think that this issue is that important at the moment and
hope that it will be fixed after resolving issues 1 and 2.
We uninstalled all four rollup updates in hopes that everything would go back to normal but it hasnt. We still have the same issues.
Currently we are running Exchange 2010 SP3 on 2008R2 SP1.
Please help.
Thanks.
Greg

Hi,
Based on the description, you got the error below when you tried to accessed OWA after rollup update installation.
"An unexpected error occurred and your request couldn't be handled, and Your network connection is unavailable. Please reconnect and try again."
For this issue, I recommend you check the OWA virtual directory to see if "Redirect requests to this destination" is checked. If it is checked, please uncheck the option. Then please restart IIS service to check the result.
Open IIS Manager -> owa -> HTTP Redirect -> uncheck "Redirect requests to this destination:"
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Upgrade Exchange 2010 SP2 to SP3 getting fail

Hi,
I am trying to upgrade from exchange 2010 SP2 to SP3, but it getting failed.
I have already run the prepare schema, prepare and domain prep in all domains and it got replicated in DR Domain controllers.
But, still i am not able to upgrade the server. The error says,
Preparing Exchange Setup
    Copying Setup Files                           COMPLETED
The following server roles will be upgraded
Languages
Hub Transport Role
Client Access Role
Management Tools
Performing Microsoft Exchange Server Prerequisite Check
    Configuring Prerequisites                                 COMPLETED
    Organization Checks
FAILED
     Setup needs to contact the Active Directory schema master but this computer
is not in the same Active Directory site as the schema master (Default-First-Si
te-Name).
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have been created but have not yet replicat
ed to the local domain. Wait for replication to complete and then run setup aga
in.
    Language Pack Checks
COMPLETED
    Hub Transport Role Checks                                 FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have been created but have not yet replicat
ed to the local domain. Wait for replication to complete and then run setup aga
in.
    Client Access Role Checks                                 FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have been created but have not yet replicat
ed to the local domain. Wait for replication to complete and then run setup aga
in.
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
Exchange Server setup encountered an error.
Thanks,
San

Hi,
Schema updates should be done on a schema master or on a DC in the same AD site as the schema master. Once extended, the updates will replicated via AD replication. To narrow down the issue, I recommend you check if there is any event related to replication
on domain controller holding schema master role.
Is the schema master role in the same site as the Exchange server which you want to upgrade? If not, you can try to transfer FSMO role to a domain controller which is in the site where you want to install Exchange 2010 SP3 and then upgrade to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Applying Windows 2008 R2 SP1 on Exchange 2010 SP2 servers

Hi All,
Our current setup is Primary Site and DR site with a DAG.
Primary site is having 2 Mailbox servers, 2 hubcas servers with an NLB and one CAS server for OWA.
DR Site is having 1 mailbox server, one hubcas server and one CAS server. All these exchange servers are SP2 with update roll up5.
But the OS is Windows 2008 R2, need to apply Windows 2008 R2 SP1 on these servers, and what are things to be considered.
Does this affect CAS servers IIS?
Thanks,
Kanishka.

Agreed. One thing to mention - Win 2008 R2 needed SP1 a while back, no security updates have been released for a while.
Exchange 2010 SP2 goes out of support next month. please plan to update to SP3 for Exchange 2010.
http://blogs.technet.com/b/rmilne/archive/2013/10/08/save-the-date-end-of-exchange-2003-support-t-minus-6-months.aspx
The details for that, and a link to the lifecycle page are in the above post.
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.

Exchange 2010 SP2 UR8 Build number

After upgrading to Exchange 2010 SP2 UR8 from SP2 UR6 the build number shows 14.02.0387.000 instead of
14.2.390.3 as detailed in MS documentation. Is this expected behavior?

Yes, that is expected.
AdminDisplayVersion doesn't change when a rollup is installed.
Dude, where's my rollup?
http://blogs.technet.com/b/exchange/archive/2010/03/08/3409469.aspx
Martina Miskovic

Exchange 2010 SP2, Update Rollup 7

Similar Messages

Maybe you are looking for