Exchange 2013 SP1 Installation

Posted on 2014-07-16
Last Modified: 2014-07-29
I am planning on installing SP1 for Exchange 2013. This is to prepare the server for Office 365 mailbox migration.

My question is after installing SP1 is there a system reboot required and are there any other major implications to consider?

If anyone has any experience with this issue your advice is welcome.
Thank you
Question by:carloc
    LVL 34

    Expert Comment

    by:Seth Simmons
    yes you will need to reboot when it finishes

    can't comment on the office 365 part; only did hybrid setup with exchange 2010 a couple years ago
    LVL 5

    Expert Comment

    Didn't check the documentation but a reboot is required.
    And a schema upgrade.

    Just checked: After you install a service pack, you must restart the computer so that changes can be made to the registry and operating system. quote from the technet article After you install a service pack, you must restart the computer so that changes can be made to the registry and operating system. so yes.

    Hybrid setup is the same as in 2010, no changes here.
    LVL 19

    Accepted Solution

    SP1 = CU4, and at this point due to bug fixes I would recommend CU5 instead.

    When you run any CU (Commutative Update) on Exchange, the update will prepare the schema and active directory for you as long as you are an Enterprise and Schema admin (or the account running the update is in those AD Security Groups).

    In addition, when Exchange does the CU installation services will stop and start. Post installation for the server to function properly you will need to reboot the server.

    Last thing to keep in mind is if you have any customer IIS level changes (such as authentication changes, custom OWA, OWA shortening or SSL offloading) these settings should be documented and backed up, as Exchange 2013 CU installation resets IIS back to the factory defaults unless they are settings that are done within Exchange (the ones listed above are done within the IIS 8 / 8.5 console, so these are not Exchange managed properties).

    That is all I can think of. Just plan for an outage window of at least 1-2 hours to be on the safe side.

    Author Closing Comment

    Thanks for your help.
    Yes we needed to reboot the server. The install took about 3 hours to complete after we performed database backups . We did not have any issues at all during or after the reboot. OWA and other services connected straight away.


    Featured Post

    IT, Stop Being Called Into Every Meeting

    Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

    Join & Write a Comment

    Suggested Solutions

    Data center, now-a-days, is referred as the home of all the advanced technologies. In-fact, most of the businesses are now establishing their entire organizational structure around the IT capabilities.
    Easy CSR creation in Exchange 2007,2010 and 2013
    The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
    Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

    731 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now