In this case, you have agent devices on remote networks, but the networks are connected via a point-to-point VPN (typically an “always up” link established between firewalls) or the agent devices are running VPN clientĬonnects the agent device to the local network where your Spiceworks Desktop app server is running.
Tip: Agent devices using a DNS hostname or FQDN? Be sure to check your DNS server’s forward lookup zone to ensure there is an address record (“A” or “AAAA”) with the correct current IP address of the Spiceworksĭesktop app server. 192.168.1.12), but only if the Desktop server has a static IP address Your agents should be configured to connect to the Desktop server using the Desktop server’s HTTPS port, and you can use any of the following: In this case, all of your agent devices are on the same network with the server where Spiceworks Desktop is installed. More about agent deployment see this article. Once you’re ready to deploy agent to all of your devices, the information here will help you determine the best hostname/IP and port combination to use when deploying the agent via command line. Troubleshooting? Check out this guide on troubleshooting agent connectivity problems. It is important to configure your agents properly to ensure they can consistently connect to your Desktop app. accessing Spiceworks using a browser from other workstations or servers on your network(s).
#Spiceworks agent setup android
In fact, these same principals also apply to When installed on devices on your network, the Spiceworks Agent connects to your Desktop app using HTTPS. Agent Best Practices Applies to: Inventory
0 kommentar(er)
