How to programatically change group fiolder properties and session properties
Hi Maurice,
Sorry for reviving a dead post but I'm was wondering if you have these document now or can you tell me where I can find all the GUID settings for session?
Thanks!
RDM for Team based on individual login to multiple domains
Hello Maurice,
Please see my answer to your questions in bold below. I understand that this type of setup is neither simple or common but it is a business requirements. Let me know if you have any other questions.
Hello,
The issue is with somedomain\Alice, she has a single account to gain entry to the system, yet she has two accounts for external resources.
This means a folder level override would not be the best option to use.
We would need to see more of the content in order to come up with a proposal.
- How will the tree be structured
This is what I'm trying to figure out. My current structure requires a lot of manual work with no ability to scale. Each user will need to do a batch edit to a folder to override the credential to login to each Azure domain. I'm trying to avoid this method.
- how many servers will be defined
Currently, I have 30 different domains with about 5 to 10 servers per domain. There are no trust between the domains. This will likely grow over time.
- is that azure credential used for most resources or you have many other shared credentials
Each user will have their own RDM credential and their own Azure credential for each of the 30 domains.
The only proposal I could make right now would mean to create a security group for each user, create a credential entry and a server session, both tied to that security group and grant the view permission only to that user.
RDM for Team based on individual login to multiple domains
Hello,
Version: Enterprise 10.6.3
I am looking for some help with setup/best practices for the following requirements. If possible, I would like to setup/manage with Powershell. I will be deploying this to about 100 users.
1. Each users will be logging into RDM with their own account tied to AD.
2. Each users will use their own credentials to connect to Azure VM.
3. Users should not be able to view/edit/delete their account/credentials.
Here's a simple example that I hope can be scale much further.
User Alice (somedomain\alice) log into RDM with her credential and connect to Azure VM with her credential (azure1\alice).
User Alice (somedomain\alice) log into RDM with her credential and connect to Azure VM with her credential (azure2\alice).
User Bob (somedomain\bob) log into RDM with his credential and connect to Azure VM with his credential (azure1\bob).
Thanks!