This is finally resolved in OMSA 10.3.0.0.  The CSR OMSA generates results in a certificate that contains the NETBIOS name (SERVER) and the FQDN (SERVER.domain.local) in the SAN attribute.
I open Server Administrator (9.5 - the latest version) in Chrome or Edge and get a warning that the certificate is invalid. I go to Preferences > General Settings > X.509 Certificate > Certificate Maintenance > Certificate Signing Request (CSR) and generate a CSR. I submit the CSR to the domain CA and receive a P7B file back. I load the P7B file via Preferences > General Settings > X.509 Certificate > Import a certificate chain. Then I reload Server Administrator in Chrome or Edge and get a certificate warning. Why? - Because the CSR did not include a Subject Alternative Name (SAN) attribute, and it is missing from the certificate. Both Chrome and Edge reject certificates that don't have a SAN attribute, and Firefox is planning to do the same in a future version. The SAN attribute has been required by Chrome since April 2017. Why is the version of OMSA released 5 years later not generating proper CSRs?
OpenManage Server Administrator Managed Node (OMSA) Subject Alternative Name 
Missing