HPC Pack 2019: Domain verification during setup

Alexander McQuarters 1 Reputation point
2021-02-18T15:41:32.01+00:00

During the installation of HPC Pack 2019(on-premise), it gives an error stating to verify that my server is joined to a domain. After passing that message and trying to use Windows Authentication to connect to remote databases(Built-in high availability), it states windows authentication is not supported because a domain is not available. This server has been added to the domain. Is there a certain port or policy, that hpc pack 2019 uses to verify that it is part of a domain, that could be currently blocked?

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,174 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. prmanhas-MSFT 17,891 Reputation points Microsoft Employee
    2021-02-22T16:22:01.433+00:00

    @Alexander McQuarters Apologies for the delay in response and all the inconvenience caused because of the issue.

    Can you check below and see if it helps:

    https://learn.microsoft.com/en-us/powershell/high-performance-computing/step-2-install-hpc-pack-with-remote-databases?view=hpc19-ps

    Got below response from our internal team as well:

    HPC Pack verifies whether the machine is domain joined by simply translating the current machine account name to the SID with NTAccount.Translate. I don’t think it will be blocked.
    Could you please share the HPC Setup logs in C:\Windows\Temp\HPCSetupLogs?

    Hope it helps!!!

    Please "Accept as Answer" if it helped so it can help others in community looking for help on similar topics.

    Thanks

    1 person found this answer helpful.
    0 comments
  2. Hinsley, Wes R 1 Reputation point
    2022-11-16T10:57:55.49+00:00

    Apologies for resurrecting such an old question; this is the only reference to that warning message I've found online.

    I can replicate this warning when trying to add nodes to an on-premises HPC Pack 2019 cluster, where the nodes belong to a subdomain. - i.e., my domain name is called "mydomain.local", but the head-node and compute nodes are being added to a sub-domain "hpc.mydomain.local". I get the warning message reported above, even though the nodes are already joined to the domain and work perfectly. C:\Windows\Temp\HPCSetupLogs contains the following:-

    10:45:17.773 - [CheckRule] Checking rule Domain -- Check if the computer belongs to a domain.
    10:45:17.804 - [DomainRelationshipVerified] NTAccount (hpc.mydomain.local\node-003$) translation failed with exception: System.Security.Principal.IdentityNotMappedException: Some or all identity references could not be translated.
    at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
    at System.Security.Principal.NTAccount.Translate(Type targetType)
    at Microsoft.Hpc.Setup.Chainer.MachineDataProvider.get_DomainRelationshipVerified()

    So it looks like the setup is assuming the domain name is "hpc.mydomain.local" rather than just "mydomain.local", and then throws the warning.

    More info - my head node is running Win Server 2022, and the nodes being added above are Windows 10 with the OS set up, already joined to the domain, running \hn\REMINST\setup to add them as workstation nodes.

    On the next page, I have to manually type in the full headnode name (hn.hpc.mydomain.local) rather than choosing it from the dropdown menu as I normally would, but after that it appears to add successfully to the cluster. Hoping that we won't run into any problems later though.

    0 comments