Exchange 2010 Sp3 AD Schema Changes

I am looking for a listing of Active Directory Schema Updates that Exchange 2010 SP3 makes. We are currently on SP1, and we will most likely end up at SP2 RU6, but if the changes are minimal to SP3, we may go ahead and extend the AD Schema to SP3 just
so we don't need to involve the AD Team again. Does anyone know where to find a complete list of AD Schema updates from Exchange 2010 SP3? I've checked:
Exchange Server changes to the Active Directory Schema webpage, but it does not have SP3, only Sp2.
Any help would be GREATLY appreciated.
Thanks!
Mark Currans

Please ensure that SP3 has been tested and validated by all the 3rd party apps and services in your org. You do not want to install it to find out that vendor X will no longer support you.
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.

Similar Messages

Exchange 2010 SP3 upgrade

Dear Exchange admin,
We tried to upgrade Exchange 2010 SP1 to Exchange 2010 SP3 .In HQ site all preparation finished smoothly.
But in DR we are unable to do even preparation.We are getting the following error.
Please advice me how can proceed.
Summary: 4 item(s). 2 succeeded, 2 failed.
Elapsed time: 00:00:37
Configuring Prerequisites
Completed
Elapsed Time: 00:00:00
Organization Prerequisites
Failed
Error:
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-Site-Name).
Click here for help... http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=2376fec1-b9ce-44db-beb6-cb9ac4788988
Error:
Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run
setup with the /prepareAD parameter on a computer in the domain kfupm and site Default-First-Site-Name, and wait for replication to complete.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
Elapsed Time: 00:00:14
Languages Prerequisites
Completed
Elapsed Time: 00:00:04
Mailbox Role Prerequisites
Failed
Error:
Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run
setup with the /prepareAD parameter on a computer in the domain kfupm and site Default-First-Site-Name, and wait for replication to complete.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
Error:
Setup cannot continue with the upgrade because the 'mmc' () process (ID: 4508) has open files. Close the process and restart Setup.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
Error:
Setup cannot continue with the upgrade because the 'powershell' () process (ID: 3808) has open files. Close the process and restart Setup.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
Error:
Setup cannot continue with the upgrade because the 'mmc' (4508) process (ID: ) has 'Microsoft.Exchange.Management.SnapIn.Esm.dll' loaded. Close the process and restart setup.
Click here for help... http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=f0d3f291-5a52-43ea-9121-24aa7cd0c30e
Warning:
Install hotfix Microsoft Knowledge Base article 2550886 from http://support.microsoft.com/kb/2550886 to improve Windows Failover Cluster transient communication instability when deploying stretched Database Availability Groups across datacenters.
Elapsed Time: 00:00:18
Ashraf

Hi Ashraf
Thank you for your question.
Exchange update cannot continue because the computer that is running update is not in the same Active Directory site or domain as the server that is assigned the domain schema master role, also known as flexible single master operations or FSMO.
You can refer to the following link to change exchange site schema:
http://technet.microsoft.com/en-US/us-cn/zh-hans-cn/library/2376fec1-b9ce-44db-beb6-cb9ac4788988.aspx
You also notice the order for updated:
1.Client Access servers (beginning with the internet-facing site)
2.Hub Transport and Edge Transport servers
3.Mailbox servers
4.Unified Messaging servers
You can refer to the following link to update:
http://exchangeserverpro.com/installing-exchange-server-2010-service-pack-3/
If there are any questions, please let me know.
Best Regard,
Jim

Exchange 2010 SP3 install

Hi,
I am running with Exchange 2010 SP1 in DAG & CAS/HUB in cluster mode. need to upgrade to SP3. few things need to know
1. Schema upgrade will be done I as read in the article. can this create any issue? what is the best measure to safeguard any problems of schema upgrade. Do we do this along with exchange setup or we should run schema upgrade prior to install exchange 2010
SP3?
2. Any impact on active sync, outlook anywhere & HUB connectors side post SP3?
3. Do we need to take any exchange related backups as we are running mailbox, CAS/HUB servers in redundant mode?
Please share your experiences.
Regards,
VIpin

Hello,
1. It is a good practice to run schema updates before launching Exchange update. You should also make backups of your domain controllers before any schema updates because these
particular changes cannot be rolled back easily.
3. Yes, you should have backups (tested!) of your Exchange servers. Server's redundancy (DAG's, CAS Arrays etc) doesn't protect your servers if the update fails.
Hope it helps,
Adam
www.codetwo.com
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others
find the answer faster.

Moving to a new CAS box exchange 2010 sp3 ru6

I am entertaining the idea of creating a second CAS box for our environment.
in the current environment
we have:
All servers have Exchange 2010 sp3 RU6
Ex1 (physical box) - have HUB/Transport/DAG with Ex2
Ex2 (physical box) - have HUB/Transport/DAG with Ex1
CAS1 (VM on hyper v 2008r2 cluster) - Client access role
outlook 2010 profiles all point to cas1
what I want to achieve is to build a cas2 box on a new hyper cluster. we v have a hyper v 2012r2 cluster that has a different ip scheme (cas1 ip is 12.12.100.x, and cas2 would have 12.12.103.x)
what would I need to do in order to get my users to point to the new cas box. downtime is not a major issue. but I want to make sure that if I build cas2, it would prevent cas1 from working and users getting mail. I am sadly unfamilure
because I did not set up the ex1/2 or the cas box. I have only ever installed SPs and RUs.
I have no existing CAS Array.
I would happy to read any setup docs, or anything of that nature if you have links available.
let me know what you can, and feel free to ask any further questions if you have need of additional info.
thanks
Ian
Ian

Hi,
You need to install CAS2 in existing exchange environment and need to move\change URLs OWA,EWS,Autodiscover , ActiveSync, outlookanywhere, OAB , SSL certifcates and your DNS IPs to point new CAS2.
Pls check similar threads :
http://blogs.technet.com/b/exchange/archive/2009/11/20/3408856.aspx
http://social.technet.microsoft.com/Forums/lync/en-US/faaabe2e-fafb-4d62-a01b-25c1c65bb9c4/move-cas-ht-roles-onto-a-new-exchange-server
http://social.technet.microsoft.com/Forums/exchange/en-US/40cbe4bc-8b7b-438a-9c28-668e4211acf1/moving-client-access-role-to-different-server

After Exchange 2010 SP3 upgrade, UAG publised OWA is throwing a "You do not have permissions to view this folder or page" error

Hi,
We have an issue with our OWA page. We are currently publishing OWA via UAG.
We recently upgraded to Exchange 2010 SP3 and then SP3 Rollup7. Since the upgrade, we are keep getting the following error after entering our credentials on the login page. I've tried with every possible browser.
You do not have permissions to view this folder or page
Strangely enough, the mobile phones are sending and receiving emails just fine, the phones use the same OWA link, so it's not an authentication issue, the phones login into the UAG servers with no issues. I can see this on the Active Sessions screen
on Web Monitor.
I've attempted to connect to the OWA by bypassing the UAG server, so putting in the local OWA address of one of my Exchange servers, it works... so the OWA page is up and running.
No error logs get generated on Web Monitor when we receive the permission error, I think this is because it's past authentication, it's on the Exchange layer.
Any insight would be helpful? I'm assuming something changed on the Exchange side after the upgrade.
Just in case, I've upgraded the UAG and TMG servers to the latest SP and Rollup packets.
UAG > SP4
TMG > SP2 Rollup 5

I've found a solution; UAG requires Basic Authentication over OWA. For some reason Integrated Windows Authentication got turned on after the SP3 upgrade.
http://technet.microsoft.com/en-us/library/ee921443.aspx
Turning Integrated Windows Authentication off via the Client Access OWA settings resolved the issue. Though beware, you
have do this on all your Client Access servers.

SME 7.1 not working with Exchange 2010 SP3 UR8v2 and OnTap 8.2.3 7mode

Followed IMT and installed software that NetApp said would work.Ontap 8.2.3 7-modevmWare 5.0 SP3Microsoft Windows Server 2008 R2 SP1Exchange 2010 SP3 UR8v2NetApp Host Tools 6.0.2SnapDrive 7.1.1SME 7.1 Everything connects fine. SnapDrive sees my drives. SME connects to Exchange Server. However in the process of configuring SME, I get the following error. I have followed knowledge base article and increased the timeout of DFM connection in registry, but that has not solved the problem. Has anyone run into this before? SME 6.1 works fine, but is not compatible with SnapDrive 7.1.1 (causes verifications to fail because server can't mount clone) and lower SnapDrive versions are not compatible with Ontap 8.2.3. I am in a real bind here. Thanks in advance.

the following configuration for SME 7.1 is no longer supported: Windows Server 2008 R2Exchange 2010 SP3 RU1 – RU5WMF/PowerShell 3.0SME 7.1 The supported configuration will now be: Windows Server 2008 R2Exchange 2010 SP3 RU5WMF/PowerShell 4.0SME 7.1 this is because Microsoft does not support WMF 3.0 on Server 2008 R2 running Exchange 2010 SP3, with any RU version.SME 7.1 requires a minimum of PowerShell 3.0 (part of WMF 3.0) in order to run. Feel free to review the Exchange Server Supportability Matrix located here: https://technet.microsoft.com/en-us/library/ff728623%28v=exchg.150%29.aspx. All existing documentation (ISG, Admin Guide, IMT) will be updated shortly to reflect this change in requirements. hope that helps,Domenico.

Exchange 2010 SP3 UR9 OWA users cannot open mail items

We recently had users reporting unable to open items in OWA. Issue is confirmed across all CAS servers.
Issue started while on Exchange 2010 SP3 UR8v2, we upgraded to Exchange Server 2010 SP3 UR9 during troubleshooting.
3 AD Site DAG, multi-role servers
So far we have done the following to troubleshoot:
* Check security propagation for account permissions.
* Check security on all virtual directories.
* Check permissions on web.config
* Re-run PrepareAD
* Uninstall and reinstall CAS role
Please review the errors below and let me know if you have any words of wisdom on this issue. Thanks!
Errors:
Request
Url: https://domain.com:443/owa/forms/premium/SubPageEventHandler.aspx?ae=Item&a=Preview&t=IPM.Conversation&id=CID.K5jy5dmxQru9sRoituQBvQ%3d%3d.LgAAAAD5wKVzMPRWToarE%2bpbowlJAQAqvhe3P6jjT4tregHxbY2pANbZjrf2AAAB.1DEA1tmOt%2fIAAAAAiIUWAAAAAAA%3d&calist=&canary=BV_LDf9RIkOwB1AREM0QuJ6gLZ_9QNIIWwpFOZKWH-iRvFnaQLhvOrQQBEkvAoafNX8eyWt3pOI.&SP=1&pfmk=M46%3a1427993956363&subpage=ReadConversation.ascx
User: user
EX Address: /o=company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user
SMTP Address: [email protected]
OWA version: 14.3.235.1
Mailbox server: server.domain.com
Exception
Exception type: System.UriFormatException
Exception message: Invalid URI: The format of the URI could not be determined.
Call stack
System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
Microsoft.Exchange.Security.RightsManagement.DrmClientUtils.GetServiceLocation(SafeRightsManagementSessionHandle sessionHandle, ServiceType serviceType, ServiceLocation serviceLocation, String issuanceLicense)
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetOnPremiseRmsServerUri()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetRmsServerActiveCryptoMode()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.DrmEnvironment.InitializeEnvironment()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.Initialize()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.InitializeIfNeeded()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.get_IRMConfig()
Microsoft.Exchange.Clients.Owa.Core.UserContext.get_IsIrmEnabled()
Microsoft.Exchange.Clients.Owa.Premium.ConversationUtilities.LoadConversation(UserContext userContext, OwaStoreObjectId owaConversationId, PropertyDefinition[] requestedProperties)
Microsoft.Exchange.Clients.Owa.Premium.ReadConversation.OnLoad(EventArgs e)
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Request
Url: https://domain.com:443/owa/forms/premium/SubPageContainer.aspx?ae=Item&a=Open&t=IPM.Note&id=RgAAAAD5wKVzMPRWToarE%2bpbowlJBwAqvhe3P6jjT4tregHxbY2pANbZjrf4AACsvITjR9r%2fQaXcC90BhfOwAI8oXwgBAAAJ&pspid=_1427993955843_521407833&subpage=ReadMessage.ascx
User: user
EX Address: /o=company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user
SMTP Address: [email protected]
OWA version: 14.3.235.1
Mailbox server: server.domain.com
Exception
Exception type: System.UriFormatException
Exception message: Invalid URI: The format of the URI could not be determined.
Call stack
System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
Microsoft.Exchange.Security.RightsManagement.DrmClientUtils.GetServiceLocation(SafeRightsManagementSessionHandle sessionHandle, ServiceType serviceType, ServiceLocation serviceLocation, String issuanceLicense)
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetOnPremiseRmsServerUri()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetRmsServerActiveCryptoMode()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.DrmEnvironment.InitializeEnvironment()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.Initialize()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.InitializeIfNeeded()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.get_IRMConfig()
Microsoft.Exchange.Clients.Owa.Core.UserContext.get_IsIrmEnabled()
Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.AddIrmMessageToInfobar()
Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.AddMessagesToInfobar()
Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.OnLoad(EventArgs e)
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Hi Noel,
Base on my search, it may be due to IRM feature been enabled for OWA.
I recommend you use the following command to check if the value of IRMEnabled parameter is true:
Get-OWAVirtualDirectory – Identity “servername\owa (default web site)” |FL name,IRMEnabled
If the value is true, you can use "Set-OWAVirtualDirectory" cmdlt to change it to false, and check if any helps.
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]
Niko Cheng
TechNet Community Support

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

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 Rollup 8 and Rollup 7

Hi
I have a customer with a Small Business Server 2010 with Exchange 2010 SP3.
The Customer installed updates on the server 10/12/2014 where Rollup 8 for Exchange was included.
After that the Customer has a lot of problems with connection from Outlook to Exchange and they phoned us.
We have looked on the problem and found a Microsoft article about rollup 8 where they said DO NOT INSTALL
We ran Windows Update again on the 13/12/2014 where Rollup 7 was installed
The customers still has problems with connection from Outlook.
One of the errors:
From: Systemadministrator
Sent: 15. december 2014 10:54
Subject: Unable to be delivered: Test
This message did not reach one or all of the recipients.
      Subject:     Test
      Sent:15-12-2014 10:54
Unable to deliver to the following recipient(s):
      MST the 15-12-2014 10:54
            This message could not be sent. Try to send the message again later, or contact the networkadministrator. Error [0x80004005-00000000-00000000].
Another error in Application log:
Log Name:      Application
Source:        MSExchange Common
Date:          16-12-2014 08:09:00
Event ID:      4999
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      <servername>.<domain>.local
Description:
Watson report about to be sent for process id: 9340, with parameters: E12, c-RTL-AMD64, 14.03.0224.001, M.E.RpcClientAccess.Service, M.E.RpcClientAccess.Handler, M.E.R.H.ViewCache.IsRowWithinUnreadCache, System.IndexOutOfRangeException, 8e38, 14.03.0224.001.
ErrorReportingEnabled: False
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchange Common" />
    <EventID Qualifiers="16388">4999</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-12-16T07:09:00.000000000Z" />
    <EventRecordID>174679</EventRecordID>
    <Channel>Application</Channel>
    <Computer><servername>.<domain>.local</Computer>
    <Security />
</System>
<EventData>
    <Data>9340</Data>
    <Data>E12</Data>
    <Data>c-RTL-AMD64</Data>
    <Data>14.03.0224.001</Data>
    <Data>M.E.RpcClientAccess.Service</Data>
    <Data>M.E.RpcClientAccess.Handler</Data>
    <Data>M.E.R.H.ViewCache.IsRowWithinUnreadCache</Data>
    <Data>System.IndexOutOfRangeException</Data>
    <Data>8e38</Data>
    <Data>14.03.0224.001</Data>
    <Data>False</Data>
    <Data>
    </Data>
</EventData>
</Event>
What to do ?
Best Regards
John B

Hi John,
Please type
outlook /safe in RUN to start Outlook in safe mode and then check if this issue still exists. Meanwhile, please run Exchange Best Practices Analyzer and check if find relevant issues.
à
This message could not be sent. Try to send the message again later, or contact the networkadministrator.
Error [0x80004005-00000000-00000000].
The issue typically occurs if send messages to a large number of recipients.
When this issue occurred, did you check if send message successfully via OWA?
à
We have looked on the problem and found a Microsoft article about rollup 8 where they said DO NOT INSTALL
Did you mean this article:
Exchange releases: December 2014?
à
We ran Windows Update again on the 13/12/2014 where Rollup 7 was installed
From the Event ID 4999, I noticed that point to
14.03.0224.001, it should mean the old Exchange Server 2010 SP3 Update Rollup 8. From above
mentioned article (Exchange releases: December 2014),
Exchange Server 2010 SP3 Update Rollup 8 has been re-released to the Microsoft download center resolving a regression discovered in the initial release. The update RU8 package
corrects the issue which impacted users connecting to Exchange from Outlook. The updated RU8 package is version number 14.03.0224.002. Just a confirmation, did you
reinstall that re-released Exchange Server 2010 SP3 Update Rollup 8? Any difference?
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Exchange 2010 SP3 - RU3 RU4 Public Folders issues ( not refreshing ) when grouping by Categories for "(None)" Group

After installing Exchange 2010 SP3 RU3, I had an issue in Public Folders, once having group by categories in Outlook, the Group of "(None)" categories is not refreshing when changing flag... I also installed RU4 but nothing changed, any reason
Thx

Hi,
From your description, the group with none categories won’t fresh when changing flag in Category view. If I misunderstood, please point it out.
As you can in the View tab as below, there is Category as well as Flag: Start date or Due Date. It means that grouping per color categories is more or less different from that
grouping by flag.
Should you need more assistance, feel free to tell me.
Regards,
Rebecca Tu
TechNet Community Support

Exchange 2010 SP3 upgrade - Event ID 4999 - Address Book Crash

0
I just upgraded an Exchange 2010 SP1 CAS server to SP3 - since then anytime an outlook client connects to the CAS server, the Address Book service crash's and event 4999 is logged in App log. I can reproduce the issue by attempting to create a new
outlook profile and checking the name against the CAS server. This crash's the service and the client recieves an error message. The contents of event ID 4999 is below. I've tried re-installing the CAS role, re-applying the schema extension
for SP3. I've installed all windows updates, enabled logging but I'm not getting anywhere. If anyone can help with this issue, I would greatly appreicate it.
Watson report about to be sent for process id: 10168, with parameters: E12, c-RTL-AMD64, 14.03.0123.004, M.E.AddressBook.Service, M.Exchange.Rpc, M.E.R.R.RfriRpcOperationBase.Complete, System.ArgumentException, a3e, 14.03.0123.002.
ErrorReportingEnabled: True
That error is followed by a message that the Address Book service has sucessfully started

Hello,
For exchange 2010 sp3, there is no article to explain the issue.
I suggest you run EXBPA aganist your exchange server health check.
Cara Chen
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

Force email download in HTML or text format on iPhone/iPad with ActiveSync (Exchange 2010 SP3)

Hi,
When an HTML email with attachment is received on iPhone/iPad (iOS 8.2),
it can be downloaded in three cases of
intermittents ways :
- The full message is downloaded in HTML format
- The message is download in text format and a
"Download full message" link is displayed
at the bottom of the message
- The message is displayed in text format,
but continues to download the rest of the message.
When the download is complete, the message is displayed
in HTML format.
This behavior is intermittent. The Apple's support
says it is a particular configuration on Exchange server
that causes this behavior.
I want to know if there is a way to fix
this problem and force download email
either in text or HTML format ?
This problem occurs on iPhones/iPad
(iOS8.2) with ActiveSync account (Exchange 2010
SP3). It occurs also with Outlook.com account.
On the Exchange 2010 SP3 server, The MaxEmailBodyTruncationSize
and MaxEmailHTMLBodyTruncationSize settings are
unlimited in ActiveSync policies.
Thank you for your help.

Hi,
We can configure Exchange ActiveSync Mailbox Policy Properties to force device download HTML or text format email.
Use the EMC to view or configure Exchange ActiveSync Mailbox Policy by the following steps:
In the console tree, navigate to Organization Configuration >
Client Access.
In the result pane, click the Exchange ActiveSync Mailbox Policies tab, and then select the policy you want to view or configure.
In the action pane, click Properties.
Under the Sync Settings tab, check or uncheck the box
Allow HTML-formatted e-mail. Select this check box to enable e-mail messages that are formatted in HTML to be synchronized to the mobile phone. If this check box isn't selected, all e-mail messages will be converted to plain text before synchronization.
And use this command to configure whether allow text messaging on the mobile phone. The Exchange Enterprise Client Access License is required to change the values of this setting.
Set-ActiveSyncMailboxPolicy -Identity PolicyName –AllowTextMessaging $True
For more information, please refer to this document.
https://technet.microsoft.com/en-us/library/bb123484(v=exchg.141).aspx
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]
Lynn-Li
TechNet Community Support

Opportunistic TLS between our Exchange 2010 SP3 on Premise (WIth Edge) and Exchange Online Protection.

Hi,
We would like to configure Opportunistic TLS between our Exchange 2010 SP3 On Premise Systems (with Edge) and EOP.
I can see that Opportunist TLS is enabled on both the send and receive connectors in EOP. SO I think no change required here.
The On premise Send Connector (Configured by EdgeSync) does not have the option for Opportunistic TLS. Under "Configure Smart Host Authentication Settings" it is currently set to "None". I have the option for "Basic Authentication
over TLS" but this requires a Username and Password. No option for Opportunistic TLS. When I look at the properties of the send connector (get-sendconnector "sendconnector_name" | fl) I
can see that the IgnoreSTARTTLS parameter is set to FALSE - so I think that means it is enabled. So I think no changes required here- right?
The receive connector on the Edge Server has the TLS option on the Authentication tab - so I guess I just check that option right?
The Edge servers also run TMG and the two are integrated. I don't think this changes anything but thought I would include it in case it does.
Anything I have missed?
Thanks very much.
Geoff
ilmuro69

Hi,
We would like to configure Opportunistic TLS between our Exchange 2010 SP3 On Premise Systems (with Edge) and EOP.
I can see that Opportunist TLS is enabled on both the send and receive connectors in EOP. SO I think no change required here.
The On premise Send Connector (Configured by EdgeSync) does not have the option for Opportunistic TLS. Under "Configure Smart Host Authentication Settings" it is currently set to "None". I have the option for "Basic Authentication
over TLS" but this requires a Username and Password. No option for Opportunistic TLS. When I look at the properties of the send connector (get-sendconnector "sendconnector_name" | fl) I
can see that the IgnoreSTARTTLS parameter is set to FALSE - so I think that means it is enabled. So I think no changes required here- right?
The receive connector on the Edge Server has the TLS option on the Authentication tab - so I guess I just check that option right?
The Edge servers also run TMG and the two are integrated. I don't think this changes anything but thought I would include it in case it does.
Anything I have missed?
Thanks very much.
Geoff
ilmuro69

Exchange 2010 Sp3 AD Schema Changes

Similar Messages

Maybe you are looking for