@DustinB I think I expressed myself poorly; the iSCSI SR creation test does not remove the gfs2 check and does not allow it to be created as LVM.

In LVMoISCSI.cs if you set:

var performSecondProbe = Helpers.KolkataOrGreater(Connection) && !Helpers.FeatureForbidden(Connection, Host.RestrictCorosync);

The SR can be created.

Hi, with this modification on MainWindow.cs in

        private List<TabPage> GetNewTabPages()

adding this at the end:

           if (!multi && !SearchMode && (isPoolSelected || isHostSelected && isHostLive))
                newTabs.Add(TabPageAD);

the AD tab appears:

I test this modification and is working.

Maybe @michael.manley can update this and the modification to support attach iSCSI SR without error with gfs2

@michael.manley
Hi, I test Build 25120 ( rev: d7ac261f ) and Is working with XenServer 8.2 CU 1 and XCP-ng 8.2 LTS.

Great Work, thanks for all

@michael.manley

Hi this is the result with pdb installed:

and:

Settings.txt

and the log:

XCP-ng Center.txt

@michael.manley
Hi, These are the results of the execution:

and the log and settings:
Settings.txt
XCP-ng Center.txt

Debuggin XCP-Center I see in this
private static bool SameProductBrand(Host host)
{
var brand = host.ProductBrand();
return brand == BrandManager.ProductBrand || brand == BrandManager.LegacyProduct ||
BrandManager.ProductBrand == "[XenServerProduct]";
}
The value of brand is "Citrix Hypervisor" and BrandManager.LegacyProduct is "[Citrix Hypervisor]"
If I set in Branding.resx this:
<data name="LEGACY_PRODUCT" xml:space="preserve">
<value>Citrix Hypervisor</value>
</data>

@michael.manley

Hello, I am in the process of migrating from XenServer 8.2 CU 1 first to XCP-ng 8.2 and then to XCP-ng 8.3. I am more used to using XenCenter, therefore I try to use XCP-ng Center to access the machines with XenServer 8.2 CU 1 and the machines with XCP-ng both 8.2 and 8.3, but this version does not allow me to access XenServer. I have verified that by changing [Citrix Hypervisor] to Citrix Hypervisor in Branding.resx I can access both environments without problems. Is this change possible in XCP-ng Center?