12th March, 2010  

Always install Exchange 2010 rollups from an elevated command shell

If you simply double-click on an Exchange 2010 rollup package to install, as the installation instructions tell you to, it will prompt for elevation. Grant it, and it will appear to install correctly. However, you may soon find that your Outlook Web Access is tanked.

Always launch the rollup installer from an elevated command shell, by right-clicking on the Cmd or PowerShell shortcut (depending on which one you’re using) and selecting Run as Administrator.

If you’ve already run it the normal way and your OWA is currently a steaming pile of wreckage, simply run the rollup again from the elevated shell, and it should be working after the second install.

This was widely reported with rollup 1 and is definitely still a problem with rollup 2. Perhaps with rollup 3, Microsoft will actually document the correct install procedure.

Tags: , ,

About The Angry Technician

The Angry Technician is an experienced IT professional in the UK education sector. Normally found in various states of annoyance on his blog. All views are those of his imaginary pet dog, Howard.

5 responses to “Always install Exchange 2010 rollups from an elevated command shell”

  1. Tom Bennett says :

    How are you getting on with Exchange 2010? Like?

    • AngryTechnician says :

      Other than the above, I’ve had no issues with it. Really like the cross-platform OWA client.

      • TheCrust says :

        Me too.

        I just wish they would give me the option to disable the conversational view for all OWA users from a single central point – I haven’t found it yet and I strongly suspect it’s not there.

        While educating staff – and students – to use a subject line appropriate to their message (or even a subject line at all!) would perhaps be Microsoft’s response to those who have been annoyed by the “helpful” conversational threading, it’s rather a long-term view as it won’t solve the problem overnight. From my perspective right now it would be nice to have the ability to turn the feature off globally.

        It will be there in Outlook 2010 – either through an official administrative template or a custom one I write myself – but it will be there. :-)

  2. Patrick says :

    So, what do you do if you can’t run powershell? I now get .NET errors and powershell will not run. and even run from an admin cmd prompt, the install will still try to run powershell.