Video Screencast Help

Agent Deployment is using NetBIOS name instead of FQDN

Created: 23 Jan 2013 | 2 comments

In Altiris 7.1, I have a scheduled Symantec Management Agent Push to computers.  It is configured to deploy to "Windows Computers with no Symantec Managment Agent Installed".  Altiris Syncs with my domain-joined computers, and my intention is to have this task automatically deploy the agent to those newly discovered computers.  Unfortunately, the agent deployment has been failing, status: "Failed to copy 'Symantec Management Agent install service'.

When I look at the logs on the NS, I can see that it's trying to copy the client to the Admin share on the target system, but unfortunatly it uses the netbios name.  Example error " Failed to copy the eXpress Client service to \\Computer1\ADMIN$\AltirisAgentInstSvc.exe.  Error: The network path was not found.

The NS will not be able to connect to the servers which are spread across a half dozen different domains unless it uses the FQDN (i.e. \\Computer1.test.local\ADMIN$) to connect.  Is there a wasy to force it to use the FQDN?  Since Altiris did the AD import, It seems like it should know the FQDN on some level.  If possible, it would be nice to ALWAYS have Altiris use FQDNs instead of short names since I've seen a few other issues, which I'll save for other forum postings, caused by it using short names. 

Comments 2 CommentsJump to latest comment

mclemson's picture

If the NS has the proper DNS suffixes for each domain, shouldn't it be able to populate this on its own?  For example, if you have east.company.com, west.company.com, and cent.company.com for domains, add these as DNS suffixes.  When it tries and fails to resolve computer1, it should try computer1.east.company.com, computer1.west.company.com, and computer1.cent.company.com, eventually striking upon the correct computer.

Does this work?

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

DaveDurkee's picture

We ran into this. NS/DS 7.1 uses a different means to determine the unique name of a client. NS 6.x used the computername and NS 7.x uses the hostname. For a domain joined windows device this is a no brainer because the hostname IS the computername. However this is not necessarily the case for a Non-Domain joined device. I have a couple of .reg hacks that will make the computername = hostname. I can provide this to you if you think this might help.

Dave Durkee