Patching Exchange 2010

I have just taken over administration of an environment that has an exchange server running Exchange 2010 on Windows Server 2008R2. The windows portion of the server does not have SP1 installed and there appear to be few if any patches installed for exchange,
it is not at SP1 even. Obviously I need to install SP1 for Windows 2008R2 first and get all the windows updates up to date, my concern is patching exchange. The environment, like all I assume, is very email dependent and they are sensitive to downtime and
email interruptions, the exchange server is a virtual server running on VMware 4.0, I do not have the luxury of a test environment unfortunately. Can I go ahead and install Exchange 2010 SP3 once I have SP1 for Windows and all the windows patches installed?
Or would it be better to first install SP1 for Exchange then move to SP3? This is a single Exchange server environment with about 50 mailboxes.

Obviously - Backup, Backup, Backup!
Now read the rest below :)
No just install SP3 then install RU5 that just came out.
Here is some reading:
http://blogs.technet.com/b/exchange/archive/2013/02/12/released-exchange-server-2010-sp3.aspx
then some of this:
http://blogs.technet.com/b/exchange/archive/2014/02/25/released-update-rollup-5-for-exchange-2010-service-pack-3-and-update-rollup-13-for-exchange-2007-service-pack-3.aspx
you should be all set after you've gotten those sorted installed.
And yes - if you do nothing else - build a test lab.  Find some old machines and install Hyper-V Server 2012 R2 and some 180 trials of Windows Server 2012 R2 and start testing. If you have no spares, you can even run it on a desktop with more RAM
and go from there.

Similar Messages

  • Best Practices for patching Exchange 2010 servers.

    Hi Team,
    Looking for best practices on patching Exchnage Server 2010.
    Like precautions  , steps and pre and post patching checks.
    Thanks. 

    Are you referring to Exchange updates? If so:
    http://technet.microsoft.com/en-us/library/ff637981.aspx
    Install the Latest Update Rollup for Exchange 2010
    http://technet.microsoft.com/en-us/library/ee861125.aspx
    Installing Update Rollups on Database Availability Group Members
    Key points:
    Apply in role order
    CAS, HUB, UM, MBX
    If you have CAS roles in an array/load-balanced, they should all have the same SP/RU level.  so coordinate the Exchange updates and add/remove nodes as needed so you do not run for an extended time with different Exchange levels in the same array.
    All the DAG nodes should be at the same rollup/SP level as well. See the above link on how to accomplish that.
    If you are referring to Windows Updates, then I typically follow the same install pattern:
    CAS, HUB, UM, MBX
    With windows updates however, I tend not to worry about suspending activation on the DAG members rather simply move the active mailbox copies, apply the update and reboot if necessary.

  • Outlook 2011 for Mac Exchange 2010 asking for credentials after Patch Tuesday March 2015

    Up till this past Tuesday when Microsoft released its new security patches, I had all my Outlook 2011 for Mac working just fine. Since the release of March 2015, we have heard of issues resulting in Outlook problems with a certain security patches blocking
    connectivity. We are carrying Exchange 2010 with SP3 roll up 7. This is only happening on my macs. I have uninstalled the patch in question but the problem persists. Can anyone please shed some light as to what I can do?
    Any assistance would be greatly appreciated.
    Thank you in advance...
    Carlos

    Hi Carlos,
    This forum is for general questions and feedback related to Outlook for Windows. Since the problematic account can work well in Outlook 2010 with Windows 7 but not in Outlook for Mac 2011, I suggest we can ask a question in
    Outlook for Mac 2011 forum for more troubleshooting.
    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.
    Thanks for your understanding.
    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 multi-day (not 'all day') meeting requests showing up as 1 day off on iphone attached Activesync Exchange 2010 accounts

    Exchange 2010 SP2 Server
    iPhone iOS 5.01 (4/4s) using ActiveSync
    Outlook 2007 clients
    When multi-day (not 'all day') meeting requests or appointments are being sent to email accounts which have an iPhone attached to the Exchange account via ActiveSync, the iPhone accepts the meeting request but then moves the event one day later than what it was originally scheduled and posts it to Outlook - also 1 day later than it is supposed to be.
    For example:  A meeting request comes into my that is schedule for 9AM-4PM M-W but when I accept it on my iphone it gets posted to my calendar as an ALL DAY event but T-Thu
    We upgraded to Exchange SP2 because some of the threads were alluding that SP2 would fix it - it didn't.  I know the fix is to rip out the event to separate calendar events but this will not work for reqeusts coming from outside.  And this is too tedious.  If anything, it is a serious bug.
    Anybody seen this before?
    Thanks,
    Monty.

    I am experiencing a similar problem with a client of mine who is using Microsoft's Cloud-based Exchange server, Office 365.  I suspect the Office 365 server is an Exchange 2010 server, similar to your environment.  Check out my tests below which I think define when the day shifting happens. 
    I see that you applied SP2 to your Exchange 2010 environment, but have you also applied Update Rollup 1?  See this article:  http://support.microsoft.com/kb/2563324.  It would be interesting to know whether that rollup resolves your problem.
    I have done some pretty extensive testing and have posted in the Office 365 Support Forum (http://community.office365.com/en-us/f/146/p/53396/192332.aspx#192332)  Here is a summary of my testing.
    I am having the exact same problem described by Jim Edmonds and jkwmail (http://community.office365.com/en-us/f/176/p/19921/93304.aspx#93304) with one of my clients who is not very happy about this or our inability to resolve the problem.  Here is what I am experiencing:
    When an appointment in Office 365 spans multiple days, the appointment gets converted to an All Day Event and moved forward one day on an iPhone ActiveSync client.
    I have completed the following troubleshooting:
    1 - Using my GMail Account and my work email account on MS Exchange 2007 SP 2 Server I created separate single day appointments in the morning from each account spanning two hours and invited my client who is using MS Outlook 2010 and Office 365. 
        Result:  The appointments show the correct date and time on my Outlook, MS Exchange 2007 SP 2 OWA, and iPhone as well as my client's Outlook, Office 365 webmail, and iPhone.
    2 - Using my GMail Account and my work email account on MS Exchange 2007 SP 2 Server I created separate single day appointments in the afternoon from each account spanning two hours and invited my client who is using MS Outlook 2010 and Office 365. 
        Result:  The appointments show the correct date and time on my Outlook, MS Exchange 2007 SP 2 OWA, and iPhone as well as my client's Outlook, Office 365 webmail, and iPhone.
    3 - Using my GMail Account and my work email account on MS Exchange 2007 SP 2 Server I created separate multi-day appointments from Friday at 5 PM to Monday at 8 AM from each account and invited my client who is using MS Outlook 2010 and Office 365. 
        Result:  The appointments show the correct date and time on my Outlook, MS Exchange 2007 SP 2 OWA, and iPhone as well as my client's Outlook and Office 365 webmail.  However, on my client's iPhone, the time on the appointments had changed to an all day event and the start date was shifted one day forward, Saturday, and the end date was Monday unless the appointment end time was after the appointment start time in which case it created an All Day Event on Tuesday as well.  For Example:  If the appointment was from 8 AM Friday Morning to 8 AM Monday Morning, the iPhone would show an All Day Event on Saturday, Sunday, and Monday.  If the appointment was from 8 AM Friday Morning to 8:30 AM Monday Morning, the iPhone would show an All Day Event on Saturday, Sunday, Monday, and Tuesday.  If the appointment was from 8 AM Friday Morning to 7:30 AM Monday Morning, the iPhone would show an All Day Event on Saturday, Sunday, and Monday.  This was also true for appointments starting on Friday at 5 PM and ending on Monday at 5 PM, starting on Friday at 5 PM and ending on Monday at 5:30 PM, and starting on Friday at 5 PM and ending on Monday at 4:30 PM as in the above AM examples. 
    *** Again I would like to note that on my iPhone which is connected to my company's MS Exchange 2007 SP 2 server, the multi-day appointment shows up correctly with correct start and end times and is not converted to an All Day Event. *** 
    It would seem this is a problem with ActiveSync on Office 365 and iOS devices.  What is particularly frustrating is that this exact problem is identified in KB 2563324 (http://support.microsoft.com/kb/2563324) Issue 1.6 - "An appointment is longer than 24 hours is changed to a multi-day All Day Event" which states:  "To resolve this issue, install Update Rollup 1 for Exchange Server 2010 Service Pack 2 (SP2)."  Since this is a cloud based service, we do not have the ability to either see what the current version of the Exchange service we are connected to is or update the service with this patch level.
    4 - I performed the above three tests with my client creating the events in MS Outlook 2010 and inviting my work account on the MS Exchange 2007 SP 2 Server and got the exact same results.
    5 - My client's iPhone is running iOS 4.3 and my iPhone is running iOS 5.1.0.  In order to test this without going through the update process on my client's iPhone, I set up his Office 365 account on my iPhone and performed the tests in numbers 1-4 from above, viewing the results on my iPhone, and got the exact same results.
    6 - Today, I tried this with a different Office 365 account, performed the multi-day test in number 3 from above and got the exact same results.
    7 - Today I also upgraded my iPhone to iOS 5.1.1, performed the multi-day test in number 3 from above and got the exact same results.
    8 - I have confirmed that all time zones are set correctly.  I have checked the iPhone, OWA, Office 365 Webmail, etc.
    I believe the problem in my case is with the Office 365 environment and not the iOS device.  However, trying to get support from these large companies seems to be very difficult?
    Does anyone from Apple know if this is an iOS bug or a problem with Exchange 2010/Office 365?
    Thanks...
    Jp

  • Exchange 2010 Autodiscovery & Outlook Anywhere kind of but really not working

    This is driving me nuts. We have a single Exchange Server 2010 running (everything is on one box). It works fine internally (all Outlook clients can see and grab the login info from the user login). OWA works from outside, mail delivers nicely. My problems
    all seem to stem around some mysterious problem in autodiscover and outlook anywhere.
    Our domain is internally like this: mycompany2.com and outside like this: mycompanyllc.com
    So the mail server inside looks like server1.mycompany2.com and outside: mail.mycompanyllc.com - from what I can see it's all set up correctly in both.
    I've run the connectivity analyzer and apart from a minor certificate warning ('Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled) it passes every test on the site for EAS and Outlook Anywhere
    (and for good measure I ran everything, all green checks!). Autodiscover works in the test, everything gets found and pointed to the right place.
    When I have a user that wants to configure Outlook 2010 or 2013 outside
    the org. they start the wizard, type their name, their email, their password. The server or user can't be found and no matter what they do it won't find it. If you go in and manually configure the
    internal server name, domain, username you can connect. It just won't set it up automatically. The odd thing is, in the analyzer the autodiscovery XML is found and downloaded fine, all the server name info and detail is displayed.
    In Outlook 2013, both Exchange and EAS connection doesn't work even though phones can be set up through EAS (although they require the same kind of manual setup--autodiscover doesn't seem to work even though it keeps telling me everything
    is fine).
    I'm at wits end, all the tests show it's working, but in the real world the server can't be found. It's right on the DNS servers, it's right in the tests, it responds correctly manually. I'd love users to be able to set up their own mail without a 10 page
    printout of all the manual settings. It's all relatively late model hardware, Outlook 2010 or 2013, and a fully patched up to date Exchange 2010 server. Anyone have an idea?
    Curt Kessler - FLC

    We don't use TMG we use a WatchGuard Firewall and it is configured to allow all traffic to this server (that's why manual works fine with Outlook and OWA).
    When I run the get-autodiscovervirtualdirectory it returns my internal server under the Server, and nothing more, so this possibly could be it?? I'm definitely not good at IIS at all, I would need guidance to investigate that further...
    This is my EXRCA results, the first fail is because it tests the root of mydomain.com rather than mail.mydomain.com which is a different server. I've replaced some names for security purposes:
    The Microsoft Connectivity Analyzer is attempting to test Autodiscover for
    [email protected].
    Autodiscover was tested successfully.
    Test Steps
    Attempting each method of contacting the Autodiscover service.
    The Autodiscover service was tested successfully.
    Test Steps
    Attempting to test potential Autodiscover URL https://mydomain.com/AutoDiscover/AutoDiscover.xml
    Testing of this potential Autodiscover URL failed.
    Test Steps
    Attempting to resolve the host name franklinlc.com in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 76.79.142.101
    Testing TCP port 443 on host franklinlc.com to ensure it's listening and open.
    The port was opened successfully.
    Testing the SSL certificate to make sure it's valid.
    The SSL certificate failed one or more certificate validation checks.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server franklinlc.com on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
    Additional Details
    Remote Certificate Subject: CN=apps.franklinlc.com, OU=Domain Control Validated, O=apps.franklinlc.com, Issuer: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale,
    S=Arizona, C=US.
    Validating the certificate name.
    Certificate name validation failed.
     <label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl02_ctl01_tmmArrow">Tell
    me more about this issue and how to resolve it</label>
    Additional Details
    Host name franklinlc.com doesn't match any name found on the server certificate CN=apps.franklinlc.com, OU=Domain Control Validated, O=apps.franklinlc.com.
    Attempting to test potential Autodiscover URL https://autodiscover.mydomain.com/AutoDiscover/AutoDiscover.xml
    Testing of the Autodiscover URL was successful.
    Test Steps
    Attempting to resolve the host name autodiscover.mydomain.com in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 76.xx.xx.xx this is the mail server IP address
    Testing TCP port 443 on host autodiscover.franklinlc.com to ensure it's listening and open.
    The port was opened successfully.
    Testing the SSL certificate to make sure it's valid.
    The certificate passed all validation requirements.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.mydomain.com on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
    Additional Details
    Remote Certificate Subject: CN=mail.franklinlc.com, OU=Domain Control Validated, O=mail.mydomain.com, Issuer: SERIALNUMBER=xxxxxxxxxxxxx, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale,
    S=Arizona, C=US.
    Validating the certificate name.
    The certificate name was validated successfully.
    Additional Details
    Host name autodiscover.mydomain.com was found in the Certificate Subject Alternative Name entry.
    Testing the certificate date to confirm the certificate is valid.
    Date validation passed. The certificate hasn't expired.
    Additional Details
    The certificate is valid. NotBefore = 9/28/2012 10:20:20 PM, NotAfter = 9/28/2015 10:20:20 PM
    Checking the IIS configuration for client certificate authentication.
    Client certificate authentication wasn't detected.
    Additional Details
    Accept/Require Client Certificates isn't configured.
    Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
    The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.mydomain.com/AutoDiscover/AutoDiscover.xml for user [email protected].
    The Autodiscover XML response was successfully retrieved.
    Additional Details
    Autodiscover Account Settings
    XML response:
    <?xml version="1.0"?>
    <Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
      <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
        <User>
          <DisplayName>Curt Kessler</DisplayName>
          <LegacyDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Curt Kessler</LegacyDN>
          <DeploymentId>14a1e263-943a-4609-865c-ba22802e45aa</DeploymentId>
        </User>
        <Account>
          <AccountType>email</AccountType>
          <Action>settings</Action>
          <Protocol>
            <Type>EXCH</Type>
            <Server>FLC5.internaldomainname.com</Server>
            <ServerDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=FLC5</ServerDN>
            <ServerVersion>7383807B</ServerVersion>
            <MdbDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=FLC5/cn=Microsoft Private MDB</MdbDN>
            <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl>
            <OOFUrl>https://mail.mydomain.com/ews/exchange.asmx</OOFUrl>
            <OABUrl>https://mail.mydomain.com/OAB/9c85c0c4-48f4-4aa8-99b2-f640651b130a/</OABUrl>
            <UMUrl>https://mail.mydomain.com/ews/UM2007Legacy.asmx</UMUrl>
            <Port>0</Port>
            <DirectoryPort>0</DirectoryPort>
            <ReferralPort>0</ReferralPort>
            <PublicFolderServer>FLC5.internaldomainname.com</PublicFolderServer>
            <AD>PRIME.internaldomainname.com</AD>
            <EwsUrl>https://mail.mydomain.com/ews/exchange.asmx</EwsUrl>
            <EcpUrl>https://flc5.internaldomainname.com/ecp/</EcpUrl>
            <EcpUrl-um>?p=customize/voicemail.aspx&amp;exsvurl=1</EcpUrl-um>
            <EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;</EcpUrl-mt>
            <EcpUrl-ret>?p=organize/retentionpolicytags.slab&amp;exsvurl=1</EcpUrl-ret>
            <EcpUrl-sms>?p=sms/textmessaging.slab&amp;exsvurl=1</EcpUrl-sms>
          </Protocol>
          <Protocol>
            <Type>EXPR</Type>
            <Server>mail.mydomain.com</Server>
            <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl>
            <OOFUrl>https://mail.mydomain.com/ews/exchange.asmx</OOFUrl>
            <OABUrl>https://mail.mydomain.com/OAB/9c85c0c4-48f4-4aa8-99b2-f640651b130a/</OABUrl>
            <UMUrl>https://mail.mydomain.com/ews/UM2007Legacy.asmx</UMUrl>
            <Port>0</Port>
            <DirectoryPort>0</DirectoryPort>
            <ReferralPort>0</ReferralPort>
            <SSL>On</SSL>
            <AuthPackage>Ntlm</AuthPackage>
            <EwsUrl>https://mail.mydomain.com/ews/exchange.asmx</EwsUrl>
            <EcpUrl>https://mail.mydomain.com/ecp/</EcpUrl>
            <EcpUrl-um>?p=customize/voicemail.aspx&amp;exsvurl=1</EcpUrl-um>
            <EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;</EcpUrl-mt>
            <EcpUrl-ret>?p=organize/retentionpolicytags.slab&amp;exsvurl=1</EcpUrl-ret>
            <EcpUrl-sms>?p=sms/textmessaging.slab&amp;exsvurl=1</EcpUrl-sms>
          </Protocol>
          <Protocol>
            <Type>WEB</Type>
            <Port>0</Port>
            <DirectoryPort>0</DirectoryPort>
            <ReferralPort>0</ReferralPort>
            <Internal>
              <OWAUrl AuthenticationMethod="Basic, Ntlm, Fba, WindowsIntegrated">https://flc5.internaldomainname.com/owa/</OWAUrl>
              <Protocol>
                <Type>EXCH</Type>
                <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl>
              </Protocol>
            </Internal>
            <External>
              <OWAUrl AuthenticationMethod="Fba">https://mail.mydomain.com/owa/</OWAUrl>
              <Protocol>
                <Type>EXPR</Type>
                <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl>
              </Protocol>
            </External>
          </Protocol>
        </Account>
      </Response>
    </Autodiscover>
    I've replaced my public domain with mydomain.com and my internal domain with internaldomainname.com, and hidden the IP, but everything else is the same. The tests all pass
    Curt Kessler - FLC

  • 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

  • OOF not working for mailboxes homed on Exchange 2010 server during migration

    Hi There
    I'm troubleshooting an issue during a exchange 2010 to exchange 2013 migration where the OOF is not working for users homed on the exchange 2010 mailbox servers. This applies to users using outlook 2010 and outlook 2013 .OWA works perfectly and you can also
    enable OOF via exchange powershell.
    Users homed on the exchange 2013 servers does not have any issues.
    The exchange 2010 servers is on SP3 rollup 4 and the 2013 servers on SP1 only without any rollups installed.
    So my question will be - have anyone experienced this issue during migration and will patching the exchange 2010 servers to rollup 5 or 6 and the exchange 2013 to sp1 rollup 5 fix the OOF issue then? If requested the client to patch to these levels, but
    in the meantime I'm checking if anyone else had similar issues.
    Any pointers will be welcome.

    Hi ,
    1.Please check the problematic exchange 2010 user account can able to access the ews virtual directory internal url and you can check that via browser's.It will prompt for the user name and password , please provide that .
    EWS url wopuld be like - https://mail.youdomain.com/EWS/Exchange.asmx
    2.Then the second step would be autodiscover check for the problematic user account.you can find that via test email configuration .There you came to know whether outlook is fetching up the proper url for ews and autodiscover.
    3.Then please un check the proxy settings in browsers and check the same.
    4.please use the command to check the auto discover 
    test-outlookwebservices
    Please check the below links also.
    http://exchangeserverpro.com/exchange-2013-test-outlook-web-service/
    http://www.proexchange.be/blogs/exchange2007/archive/2009/07/14/your-out-of-office-settings-cannot-be-displayed-because-the-server-is-currently-unavailable-try-again-later.aspx
    http://port25guy.com/2013/07/20/user-cannot-set-an-out-of-office-in-exchange-20102013-or-eventid-3004-appears-in-your-event-log/
    http://www.theemailadmin.com/2010/06/exchange-server-2010-out-of-office/
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Outlook 2013/Exchange 2010 Free/Busy access issues.

    Good Day Everyone,
    I am running a Win 2008 R2 environment with Win7 users, using Exchange 2010 and Outlook 2013. Last week my users started experiencing issues with being able to view Free/Busy in the Calendar for any other user. I have checked past issues with this with patches
    KB 2837618 and KB 2837643. Neither patch is showing as installed and I have tried a nummber of the suggested fixes offered for that issue to no avail. OWA seems to be working just fine.
    Our Outlook version is: 15.0.4605.1003
    I need a fix for Outlook users and since I havve 140 users, individual fixes are a not realistic option.
    Any assistance would be greatly appreciated.

    Hi,
    Please test if Out of Office feature works well in Outlook. If Out of Office doesn't work either, it should be Autodiscover related.
    Once Autodiscover has not been configured properly, the Free/Busy information may not display correctly. If you are also seeing issues with Out of Office assistant, we may assume that you haven’t correctly setup Autodiscover, since these two symtoms are
    common when Autodiscover is not configured correctly.
    To verify that, please test Outlook Autodiscover Connectivity:
    http://technet.microsoft.com/en-us/library/bb123573.aspx
    We can also learn Configure Exchange Services for the Autodiscover Service from:
    http://technet.microsoft.com/en-us/library/bb201695.aspx
    Regards,
    Melon Chen
    TechNet Community Support

  • Help needed with buggy Outlook 2013 and Exchange 2010 trashing profiles

    Hi All,
      I have a customer who has eschewed MOLP and buys all their Office OEM from Dell.  So as a result they are starting to have more and more office 2013 be deployed.  They have a SBS 2011 server with Exchange 2010 and it is patched to the latest
    rollups and service packs.  (SP3, RU2)  Their Outlook 2010 and earlier clients are just peachy on this.  But the Outlook 2013 clients are having problems.
      What is going on is that periodically I'll get a complaint from a user that their Outlook 2013 is randomly crashing.  In all cases the fix is going into the Outlook Profiles, creating a new profile, then setting the new profile as the default
    and going back into Outlook 2013 and letting it rebuild the cached data on the PC.  This seems to happen a few times a month with random users on the network.
      I told the customer it was probably people not logging out of Outlook 2013 at night and their machines being power spiked but I think that's highly unlikely since it doesen't happen to the Outlook 2010 clients.
      I don't know if any Microsoft developers read this but if you do, please take it back to your bug database.  Any other suggestions would be appreciated (other than scotch Outlook 2013 - while I'd appreciate that, my customer wouldn't)

    In all cases the fix is going into the Outlook Profiles, creating a new profile, then setting the new profile as the default and going back into Outlook 2013 and letting it rebuild the cached data on the PC. 
    The Outlook 2013 crash problem would be fix after you re-create a new profile and re-sync the data from Exchange, right?
    When we meet the same problem in next time, I suggest we run the Outlook Product Stability Diagnostic tool to isolate known causes of crashes in Outlook. The Outlook Product Stability Diagnostic also creates a diagnostic report outlining the data it collected
    and recommendations on possible steps you can take to reduce or eliminate Outlook stability issues.
    Please click the following link to run the Outlook Product Stability Diagnostic tool in the Microsoft Fix it Center Pro portal:
    Outlook Product Stability Diagnostic:
    https://wc.ficp.support.microsoft.com/SelfHelp?knowledgebaseArticleFilter=2764035
    Other troubleshoot steps for Outlook 2013, please refer to the link below.
    Let me know the result.
    http://support.microsoft.com/kb/2632425/en-us 
    Tony Chen
    TechNet Community Support

  • 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

  • Questions about upgrading from Exchange 2010 RTM to Exchange 2010 Service Pack 3

    I am preparing to perform an maintenance upgrade on our current Exchange 2010 Server, to Service Pack 3 (and any post-SP3 roll ups), but I have a couple questions about the process.
    Current Exchange Server details:
    Exchange 2010 Standard
    Version: 14.0 (Build 639.21) - from Exchange Management Console
    Version: 14.0.702.4000 - from Outook client
    Active Directory forest and domain levels: Windows 2008 R2 native
    The questions I have are:
    1.  Can I assume that because it's version 10.0.702.4000 I am on Exchange Server 2010 RTM Update Rollup 4?
    2.  Can Exchange 2010 Standard RTM be patched directly to Service Pack 3, or would I need to perform incremental patches (i.e. SP1, SP2, etc.) before going to SP3?
    3.  Do I need to manually perform the AD domain schema prep before applying Service Pack 3, or will the Service Pack 3 update process automatically handle the modifications of the AD schema?

    Hi,
    Here are my answers you can refer to:
    1. Firstly, I’d like to explain , we can use connection status to check our Exchange server version from Outlook client:
    http://office.microsoft.com/en-in/outlook-help/determine-the-version-of-microsoft-exchange-server-my-account-connects-to-HA010117038.aspx
    And I check my version from both EMC and Outlook client. It’s same.
    2. We can directly update RTM version to SP3 , and the update will take an additional 30 minutes or longer per database.
    3. Since Exchange 2010 SP3 makes updates to the Active Directory schema, we need prepare AD domain schema. However, it will automatically prepare AD and the domain when you install the update.
    For more information, you can refer to the following article:
    http://technet.microsoft.com/en-us/library/jj965774(v=exchg.141).aspx
    If you have any question, please feel free to let me know.
    Thanks,
    Angela
    Angela Shi
    TechNet Community Support

  • Exchange 2010 SP3 upgrade on Windows Server Standard SP2

    I'm midway through the swing upgrade process of migrating from Exchange 2003 - Exchange 2010 to Exchange 2013.  Everything has gone smoothly between the Exchange 2003 and Exchange 2010 migration which I started two days ago.  it has been running
    great.  I am beginning the final stages of moving from the Exchange 2010 server to a new Exchange 2013 server, but it requires my Exchange 2010 server to be upgraded to SP3.  I am now trying to install Exchange Server 2013 SP3 Upgrade and I'm
    getting (3) Client Access Role Prerequisites errors.  Finding any of these HotFixes and patches is frustrating, because any link provided does not work.  It has gotten me nowhere.  Here is my Readiness Checks:
    Summary: 6 item(s). 5 succeeded, 1 failed.
    Elapsed time: 00:01:06
    Configuring Prerequisites
    Completed
    Elapsed Time: 00:00:00
    Organization Prerequisites
    Completed
    Elapsed Time: 00:00:08
    Languages Prerequisites
    Completed
    Elapsed Time: 00:00:02
    Hub Transport Role Prerequisites
    Completed
    Elapsed Time: 00:00:15
    Client Access Role Prerequisites
    Failed
    Error:
    Install hotfix Microsoft Knowledge Base article 982867 from http:// code.msdn.microsoft.com/KB982867.
    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:
    Install hotfix Microsoft Knowledge Base article 979917 from http:// code.msdn.microsoft.com/KB979917.
    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:
    This computer requires the update described in Microsoft Knowledge Base article KB977592 (http:// go.microsoft.com/fwlink/?LinkId=194843). Without this update, the Outlook Anywhere feature may work unreliably.
    Click here for help... http:// go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=249bbd89-16b4-4efa-9b66-7ec87f90e44c
    Elapsed Time: 00:00:15
    Mailbox Role Prerequisites
    Completed
    Warning:
    Multi-mailbox search of on-premises and Office 365 mailboxes in a hybrid configuration requires installation of the update mentioned in Microsoft Knowledge Base article 982867 (http:// code.msdn.microsoft.com/KB982867).
    Elapsed Time: 00:00:24
    I put a space between the http://" space "URL so I could display the links.
    Any help/guidance suggestions would be greatly appreciated.
    Chris

    I just got these two to go away:
    Error:
    Install hotfix Microsoft Knowledge Base article 982867 from http:// code.msdn.microsoft.com/KB982867.
    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:
    This computer requires the update described in Microsoft Knowledge Base article KB977592 (http:// go.microsoft.com/fwlink/?LinkId=194843). Without this update, the Outlook Anywhere feature may work unreliably.
    Click here for help... http:// go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=249bbd89-16b4-4efa-9b66-7ec87f90e44c
    still have this one outstanding:
    Error:
    Install hotfix Microsoft Knowledge Base article 979917 from http:// code.msdn.microsoft.com/KB979917.
    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
    I have tried the FIX: WCF services that are hosted by NLB computers to route messages to Exchange Server fail when WebHeader settings are added by using a .NET Framework 3.5 SP1 application
    Windows6.0-KB2637518-x64.msu
    when I run it, it tells me "The Update does not apply to your system.  So im thinking I need to remove the .NET Framework 4 Client Profile and the .NET Framework 4 Extended.  reboot, then install
    Windows6.0-KB2637518-x64.msu and then reinstall .NET Framework 4 Client Profile and the .NET Framework 4 Extended
    this has taken a day or so to figure out the order of dependencies and the order to put them on.
    Frustrating, since I won't be using Exchange 2010, were moving all the way to Exchange 2013 on a brand new server.
    Chris

  • Second Exchange 2010 installation

    I have one exchange 2010 installed in current forest.
    I want to install second exchange 2010 server.
    What are the pre-requests for 2nd exchange server 2010 installation.
    After installation, if i want to make DAG what are its requirement?
    Regards,
    Sadanand Velechi

    Hi Sadanand,
    In addition to Andy's suggestion, I would like to clarify the following things:
    1. You need to have Enterprise edition of Windows on all nodes for the DAG.
    2. All DAG nodes need to be the same version of Windows and ideally keep as close as possible on patch levels.
    What's more, here is an article for your reference.
    Planning for High Availability and Site Resilience
    http://technet.microsoft.com/en-us/library/dd638104(v=exchg.141).aspx
    Hope it helps.
    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)

  • Entourage 2008 EWS Attachment limit on Exchange 2010

    Hi Folks,
    I'm having a problem allowing my Entourage users to attach files larger than 10MB. I've looked through all of the potential attachment limits on Transport config/Send connectors/Receive connectors/Users mailbox settings, but they all look okay to me.
    [PS] C:\Windows\system32>get-mailbox user | fl max*
    MaxSafeSenders    :
    MaxBlockedSenders :
    MaxSendSize       : 150 MB (157,286,400 bytes)
    MaxReceiveSize    : 150 MB (157,286,400 bytes)
    [PS] C:\Windows\system32>get-sendconnector | fl max*
    MaxMessageSize : 150 MB (157,286,400 bytes)
    MaxMessageSize : 150 MB (157,286,400 bytes)
    [PS] C:\Windows\system32>get-receiveconnector | fl max*
    MaxInboundConnection                    : 5000
    MaxInboundConnectionPerSource           : unlimited
    MaxInboundConnectionPercentagePerSource : 100
    MaxHeaderSize                           : 64 KB (65,536 bytes)
    MaxHopCount                             : 30
    MaxLocalHopCount                        : 8
    MaxLogonFailures                        : 3
    MaxMessageSize                          : 150 MB (157,286,400 bytes)
    MaxProtocolErrors                       : 5
    MaxRecipientsPerMessage                 : 5000
    MaxAcknowledgementDelay                 : 00:00:30
    MaxInboundConnection                    : 5000
    MaxInboundConnectionPerSource           : 20
    MaxInboundConnectionPercentagePerSource : 2
    MaxHeaderSize                           : 64 KB (65,536 bytes)
    MaxHopCount                             : 30
    MaxLocalHopCount                        : 8
    MaxLogonFailures                        : 3
    MaxMessageSize                          : 150 MB (157,286,400 bytes)
    MaxProtocolErrors                       : 5
    MaxRecipientsPerMessage                 : 200
    MaxAcknowledgementDelay                 : 00:00:30
    [PS] C:\Windows\system32>get-transportconfig | fl max*
    MaxDumpsterSizePerDatabase : 100 MB (104,857,600 bytes)
    MaxDumpsterTime            : 7.00:00:00
    MaxReceiveSize             : 150 MB (157,286,400 bytes)
    MaxRecipientEnvelopeLimit  : unlimited
    MaxSendSize                : 150 MB (157,286,400 bytes)
    I'm running Exchange 2010 (with Rollup3 installed), on Server 2008R2.
    My clients are running Entourage 2008 EWS, patched up with the latest Office Mac updates.
    Apart from their inability to send 10+MB attachments, everything else is fine.
    Regards,

    Shane
    Toutges solution worked for us.  Exchange Server 2010 (current patch level as of March 2015), Mac OS Outlook 2011 via EWS.
    Key to the solution is this revision:
    maxReceivedMessageSize value
    to [example value]
    51200000 underneath the heading <EWSMessageEncoderSoap11Element />. There are 6 places to make this change (bytes)
    I have not seen this noted under the several MS Tech Net articles that pertain to the problem of sending large email attachments via Mac Outlook 2011 via EWS.

Maybe you are looking for