PowerShell 远程会话：ESET Nod32 AntiVirus 的问题
我正在第一次尝试使用 PowerShell 远程处理功能。我已经使用帮助文档中的说明设置了“目标”服务器。但是，当我尝试启动远程会话（通过执行“Enter-PSSession servername1”命令）时，它会在那里停留很长时间，并最终给出此错误：
Enter-PSSession：连接到远程服务器失败，并显示以下错误消息：WinRM 客户端无法在指定时间内完成操作。检查计算机名称是否有效且可通过网络访问，并且启用了 Windows 远程管理服务的防火墙例外。有关详细信息，请参阅 about_Remote_Troubleshooting 帮助主题。
我还注意到，当它坐在那里时，我的计算机的性能下降了。查看任务管理器，我发现 ekrn.exe（Nod32 Antivirus 的内核进程）使用了大量 CPU（约 50%，有时甚至更高）。它似乎永远不会停止使用 CPU，直到我终止该进程，并且我做了一些测试，很明显，一旦我执行 Enter-PSSession 命令，它就开始使用所有 CPU。
然后我尝试禁用 Nod32 防病毒软件，执行相同的命令，瞧，它起作用了，并且远程会话正常启动。
但显然禁用我的防病毒软件并不是一个解决方案。谁能建议一个更好的吗？
I am making my first attempts at using PowerShell remoting features. I've set up the "destination" server using the instructions in the help docs. But when I attempt to start a remote session (by executing an "Enter-PSSession servername1" command), it sits there for a long time, and eventually gives this error:
Enter-PSSession : Connecting to remote server failed with the following error message : The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. For more information, see the about_Remote_Troubleshooting Help topic.
I also noticed that while it was sitting there, my computer's performance had degraded. Looking at Task Manager, I see that ekrn.exe, which is the kernel process for Nod32 Antivirus, was using a lot of CPU (~50%, sometimes edging higher). It seems to never stop using the CPU until I kill the process, and I did some testing, and it clearly begins to use all that CPU as soon as I execute that Enter-PSSession command.
I then tried disabling the Nod32 anti-virus, executed the same command, and voilà, it worked, and the remote session started properly.
But obviously disabling my anti-virus isn't a solution. Can anyone suggest a better one?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
事实证明我没有运行最新版本的Nod32。我运行的是版本 3，之后我能够升级到版本 4，问题就消失了。
It turns out I wasn't running the latest version of Nod32. I was running version 3, the I was able to upgrade to version 4, and the problem went away.