Exchange Server 2007 rollups nightmares – automate the .config file modification


Most of you Microsoft Exchange Server 2007 admins or Loadgen users as have been confronted with the problem described here : (Exchange 2007 managed code services do not start after you install an update rollup for Exchange 2007).


Those who read the above technote probably felt as I did that every solution given where stupid. You know what? They are ! Who wants to configure Internet access on an Exchange server?  


A very good description and the ‘right” solution is given by Nino and the team on the EHLO blog : http://msexchangeteam.com/archive/2008/07/08/449159.aspx


I’ve taken the liberty to automate the .config file modification for you, just run the script on your server and this will do the job:  


ChangeExchangeConfigFile.PS1 will create, modify any .config file for :




  • Exchange services only (checking them against the service database)


  • Any exchange .exe file in the Exchange installation folder


  • or any path you will want to give

Click here for the script itself.


Edit : small bug correction on the script.
Edit2: (version 1.2) let’s home is is the last bug !


 


 

changeExchangeConfigFiles.PS1

Comments (7)

  1. Anonymous says:

    La plupart d’entre vous le savent déjà, passer les rollups Exchange 2007 dans des infrastructures non

  2. Anonymous says:

    My previous post about Exchange 2007 SP1 RU5 at () explained why Exchange Services where so slow to start

  3. Anonymous says:

    Impatient à l’ouverture de vos consoles Exchange ? Mes VirtualLab ont bon dos. Cependant lorsque ce cas

  4. Anonymous says:

    La plupart d’entre vous le savent déjà, passer les rollups Exchange 2007 dans des infrastructures non

  5. Anonymous says:

    Quick update from my previous post about rollups. RU4 still has the same CRL check behavior and the script

  6. JOhn Dillinger says:

    This script worked perfectly for me. I had exact same problem and this solved it.

    Cannot believe that after so much time this issue is still not resolved and even that something like this happens on a clean Windows Server 2008 and Exchange 2007 SP1 RU4 install???