Synchronizer - Structure

0 vote

avatar

Hello,
Could it be possible to configure the Synchronizer for not moving objects if it exist in a subfolder (at destination) ?
Like a lot of other users (I suppose) my Active Directory / vCenter directory structure isn't the same as the Devolutions one.

Here is my use case:

  • I configure the synchronizer to read a specific OU and create all the RDP sessions in a specific directory in DVLS, let's say "Servers"
  • Then I move manually all the newly created entries to other subfolders based on our needs, for example Servers\Citrix
  • Next time the synchronizer run it will identify the entries in subfolder and doesn't re-sync nor move them


Actually, only the last point isn't working. When synchronizer run it identifiy the entries and move them back to the destination folder (in that case Servers\".


PS: We already did troubleshooting together and concluded that isn't a bug, it's just how it works actually and you asked me to do a feature request. I think the ticket number is 00060890 but I'm not 100% sure about that because this number is also mixed with another case for a gateway issue.

All Comments (5)

avatar

Hello Arnaud,

Thank you for the request. We have had a similar request in a prior thread (https://forum.devolutions.net/topics/41588/hyperv-syncronizer-destination-folder-additions) and we will add your interest in this feature. I would like for us to be able to add an option for this behavior as this seems to be a common way to work with synchronizer. I will try to add this in our current 2024.3 roadmap.

Regards,

Hubert Mireault

avatar

Hi Hubert and thanks you for your response.
I've read the topic you linked but op is asking for change with Hyper-V synchronizer.
My first and more important need is Active Directory synchronizer.

Will you work on both?

avatar

Yes, we are planning to make this change for all synchronizers.

Regards,

Hubert Mireault

avatar

Great, thanks for the information !

avatar

Hello,

A new setting called "Update folder only for newly discovered items" will be available in our 2024.3 release, which will prevent the synchronizer from moving already created entries :



Regards

Jonathan Del Signore

f35fdd0c-6653-463c-8a83-ea549a1f968c.png