I had a lot of trouble getting the LDAP integration to work with Active Directory domain controllers, and i kept finding this post over and over. So i wanted to share my configuration and make it easier on others trying to do the same thing in the future. Using this config i was able to get everything working, but i found a few limitations: Xen Orchestra cannot find any group members where the member has the "Primary Group" attribute set. Only direct members of a group are recognized (nested groups don't work). When signing in, i have to specify "username" instead of "username@cxlab.domain.com" Groups are created by clicking "Synchronize LDAP groups", however users are not created until they sign into XOA the first time. Users are not deleted from Xen Orchestra when they are removed from the domain. (but they can no longer log in to XOA) auth-ldap (v0.10.6) - LDAP authentication plugin for XO-Server Auto-load at server start [checked] Configuration URI: ldap://domaincontroller1.cxlab.domain.com **Certificate Authorities** Check certificate [disabled] Use StartTLS [disabled] Base: DC=cxlab,DC=domain,DC=com **Credentials** dn: cxadmin@cxlab.domain.com password: ****************** User filter: (sAMAccountName={{name}}) ID attribute: dn **Synchronize groups** [checked] Fill information (optional) Base: CN=Users,DC=cxlab,DC=domain,DC=com Filter: (ObjectClass=group) ID attribute: dn Display name attribute: cn **Members mapping** Group attribute: member User attribute: dn

hi @lawrencesystems You still need to enable it in config fr now. I hope we 'll be able to improve the ui to enable it on a per backup setting later The nbd protocol use the 10809 port in TCP by default. XO only read from this port f the host. The Nbd setting is used for the whole xo, regardeless of the pool The lock have been replaced by a select, which is more self explanatory . I think the main control pint is to check if there is multiple NBD network for a VM, XO use the first one returned by the Xapi, and it may be , for example, a managemet network as opposed to a backup / high speed one Regards

@Brice it's included within XCP-ng pro support.

@Andrew thank you very much

@savage79 Please take a look at https://xcp-ng.org/forum/post/58196

You are welcome!

@robyt There are no logs at this time (unless executed as part of a backup), only a notification at the end of the execution. We are currently working on a global task/log system that will be used throughout XO (Restore Health Check is obviously on our todo list)

You are welcome

As explained in the link, please update to the latest commit, be sure to rebuild everything and try again

@olivierlambert I uploaded the disk. https://mega.nz/folder/53YTGRCI#4qP16Kfj-XtKcwkWduGEOg

If it's a problem or a missing feature, it will be announced in the next changelog for everyone

@OhSoNoob said in VHD export and (delta) backup stuck at 99%: uploading de XVA in XO didn't work for some reason, it prompts about prepairing and then just stops. Hmmm.... never encountered that situation.

See this prior thread for explanation and solutions. https://xcp-ng.org/forum/topic/3529/increase-24-hour-timeout-limit-on-backup-copy

Maybe this idea will help xe vm-list params=networks | awk '{print $5}'| sed 's/.$//'

Hi! I was able to isolate the issue: It does happen, if NBD is activated on one of the network interfaces! xe network-param-remove param-name=purpose param-key=nbd uuid=xxxxxxxx --> Disabling "useNBD" did not solve the issue. I had to disable the feature in XCP-ng

@florent Nothing large. Either 10 or 20GB. I'm thinking it's due to the same issue as here.

So you are using a thick provisioned storage. Any snapshot will create a base copy, but also an active disk (which will be the total size of the disk). You can't cheat on that. Transforming a snapshot into a VM will create a new active drive that will use the total size of the disk.

@ysageev we're fisrt making the transfer from vmware work through an HTTP link in xo-cli. After this we'll do a UX, allowing a user to migrate from XO , it will probably be a three steps form : connect to an host, choose which VM(s) to migrate , transfer progress Then, depending on the priority , we may make other transport ( for example if you mounted the VMFS datastore in XO, copied files locally or through SSH) By the way, we fixed a timeout bug in xo-server, that was cutting the vmdk/ova import around the 5mn mark, you may retry the old method

Thanks @lawrencesystems - I've finally got around to watching that video, explains the content well, quite interesting to see that happening in real time when the RAM is being land-grabbed by other VMs when things are getting full based on the different configuration settings.

The ddelnano/packer-plugin-xenserver release v0.5.1 has been released and includes @bagas's fix for this issue.