Device creation automation - HTML5 tag

I agree with this. His use case is to permit a user to go to the website and click something, and have it download and install the client (optionally automatically with unattended access enabled, and a pre-loaded password), and then put the site with it’s id into the support engineer’s device list. That way, the support engineer doesn’t need to ask the user for their id, or walk them thru something. It is the kind of thing we would want all of our customers to install on all of their machines. You could grab either the local machine name or ip address (or both) to use as a device name. It would be acceptable to just have installing from a website like this generate an email back to the support department, that would include the device id and some computer/customer information. Perhaps when you install the software, it should come up to ask the client what their name is, and to verify/approve sending the email. I’m almost thinking of a distribution version of the software, which would be a front end installer. It would ask the user for some information, have the email address of the provider already in it, and possibly generate a password that it would send in the email (possibly encrypted in a form that the remote support app would be able to decrypt). Also, it would download whatever the latest version of the actual remote support application would be.

Again, the use case is a service provider, who wants to make it easy for both the client and the support people to get reliable remote access to all of their machines.