Browsed by
Month: June 2014

error connecting to EMS on exchange server – The WinRM client cannot process the request

error connecting to EMS on exchange server – The WinRM client cannot process the request

Connecting to remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.     + CategoryInfo          : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc    eption     + FullyQualifiedErrorId : PSSessionOpenFailed

 

check: https://localhost/powershell

if it says module WinRM not found, edit C:WindowsSystem32InetsrvconfigApplicationHost.config file.

insert         <add name=”WSMan” image=”C:Windowssystem32wsmsvc.dll” />

under <globalmodules> section

may need to restart iis (iisreset in commandline). When running EMS it may take a while before finally connecting, then it’s plain sailing.

dns fails registration in windows 2008r2 cluster

dns fails registration in windows 2008r2 cluster

taken from: http://jaminquimby.com/joomla253/servers/81-windows-server/windows-server-2008-r2/473-cluster-name-resource-failed-registeration-in-dns

 

In DNS Management (dnsmgmt.msc):

  1. Find the VirtualClusterName that is failing to register.
  2. Right-Click Properties.
  3. Select Security Tab.
  4. Click Add.
  5. Click Object Types.
  6. Check off “Computers“; uncheck other options selected.
  7. Enter in the name of the cluster (a.k.a Cluster Name Object (CNO)).
  8. Click Check Names; Verify that the entry has been found.
  9. Click OK.
  10. Give the CNO FULL Control over this record.
  11. Click OK.
loading and unloading peformance counter in Exchange 2010

loading and unloading peformance counter in Exchange 2010

To unload performance counters for ESE, perform the following steps:

  • Close down any running versions of Performance Monitor and stop any other monitoring services that might be attempting to use those counters
  • Open the Exchange Management Shell
  • Type add-pssnapin Microsoft.Exchange.Management.PowerShell.Setup and hit enter
  • Type remove-perfcounters –definitionfilename “C:Program FilesMicrosoftExchange ServerV14BinperfAMD64eseperf.xml” and hit enter
    Note: Ensure that the path is changed to the correct location of eseperf.xml on your server

To reload performance counters for ESE, perform the following steps

  • Close down any running versions of Performance Monitor and stop any other monitoring services that might be attempting to use those counters
  • Open the Exchange Management Shell
  • Type add-pssnapin Microsoft.Exchange.Management.PowerShell.Setup and hit enter
  • Type new-perfcounters –definitionfilename “C:Program FilesMicrosoftExchange ServerV14BinperfAMD64eseperf.xml” and hit enter
    Note: Ensure that the path is changed to the correct location of eseperf.xml on your server

http://blogs.technet.com/b/mikelag/archive/2010/09/10/how-to-unload-reload-performance-counters-on-exchange-2010.aspx