Update Exchange 2010 - Things to Consider?

I also like to run BPA and check the event logs and system resources before installing any Exchange updates. If the VM has been up for a while, give it a reboot first. I usually check the release notes too: https://support.microsoft.com/en-us/kb/3049853

We haven't updated our exchange 2010 server in a long time.
In the Update queue is 'Update Rollup 10 for Exchange Server 2010 Service Pack 3'
Anything to consider or watch out for before pulling the trigger?
It's running on Server 2012 standard as a VM.
Thanks for all input!
This topic first appeared in the Spiceworks Community

Similar Messages

Updating exchange 2010 accounts after provisioning

Hi Guys,
I am looking for the information on modifying exchange 2010 accounts information once we provisioined an exchange 2010 account.
For example, renaming the mailbox in exchange2010 when there is a change in the lastname like that. All of the "UPDATED" tasks
were given as "Required for completion". So, did not understand how the "UPDATED" tasks will work.
Will exchange 2010 support email attribute as multi-valued?
And how the move mailbox will work? Please provide some information.
Thanks for your help.

In exchange connector, all of the UPDATED tasks were given as required for completion. I believe required for completion will needed only for create user task not for all of the updated tasks.It depends on the requirement. Generally we make these task as Required for Completion only.
If I want to update exchange 2010 mailbox, I just need to update mail atribute in AD. Is that correct?Right now, I am not sure which attribute we have to modify for renaming mailbox and whether it is supported with OOTB connector or not.
If not then you need to extend the connector functionality but I have seen couple of threads on Google which talks about Renaming Mailbox in Exchange.
And
So, did not understand how the "UPDATED" tasks will work.SO I have given you link that how OIM triggers UPDATED task in any Process Defn.
Required for Completion means: Whether task should be completed for completing the process/operation or not. It is nothing to do with UPDATED Task trigger.

Need to update Exchange 2010 to SP1 from base

I need to update my base install of Exchange 2010 to SP1 and eventually SP2. This sits on a 2008 R2 server. in reading other upgrade articles, there are references to needing hotfixes at the server level - 2008 R2. There are about 5 hot fixes referenced
to upgrade to SP1 and I would assume there are a few others for the update to SP2.
Currently the 2008 R2 server is patched via Windows update through February 2014 (including SP1 for the server). Given that, can I assume that the hot fix updates have been incorporated into other updates/patches along the way for the Windows 2008 R2
server? Or do i still have to install each of those hotfixes manually?
Also, in one of the patches, it spoke of needing, or using .net framework 2.0 and 3.51. currently my system has 4.5.1 on it. do i need 2.0 and 3.51 for SP1 to be installed and work correctly?
thanks
dave

Hi Dave,
I recommend you install Exchange 2010 SP3 directly. There is no need to upgrade to Exchange 2010 SP1 and then to SP2.
Service Packs are cumulative, Exchange 2010 SP3 include all fixes included in previous RUs and service packs. Here is a blog for your reference.
Released: Exchange Server 2010 SP3
http://blogs.technet.com/b/exchange/archive/2013/02/12/released-exchange-server-2010-sp3.aspx
Since Windows updated through February 2014, you don't need to install each of those hotfixes manually.
Besides, I would like to verify if you download .net framework 4.5.1 from website. There is no need to install it that way. You just need to open Server Manager, add .Net Framework 3.5.1 feature.
Hope my clarification is helpful.
Best regards,
Amy
Amy Wang
TechNet Community Support

Updating Exchange 2010 to SP3

Hi,
I'm going to install Sp3 on my Exchange 2010 server today. I've already done the install on my test system and it went fine.
I have a question though. I am running a DAG. The docs I find online all say to move the databases to another node when running the update. Is this solely to keep users up and running or is it necessary to to in order for the upgrade to run properly.
I ran the upgrade on TEST without moving databases around and it seems to have worked fine (only a few users on my TEST system though).
Thanks,
Nacht

If you are running a DAG, your databases would automatically fail over when the system is rebooted. However, if you don't want any surprises, it's common practice to move everything over prior to the patching, then move back afterward. Here's a typical patching
process:
Mailbox Server patching procedures (patch DR Servers first, then Mailbox Servers last):
Install update on DR servers and reboot
On the A node in the primary site, open EMS and run this command to check the status of indexes:
Get-MailboxDatabaseCopyStatus | Fl name, contentindexstate
It should look like this for all databases:
Name
: DB01\ServerA
ContentIndexState : Healthy
If the content index state is not healthy, run this command for each database that isn't healthy:
Update-MailboxDatabaseCopy "DB01\ServerA" -CatalogOnly
Repeat this check on the B node for the primary site, and if all is healthy, proceed to next step
On the A node in the primary site, open EMS and move active mailbox databases to the B node:
Move-ActiveMailboxDatabase -Server ServerA -ActivateOnServer ServerB -MountDialOverride:none -confirm:$false
Refresh EMC and select each DB moved, then check copy status, copy queue length and replay queue length (everything should be healthy or mounted and all queues should be at
zero)
Once databases are verified running on the B node, install patch/update on A node and reboot
Check event logs and services on the A node once it's back online
On the B node, open EMS and move all databases from B to A
Open or Refresh EMC and select each DB moved, then check copy status and queues
Once databases are verified running on the A node, install patch/update on the B node and reboot
Check event logs and services on the B node once it's back online
On the A node, open EMS and browse to
D:\Program Files\Microsoft\Exchange Server\V14\Scripts> and run this script to automatically put all databases on A node that have an activation preference of 1 on that server and leave all databases
on the B node that have an activation preference of 1 for that node
.\RedistributeActiveDatabases.ps1 -DagName DAG1 -BalanceDbsByActivationPreference -confirm:$false
Check Failover Cluster Manager:
On one of the mailbox servers, go to Start > Failover Cluster Manager, expand the DAG, then click on DAG1.contoso.local
Current Host Server (which server holds the Primary Active Manager role) should be either the A or B node. If it is the DR node, run the following command from an elevated command prompt:
cluster.exe DAG1.contoso.local group “Cluster Group” /moveto:ServerA (or ServerB)

Update Exchange 2010 from 14.1.218.15 to SP2

HI All,
We are using Exchange server 2010, it is recently deployed in the production environment, I want to know what is the process to apply patches and SP update on exchange server.
As we are running exchange 2010 SP1 14.1.218.15 and should I apply SP 2 diretly on it or I have to apply from
Update Rollup 1 to Update Rollup 7-v3 for Exchange Server 2010 SP1
first and then apply SP2,
Your suggestions are required.
Regards
Sameer

As lynn said you don't need to apply RU's as you can directly install the latest service pack.
Please note that Support for SP1 & SP2 (Exchange 2010) is ended and hence i recommend you to upgrade to SP3.
You should upgrade your Exchange 2010 server roles in the following order:
Client Access
Hub Transport
Unified Messaging
Mailbox
Edge Transport
Also, while patching CAS Servers, Internet Facing CAS Servers should have to be patched first. In case if you have CAS Servers in CAS Array then you will have to remove the CAS Server from the array while patching and should add CAS Server back to CAS Array
after patching/reboot.
For more information about patching/upgrading exchange you can refer: https://technet.microsoft.com/en-in/library/bb629560(v=exchg.141).aspx
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!!

Updating Exchange 2010 SP2 to SP3

Hi,
I'm trying to migrate our Exchange 2010 to Exchange 2013 to different server but first I need to update it. I managed to update from SP1 to SP2 without any major problems but now I'm trying to update form SP2 to SP3.
Update fails when it goes to Client access role phase. In ExchangeSetup log I have following error messages:
[07.03.2014 07:39:27.0982] [2] Active Directory session settings for 'precompile-ManagedBinary' are: View Entire Forest: 'True', Configuration Domain Controller: 'MASTER.domain.local', Preferred Global Catalog: 'MASTER.domain.local', Preferred Domain Controllers: '{ MASTER.domain.local }'
[07.03.2014 07:39:27.0982] [2] Beginning processing precompile-ManagedBinary -BinaryName:'C:\Program Files\Microsoft\Exchange Server\V14\bin\microsoft.exchange.addressbook.service.exe'
[07.03.2014 07:39:27.0982] [2] Starting: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe with arguments: install "C:\Program Files\Microsoft\Exchange Server\V14\bin\microsoft.exchange.addressbook.service.exe" /queue /nologo /verbose
[07.03.2014 07:39:28.0247] [2] Process standard output: Installing assembly C:\Program Files\Microsoft\Exchange Server\V14\bin\microsoft.exchange.addressbook.service.exe
Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))
[07.03.2014 07:39:28.0263] [2] Process standard error:
[07.03.2014 07:39:28.0263] [2] Process standard error: Retry(1/3): exception: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code -1.
[07.03.2014 07:39:29.0292] [2] Process standard output: Installing assembly C:\Program Files\Microsoft\Exchange Server\V14\bin\microsoft.exchange.addressbook.service.exe
Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))
[07.03.2014 07:39:29.0292] [2] Process standard error:
[07.03.2014 07:39:29.0292] [2] Process standard error: Retry(2/3): exception: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code -1.
[07.03.2014 07:39:30.0322] [2] Process standard output: Installing assembly C:\Program Files\Microsoft\Exchange Server\V14\bin\microsoft.exchange.addressbook.service.exe
Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))
[07.03.2014 07:39:30.0322] [2] Process standard error:
[07.03.2014 07:39:30.0322] [2] Process standard error: Retry(3/3): exception: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code -1.
[07.03.2014 07:39:31.0367] [2] Process standard output: Installing assembly C:\Program Files\Microsoft\Exchange Server\V14\bin\microsoft.exchange.addressbook.service.exe
Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))
[07.03.2014 07:39:31.0367] [2] Process standard error:
[07.03.2014 07:39:31.0367] [2] [ERROR] Unexpected Error
[07.03.2014 07:39:31.0367] [2] [ERROR] Process execution failed with exit code -1.
[07.03.2014 07:39:31.0367] [2] Ending processing precompile-ManagedBinary
[07.03.2014 07:39:31.0367] [1] The following 1 error(s) occurred during task execution:
[07.03.2014 07:39:31.0367] [1] 0. ErrorRecord: Process execution failed with exit code -1.
[07.03.2014 07:39:31.0367] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code -1.
[07.03.2014 07:39:31.0367] [1] [ERROR] The following error was generated when "$error.Clear();
$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\microsoft.exchange.addressbook.service.exe");
precompile-ManagedBinary -BinaryName $fullPath;
" was run: "Process execution failed with exit code -1.".
[07.03.2014 07:39:31.0367] [1] [ERROR] Process execution failed with exit code -1.
[07.03.2014 07:39:31.0367] [1] [ERROR-REFERENCE] Id=AddressBookComponent___6f3e1aaa7a2d468a9f3e83382ec479b2 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[07.03.2014 07:39:31.0383] [1] Setup is stopping now because of one or more critical errors.
[07.03.2014 07:39:31.0383] [1] Finished executing component tasks.
[07.03.2014 07:39:31.0383] [1] Ending processing Install-ClientAccessRole
I have tried couple of times and rebooted the server without success. Any help?
Thank you.

Hi,
I'm running SBS2011 and was not able to use ExBPA.
I ended to create new domain + exchange to my enviroment since I had backed up data from server previously.
Thank you

Updating Exchange 2010 SP2 to SP3UR9

Dear Experts,
I am currently preparing my SBS 2011 for a migration to Server 2012 R2 with Exchange 2013 installed. On my SBS 2011 I ran the Best Practices Analyzer 1.3 and it mentions that "the most recent Update Rollup is not installed". In the Exchange
Management Console I see that I have Version 14.2 (Build 247.5) installed.
I have seen that there is an Exchange SP3 along with Update Rollup 9 available. I have installed all Windows Updates - no Exchange rollups were installed. Should I update to 2010SP3UR9? How do I best perform this update - install 2010SP2RU8, then 2010SP3
and finally 2010SP3UR9?
Thanks for your help.

You have to upgrade to 2010 SP3 first, then upgrade to the latest RU after that.
I would also ask in the SBS forums as sometimes there are special considerations around upgrades.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Change to Exchange 2010 after SP3, Update 5 installed

After updating Exchange 2010 from SP3 Update 2 to Update 5, a change has occurred for users with SendAs and Full Access to other mailboxes. Version 14.3 (build 123.4).
Before the Update, after giving a user these permissions to another user's mailbox, the mailbox would show in their Outlook 2010 client, and everything worked as expected.
After Update 5 was installed, when users select the other user's mailbox, they get a message "the folders are not available," or the connection to the Exchange server is not working." They can access their own mailbox with no issues.
The other mailbox has to be added to the Outlook client via Account Settings, Account Settings, Change, More Settings, Advanced tab, Add the other mailbox. The mailbox then shows up twice on the client, but only the one that has been added works,
the original still gives the same error.
Lou H.

Hi,
I have seen some people have the same issue with you. After upgrading to Rollup 5, they need to add others' mailboxes that they have full access permission and send as permission manually on Outlook. But when they upgrade Outlook to 2010 SP2, this issue
is solved. I recommend you upgrade your Outlook to 2010 SP2 and check the result.
Besides, I'm not sure what changes after Rollup 5 lead to this issue, there is no official article explain it, thanks for your understanding.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exchange 2010 coexist with exchange 2013

Hi All ,
Planning to have a coexistence scenario in my environment which is mentioned below
Exchange 2010 - ambiguous url in place - OA enabled
For mapi/rpc traffic - mail.domain.in - exchange 2010
For https traffic - mail.domain.in - exchange 2010
mail.domain.in will get resolved in to cas array in exchange 2010 .
After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining
exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.
just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.
Note :
On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in
Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in
Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010
exchange server via exchange 2013 server.
question : I would like to know above mentioned scenario is possible or not ?
On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.
So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.
All of you tell me your valuable suggestions.
Regards
S.Nithyanandham

Hi,
Going Straight to the point... and answering your question...
The scenario above IS possible For a while... But going ahead in the migration process, You'd face problems once the Exch2013 doesn't know how to handle MAPI connections:
As per Exchange Team...
In this scenario where both the MAPI/RPC and HTTP workloads are using the same FQDN you cannot successfully move the FQDN to CAS 2013 without
breaking your MAPI/RPC client connectivity entirely. I repeat, your MAPI/RPC clients will start failing to connect via MAPI/RPC once
their DNS cache expires after the shared FQDN is moved to CAS 2013.
As their recommendation, and I would tell you too by experience, the best option is to really use different internal and external URLs for the clients to connect to.
change your design to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous
URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values
on all Exchange 2010 mailbox databases accordingly. Fixing this item mid-migration to Exchange 2010 or even in your fully migrated environment will ensure any newly created or manually repaired Outlook profiles are protected, but it will not automatically
fix existing Outlook clients with the old value in the server field.
So the overall for this first point is to enable the OA for all internal users, so as to ease the migration process in the future, even if for the time being its not necessary.
Also another point you should take into consideration is the version of yours OLK versions, as the minimum supported are as per below:
Outlook 2007: 12.0.6665.5000 (SP3 + the November 2012 Public Update or any later PU)
Outlook 2010: 14.0.6126.5000 (SP1 + the November 2012 Public Update or any later PU)
Outlook 2013: 15.0.4420.1017 (RTM or later)
I don't know the size of you network, but it might be necessary for you to use an inventory tool in order to identify that.
As advised, its really worthy to have a look at the following article, thus to clarify your view about this issue.
Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
From <http://blogs.technet.com/b/exchange/archive/2013/07/17/3574451.aspx>
Hope it can help you!
Cheers,
Think before you ask, give detail as much as possible, then ask and you will get help! Always have in mind, people do not guess! :)

Exchange 2010 - 2013 Coexistence Issues

I am migrating from Exchange 2010 to Exchange 2013, the Exchange 2013 is built in a different Geo-location site with its dedicated domain controllers in the new site. I have confirmed the mail flow between Exchange 2010 and 2013 mailboxes. I am able to discover
Exchange 2010 servers from 2013 environment via Get-ExchangeServer shell command. However, I am not to discover Exchange 2013 servers from 2010 environment.
I need to configure Outlook Anywhere and Service Connection Point (Autodiscover) on Exchange 2010 to accept connections from Exchange 2013 servers.
Any suggestions would be much appreciated, thanks!

Hi ,
Please have a look in to the below mentioned blog after reading that blog i came to know few things .
I am not sure ,i thought exchange 2013 servers will not be displayed in exchange 2010 management shell.
Better and advisable method is to configure your exchange 2010 and 2013 servers via EAC or Shell in exchange 2013.
http://exchangeserverpro.com/exchange-server-2010-2013-migration-managing-co-existence-environment/
Taken from the above blog :
You can’t use the Exchange 2010 EMC to manage Exchange 2013 objects and servers. While customers upgrade to Exchange 2013, we encourage them to use the EAC to:
Manage Exchange 2013 mailboxes, servers, and corresponding services.
View and update Exchange 2010 mailboxes and properties.
View and update Exchange 2007 mailboxes and properties.
We encourage customers to use Exchange 2010 EMC to create Exchange 2010 mailboxes.
We encourage customers to use Exchange 2007 EMC to create Exchange 2007 mailboxes.
Customers can continue to perform management tasks using the Exchange Management Shell and script tasks.
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Outlook 2013 Category view not updating after Exchange 2010 SP3 RU3

After updating to Exchange 2010 SP3 RU3 last night, users who use categories view in Outlook 2013 are complaining that the view does not update. The alert is received in the notification area and the unread message count next to Inbox updates appropriately.
The view can be force updated by switching between All and Unread, by using Reset View, or closing and opening Outlook. It seems anything that forces a 'redraw' of the view will update it - except for the actual reception of email. I easily replicated
this issue. For reference:
Exchange 2010 SP3 RU3
Windows 7 x64 Ent
Outlook 2013 (15.0.4551.1004) 32-bit
I do see that SP3 RU4 has been released, however the only change listed is a security patch.
Thank you for any ideas.

Hi, Everyone –
This has been a known issue for a very long time – we have people at our workplace that are very disappointed since a feature as great as categorizing email (not using tasks) has become broken and has not even been considered to be fixed for
over half a year. It was not fixed in the updates for Patch Tuesday this week.
I would like to confirm that this is an issue with Outlook 2010 and 2013 when running the latest Exchange 2010 and there is NO FIX
– I have scoured the internet for a solution – all proposed "textbook" solutions do not work and I am positive that the issue can be recreated; however, everyone from Microsoft does not mention trying to recreate the issue at all.
The workaround of creating a rule to send new emails to a category could break other pre-existing rules and cause more frustration and wasted time for users/IT before and after the issue is fixed.
Please fix this issue sooner than later, as the Categories view is completely broken and unusable at this point in time.
Regards,
IT Helper

AutoDiscover not working after Exchange 2010 SP2 - SP3 update.

Hi Everyone,
I'm sorry if this is a really simple thing, but i've played around for hours and exhausted google.
I run a 2010 exchange server for everyone at the office, and today I updated from 2010 SP2 to SP3.
The problem I have is auto discover no longer accepts anyones username or password. If you set the account up on the client machine by manually entering the details everything works great.
All the DNS records are correct and have been working for 2+ years. I have recreated the Autodiscovery virtual directory in EMC.
If i manually browse to mydomain/Autodiscover/Autodiscover.xml, when asked for a username and password it says it incorrect. I can then log in to OWA with the same credentials and it works.
Thanks,
Garrett
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://mydomaincom.au:443/Autodiscover/Autodiscover.xml for user mydomain.com.au.
The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
Additional Details
An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).
HTTP Response Headers:
Transfer-Encoding: chunked
Connection: keep-alive
Content-Type: text/html
Date: Wed, 22 Apr 2015 00:44:51 GMT
Set-Cookie: __cfduid=dc0261b4643b5dbe27f750bbc28bfef7c1429663490; expires=Thu, 21-Apr-16 00:44:50 GMT; path=/; domain=.macarthurcs.com.au; HttpOnly
Server: cloudflare-nginx
WWW-Authenticate: Negotiate,NTLM,Basic realm="mydomain.com.au"
X-Powered-By: ASP.NET
CF-RAY: 1dad4d701ae911c5-SJC
Elapsed Time: 3357 ms.
Attempting to test potential Autodiscover URL https://autodiscover.mydomain.com.au:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.

Hi,
Based on my knowledge, the above issue is caused by the loopback check being enabled. Please follow the steps below to disable loopback on the CAS servers:
1. Run regedit, in Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
2. Right-click Lsa, point to New, and then click DWORD Value.
3. Type DisableLoopbackCheck, and then press ENTER.
4. Right-click DisableLoopbackCheck, and then click Modify.
5. In the Value data box, type 1, and then click OK.
6. Quit Registry Editor, and then restart your computer.
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support

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

Just updated to my macbook pro to 10.8.2. ical not synching with my Exchange 2010 server. Worked flawlessly prior to the upgrade. Settings set to auto discover. I matched settings of a partner in my who is still using 10.7.1 without issues. Help!

Just updated to my macbook pro to 10.8.2. ical not synching with my Exchange 2010 server. Worked flawlessly prior to the upgrade. Settings set to auto discover. I matched settings of a partner in my who is still using 10.7.1 without issues. Help!

Also - my battery has been telling me "service battery" for a LONG time and then it switched to "replace soon" som time ago. Can't really see what this has to do with anything but whatever.
That could conceivably explain all the problems you're describing. Replacing a Mac's battery should not be postponed since a failed battery will cause other problems to occur. It is also possible that its hard disk has failed, which means the information on it may soon become unrecoverable.
... my latest TM back up was from April 2014, can I just run this when I have rescued everthing and then it might not be as slow?
If that Time Machine backup remains intact, it may be the only viable means of recovering that Mac's information. I suggest you do not attempt to restore its contents to your ailing Mac.
Given that you are having trouble creating a newer Time Machine backup you should stop using that Mac immediately and have it serviced as soon as you are able. Do not take it to anyone other than Apple or a service facility authorized by Apple, for the very reasons you explained. If there are no Apple Stores in your vicinity search for an Authorized Apple Service Provider using the Contact Us link below. Use one of the options that appear under Contact Apple Support. The language on that page will be different for your location.

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.

Update Exchange 2010 - Things to Consider?

Similar Messages

Maybe you are looking for