Turns out this is a known fault in SP3 updates... although unfortunately for me, following the setup.com /prepareschema approach failed with a rather innocuous 'exchange experienced a problem' error in powershell.