Package Server publishes its codebase to the SMP using the internal FQDN. How to generate codebases using a different host name rather than its actual internal FQDN.

book

Article ID: 158437

calendar_today

Updated On:

Products

Management Platform (Formerly known as Notification Server)

Issue/Introduction

Example Use Case 1:
Agents not on the internal network (aka disconnected computers) are unable to download packages from the assigned Package Server (PS).

Example Use Case 2:
The customer is looking for a way to have certain package servers generate codebases using a different host name rather than its actual internal FQDN. 

Cause

The Package Server publishes its codebase to the SMP using the "internal FQDN" or host name (e.g. servername.ADdomain.com). The agent computer on the external network cannot resolve this address because it is not publicly resolvable.

For Use Case 2, The customer was under the impression that the communication profile governed this (Agent Communication Profiles provided names and certificates to clients in the event they are instructed to access a PS but it doesn't govern codebases from the PS). This is before ITMS 8.5 was released.

Environment

ITMS 7.5 and later

Resolution

For 7.5 SP1, 7.6, 8.0, 8.1

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. Example: servername.corpname.com
  • 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.

 

For 8.5

With ITMS 8.5 release, Site Servers have their own Communication Profile where we can specifiy what alternate host names we want to use. See under SMP Console>Settings>Agents/Plug-ins>Symantec Management Agent>Symantec Management Agent Communication profiles>Site Server Communication profiles

Those two keys were created in order for a Package Server to publish the codebases to the SMP with alternate FQDN and they are still work for this release.

 


For ITMS 7.5

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:

  1. On the package server stop the AexNSClient service
  2. Back-up original AexNSCPackageServer.dll located in Agent directory, by default "c:\program files\altiris\altiris agent\"
  3. 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
  4. Start AexNSClient service

 

Related Issues

 

To resolve the same issue with the Task Server, please refer to TECH211202.

 

Applies To

ITMS 7.5 environment using third party trusted SSL certificates on the SMP and Site Servers serving CEM Agents.

Attachments

AeXNSCPackageServer.dll get_app
AeXNSCPackageServer-x86.dll get_app