Exchange Powershell Not working

Question

Exchange Powershell Not working

Sachin Shinde 1

Hi,
We have Windows Server 2016 & Exchange Server 2016 Standard installed on same server. Windows Server is having role of Active Directory, DNS, Global catlog and all.

When we start Exchange Powershell on server it wont connect and gives below error.

VERBOSE: Connecting to Hostname.Domain.COM.
New-PSSession : [hostname.domain.com] Connecting to remote server hostname.domain.com failed with the
following error message : WinRM cannot process the request. The following error occurred while using Kerberos
authentication: Cannot find the computer hostname.domain.COM. Verify that the computer exists on the network
and that the name provided is spelled correctly. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1

New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
FullyQualifiedErrorId : NetworkPathNotFound,PSSessionOpenFailed
VERBOSE: Connecting to hostname.domain.COM.
New-PSSession : [hostname.domain.com] Connecting to remote server hostname.domain.com failed with the
following error message : WinRM cannot process the request. The following error occurred while using Kerberos
authentication: Cannot find the computer hostname.domain.COM. Verify that the computer exists on the network
and that the name provided is spelled correctly. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
FullyQualifiedErrorId : NetworkPathNotFound,PSSessionOpenFailed
VERBOSE: Connecting to hostname.domain.COM.
New-PSSession : [hostname.domain.com] Connecting to remote server hostname.domain.com failed with the
following error message : WinRM cannot process the request. The following error occurred while using Kerberos
authentication: Cannot find the computer hostname.domain.COM. Verify that the computer exists on the network
and that the name provided is spelled correctly. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
FullyQualifiedErrorId : NetworkPathNotFound,PSSessionOpenFailed
VERBOSE: Connecting to hostname.domain.COM.
New-PSSession : [hostname.domain.com] Connecting to remote server hostname.domain.com failed with the
following error message : WinRM cannot process the request. The following error occurred while using Kerberos
authentication: Cannot find the computer hostname.domain.COM. Verify that the computer exists on the network
and that the name provided is spelled correctly. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
FullyQualifiedErrorId : NetworkPathNotFound,PSSessionOpenFailed
VERBOSE: Connecting to hostname.domain.COM.
New-PSSession : [hostname.domain.com] Connecting to remote server hostname.domain.com failed with the
following error message : WinRM cannot process the request. The following error occurred while using Kerberos
authentication: Cannot find the computer hostname.domain.COM. Verify that the computer exists on the network
and that the name provided is spelled correctly. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
FullyQualifiedErrorId : NetworkPathNotFound,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.: hostname.domain.com
VERBOSE: Connecting to hostname.domain.com.
New-PSSession : [hostname.domain.com] Connecting to remote server hostname.domain.com failed with
the following error message : WinRM cannot process the request. The following error occurred while using
Kerberos authentication: Cannot find the computer hostname.domain.com. Verify that the computer exists on
the network and that the name provided is spelled correctly. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSR
emotingTransportException
FullyQualifiedErrorId : NetworkPathNotFound,PSSessionOpenFailed
[PS] C:\Windows\system32>

When we ping host name from server it shows result (Reply From : : 1 time <1ms)

We have unbind and disabled IPV6 from Network card.

Thanks,
Sachin Shinde

2 answers

Your answer

Answer 1

Manu Philip 20,491 MVP Volunteer Moderator

Have you connected to the server using domain login? check it using the command whoami in command prompt. If not, re-login as domain user with proper privilege and check Exchange PS again

Sachin Shinde 1 Reputation point

2021-12-09T09:28:47.257+00:00

Hi,

Yes connected with domain administrator account. Issue with all domain admin accounts.

Thanks,
Sachin
Manu Philip 20,491 Reputation points MVP Volunteer Moderator

2021-12-09T10:22:26.18+00:00

Another reason can be the SSL certificate is not selected for the Exchange Back End website in IIS console. To correct this, Go to IIS Manager right-click the Exchange Back End website and click Bindings. Highlight https and click Edit. If you see “Not selected”, click on Select. Choose the certificate you want to bind to the site. Apply the changes and retry the Exchange management shell.
Sachin Shinde 1 Reputation point

2021-12-09T11:54:11.347+00:00

Hi,

We have already selected certificate for Https on Exchange Back End.

Thanks,
Sachin Shinde
Manu Philip 20,491 Reputation points MVP Volunteer Moderator

2021-12-09T13:37:16.907+00:00

Looks like there are some basic things not working.
If it's a WinRM config issue, the document need to follow is here: fail-to-start-exchange-management-shell-console
If it not helps, check all services are fine including windows services, IIS etc. If needed, recreate PS virtual directory and test again
Sachin Shinde 1 Reputation point

2021-12-09T14:03:08.963+00:00

Hi,

We have tried those steps mentioned in below link
https://learn.microsoft.com/en-US/exchange/troubleshoot/administration/fail-to-start-exchange-management-shell-console

Exchange Management Powershell not working with any user so cant run Get-User command to check powershell enabled user.

Also when we open WinRM QuickConfig & WinRM enumerate winrm/config/listener its just flashes and closes the window.

Seems some issue with DNS as we ping with host name it gives below result.
(Reply From : : 1 time <1ms)

Thanks,
Sachin Shinde
Manu Philip 20,491 Reputation points MVP Volunteer Moderator

2021-12-09T14:46:35.61+00:00

Check, if the DNS settings are correct in DNS console.
Right click the DNS server and select properties> Check Interfaces, Forwarders settings are fine
_msdcs.domain.com > Check the name servers are correctly added

Answer 2

KyleXu-MSFT 26,396

@Sachin Shinde

Do you install Exchange server on the DC? It isn't suggested which may cause many issues.

About this issue, I would suggest you try to ping the hostname.domain.com first, mare there doesn't exist issue with DNS record.

Then try to connect to Exchange on-premises with remote PowerShell, check whether there exists an issue with EMS virtual directory.

If you could connect to Exchange with remote PowerShell, you can use command below to check configuration for EMS virtual directory:

Get-PowerShellVirtualDirectory -Server Exch2016 | fl

If you cannot connect to Exchange with remote PowerShell, you could take step below to recreate EMS virtual directory:

Run PowerShell with administrator permission.
Import manage module with command below: add-pssnapin Microsoft.Exchange.Management.PowerShell.SnapIn
Remove old EMS virtual directory: Get-PowerShellVirtualDirectory -Server Exch2016 | Remove-PowerShellVirtualDirectory
Create a new one with command below: New-PowerShellVirtualDirectory -Name Powershell -RequireSSL:$False

Then run IISReset in PowerShell, after that, try to open EMS again.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Sachin Shinde 1 Reputation point

2021-12-10T10:10:30.793+00:00

Hi,

Yes we have installed Exchange server on domain controller which also has DNS server. We are using this server only for 20 users so installed everything on single server. As it is small setup we cant move any role at this moment.
When we ping with hostname we are getting below result-
(Reply From : : 1 time <1ms)

Tried to connect to Exchange on-premises with remote PowerShell, and its connecting with PowerShell.

Thanks,
Sachin
KyleXu-MSFT 26,396 Reputation points

2021-12-13T08:43:53.09+00:00

Try to check and compare the configuration with the information I provided. If all configuration are same, you could try to recreate the virtual directory with above suggestion.
Sachin Shinde 1 Reputation point

2021-12-13T09:34:27.697+00:00

Hi,

Compared directory configuration with the information provided, it is same as given. Also tried by recreating virtual directory but same issue.

Is it because of ping issue result with hostname?

Thanks,
Sachin
KyleXu-MSFT 26,396 Reputation points

2021-12-14T08:51:37.787+00:00

Since you could connect to it from remote PowerShell, I think this phenomenon is caused by DNS confusion in your organization. It is suggested to split Exchange from DC.

Share via

Exchange Powershell Not working

2 answers

Your answer