Client web administration
You may have already worked with an endpoint's local configuration application, or even with NoTouch Center. Another way exists to configure the local OS - you can simply point your web browser to the client's hostname or IP address and you will see exactly the same configuration application as if you were working locally.
Note: As of version 2.35, this configuration frontend is only available via HTTPS (SSL-encrypted connection). Connection via HTTP will lead to a link that takes you to the secure site. There is no public certificate installed though (you would have to pay for that to a third party certificate authority), so your browser will display a more-or-less dramatic warning. If both your browser and the client are inside your own trusted network, you may choose to ignore the warning. It is still more secure than any unencrypted connection.
We suggest to turn this feature off / keep it off once you have implemented NoTouch and are using NoTouch Center. Just enable it, if you have to get a support file or want to do specific tests with individual devices.
This is useful for example in these cases:
- You only have a couple of machines and don't want to use a central management solution
- You want to remotely configure a specific machine without NoTouch Center and don't like Shadowing
This web administration is not a replacement for NoTouch Center as it is "remote", but not "central" management. NoTouch Center allows to configure dozens, hundreds, thousands of machines at once via multilevel, inheritance based management; this remote web administration allows to configure exactly the one machine you are connecting to.
Web administration service control
The parameter "Web administration service" among the Services parameters (Webservice subsection) controls the availability of the web server. If you don't like the web server running, e.g. for security reasons, set it to "off" and reboot your machine.
Furthermore the parameter "Protocol" allows to specify which protocol(s) shall be used:
- HTTPS plus HTTP redirect. This is the default. The system will listen both on HTTP (80) and HTTPS (443) ports. Administration is only possible via HTTPS, on the HTTP port there will only be a redirect link.
- HTTPS. Listen on HTTPS only.
- HTTP. Listeon on HTTP only.