Agent Deployment is using NetBIOS name instead of FQDN
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.