Rule Based Sync for Hyper-V

[Crille]

Hi!
I would like a feature where you build up what properties in ASG-RD gets populated from which properties from the Hyper-V. IE today, sync puts hostname without FQDN and so on in destination. I would like to either do it rule-based where I can say, Hostname + "own domainname.local", Specify that I want to skip the destination field and only populate the IP field and so on...

As a clarification, we have a Hyper-V cluster with all different customer servers thats being used by us to deliver services to these customers. All machines belongs to different domains and so on. We have a MGMT network that has access into all customers that can use DNS resolving for some computers but needs IP for some.  Today, The Sync creates all computers but they are left unsuable since they only have hostname in destination. To be usable, I need to manually update with correct domainname or clear the destination field since the IP field gets populated correctly. After next Sync, all my changes gets overwritten and I need to start all over again... :-(

The other workaround is to rightclick and say that I want to connect via IP... I would accept that as a workaround in some unique cases but not for everyday use. 

This would really help me lot if this was implemented!

Regards
/Christian Lagerhorn

[DevOma]

Ok - will see what it is possible with HyperV - we didn't work a long time on HyperV issues - so must check the environment first and so on... Then decide what and how we can implement...

[DevOma]

Connect via IP is also possible => Connect with Options=>Connect via IP address"

[Crille]

Yes... I know it works via "Conenct via IP address". But I would like to just double click the object like normal and get it to connect as it normally functions. If there is nothing in the Destination property and the IP address property is set, then it works normally without going into sub-menus to select "Connect via IP".

So if there could be a way to tune how the Hyper-V sync works, Example set it to ignore populating the Destination property, it would be great! ;-)