Package Server publishes its codebase to the SMP using the internal FQDN
Last Updated July 08, 2015
Agents not on the internal network (aka disconnected computers) are unable to download packages from the assigned Package Server.
This is a known issue. The Package Server publishes its codebase to the SMP using the "internal FQDN" (e.g. servername.ADdomain.local). The agent computer on the external network cannot resolve this address because it is not publicly resolvable.
A pointfix is available for ITMS 7.5 initial release and HotFix versions, this is included in ITMS 7.5 SP1 release.
See the two attached DLLs: AeXNSCPackageServer.dll and AeXNSCPackageServer-x86.dll.
How to apply the pointfix:
On the package server stop the AexNSClient service
Back-up original AexNSCPackageServer.dll located in Agent directory, by default "c:\program files\altiris\altiris agent\"
Depending on the OS of the Package Server:
For 64bit OS Package Servers: Copy AeXNSCPackageServer.dll to the Agent directory, by default "c:\program files\altiris\altiris agent\"
For 32bit OS Package Servers: Copy AeXNSCPackageServer-x86.dll to the Agent directory, by default "c:\program files\altiris\altiris agent\", rename the file to AeXNSCPackageServer.dll
Start AexNSClient service
How to use pointfix:
Two new registry keys have been added which will allow administrators to specify custom FQDN strings which will be used as alternative host-names when generating HTTP & HTTPS codebases on the Package Server (UNC not affected by this change).
The keys should be created manually under the registry hive: HKLM\Software\Altiris\Altiris Agent\Package Server
The key "FQDN Alternate" (REG_MULTI_SZ) should contain alternate FQDN strings.
The key "FQDN Keep System" (RED_DWORD) should contain a value in order for the Package Server to keep providing original system based hostname, or 0 (zero) - not to provide codebases with system hostname.
If no alternate FQDN strings are specified, the Package Server will still provide the original, system based, hostname.
To resolve the same issue with the Task Server, please refer to TECH211202.
ITMS 7.5 environment using third party trusted SSL certificates on the SMP and Site Servers serving CEM Agents.