none
Exchange 2010 SP1 RU 1 - Install issue

    Question

  • I've tried installing rollup 1 for Exchange 2010 SP1 on four servers so far (client access roles, 2008 R2 Standard) and had poor results. After some testing, it seems that it disables a bunch of services as it stops them, but when it gets to the point that it wants to start them, it doesn't re-enable them first. The update then rolls back, but the services are still disabled, forcing me to fix them manually.

    If I manually fix the startup type of each affected service shortly after the patch stops the services (while it's still installing) then the patch will be able to start the services and appears to install correctly.

    Has anyone else experienced this?

    FYI on the powerShell code I've been using to fix the services, in case this happens to anyone else:

    Set-Service "IISADMIN" -StartupType Automatic
    Set-Service "MSExchangeADTopology" -StartupType Automatic
    Set-Service "MSExchangeAB" -StartupType Automatic
    Set-Service "MSExchangeFDS" -StartupType Automatic
    Set-Service "MSExchangeFBA" -StartupType Automatic
    Set-Service "MSExchangeImap4" -StartupType Manual
    Set-Service "MSExchangeMailboxReplication" -StartupType Automatic
    Set-Service "MSExchangeMonitoring" -StartupType Manual
    Set-Service "MSExchangePop3" -StartupType Manual
    Set-Service "MSExchangeProtectedServiceHost" -StartupType Automatic
    Set-Service "MSExchangeRPC" -StartupType Automatic
    Set-Service "MSExchangeServiceHost" -StartupType Automatic
    Set-Service "RemoteRegistry" -StartupType Automatic
    Set-Service "Winmgmt" -StartupType Automatic
    Set-Service "W3SVC" -StartupType Automatic

    • Edited by Dragonskin Friday, October 08, 2010 3:47 PM
    Friday, October 08, 2010 2:46 PM

All replies

  • Hi Dragonskin.

    Just like it used for previous RU's, you'd better open an elevated prompt and then launch the RU .msp package from the command line.

    That did the trick for me, and I've had no issues with services nor functionalities.

    So far, Win 2008SP2, upgrading from 218.13 (SP1RTM) to 255.0 (SP1RU1).

    Hope this helps.

    -francesco


    Francesco Bosticco General HQ of Guardia di Finanza Datacenter Manager TAP since year 2000 ***
    Friday, October 08, 2010 3:00 PM
  • Thanks for the response, but unfortunately, that's how I have been running it. :|

    Friday, October 08, 2010 3:01 PM
  • After using the method I mentioned above to finish getting it applied to all of my client access servers (and I did try to apply it normally to each one before I resorted to fixing the services during the patch), I moved on to the hub transport servers. Even though I make absolutely sure I ran it from an administrative command prompt, it acted exactly the same as with the client access servers... rolled back and left services disabled.

    So, I tried again with the method listed above (and a new list of services) and then it installed fine.

    Additional history/information: The Exchange installs aren't even a week old, and were installed straight from the Exchange 2010 SP1 files (they were not upgrades from Exchange 2010 RTM).

    Additional weirdness: I have a test environment where Exchange 2010 was upgraded from RTM to SP1 (all running on servers built from the same OS image as the production servers). The rollup appears to apply correctly on those servers, but not the ones that started out as Exchange 2010 SP1.

    Commands to fix the services for the hub role:

    Set-Service "MSExchangeADTopology" -StartupType Automatic
    Set-Service "MSExchangeAntispamUpdate" -StartupType Automatic
    Set-Service "MSExchangeEdgeSync" -StartupType Automatic
    Set-Service "MSExchangeMonitoring" -StartupType Manual
    Set-Service "MSExchangeProtectedServiceHost" -StartupType Automatic
    Set-Service "MSExchangeServiceHost" -StartupType Automatic
    Set-Service "MSExchangeTransport" -StartupType Automatic
    Set-Service "MSExchangeTransportLogSearch" -StartupType Automatic
    Set-Service "RemoteRegistry" -StartupType Automatic
    Set-Service "Winmgmt" -StartupType Automatic
    Set-Service "W3SVC" -StartupType Automatic

     

    Friday, October 08, 2010 4:02 PM
  • I can corroborate this behavior on new installs with Exchange 2010 SP1.  UR1 disables services and then does not re-enable them, causing the MSP to roll back.  I thought this might be a glitch with the beta of Windows Server 2008 R2 SP1, but it seems to be the Exchange rollup script.

     

    The workaround procedure is to launch the MSP install from an elevated command line.  It goes through the pre-check and generation sequence, and you click OK when it is ready.  If you watch the status phases, you will see it stop the services, validate the install, copying files, writing registry values, and creating native images for Exchange assemblies.  At this stage of the install (which takes the longest), you will want to re-enable all the required exchange services.  Then it will restart the services and complete patching successfully.

     

    I have included a full list of commands you can copy into a batch file to run while the update is “Creating native images for Exchange assemblies.”  The first script assumes the MBX, HTS, CAS, and UM roles are all installed on one box; the second script is for the Edge Role.  Customize to fit your server’s role.

     

    I use the sc command instead of Set-Service because it provides more options for startup type; I find the servers boot up cleaner when heavy services are delayed – a nice feature of 2008/R2. 

     

    Exchange2010-MBX-HTS-CAS-UM-Enable.cmd

    ======================================

    @echo off

    rem sc config <service_name> start= {boot|system|auto|demand|disabled|delayed-auto}

     

    sc config IISADMIN start= delayed-auto

    sc config MSExchangeADTopology start= delayed-auto

    sc config MSExchangeAB start= delayed-auto

    sc config MSExchangeAntispamUpdate start= delayed-auto

    sc config MSExchangeEdgeSync start= delayed-auto

    sc config MSExchangeFDS start= delayed-auto

    sc config MSExchangeFBA start= delayed-auto

    sc config MSExchangeImap4 start= delayed-auto

    sc config MSExchangeIS start= delayed-auto

    sc config MSExchangeMailSubmission start= delayed-auto

    sc config MSExchangeMailboxAssistants start= delayed-auto

    sc config MSExchangeMailboxReplication start= delayed-auto

    sc config MSExchangeMonitoring start= delayed-auto

    sc config MSExchangePop3 start= delayed-auto

    sc config MSExchangeProtectedServiceHost start= delayed-auto

    sc config MSExchangeRepl start= delayed-auto

    sc config MSExchangeRPC start= delayed-auto

    sc config MSExchangeSearch start= delayed-auto

    sc config wsbexchange start= delayed-auto

    sc config MSExchangeServiceHost start= delayed-auto

    sc config MSExchangeSA start= delayed-auto

    sc config MSExchangeThrottling start= delayed-auto

    sc config MSExchangeTransport start= delayed-auto

    sc config MSExchangeTransportLogSearch start= delayed-auto

    sc config MSExchangeUM start= delayed-auto

    sc config msftesql-Exchange start= delayed-auto

    sc config RemoteRegistry start= delayed-auto

    sc config Winmgmt start= delayed-auto

    sc config W3SVC start= auto

     

    Exchange2010-EdgeEnable.cmd

    ==========================

    @echo off

    sc config ADAM_MSExchange start= delayed-auto

    sc config MSExchangeAntispamUpdate start= delayed-auto

    sc config MSExchangeEdgeCredential start= delayed-auto

    sc config MSExchangeMonitoring start= delayed-auto

    sc config MSExchangeServiceHost start= delayed-auto

    sc config MSExchangeTransport start= delayed-auto

    sc config MSExchangeTransportLogSearch start= delayed-auto

    sc config RemoteRegistry start= delayed-auto

    sc config Winmgmt start= delayed-auto

    Thursday, October 21, 2010 5:24 PM
  • AT LAST !!!!  I find an article on a problem I've been experiencing for a long time !!

    I thought I was doing something wrong ... Is it me or MS should be more carefull when making their installables ???

    It took me forever to notice WMI was stopped ....

    Anyhow ... Roll Up 1 was finally installed successfully

    Chantal


    Chatou7
    • Proposed as answer by PB_Mike Monday, March 21, 2011 2:53 PM
    Monday, November 29, 2010 4:34 PM
  • Chantal

     

    Im having the exact same issues. IM assuming your referring to WMI performance Adapter service should be started? Should I uninstall or just re-try to install rhw Rollup 5 for Exchange 2011 KB 2582113.

     

    Jerry

    Monday, October 17, 2011 9:13 PM
  • Dragonskin,

     

    Im having the exact same issues. IM assuming your referring to WMI performance Adapter service should be started? Should I uninstall or just re-try to install rhw Rollup 5 for Exchange 2011 KB 2582113. I uninstalled rebooted and all services are still disabled. Manually kicked them off and system is working. Please let me know your recommnedations:

    1: Should I re-install Roll up 5 to SP1 KB 2582113?

    2: If I re-install will the service pack fix the "start-up type". how it should be?

    Let me know your thoughts.

     

    Jerry

     

    Monday, October 17, 2011 10:16 PM
  • Posted in your other post, youre on the right track, do it manually, it still works.
    Sukh
    Tuesday, October 18, 2011 6:59 PM
  • Weltklasse...damit hab auch den SP 2 installiert bekommen nach langer Fehlersuche!!

     

    Thanks

    Saturday, February 04, 2012 9:28 AM