Exchange 2010 SP3 UR2 and Event 4999 = AirSync, M.E.Data.Storage, M.E.D.S.AppointmentTombstone

Hello together,
i'm having the following event on my cas servers every about 30 minutes:
Event 4999 MSExchange Common
Watson report about to be sent for process id: 5780, with parameters: E12, c-RTL-AMD64, 14.03.0151.000, AirSync, M.E.Data.Storage, M.E.D.S.AppointmentTombstone..ctor, System.OverflowException, 7f09, 14.03.0158.001.
ErrorReportingEnabled: False
it looks like it is a known bug fixed in SP3 UR3 (http://support.microsoft.com/kb/2891587/de) ?
http://support.microsoft.com/kb/2888911/de
they are talking there about a workarround to delete the problematic "thumbstone data". but how to find and identiy them before deletion ?
"To work around this issue, use the MFCMAPI tool to remove the corrupted tombstone data."
thanks for feedback,
best,
martin

Hello Martin,
I have a user who is having this exact same issue. I know this thread is a few months old, did you ever find an answer to where the corrupted tombstone data was located at?
thanks,
Emmanuel Fumero Exchange Administrator

Similar Messages

  • Real-world experience with Exchange 2010 SP3 RU5+ and Powershell 4?

    The support-ability matrix for Exchange (http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx) says Exchange
    2010 SP3 RU5+ and Powershell 4 are compatible.  But, there is very little actual discussion about how well that works. 
    I use Powershell extensively for mission critical and somewhat complex processes, with Exchange 2010 on 2008 R2 and AD access/reads/updates. 
    Can I get a summary of the caveats and benefits from someone who has actually done this in a
    real-world/production scenario (more than one server, managing from a separate non-Exchange server), and who has scripting experience with this configuration?  
    Also, how has this affected EMC operations?  
    As always thank you in advance!  

    I believe the matrix states that its supported to install Exchange into an environment where __ version of WMF is present.  Exchange 2010, launched from a Win 2012 server, reports version 2.0 when you call $host.  For example, calling the ActiveDirectory
    module from EMS on an Win 2012 server (ps 3.0) fails.
    I'll double check the extent of this scenario and get back to you.
    Mike Crowley | MVP
    My Blog --
    Planet Technologies

  • Exchange 2010 SP3 RU 5 - Event id 4999

    We have Exchange 2010 SP3 RU5 with four CAS/HT and five mailbox servers. We get tons of event 4999 on the four CAS/HT during the last weeks:
    Watson report about to be sent for process id: 6456, with parameters: E12, c-RTL-AMD64, 14.03.0178.000, AirSync, MSExchange ActiveSync, Microsoft.Exchange.Data.Storage.GlobalObjectId.IsForeignUid, UnexpectedCondition:NullReferenceException, 54b1, 14.03.0178.000.
    ErrorReportingEnabled: False
    We have 10000+ mailboxes and no problem with activesync has been reported. I increased diagnostic logging of activesync to "expert" without getting more details about this. I have also restarted all four CAS/HT servers but event 4999 is
    still there.
    Any ideas?

    Thanks for your reply Willard Martin
    This event is also from MSExchange Common and the process id 6456 referred to in the event text is w3wp.exe.
    I also checked both your links but they are not similar to my problem. The first of your links is about  "System.IndexOutOfRangeException" and doesn't seem to have anything to do with ActiveSync. The second is about ActiveSync but with another kind
    of error: "UnexpectedCondition:ArgumentNullException". 
    My error text is "UnexpectedCondition:NullReferenceException"

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

  • Event ID: 4999 - MSExchange Common - Exchange 2010 SP3

    Hi all,
    I have Exchange 2010 SP3 RU4 and since yesterday without reason (I didn´t patch anything, configure etc.) following error randomly appears in app eventlog:
    Watson report about to be sent for process id: 6000, with parameters: E12, c-RTL-AMD64, 14.03.0151.000, AirSync, MSExchange ActiveSync, Microsoft.Exchange.Data.Storage.GlobalObjectId.IsForeignUid, UnexpectedCondition:NullReferenceException, 54b1,
    14.03.0151.000.
    ErrorReportingEnabled: True
    I´ve tried to find some info but no luck.
    Does anybody know how to fix this?
    Thanks in advance, O.

    Resolved..
    A few days ago I hid some testing resource mailboxes (rooms) in GAL, which were used in Cisco TMSXE (Videoconferencing SW). Then, when I restarted the IIS, these errors appeared, because of Cisco TMSXE couldn´t find the room mailboxes. So I unhide
    them and errors are gone..

  • Exchange 2010 SP3 Rollup Update 6

    Our Exchange environment is currently on Exchange 2010 SP3 RU3 and the Forefront Protection 2010 for Exchange server version is 11.0.713.0 (Rollup 3). 
    We planning to upgrade Exchange servers and install Exchange 2010 SP3 RU6, question which I have is it Mandatory to upgrade the Forefront Protection 2010 for Exchange server version is 11.0.727.0 (Rollup 4) before we install Exchange 2010 SP3 RU6 on the
    Exchange servers.
    Thanks,
    AJ

    Thanks Adam for the prompt response and yes I recall these cmdlets to disable and there is a similar cmdlet to enable it. Also after Exchange 2010 SP2 after some RU there is no need to disable FPE before installing RU however it is recommended to disable
    it.
    If you refer the comments section mentioned in the blog below it talks about it:-
    http://blogs.technet.com/b/exchange/archive/2014/05/27/released-update-rollup-6-for-exchange-2010-service-pack-3.aspx
    If you read the comment posted by James Knoch posted on this blog which is as below,
    SP3 & the Rollup Updates are not supposed to require you to disable Forefront anymore, but it doesn't hurt to be safe and disable/enable it anyways. Make sure you are running Forefront Rollup 4 (http://support.microsoft.com/kb/2619883)
    & the latest security update (http://www.microsoft.com/en-us/download/details.aspx?id=41836).
    Above stated confused me a bit, is it mandatory to upgrade Forefront or it is NOT.
    Thanks,
    AJ

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

  • Event ID 9877, Exchange 2010 SP3 RU4

    On 2/19 I installed RU4 for Exchange 2010 SP3 on a server at a client's site.  This is a single server with all the roles on it, with about 40-45 mailboxes. Ever since then, during the busiest hours of the day (around 7AM to 5:30PM or so), I get the
    following event log error on this server:
    Log Name:      Application
    Source:        MSExchangeIS Mailbox Store
    Date:          2/20/2014 6:58:49 AM
    Event ID:      9877
    Task Category: Content Indexing
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      server.domain.com
    Description:
    Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch.
    Mailbox Database: Mailbox Database 0784353824
    Error Code: 0x80043629
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeIS Mailbox Store" />
        <EventID Qualifiers="49198">9877</EventID>
        <Level>2</Level>
        <Task>46</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-20T11:58:49.000000000Z" />
        <EventRecordID>423922</EventRecordID>
        <Channel>Application</Channel>
        <Computer>server.domain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>CISearch::EcGetRowsetAndAccessor</Data>
        <Data>Mailbox Database 0784353824</Data>
        <Data>0x80043629</Data>
        <Binary>5B444941475F4354585D00000E020000FFC8070000000000000300020000EBF410101B000000F7991010000000008B304010E7FAFFFFEBB410101B0000006DA74010E7FAFFFF6DE74010E7FAFFFF85C710100000008085C710100000008085C7101000000080BDCC101000000C00D4224010E7FAFFFFEBD410101B0000008B3B4010E7FAFFFFEBF410101B000000F7991010000000008B304010E7FAFFFFEBB410101B0000006DA74010E7FAFFFF6DE74010E7FAFFFF85C710100000008085C710100000008085C7101000000080BDCC101000000C00D4224010E7FAFFFFEBD410101B0000008B3B4010E7FAFFFFEBF410101B000000F7991010000000008B304010E7FAFFFFEBB410101B0000006DA74010E7FAFFFF6DE74010E7FAFFFF85C7101000000080D25560200F01048040008F6600000C00D25560200F01048040008F661B000000AD0C4010BFF9FFFFE3D400101B00000029D14010E7FAFFFFADC34010E7FAFFFF53BD00101B000000D25560200F01048040008F66E7FAFFFFD25560200F01048040008F6600000080D25560200F01048040008F6600000C00C5C14010EE030000715D4010EC030000D25560200F0104800B00AA671B000000543760201DFAFFFF0B005C0EE7FAFFFFD42160200F0104800B005C0EE7FAFFFFD25560200F0104800B005C0E00000080D25560200F01048040008F660000008023C3001000000C0023FC4010370A0000D25560200F01048040008F66E7FAFFFF</Binary>
      </EventData>
    </Event>
    The frequency of these errors varies and it definitely seems to be related to the amount of traffic. Over the weekend it only occured about 5-10 times a day.  For the past couple of days, it's been pretty constant about every 15 minutes or
    so all day.
    I've looked this up, but I've only found a few posts mentioning similar errors, all relating to earlier versions of Exchange 2010. Supposedly this problem was fixed in one of the rollups to SP1 or SP2, I think.  I never saw these errors, though,
    until the SP3 RU4 rollup.  I haven't heard any complaints from users, but I'm concerned that this might escalate and start causing noticeable searching issues.
    Any ideas would be appreciated.
    Deb

    Hi Deb,
    We're getting the same error as you on Exchange 2010. We have exchange 2010 and exchange 2013 running in a coexisting environment. Since we applied Service Pack 1 for Exchange 2013, we've had nothing but issues!
    I've tried the rebuild of the index catalogues by following these instructions:
    http://ghousewin.blogspot.in/2012/08/not-able-to-search-in-owa-event-id-9877.html
    This failed to resolve the issues too. We've rebooted the server, restarted all the search services and still nothing! We're pulling our hair out here!
    The only thing I haven't tried is the prepareAD commands in this post:
    http://social.technet.microsoft.com/Forums/exchange/en-US/7a4a7400-a582-4f95-9360-6d84e66e87ad/ex2010-2node-dag-search-in-owa-not-working-caused-by-eventid-9877-content-indexing-function
    I'm unable to try this during the day as we have no testing
    environment and would hate to mess the production environment up if this went wrong.
    If you're able to try this during the day, would you let us know how it goes?
    Many thanks,
    Stephen

  • List of all historical meetings and attendants - resource mailbox exchange 2010 sp3

    Hi,
    I'm an exchange admin, and i'm looking for a PS script of some sort to get a list of all the meetings held in a resource mailbox and its attendants.
    ie: meeting room 1 -> get a list of all the meetings held there and the attendants for a period of 3 months.
    Is there anybody who has experience with this ?
    (Exchange 2010 sp3)u

    Hi,
    I recommend that you post this in Script Forum,there are more Powershell experts to help you:
    http://social.technet.microsoft.com/Forums/scriptcenter/en-US/home?category=scripting
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Exchange 2010 SP3 and UR6 Query - Order of Install

    hi,
    I need to update my Exchange 2010 SP2 Servers to SP3 and Update Rollup 6.
    Can someone confirm the update order for me?
    I have 5 servers;
    Live Data Centre:
    2 x HUB / CAB (Using Windows NLB)
    2 x Mailbox (DAG)
    Disaster Recovery:
    1 x Multi-Role Server (CAS / HUB and Mailbox) - this is also Part of the DAG
    Two Questions:
    1.) What is the Order in which I install SP3 on these Servers? Should it be Live Data Centre: HUB / CAS, Mailbox Servers and THEN the Multi-Role Server at DR?
    2.) When Upgrading each server, should I do SP3, reboot, check and THEN install Update Rollup 6 - or should I upgrade all Servers to SP3 and then start the process again to get to Update Rollup 6?
    Thanks in advance for your help with this query.
    Regards,
    Adam

    1) Internet facing CAS first in each AD site. Order: CAS> HUB> UM> MBX
    2) Personally, I would install SP3, reboot, then install SP6, but its really up to you.
    http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx
    Upgrade Exchange 2010 to Exchange 2010 SP1, Exchange 2010 SP2, or Exchange 2010 SP3
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Outlook 2010 and Exchange 2010 SP3

    Hello,
    we are planning to upgrade from Exchange 2010 sp1 to SP3, most of client PCs has Windows XP sp3 and Oultook 2010 with VSTO addins working with mapi properties.
    I need to know if there are any known issues between this client environment and Exchange 2010 SP3 ??
    thanks a lot,
    Mauricio.
    Mauricio

    Windows XP is not supported in any scenario, so yes, I'd call that a known issue.
    Mike Crowley | MVP
    My Blog --
    Planet Technologies

  • Exchange 2010 SP3 and meeting forward notification options

    I'm having an issue with meeting forward notifications in Exchange 2010 SP3. I'm working on an integration project with an existing system using the EWS Managed API. Part of this system is handling forward notifications and responses. However, we've hit
    an issue regarding the way forwards are generated by Exchange.
    In short, when a meeting request is forwarded to an external address (could be an Exchange server outside of our domain, gmail, or anything, really), the notification they receive places the meeting owner in the "sent representing" field, not the
    person who actually sent the forward. As a result, any responses from the forward recipient will go directly back to the organizer, and the user who forwarded the request may not even be visible. We do not want this to happen. We'd prefer that the forward
    show the person who actually sent it as the sender, and as a result, the response should go directly back to them, not the organizer.
    Is this possible, either through settings or flags on the Appointment object itself or through some additional configuration options in Exchange? Installing a third-party transport agent (even one that we write) is probably out of the question.

    What if you "Forward as iCalendar"
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on www.exchangequery.com

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

Maybe you are looking for