I would to thank you for the time spent in resolve my problem

Modifying my script, and simply adding the IP of management as you suggest I got it functioning. $syncInterface="#p2=192.168.1.21:3260" -f $addr2, $hbInterface="#p2=192.168.2.21:3260", 192.168.0.41:3260" -f $addr2, $syncInterface2="#p1=192.168.1.11:3260" -f $addr, ...

If I try to manually sync device with the SyncHaDevice.ps1 script I obtain this error:

After applying the cfg files I obtain this error:

Disk are correctly created

It's a fresh install

Here some screenshot

Were you able to connect the targets to ESXi?
I added the target to the ESX hosts, but rescan doesn't discover any disk

Network condfiguration is: Management connected to a switch (192.168.0.11 for ESX-01, 192.168.0.21 for ESX-02, 192.168.0.31 for VSA-01 e 192.168.0.41 for VSA-02) Sync interfaces (192.168.1.11 for VSA-01 and 192.168.1.21 for VSA-02) are connected with a cross cable Heartbeat and iSCSI interfaces (192...

I obtain this message on VSA1: - Synchronization channel '192.168.1.21:3260'on 'iqn.2008-08.com.starwindsoftware:192.168.0.41-sw-vsa02' is down - Hwartbeat channel '192.168.2.21:3260'on 'iqn.2008-08.com.starwindsoftware:192.168.0.41-sw-vsa02' is down - Partner '192.168.1.21:3260'on 'iqn.2008-08.com....

No, in the trial license I create the device with the management tool.
I tried the script but it failed with the same result: synchronization at 0%
At the moment I haven't try to connect the created target in ESXi, but I will update as soon as possible

For completetion I add this information:
192.168.0.x is my mangement network
192.168.1.x is synchronization network
192.168.2.x is iSCSI\heartbeat network
Testing the same configuration with a trial license works great.