Scripting Agent and Exchange Server Woes

I recently worked with a client that we were working to move to Office 365. During the process we wanted to put in new Exchange 2016 servers which required upgrading the existing Exchange 2010 servers to a newer Update Rollup for Service Pack 3. Just trying to kick off an update resulted in an error:

Doing some research I was able to find out that PowerShell can reveal a series of Cmdlet Extensions, of which the Scripting Agent is one of. So running Get-CmdletExtensionAgent, we can reveal the current settings for these agents. On the client’s server, the Scripting Agent was enabled, as reported:
Continue reading

Advertisements