PowerShell remote sessions: Problems with ESET Nod32 AntiVirus -


I am trying my first attempt to use PowerShell Remoting features. I have set the "destination" server using instructions in the help docs. But when I try to start a remote session (by executing the "Enter-PSSession servername1" command), it sits for a long time, and finally gives this error:

enter- PSSession: Connect to the remote server failed with the following error message: WinRM client can not complete the operation within specified time. Check that the name of the machine is valid and is accessible on the network and firewall exception is enabled for the Windows Remote Management service. For more information, see about_Remote_Troubleshooting help topic

I also noticed that when it was sitting there, my computer's performance had worsened. Looking at the task manager, I know that ekrn.exe, which was the kernel process for Nod32 antivirus, was using very CPU (~ 50%, sometimes high strand). It seems that as long as I can not kill the process, I do not stop using the CPU, and I did some tests, and it clearly starts to use all the CPUs like I execute the Enter-PSSession command .

I then tried to deactivate the Nod32 anti-virus, executed the same order, and the voice, it worked, and the remote session started properly

But Obviously disabling my anti-virus is not a solution, can someone give a better suggestion?

It turns out that I was not running the latest version of Nod32. I was running Version 3, I was able to upgrade to version 4, and the problem went away.


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -