Idea ID: 1678326

PowerCMD via Host Connection by Shell should be using FQDN instead of IP address

Status : Delivered
over 2 years ago

Because PowerCMD is a PowerShell wrapper, IP addresses are generally blocked unless you use SSL or TrustedHost configurations, both of which are fairly uncommon and burdensome to implement.  The Host Connection by PowerShell does reverse the IP and use a FQDN; can this functionality be added to Host Connection by Shell for PowerCMD credentials?  At the very least make it an optional parameter to the job.  This will aid customers who need shell access for discovery but cannot use NTCMD due to security constraints.