AD Synchronizer with Folder Templates

Hello,

Thank you for notifying us of this issue.

We've made a few changes internally and this shouldn't crash anymore. Using a folder template as a template in the active directory synchronizer isn't currently supported though, could you tell us what you wanted to do by using one? Usually people use an RDP or similar template and not a folder template.

Regards,

Hi,


thanks for you input. Our intention was to create a Server Folder for each distinct host, containing Sessions as child objects. In these child objects variables are used to reduce configuration duplicates. In this way we'd be able to document all host information in a central and common place (Software, Hardware, ...) - without loosing the flexibility compared to the use of Subconnections.


Regards,
Nicolas

Nicolas,

So instead of creating an RDP entry for each host, you'd like to create a folder entry for each host and then manually create RDP/SSH/etc entries that inherit from that group?

Regards,

Hubert,

yes, this is what the idea was about. Think of a heterogeneous environment with hosts you access via RDP, HTTP, SSH - most of the time more than one of that types per host. But all of them share common information, like server roles, hardware or software properties, etc. So the idea is to always store this common host information on a "defined host object" and it's sessions reside underneath.

It's also easy to handle. If the host object was created, you could just copy a session object into it and it would work, because of the variables used.

Maybe I'm thinking a little bit complicated, but I couldn't find another way to normalize the task of remote control and documentation in one defined structure.

Regards,
Nicolas

The use case you have isn't uncommon, this would be a good thing to add through the use of templates. I'm not sure if it's easy to do or not but we'll check.

I think that right now you can work around the issue by using the synchronizer to create normal RDP entries and then give them subconnections that use the $PARENT_<value>$ variables. The thing is, it's a lot more troublesome to use subconnections rather than folders, so this would only be temporary regardless.


Regards,

I already had a look at subconnections, but the restrictions in the handling with such kind of objects (drag and drop, copy & paste, ...) lead me to search for different solution.

Addendum: Also, if the database is synchronized/connected to other systems, the handling of subconnection objects is not that easy, because of the integration of the XML code in it's owner object.

Hello Nicolas,

The case where an active directory entry wants to use folders as a template for synchronization has been fixed internally and will be available for use in the next minor release of RDM.

However, once you update to the next version of RDM, you'll have to either create new folder templates or edit your old ones and press "Ok" for them to work like intended.

Regards,