On non-domain-joined Windows endpoints, the Edge DX agent reports
the hostname with the NetBIOS workgroup name appended as a suffix
(e.g. <hostname>.<workgroup>). This occurs even when the OS itself
is clean: Primary DNS Suffix empty, DhcpDomain unrelated, no GPO
appending a suffix. The agent appears to fall back to the workgroup
name when no AD domain is present, and the suffix is not limited to
the default "WORKGROUP" — any configured workgroup name is appended.

Business impact
Third-party integrations that match assets by flat hostname —
Intune, Freshdesk, and similar ITSM / MDM platforms — cannot
correlate Edge DX devices with their records when a suffix is
present. This breaks cross-product asset matching and forces
manual reconciliation, defeating the purpose of the integration.

No supported local workaround exists today. OS-level DNS suffix
changes are not applicable because the OS is already clean; the
suffix is introduced by the agent itself.

Requested change
Add a tenant-level (or per-device-group) option to report the
flat hostname instead of hostname.<workgroup> on non-AD-joined
Windows endpoints. Ideally:

• Default behavior unchanged (backward compatible)
• Toggle scoped so it can be applied to physical endpoints while leaving VDI / AD-joined devices on current behavior
• Handles arbitrary workgroup names, not just "WORKGROUP"