We'd recently got a relevant experience regarding this weird renaming to uuids. We had one orchestra managing one pool. ISOs were in an ISO SR, with an nfs4 serving it underneath. All fine till then. We added one second pool to the orchestra. Just a single host by itself. One of the very next days we discovered that all names in the ISO SR had been replaced by uuids. Removing/readding the sr to the new pool helped temporarily. Usual names appeared again. But after a few more days, again uuids. Where uuids were appearing, we could not select anything from the dropdown list in the console's cdrom. The list per pool was unpopulated. We tried separate the shares by offering the new pool an nfs4 share from the NAS, actually sharing the same source dir. It did mount but now there was a uuid uniq constraint that was violated, so we could not see no files at all in this new SR. It would not be an illogical thought to have an 'iso sr' attached once to the orchestra and be offered by the orchestra to all managed pools, without uuids, without uniqs etc. There seems to be an unnecessary complication here I think.

@dinhngtu Hi For my i made on offline Install to solve my issue, installed failed when downloading the kernel from servers, so offline install worked fine for me.

@Chico008 Seems like you're duplicating your inquiries. As I suggested in the previous thread, I think your memberOf is missing the full DN of the group.

@Chico008 ACLs are used to assign rights to the guest users. As you said you have an admin who can do anything. In case you want to go with acl then your guest can get no leverage by using ACL create vm You as an admin will create VMs and manage other stuff but you then have ability to give three type of rights to the guest user. admin, operator, viewer In case of VMs when you give the admin right to a user then it means that user can have ability to anything with that VM. Delete, Reboot, etc But from you query you said that you want to give a right to guest user to create/run the vms to achieve this you have to look Self Service feature which is supported in XO from sources and in Premium XOA In self service you have ability to create resource sets which are pools, storage, networks, templates etc, and assign a user or group to it.

@olivierlambert said in XOCE - Language not keep when i come back (surrely dumb question): Why? I mean you are the first person to ask this. It's more work to do that and I'm not sure to really see the value A cookie is the perfect simple way to store info that are from your same browser/session, so it's very logical. Yeah, I don't see the value in having to keep a user preference within XO itself either.. just don't clear your cookies. It's what they are meant for.

@DustinB tried your command, it runs OK, restarted the vm hosting XOCE, but still have the same issue after typing an @ in console, char following are wrong

Just a reminder for myself, or other people in need in the future thanks again for all people who helped me understanding this Had to reinstall my entire XCP system, and almost forget how to configure Ldap plugin to only allow my admin accout to login So here's my Ldap plugin conf, to allow only admin user (member of specific group) to login. my AD is a windows 2K19 server with active directory without ssl. URI : ldap://dc.domain.net:389 no certificate info base : dc=domain,dc=net Credential : Fill = tick DN = full DN of service user (CN=xen,OU=service_account,DC=domain,DC=net) password = password of this account it's a simple account with no specific right, can only read AD and login User Filter, where it can stuck (&(sAMAccountName={{name}})(memberOf=CN=SG-XCP_Admin,OU=service_account,DC=domain,DC=net)) in real my OU have spaces inside their name, it work anyway. SG-XCP_Admin is a security group having my admin users inside ID Attribute : sAMAccountName and that's all.