With HDGUARD.master, all HDGUARD-protected PCs and notebooks in the network can be managed simply and conveniently.
From a central workstation in the local network, control, installation and maintenance work can be carried out quickly and effectively.
HDGUARD.remote enables access to all HDGUARD.master functions via the Internet, town/city network or company network.
All maintenance and service tasks can be carried out from a remote workstation. For schools with various sites or town/city-wide support from the relevant local education authority, HDGUARD.remote is the solution for ensuring the provision of effective support for all HDGUARD-protected PCs.
The HDGUARD.remote solution consists of three main components: a notebook/PC with HDGUARD.master and HDGUARD.remote, an HDGUARD.remote proxy on a public server and an HDGUARD.remote service in the local network LAN with HDGUARD clients.
HDGUARD.remote establishes a secure connection in order to operate remote HDGUARD clients in the same way as if they were in the local network.
The HDGUARD clients are connected to the WAN or Internet via HDGUARD.remote service. If there are several HDGUARD.master instances, these use the HDGUARD.remote service to exchange data. This exchange of data is transparent and in real time so that users at different locations have the same view of a given HDGUARD network and can control this network.
An HDGUARD.remote proxy is installed on an overlapping Internet or WAN server in order to route the data from the firewall-protected LAN network to HDGUARD.remote.
The network can be extended to include any desired number of additional PCs, HDGUARD clients and LANs. One of the special features of HDGUARD.remote is its ability to establish a route between two remote networks across several hubs. For this purpose, HDGUARD.remote service is configured in such a way that it can connect with another HDGUARD.remote service. This means that several services can be linked to one route. The way in which this route is established (hierarchically or linearly) depends on the underlying network structure and the relevant components.