Hi There,
I have Multiple Server Role deployment setup in a virtual test environment without internet connection. So my CAS and Mailbox roles are on separate servers.
A few days ago I decide to install CU3 and followed most of the online documentation in order to have a successful installation.
As recommended I started the installation on the mailbox role. Putting the server in maintenance mode, installing CU3 and taking the server out of maintenance mode went flawless. All components were back in an active state after the installation.
Then I applied the same steps on my CAS role, not knowing if it was needed by then. Afterwards it was not needed according to a forum I visited, cause they said the CAS Role is stateless and only does proxy... After the successful installation, If I run the Get-ServerComponentState –Identity <ServerID> I see a few components inactive who were active before. Also If I run Get-HealthReport I get a few HealthSets offline so unhealthy.
Are these cmdlets for the Mailbox server only? Or did the install of CU3 break something? They don't change status after rebooting either. All works well, so I don't see no issue yet. Just don't understand the inactive components which won't start after setting ServerWideOffline to active on the CAS role.
The inactive components are: ActiveSyncProxy ; EwsProxy ; OabProxy ; RpcProxy
Unhealthy HealthSets: ActiveSync (Not Applicable); AutoDiscover.Proxy (online); ActiveSync.Proxy (offline) ; Ews.Proxy (offline); OutlookMapi.proxy (online); OAB.Proxy (offline); Outlook.Proxy (offline); AutoDiscover (Not Applicable); EWS (Not Applicable) ; OWA (Not Applicable) ; FrontEndTransport (online); RPS (Not Applicable) ; ECP (Not Applicable) ; FEP (Not Applicable).
Any Ideas? Or is this normal?
Hope to hear from you