After Exchange 2010 SP3 OWA is messed up

After installing SP3 for Exchange 2010 the Outlook webapp stopped working.

Outlook Web App didn't initialize. If the problem continues, please contact your helpdesk.

Couldn't find a base theme (folder name=base).

After some digging I found out that the default theme folder for OWA was empty.

So tried to copy the entire OWA directory from a working CAS-HUB server and pasting it over the empty one.

File copy error's, warning's, what the fcuk are you doing, no go....

So some more digging, and came up with updatecas.ps1.

After running this on the faulty CAS-HUB server al is well:

[PS] C:\Program Files\microsoft\Exchange Server\V14\Bin>.\UpdateCas.ps1
[14:54:52] ***********************************************
[14:54:52] * UpdateCas.ps1: 24.12.2010 14:54:52
Creating a new session for implicit remoting of "Get-ExchangeServer" command...
[14:55:06] Updating OWA/ECP on server "E.server2010"
[14:55:06] Finding ClientAccess role install path on the filesystem
[14:55:07] Updating OWA to version 14.1.270.1
[14:55:07] Copying files from 'C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa\Current' to 'C:\Program
Files\Microsoft\Exchange Server\V14\ClientAccess\owa\14.1.270.1'
[14:55:24] Found 1 OWA virtual directories.
[14:55:24] Updating OWA virtual directories
[14:55:24] Processing virtual directory with metabase path 'IIS://"E.server2010".domain.com/W3SVC/1/ROOT/owa'.
[14:55:24] Creating metabase entry IIS://"E.server2010".domain.com/W3SVC/1/ROOT/owa/14.1.270.1.
[14:55:24] Configuring metabase entry 'IIS://"E.server2010".domain.com/W3SVC/1/ROOT/owa/14.1.270.1'.
[14:55:24] Saving changes to 'IIS://"E.server2010".domain.com/W3SVC/1/ROOT/owa/14.1.270.1'
[14:55:25] Saving changes to 'IIS://"E.server2010".domain.com/W3SVC/1/ROOT/owa'
[14:55:25] Update OWA done.
[14:55:25] Updating ECP to version 14.1.270.1
[14:55:25] Copying files from 'C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\Current' to 'C:\Program
Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\14.1.270.1'
[14:55:27] Update ECP done.

 

Now great news, but on the other hand, why does Microsoft even have this option in the default installation for Exchange? It doesn't show much faith in their own products, or is it just me rambling on about my own frustrations and another Sunday down the drain by doing scheduled maintenance in the weekends....

As we say in the Netherlands: Dan had je maar een vak moeten leren! Than you should have studied a skill! (I think something gets lost in translation....:-)