You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some environments ICMP outbound is blocked for security purposes, in these cases the default behavior of InstallAgent is to fail the install or go into offline repair mode of services.
In either case these environments need another method for determining connectivity to the server.
For backwards compatibility The System.Net.Sockets TCP class could possibly be used, but this class gives errors while running under CLI/Scripting due to some kind of .Net configuration issue, similar to the issue experienced.
Another less backwards compatible option is the Test-NetConnection -Port option, this only works on later versions of PowerShell and has some compat issues on Server 2012.
The last method may be to simply perform a https web request against the N-Central server itself, there are basic .Net methods that are compatible with all versions of powershell .
The text was updated successfully, but these errors were encountered:
In some environments ICMP outbound is blocked for security purposes, in these cases the default behavior of InstallAgent is to fail the install or go into offline repair mode of services.
In either case these environments need another method for determining connectivity to the server.
For backwards compatibility The System.Net.Sockets TCP class could possibly be used, but this class gives errors while running under CLI/Scripting due to some kind of .Net configuration issue, similar to the issue experienced.
Another less backwards compatible option is the Test-NetConnection -Port option, this only works on later versions of PowerShell and has some compat issues on Server 2012.
The last method may be to simply perform a https web request against the N-Central server itself, there are basic .Net methods that are compatible with all versions of powershell .
The text was updated successfully, but these errors were encountered: