Exactly the same scenario for me. Ultimately I have machines throughout my environment that are experiencing name resolution issues to the hostname only (without FQDN).
Clearly DNS and machine settings have a bearing, but best practice for most applications is to use FQDN - especially around URLs.
Is this addressed in a newer version of the application? Is there a mechanism to formerly request this configuration be added to the next version of the product?
The side question is - is the FQDN here relevant if using a fully functioning FQDN WSUS environment or as we suspect, the machine is downloading this specific update from the URL defined in WSUS Package Publisher or through the WSUS process?
Clearly DNS and machine settings have a bearing, but best practice for most applications is to use FQDN - especially around URLs.
Is this addressed in a newer version of the application? Is there a mechanism to formerly request this configuration be added to the next version of the product?
The side question is - is the FQDN here relevant if using a fully functioning FQDN WSUS environment or as we suspect, the machine is downloading this specific update from the URL defined in WSUS Package Publisher or through the WSUS process?