GeekSpaz , thanks for the suggestions to run C:\Program Files\MicrosoftExchange ServerV14\Bin\UpdateCas.ps1 and the IISReset, but sadly that made no difference. I also see in the troubleshooting a suggestion to run UpdateConfigFiles.ps1 after UpdateCas.ps1.
We remain unable to patch our Exchange 2010 SP3 servers with RU31 or Ru32 so it would appear to be me that RU31 is broken and the defect is also in RU32. After patching the server with the CAS role and holding the test mailbox, I see errors on the OTHER webmail server that has NOT been patched. Not patched because applying to one server takes it out. On the webmail server I found an event 136 and Source MSExchange OWA at the same time the OWA login says " The mailbox you're trying to access isn't currently available. If the problem continues, contact your helpdesk." Are these Exchange 2010 SP3 servers looking to have the same RU level in order to have basic functionality working? Is it possible that this is just an issue known to an experienced Exchange admin (which we do not have...why I am trying get us to O365)?
"The sign-in to Outlook Web App failed. User /O=xxxxx/OU=yyyyy/cn=Recipients/cn=test2 has a mailbox on 14.3.123.0 server version. However, no Client Access server or front-end server with a matching version was found to handle the request.
For users on Exchange 2007 and above, you can configure the Outlook Web Access URL for redirection using the externalURL parameter on the Exchange /owa virtual directory."