Hi Stefane,
The users are mostly not RDM administrators, they only have view rights.
What we are trying to achieve:
Our systems are divided into "environments", each "environment" has it's own windows active directory, it's own ip subnet.
We access the "environments" using a central vdi system which is running on it's own windows active directory, when we logon to a "environment" we are presented with a vdi desktop and firewall rules which allow us to access the servers in this enviroment.
( yes i know, this means i am sonetimes logged in into dozends of environments. )
There are about 80+ environments.
The requirment we got is that when you logon to an enviroment and start RDM you only see the enviroment you are logged on to.
The only way i sofar found was to use a seperate sql database for each "environment", use a simple script that checks the local ip address of the vdi, based on the local ip address it starts rdm with the correct datasource.
But.....
Creating 80+ databases means i have to administer the users in 80+ databases, which is almost impossible.
I can copy the users with sql statements from one database to another database, but when i am finished with the setup the person who is going to administer this setup is not going to be a happy puppet.
Regards
Alex
The users are mostly not RDM administrators, they only have view rights.
What we are trying to achieve:
Our systems are divided into "environments", each "environment" has it's own windows active directory, it's own ip subnet.
We access the "environments" using a central vdi system which is running on it's own windows active directory, when we logon to a "environment" we are presented with a vdi desktop and firewall rules which allow us to access the servers in this enviroment.
( yes i know, this means i am sonetimes logged in into dozends of environments. )
There are about 80+ environments.
The requirment we got is that when you logon to an enviroment and start RDM you only see the enviroment you are logged on to.
The only way i sofar found was to use a seperate sql database for each "environment", use a simple script that checks the local ip address of the vdi, based on the local ip address it starts rdm with the correct datasource.
But.....
Creating 80+ databases means i have to administer the users in 80+ databases, which is almost impossible.
I can copy the users with sql statements from one database to another database, but when i am finished with the setup the person who is going to administer this setup is not going to be a happy puppet.
Regards
Alex