three people in my company have been using the software for almost a year now, and we are very happy with it.
However, we have been using the default xml data source, and simply exporting it from one computer and importing it in the next.
this as you imagine is a Very long and clumsy way to send each other updates.
So to get around this I recently installed MSSQL Express on a spare server, and attached my RDM to it. I started adding sessions to the data store, but now have run into an issue.
We administer approx. 1500 server/pieces of equipment, over 5 companies, and growing.
having one entry for a switch or router and one credential for that piece of equipment is fine, works just great. Also having that sort of thing in a central location is wonderful, means that if the password is changed or the login info or something, only one person has to change that.
However, my issue is this.
We have approx. 500 server that are administered, and each on the person logging into it MUST use their own username and password for that domain.
I would like to store the session information within the shared data store on the SQL server.
However.
I would like to use either a local credential option, or have some way of determining that Simi instead of me is trying to access a server and use her username instead of mine.
if that makes sense.
I wonder if there is a way to set it up so that the session information (IP address conntection type etc) is stored on the MSSQL data store, But have seperate credentials that each person uses.
Please help
However, we have been using the default xml data source, and simply exporting it from one computer and importing it in the next.
this as you imagine is a Very long and clumsy way to send each other updates.
So to get around this I recently installed MSSQL Express on a spare server, and attached my RDM to it. I started adding sessions to the data store, but now have run into an issue.
We administer approx. 1500 server/pieces of equipment, over 5 companies, and growing.
having one entry for a switch or router and one credential for that piece of equipment is fine, works just great. Also having that sort of thing in a central location is wonderful, means that if the password is changed or the login info or something, only one person has to change that.
However, my issue is this.
We have approx. 500 server that are administered, and each on the person logging into it MUST use their own username and password for that domain.
I would like to store the session information within the shared data store on the SQL server.
However.
I would like to use either a local credential option, or have some way of determining that Simi instead of me is trying to access a server and use her username instead of mine.
if that makes sense.
I wonder if there is a way to set it up so that the session information (IP address conntection type etc) is stored on the MSSQL data store, But have seperate credentials that each person uses.
Please help