Is it possible to build a function in HostMonitor to change the password used for a test automaticly?
Once set up, you never have to change the passwords again, since HostMonitor wil do that for you.
See also: http://www.ks-soft.net/cgi-bin/phpBB/vi ... 50&forum=4
<font size=-1>[ This Message was edited by: Marcus on 2003-07-27 04:54 ]</font>
Automatic password change
I too set it up with its own account.
Are you thinking of HM changing the password at the:
HM (internal) test connect as
HM (as a service, startup settings)
RMA (service startup settings)
Domain/Local Account
Or all /smirk
Cool Idea.
Edit: I should clearify, I have each RMA set up with a domain account in its respective corporate domain. Multiple companies.
<font size=-1>[ This Message was edited by: smckenna on 2003-08-04 14:18 ]</font>
Are you thinking of HM changing the password at the:
HM (internal) test connect as
HM (as a service, startup settings)
RMA (service startup settings)
Domain/Local Account
Or all /smirk
Cool Idea.
Edit: I should clearify, I have each RMA set up with a domain account in its respective corporate domain. Multiple companies.
<font size=-1>[ This Message was edited by: smckenna on 2003-08-04 14:18 ]</font>
>HM (internal) test connect as
This doesn't sound as a real problem. HM is in control and can change the password. Off course the current policies must allow a password change.
>HM (as a service, startup settings)
This I don't see HM do itself, since it can't stop and start itself. So a helper program could be the solution.
>RMA (service startup settings)
Again HM can be in control and change the password and restart the agent.
>Domain/Local Account
Both.
And yes, I love to see them all implemented
>I have each RMA set up with a domain account in its respective corporate domain
This means that the current HM account must be able to change the password. In my case that's no problem.
<font size=-1>[ This Message was edited by: Marcus on 2003-08-05 03:23 ]</font>
This doesn't sound as a real problem. HM is in control and can change the password. Off course the current policies must allow a password change.
>HM (as a service, startup settings)
This I don't see HM do itself, since it can't stop and start itself. So a helper program could be the solution.
>RMA (service startup settings)
Again HM can be in control and change the password and restart the agent.
>Domain/Local Account
Both.
And yes, I love to see them all implemented
>I have each RMA set up with a domain account in its respective corporate domain
This means that the current HM account must be able to change the password. In my case that's no problem.
<font size=-1>[ This Message was edited by: Marcus on 2003-08-05 03:23 ]</font>
-
zacherynuk
- Posts: 26
- Joined: Thu Jul 20, 2006 10:24 am
Did Anything ever get done about this ?
Not knowing the remote agent password would be ideal, alowing the RMA to scramble it's password scramble itself on a schedule would be perfect.
In the mean-time, is there a way of changing passwords on remote systems from the KS-Hostmon server?
Running 8.32, multiple different customers, RMA's and sites.
Thanks,
z
In the mean-time, is there a way of changing passwords on remote systems from the KS-Hostmon server?
Running 8.32, multiple different customers, RMA's and sites.
Thanks,
z
Use RMA Manager (menu Agents -> Agent configuration)In the mean-time, is there a way of changing passwords on remote systems from the KS-Hostmon server?
http://www.ks-soft.net/hostmon.eng/rma- ... #how_setup
Regards
Alex
-
zacherynuk
- Posts: 26
- Joined: Thu Jul 20, 2006 10:24 am
Does it change ? - unclear
Hi,
So changing the password in this screen changes the remote agent service account password and restarts the agent service ?
The text doesn't state this, I was under the impression that this password simply had to match the initial password set when creating the RMA.
Thanks for the prompt reply!
So changing the password in this screen changes the remote agent service account password and restarts the agent service ?
The text doesn't state this, I was under the impression that this password simply had to match the initial password set when creating the RMA.
Thanks for the prompt reply!
-
zacherynuk
- Posts: 26
- Joined: Thu Jul 20, 2006 10:24 am
I'm talking about the account under which the active RMA runs; the Service Account, which in our case is a domain admin / local admin account at the very least.
The RMA's have the power to change their own credentials on the system and restart their own service, this I feel would be a very useful in-built functionality.
The service account password under which the RMA runs, need not be known by anybody, so if it could be self-generating and self-applied at a given schedule, the risk of it becoming known and abused in all but illuminated.
A dedicated action-taskbar so that all the powerful things which can be setup as actions to tests, can be invoked by the hostmonitor operator when they see fit (eg: changing credentials of other accounts, rebooting a system following successful updates, clearing logs etc) would also be ace.
Currently, the only way I have found to utilise this power, is to have ‘fake’ tests setup, with no schedule, which you manually run now and then, knowing that the action would be performed, eg:
Net user _hostmonserviceaccount NewPassword
sc config RMAService password="NewPassword"
net stop RMAService && net start RMAService
Cheers,
z
The RMA's have the power to change their own credentials on the system and restart their own service, this I feel would be a very useful in-built functionality.
The service account password under which the RMA runs, need not be known by anybody, so if it could be self-generating and self-applied at a given schedule, the risk of it becoming known and abused in all but illuminated.
A dedicated action-taskbar so that all the powerful things which can be setup as actions to tests, can be invoked by the hostmonitor operator when they see fit (eg: changing credentials of other accounts, rebooting a system following successful updates, clearing logs etc) would also be ace.
Currently, the only way I have found to utilise this power, is to have ‘fake’ tests setup, with no schedule, which you manually run now and then, knowing that the action would be performed, eg:
Net user _hostmonserviceaccount NewPassword
sc config RMAService password="NewPassword"
net stop RMAService && net start RMAService
Cheers,
z