积极答复者
打开exchange2016 management shell报错

问题
-
我在同一域内装了两台exchange2016,,第二台打开报错如下。
----------------------------------------------------------------------------------------------------------------------------------
Welcome to the Exchange Management Shell!
Full list of cmdlets: Get-Command
Only Exchange cmdlets: Get-ExCommand
Cmdlets that match a specific string: Help *<string>*
Get general help: Help
Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List
Show quick reference guide: QuickRef
Tip of the day #86:
Use this command to get all active mailbox move requests on a mailbox server:
$(Get-MailboxDatabaseCopyStatus -Server MBX | ?{ $_.status -eq "Mounted" }) | %{ Get-MoveRequest -TargetDatabase $_.Data
baseName } | ?{ $_.Status -ne "Completed" -and $_.Status -ne "CompletedWithWarning" }
VERBOSE: Connecting to exch02.a.com.
New-PSSession : [exch02.a.com] Connecting to remote server exch02.a.com failed with the following error message :
WinRM cannot process the request. The following error with errorcode 0x8009030e occurred while using Kerberos
authentication: A specified logon session does not exist. It may already have been terminated.
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.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : 1312,PSSessionOpenFailed
VERBOSE: Connecting to exch01.a.com.
New-PSSession : [exch01.a.com] Connecting to remote server exch01.a.com failed with the following error message :
WinRM cannot process the request. The following error with errorcode 0x8009030e occurred while using Kerberos
authentication: A specified logon session does not exist. It may already have been terminated.
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.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : 1312,PSSessionOpenFailedFailed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:------------------------------------------------------------------------------------------------------------------------------
请问应该怎么解决?
答案
-
您好,
根据您的描述和提供的错误信息,推测问题出现的原因在于您登陆的账户。
请您在Powershell中运行whoami命令确认您当前登陆的账户为域管理员账户,而不是此服务器的本地管理员账户。
此致,
Kael Yao
如果以上回复对您有所帮助,建议您将其“标记为答复”. 如果您对我们的论坛支持有任何的建议,可以通过此邮箱联系我们:tnsf@microsoft.com.
- 已标记为答案 skeleton key 2020年8月3日 3:04
-
您好,
请问是这台服务器的Exchange Management Shell无法识别命令吗?
具体是哪一个命令无法识别,还是所有命令都无效呢?
此致,
Kael Yao
如果以上回复对您有所帮助,建议您将其“标记为答复”. 如果您对我们的论坛支持有任何的建议,可以通过此邮箱联系我们:tnsf@microsoft.com.
- 已标记为答案 skeleton key 2020年8月4日 7:40
全部回复
-
您好,
根据您的描述和提供的错误信息,推测问题出现的原因在于您登陆的账户。
请您在Powershell中运行whoami命令确认您当前登陆的账户为域管理员账户,而不是此服务器的本地管理员账户。
此致,
Kael Yao
如果以上回复对您有所帮助,建议您将其“标记为答复”. 如果您对我们的论坛支持有任何的建议,可以通过此邮箱联系我们:tnsf@microsoft.com.
- 已标记为答案 skeleton key 2020年8月3日 3:04
-
您好,
请问是这台服务器的Exchange Management Shell无法识别命令吗?
具体是哪一个命令无法识别,还是所有命令都无效呢?
此致,
Kael Yao
如果以上回复对您有所帮助,建议您将其“标记为答复”. 如果您对我们的论坛支持有任何的建议,可以通过此邮箱联系我们:tnsf@microsoft.com.
- 已标记为答案 skeleton key 2020年8月4日 7:40
-
您好,
请问您现在使用的账号是域管理员账号,可以正常打开EMS,但输入任何命令都无效吗?
如果方便的话,请您提供一下EMS中报错信息的截图。
(请注意,为了安全起见,在您提供截图时请隐藏个人信息。)
此致,
Kael Yao
如果以上回复对您有所帮助,建议您将其“标记为答复”. 如果您对我们的论坛支持有任何的建议,可以通过此邮箱联系我们:tnsf@microsoft.com.