Problems installing the Symantec Management Agent with aexnsc.exe if the domain name is ending with .NS and a port is specified in the nsweb switch. The install will continue with blank ns and nsweb values.

Products

• IT Management Suite

Issue/Introduction

Problems installing the Symantec Management Agent with aexnsc.exe if the domain name is ending with .NS and a port is specified in the nsweb switch. The install will continue with blank ns and nsweb values.

 

2014-06-24 17:09:01: ==========================
2014-06-24 17:09:01: AeXInstallPreCheck started
2014-06-24 17:09:01: Symbolic link between 64 and 32 bit registry views either
created or not required.
2014-06-24 17:09:01: Current dir: C:\DOCUME~1\ADMINI~1.EPM\LOCALS~1\Temp\apt0
2014-06-24 17:09:01: AeXInstallPreCheck Finished
2014-06-24 17:09:01: ===========================
2014-06-24 17:09:01:
2014-06-24 17:09:01: Passing control to AeXNSAgent
2014-06-24 17:09:01: InstallPrecheck: target platform: x86
2014-06-24 17:09:01: Command line: AeXNSAgentInst.exe /install -a
/ns=stvsssmp01.stv.ns /nsweb=http://stvsssmp01.stv.ns:850/altiris; NOTRAYICON
NOSTARTMENU /s
2014-06-24 17:09:02: Invalid characters in server name (/ns=<server name>)
parameter. Will continue installation with blank ns and nsWeb values.
2014-06-24 17:09:02: ===============================
2014-06-24 17:09:02: Core Agent Installation started
2014-06-24 17:09:02: Symbolic link between 64 and 32 bit registry views either
created or not required.
2014-06-24 17:09:02: Installed agent version: 7.1.8470.15470
2014-06-24 17:09:02: New agent version: 7.1.8470.15470
2014-06-24 17:09:02: Installed agent is newer.  Install aborted.
2014-06-24 17:09:02: Core Agent Installation Ended 
2014-06-24 17:09:02: ===============================

 

Cause

This seems to be an issue where if you specify a port while also using a domain that ends in '.ns' inside of the nsweb switch it will trigger the error about invalid characters and then continue the install with blank ns and nsweb values.

 

 

Resolution

This development team is currently working on resolving this issue. The issue is only present in current versions of 7.1 SP2 MP1.1 so upgrading to a current version of 7.5 will resolve this issue.

 

 

Applies To

7.1 SP2 MP1.1 vanilla or with v9 rollup