Idea ID 2857717
When attempting remote management tasks and quick tasks on a managed device that is on a private network, is on the other side of a firewall, or behind a router that is using NAT there are extra steps that the administrator needs to perform for that task to be successful. I believe that these steps could be automated within ZCC therefore increasing the success rate of the tasks.
Join Proxy server is in the DMZ
Join Proxy server is not in DNS
Opportunity for improvement #1: When attempting a quick task, the administrator must set the "Select the primary server to send the Quick Task notification" to the primary in the DMZ for the quick task to be successful.
So, if the managed device you are trying to remote control is already connected to the Join Proxy, then the "Route Through Join Proxy" option is selected by default and the values for the Join Proxy and Join Proxy Port options are pre-populated (this is awesome, great work!), however the default value is the server name. This action returns a "No such host is known" error. I would like to suggest that when the managed device is connect to the Join Proxy the value pre-populated for the Join Proxy be set to the IP address of that primary.
Opportunity for improvement #2: When attempting a remote management task, the administrator must click "More Options" and select the IP address rather than the DNS name for the Join Proxy server in order to complete the remote management task. *As mentioned before our join proxy server is in the DMZ and it's hostname is not resolvable through DNS.
As seen above, ZCC is able to determine that the managed device is connected to the Join Proxy. So, it seems like the Quick Tasks could default to use the primary in the DMZ rather than the "Current primary server" when the managed device is determined to be connected to the Join Proxy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.