Problems backing up DAG after Exchange 2010 SP2 upgrade - nmm 2.3

Ever since we upgraded to MS Exchange 2010 SP2 (Rollup 4 v2) we have been having backing up our Exchange DAG with NMM 2.3 (build 087).  When the DAG backup job starts, we are getting errors that seem to be related to WinRM. 

Here are some of the log entries.  Any help would be much appreciated!!

Matt

(All in the Application Event Log)

(INFO, event ID 2021)

   The Microsoft Exchange VSS Writer has successfully collected the metadata document in preparation for backup.

(ERROR, event ID 24162) - Source: ECCRMAgent

   at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()

   at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult asyncResult)

   at System.Management.Automation.Runspaces.RunspacePool.Open()

   at System.Management.Automation.RemoteRunspace.Open()

   at RM_ESM_2010_NS.RM_ESM_2010.ExecuteCmdlet(String cmdlet, String param, String prop)

(ERROR, event ID 24162) - Source: ECCRMAgent

   Connecting to remote server failed with the following error message : The WinRM client cannot process the request. The authentication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration. Verify the unencrypted traffic setting in the service configuration or specify one of the authentication mechanisms supported by the server.  To use Kerberos, specify the computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic.

(INFO, event ID 0)

   Replication Manager Exchange Interface: Service started.

(ERROR, event ID 24162) - Source: ECCRMAgent

   Cmdlet: get-ExchangeServer  -Identity "WFPEXMBX1"

Then, there were the following lines in the application event log:

NMM initialization of VSS writers has completed.

NMM .. VSS writer objects identified and selected for backup.

The Microsoft Exchange VSS Writer has successfully collected the metadata document in preparation for backup.

The Microsoft Exchange VSS Writer has successfully collected the metadata document in preparation for backup.

Starting Replication of [application set: / job:] at time 2012 12 21 11:17:30.

Connecting to remote server failed with the following error message : The WinRM client cannot process the request. The authentication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration. Verify the unencrypted traffic setting in the service configuration or specify one of the authentication mechanisms supported by the server.  To use Kerberos, specify the computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic.

   at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()

   at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult asyncResult)

   at System.Management.Automation.Runspaces.RunspacePool.Open()

   at System.Management.Automation.RemoteRunspace.Open()

   at RM_ESM_2010_NS.RM_ESM_2010.ExecuteCmdlet(String cmdlet, String param, String prop)

Cmdlet: get-MailboxDatabaseCopyStatus  -Identity "DB3 La- Po\xxxEXMBX1"

Connecting to remote server failed with the following error message : The WinRM client cannot process the request. The authentication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration. Verify the unencrypted traffic setting in the service configuration or specify one of the authentication mechanisms supported by the server.  To use Kerberos, specify the computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic.