When attempting to create a new exchange forest i get the following error : The attempt to connect using HTTPS protocol "Kerberos" failed: Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic. The attempt to connect using HTTPS protocol "Basic" failed: Connecting to remote server failed with the following error message : The WinRM client cannot process the request. Unencrypted traffic is currently disabled in the client configuration. Change the client configuration and try the request again. For more information, see the about_Remote_Troubleshooting Help topic. The error appears after entering the friendly name and FQDN, then attempting to connect to the friendly name This is my first Exchange 2010 install please help.

hi, What's your environment? How many DC and how many exchange servers? Can you receive or send mail? Please tell us more information. Run the Exbpa to ensure that your environment is ok. Then you should make sure that you enter the right FQDN. This is a reason which can caused the issue. If you have mutiple nic cards, you can try to change the nic pirority. All DCs and exchange servers, time setting should be matched. hope can help you thanks, CastinLu TechNet Community Support