Client Management Suite

This is what I get at the console -
Symantec™ Management Console
Version 7.6.1383
Altiris Notification Server™ Version 7.6
The agents I checked are all 7.6.1xxxx depending on the agent.
I do not know what agent does the software application installs, or checks for software to see if it's installed and install it if needed. I assume it's different than what PATCHES the OS or software.

The issue is a failure on SOME computers to install SEP (and sometimes other stuff, but small - VERY small very simple installs typically go great) and it's confusing.

I have used the SEPM (Symantec Endpoint Protection Management) to export a SEP install package - a single exe file, to install SEP 64bit preconfigured for the typical employee, so that SEP will show up in the employee group in SEPM.
I took the SEP install file (setup.exe) and copied it to the whatever you want to call the server that runs the 7.6 (I think) Altiris/Symantec stuff that manages patching, software installs, inventory, tasks and jobs, etc.
It wasn't simple, but I got something created so that the agent on computers sees a whatever you want to call it, task or job or "something to do" and runs the check to see if SEP exists. Nope, it says it does not, so we need it. Cool, it says it's downloading the package.
Now this actually works most of the time, but sometimes on Windows 10 computers, it runs saying downloading (in progress) but never gets it done - timing out after 30 minutes.
Then it starts the download again - and it says this for 30 minutes, then times out and starts over again. The file never exists on the PC, it never appears and day after day week after week, over and over, the Altiris agent logs say it's downloading, then it fails with a code of 2.
I do not know what the "return code" 2 means, but it must mean it can't get the file downloaded.
I have tried to see why it fails at exactly 30 minutes.
The 2 is confusing as since there is no EXE or MSI to execute or run, I can't use the Microsoft generic "typical" install exit codes - this ain't an install code, it's a "I can't get the file" return code of 2.
So, what is return code 2
Why does it timeout after exactly 30 minutes day after day, 24/7?
I can' do anything else, other tasks and jobs work out. This same job worked on other computers (I believe - maybe I better verify!)
DNS is fine, the server name resolves, the IP address resolved and it shows the FQDN in each case so it's not like it can't find the server. And since OTHER things run - like checking for other software, etc. it IS finding the server ok.

How does one determine why or how this is failing?
Where does the 30 minute timeout come from?
Does this mean it's not getting ANY of the file at all? I never see it - and I read in the documents that if a download fails or it's interrupted that it picks up where it left off..... a "resume" of the download and not starting over.
I would expect that after over a month running 24/7 it should have the file by now!

What can be done to troubleshoot? I have one of the failing computers with me at my desk, the other is in use by an employee - and ouch, we thought SEP was on all of these Windows 10 devices only to find no, it failed on the test one I have plus a user computer! So they are out there running naked with NO SEP, no security and that's scary knowing our people.
 

Are you using a Managed Software Delivery Policy?

Does the machine that doesn't work on your desk have exactly the same Symantec Management Agent plug-ins and versions as a working one?

Can you post the section of the log where the download is failing, is it trying to download the package from the same location as a working Agent? (Double click on the Package in the Symantec Management Agent > Download History tab)

>>Are you using a Managed Software Delivery Policy?<<

Still learning, but I believe that would be a "yes".

>>Does the machine that doesn't work on your desk have exactly the same Symantec Management Agent plug-ins and versions as a working one?<<

The versions should be yes - as far as I know, and I have only applied updates using the Symantec installer, or software tool on the server 1 or 2 times since starting last November or so, with a trial setup.
The computers were all put on the network in the same 2 or 3 week time period. They are all Windows 10, some are HP, some are Lenovo - we are evaluating them. They are the combo tablet/notebook type computers, mini-notebooks, or whatever. We got them in, the helpdesk fellow put them in the domain, Altiris/Symantec server "discovered" them in AD, agents went to them automatically, all within a couple of weeks or so of each other. MOST got SEP installed pretty easily, within a day or two. One other app, FireEye, went to them before I could get a chance to look - it's a small app and went so fast and easy I almost forgot I had it already set up as a software app to manage and roll out.
SEP - well,. most got it, two did not. The one at my desk is simple to get logs from or check things, the other is about 3 or 4 hours away in another office (we have over 300 computers across 30 some offices through the state of Iowa)
 

>>Can you post the section of the log where the download is failing, is it trying to download the package from the same location as a working Agent? (Double click on the Package in the Symantec Management Agent > Download History tab)<<

We have 1 server for this, the server I guess you call "Name Server". It's the only place the Altiris/Symantec stuff is installed, and the only place any computer can get packages or tasks, etc. from. That keeps it simple - single server, single NS, single management server, all packages exist on and come from that 1 server.
The server is in the same building as the PC I have on my desk that failed. The other PC that failed is across the state in another location. That helped me determine "it's not distance or bandwidth". All were in the same building when we started testing these. Now one is here, another in another office, but the one here has extremely fast connections to the server like they all did while in this building.

Logs? I'll give it a shot.

OK, this thing has done something crazy now - I went to get onto that PC and noticed it was OFF - not rebooted, but off. (that's weird as it should reboot if an install or patch reboots but it was OFF. I turned it on and got past bitlocker, wondering now what in the world would it have rebooted or be off. Then it hit me - you don't suppose...
And sure enough, this computer now has SEP on it!
Yes, near the end of the day yesterday, it succeeded at the download and installed SEP.
Now is when I wish I would write down anything I change on things - did I make a change somewhere? Or did it really take 2 months to download the SEP install while others did it in minutes or hours at the most.

Great, now I find an email showing the OTHER failed computer also got added - but today, this AM.
So mine went later yesterday afternoon, shortly after 4pm SEPM reported a computer was added to the management group, then today I find another email saying the second computer was added to the group.
This after days, no, weeks, of the things both failing - every 30 minutes, you could almost set your clocks by it, it failed. Now today, both are in.

I must have changed something....... wow, I wish I had written it down if I DID modify that software policy or software package! Too bad there isn't a way to see what changed and when.

In any case, both are now in the SEPM management and both have SEP, both installed by the Altiris/Symantec setup.

How many clients do you have? Generally you should have at least one Task Server, it can be in the same place as your Notification Server.