Hi, Check the task view, you'll have the duration of the process visible.

@Danp Hi, Thanks for quick support.

@yzgulec said in How to deploy XO on ESXi: I just used VMware Converter for V2V (seems more practical for me) Installing from Source or using an installation script from the community is also very straight-forwards. Maybe 10 minutes worth of setup for the OS and then for at least my github it's a single line installation.

@yzgulec as people have rightly said above, no hard and fast rule. But when it comes to sizing compute for mixed workloads (or unknown workloads) I have used a 1:4 (pCPU:vCPU) contention ratio. I also try and size 2GB of memory per vCPU (so 8GB RAM per pCPU), and with this 'rough guide' I find that my CPU and memory consumption scale nicely. Obviously it gets difficult when someone has a workload that needs very low CPU but high memory (e.g. I've seen a 2-core VM with 64GB memory) and conversely high CPU and low relative memory (e.g. 8-core VM with 4GB RAM)... but these are typically exceptions. Please share your decisions and build configs here, I'd be interested to see how it worked out in terms of compute:memory, costs, etc.

@yzgulec You will likely need to install the fix given in the following post for XOA to function correctly on vSphere -- https://xcp-ng.org/forum/post/50279

Hi, This is explained in this KB article -- https://help.vates.tech/kb/en-us/30/21 Regards, Dan

@dinhngtu said in LDAP fails with error "Code: -32000 Message: Code: 0x3": sAMAccountName Thank you. (userPrincipalName={{name}}) filter made the trick. When I use (userPrincipalName={{name}}), it works for me either I set certificate check ON or not. (Actually I was expecting to check AD root cert as this connection is using LDAPS) And also test only works when I do it using UPN but not with username@domain format. Other filter options did not work at all.