Locate the packages/xo-server directory to your from sources built xen orchestra instance. There should be a file in dist/recover-account-cli.mjs, copy this file as dist/recover-account-cli.mjs and then run it from the dist directory ./recover-account-cli.mjs admin@something.tld, it'll ask password and either reset the existing users password or create a new one with admin privileges if there isn't one with the email address.

Plugin configuration has good examples for those attributes. There really is no tutorial for your specific environment, depends how your AD is setup. If you have other applications setup with ldap, try to look for hints from their configuration. Note that it does not sync users, they’re being created on successful login after plugin is configured properly and activated.

That "VM" is a snapshot of that running XOA - xbackup1 machine. Open that VM in Xen Orchestra and check snapshots tab, you'll see that the name and uuid (copy button next to snapshot) matches the results from command line.

You can ignore snapshots in listing with: xe vm-list is-a-snapshot=false

Just out of curiosity, how would you present something like "On monday, wednesday, friday, sunday, every other month at 4:30AM" or "Every day, every six hours, 15minutes past in january, march, june, september, december" in date format on that tiny space except showing the exact next scheduled time which doesn't tell anything really. Imo the cron time in that view is the best for quick overview. For those who want more details or don't understand cron time can do schedules without knowing anything about it from the edit view and also see the future scheduled execution times in date format.

Sure i get the idea for tasks that run every day at specific time, that'd be easy but as the examples above show, there can be quite complex cron schedules that would be difficult to show.

Yeah you're right, it indeed should be there already. I must have done something to it in my own lab

Nice Happy to help.

Locate the packages/xo-server directory to your from sources built xen orchestra instance. There should be a file in dist/recover-account-cli.mjs, copy this file as dist/recover-account-cli.mjs and then run it from the dist directory ./recover-account-cli.mjs admin@something.tld, it'll ask password and either reset the existing users password or create a new one with admin privileges if there isn't one with the email address.

Plugin configuration has good examples for those attributes. There really is no tutorial for your specific environment, depends how your AD is setup. If you have other applications setup with ldap, try to look for hints from their configuration. Note that it does not sync users, they’re being created on successful login after plugin is configured properly and activated.

@tristis-oris i don’t have a definitive answer what would be the perfect memory configuration for your needs. I commented based on your earlier findings that VM memory usage was high which doesn’t take into account what OS inside VM is doing with the memory. As you observed, most of the memory is used by cache so it basically has nothing to do with XO, just how Linux manages the usable memory.

Looking at the cli output this sounds like a classic confusion of how memory is used in linux. As you can see from free command output, you actually have majority of the memory still available. Graph in XO doesn’t tell much how the memory is actually being used so it might be confusing as most of it is in cache and buffers which usually is something that can be released into use immediately if an application needs ram.

I suggest reading for example this to understand more: https://www.linuxatemyram.com/

What does the memory min/max settings look like in the advanced tab of those VM's? You could try to set the dynamic min/max to same values. Could very well be that your guest OS doesn't handle it properly when host is trying to dynamically adjust the available VM memory. Although this shouldn't happen (afaik) if there's plenty of memory available on the host, but worth a try at least.

That "VM" is a snapshot of that running XOA - xbackup1 machine. Open that VM in Xen Orchestra and check snapshots tab, you'll see that the name and uuid (copy button next to snapshot) matches the results from command line.

You can ignore snapshots in listing with: xe vm-list is-a-snapshot=false

Isn't that just XenCenter/XCP-ng Center feature, nothing to do with OVA pulling image from internet. Not sure how Xen Orchestra goes around it. In that sense, Xen Orchestra section in this forum isn't probably the correct place for this thread if XCP-ng Center was used

Feature documented here for example: https://docs.citrix.com/en-us/xencenter/7-1/vms-exportimport-about.html

"If the VMs you are importing were built on a hypervisor other than XenServer, you will need to configure the Operating System Fixup feature to enable the imported VM to boot correctly on XenServer. You will also need to configure networking for the Transfer VM, a temporary VM used when importing/exporting VMs from disk images and OVF/OVA packages."