|
|
Post by ginolard on Feb 27, 2021 8:19:51 GMT
It would be really useful to be able to specify credentials for use by the UserAuth action rather than have the helpdesk technician enter them manually.
Johan Schrewelius has this feature in TSBackground to encrypt the password used to open the debug page.
|
|
|
|
Post by Jason on Feb 28, 2021 3:10:50 GMT
Sorry. I'm not following exactly. You'd want to store the credentials used to authenticate to the domain in the XML?
If so, this is quite different from what's in TSBackground as that's simply a local password that can't be used to attack the network.
|
|
|
|
Post by ginolard on Feb 28, 2021 12:51:18 GMT
Sorry. I'm not following exactly. You'd want to store the credentials used to authenticate to the domain in the XML? If so, this is quite different from what's in TSBackground as that's simply a local password that can't be used to attack the network. Hi Jason, Yes that's what I meant. I appreciate that TSBackground is merely a password to protect the debug logs. I understand fully that you may not want to implement such a feature for security reasons. Just thought I'd ask  |
|
|
|
Post by Jason on Mar 1, 2021 3:03:29 GMT
SO, you're looking for a separate password? What will this protect though? UI++ doesn't control access to anything locally on the system.
|
|
|
|
Post by ginolard on Mar 6, 2021 9:25:53 GMT
The request is redundant now We WERE using ADValidate to ensure the computer name did not already exist but we've now decided to start using the AssetID from our inventory system to uniquely identify each machine. So, even if a new machine is imaged or an old one re-installed there's no need to check if it already exists. Either it will (in which case go ahead and re-image it with the same name) or it won't (in which case it'll join itself to the domain as a new machine) |
|
