I'll tell you what I did to cause the problem. I installed Sharpoint 2007 on my exchange 2010 server and my exchange management consoles has stoped working. I have read and read articles on line. to no availe. below Ill post some meesages. I have spent days pouring through web sites checking variables from paths of the power shell vdir to eviornmental varialbles. I have ran the trouble shooter and even tried everything listed in http://technet.microsoft.com/en-us/library/ff607221(EXCHG.80).aspx. I am at a loss. What am i missing. first will be a test app results. the powershell vdir looks ok to me. second ill post the acutaul error. Welcome to the Exchange Management Troubleshooter! We recommend that you run the troubleshooter after making changes to IIS to ensure that connectivity to Exchange Powershell is unaffected. Checking IIS Service... Checking the Exchange Install Path variable... Checking the Powershell Virtual Directory... Checking the Powershell vdir SSL setting... Checking the Powershell vdir path setting... Testing for errors... VERBOSE: Connecting to Seaway-CHC-Shar.SeawayCHC.local [seaway-chc-shar.seawaychc.local] Connecting to remote server failed with the following error message : The WinRM client + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExcep + FullyQualifiedErrorId : PSSessionOpenFailed The Exchange Management Troubleshooter successfully completed connecting to: Seaway-CHC-Shar.SeawayCHC.local Failed to connect to any Exchange Server in the current site. Problem found: Looking for error... The Path of the Powershell virtual directory has been modified. The PowerShell virtual directory must point to the "\Exchange Server\v14\ClientAccess\PowerShell" directory or you will encounter problems. After each error is resolved, close this window and re-run the tool to check for additional problems. [EMTS] C:\Windows\System32\WindowsPowerShell\v1.0> now the error. VERBOSE: Connecting to Seaway-CHC-Shar.SeawayCHC.local [seaway-chc-shar.seawaychc.local] Connecting to remote server failed with the following error message : The WinRM clien t cannot process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination comp uter (Seaway-CHC-Shar.SeawayCHC.local:80) returned an 'access denied' error. Change the configuration to allow Kerberos authentication mechanism to be used or specify one of the authentication mechanisms supported by the server. To use Ke rberos, specify the local computer name as the remote destination. Also verify that the client computer and the destina tion computer are joined to a domain. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: Neg otiate For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed VERBOSE: Connecting to Seaway-CHC-Shar.SeawayCHC.local

Hi, Please follow these steps to specify a remote Exchange 2010 server for EMC: 1.OPen EMS,Enter your network credentials and store them in a variable by running the following command. $UserCredential = Get-Credential In the dialog box that opens, type the user name and password of the administrator account that has access to administer the Exchange 2010 server you want to connect to, and then click OK. 2. Open the connection to Exchange 2010 by running the following command. $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://<FQDN of Exchange 2010 server>/PowerShell/ -Authentication Kerberos -Credential $UserCredential 3 .Import the server-side PowerShell session into your client-side session by running the following command. Import-PSSession $Session What's result? Gen Lin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

Hi, Is there any update ? Gen Lin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

[PS] C:\Windows\system32>$UserCredential = Get-Credential cmdlet Get-Credential at command pipeline position 1 Supply values for the following parameters: Credential [PS] C:\Windows\system32>$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://seaway-chc -shar.seawaychc.local/PowerShell/ -Authentication Kerberos -Credential $UserCredential [seaway-chc-shar.seawaychc.local] Connecting to remote server failed with the following error message : Logon failure: unknown user name or bad password. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed [PS] C:\Windows\system32>

[PS] C:\Windows\system32>$UserCredential = Get-Credential cmdlet Get-Credential at command pipeline position 1 Supply values for the following parameters: Credential [PS] C:\Windows\system32>$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://seaway-chc -shar.seawaychc.local/PowerShell/ -Authentication Kerberos -Credential $UserCredential [seaway-chc-shar.seawaychc.local] Connecting to remote server failed with the following error message : The WinRM clien t cannot process the request. The authentication mechanism requested by the client is not supported by the server or un encrypted traffic is disabled in the service configuration. Verify the unencrypted traffic setting in the service confi guration or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the compute r name as the remote destination. Also verify that the client computer and the destination computer are joined to a dom ain. To use Basic, specify the computer name as the remote destination, specify Basic authentication and provide user n ame and password. Possible authentication mechanisms reported by server: Negotiate For more information, see the ab out_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed