This post describes how to fix the error: 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. Cause This error can occur if you're connecting via wsman to the wrong port. Note: If you don't specify a port, the connection will be attempted on port 80. connect-wsman -connectionuri http://EXCH-2K16-2.exch2016.net/PowerShell -credential exch2016\sysadmin Fix To resolve the issue, specify the appropriate port. To find out which port to use, run the following PowerShell command on your Exchange server: Get-WSManInstance -ResourceURI winrm/config/listener -Enumerate The default is 5985. connect-wsman -connectionuri http://EXCH-2K16-2.exch2016.net :5985 /PowerShell -credential exch2016\sysadmin Related Posts

In this blog post, I discuss the 'Password must meet complexity requirements' policy, what it means and a regex to test it.  I also describe how you can still set a password which does not meet the complexity requirements. Where is this policy? This policy can be accessed by running secpol.msc > Account Policies > Password Policy: What does this policy do? If you open the policy, the explain text describes what this policy does: There are a couple of things to watch out for with this explain text: 1. Non-alphabetic characters The full list from Microsoft is: ~!@#$%^&*_-+=`|(){}[]:;"'<>,.?/ You will notice that £ and € are missing from this list.  If you include those characters in your password, they are permitted but they do not count towards a category with regards to "Contain characters from three of the following four categories". 2. Length The explain text states "Be at least six characters in length&q

This blog post describes how to fix the error 'The value provided for parameter isn't in the correct format. The correct format is "\<FolderPath>".' Cause This error can occur when creating a new public folder on Microsoft Exchange 2016.  In the screenshot below, I have specified an invalid folder name, however, Exchange still attempts to create the public folder as there is no validation on the text box. You can see the invalid public folder in the list of public folders: As expected, Exchange can't handle an invalid folder name, you get an error if you try to navigate into this folder: Resolution To fix the issue, delete the invalid folder name and create a new folder without using any invalid characters: