Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Deploy image task not received

Created: 30 Jan 2013 | 18 comments

I am able to PXE boot into WinPE.

However, I cannot successfully run any tasks while in the WinPE environment.  The NS will report "Waiting for agent to receive the task" until it times out.

From the client, I check the PECTAgent log and see the following two events repeated:

<![CDATA[m_client->get_MaintenanceWindows return error -2147467263]]>
<![CDATA[CTaskAgentBase::IsPastCheckTSListTime(): Current Task Server valid until "01/31/13 16:02:08" when the server list will be refreshed]]>

I run Task Manager within WinPE to verify that PECTAgent is started.

The task server is the same as the NS.

From the client, I can ping the TS/NS.  Deployment task handlers are installed on the server as well.

Any thoughts/suggestions?

 

Comments 18 CommentsJump to latest comment

SheetalD's picture

1. Try to kill PectAgent from Task manager within WinPE and restart it again(execute PECTAgent.exe).
2. Also during task execution, run Altiris Log viewer at NS server to check if any information/error is displayed.

boonet's picture

1.  Unfortunately, this did not make a difference.  I cannot run even a basic "Get IP Config" task.  It continues to state "Waiting for agent to receive the task"

 

2.  Altiris Log viewer is full of repeated info.  For instance, I ran the Get IP Config task at 8:17:27, and here are the errors reported around that time frame (note that these errors are not only reporting within this time frame.  They are there well before and after issuing a task):

 

Thomas Baird's picture

The statusevt message "shouldn't" be an issue, though I thought that was fixed in something like MP1.  You'd have to call support / task to find out.

The other message, well, we can see the top line, but not what it says.

Suggestion: can you schedule a getIPconfig task on a production system?  Can the client actually ping the server?  Are you out of licenses?  When you do NOT schedule a task, is your log viewer just as red?

Thomas Baird
Private Consultant & open to full-time opportunities.
That means I CAN help beyond the forum (directly).

 

boonet's picture

Thomas,

Thanks for the quick response. 

Per your suggestions:

A  getIPconfig task works on multiple production systems, just not any that are within the WinPE environment (or so it appears).

The client in WinPE can ping the server and resolves the name correctly

I have verified that nearly 150 licenses are available.

The log viewer is always red.  Even when imaging would intermittently work in the past

Nelo's picture

It would be intersting to see the pect agent logs.  x:\program files\altiris\altiris agent\logs  see if there are any errors.  Probably kill the pectagent, delete the log files and start pectagent again.

 

nelo

boonet's picture

Nelo,

Here are the PECTAGENT logs from x: after running a simple get IP config task:

Here is something I am not understanding...

In the log screenshot above, it keeps referencing the hostname MININT-HTRVH55.  However, the computer that is booted into WinPE (the same computer that contains this log) actually has the hostname MININT-CQ62F9P.  On the NS, CQ62F9P is the only resource beginning with MININT-.  So why is the PECTAgent log recording the hostname of HTRVH55?  I have tried pinging this hostname to no avail.  It does not exist.

mclemson's picture

Related to the errors, it says to install hotfix rollup v3 if you are running 7.1 SP2:
http://www.symantec.com/docs/TECH47665

You are seeing a new MININT name because it creates a new one each time it loads WinPE, I believe, assuming new systems.  I believe these aren't consistent from boot event to boot event.

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

Ishani Bose's picture

The client you booted to PXE is it a managed machine with Symantec Management Agent installed, or an unknown machine with no entry present under SMP console, Managed->Computers.

Also verify if PectAgent is running,after client booted to PXE.

 

boonet's picture

Related to the errors, it says to install hotfix rollup v3 if you are running 7.1 SP2:
http://www.symantec.com/docs/TECH47665

You are seeing a new MININT name because it creates a new one each time it loads WinPE, I believe, assuming new systems. I believe these aren't consistent from boot event to boot event.

Good to know that the other MININT name is not related to the problem.

 

The client you booted to PXE is it a managed machine with Symantec Management Agent installed, or an unknown machine with no entry present under SMP console, Managed->Computers.

Also verify if PectAgent is running,after client booted to PXE.

The client referenced throughout the post is an unknown machine with no entry present under the console.  It only shows up in the console once it has booted into the WinPE environment, wtih a name of MININT-xxxxx.  PECTAgent is indeed running in WinPE mode.  I have also restarted this process.

mclemson's picture

If the Get IP Configuration task fails, try running ipconfig from a command prompt in WinPE.  Is it successful?  The task itself is just running ipconfig.exe.  You could try running a simple task like the 'DIR Pause' sample script.

So, confirm that from a command prompt you can ping the Notification Server and/or your task server.  Confirm ipconfig works.  And try a simple Run Script task like DIR Pause.

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

boonet's picture

Although the Get IP Config task fails (times out), running ipconfig from the command prompt in WinPE is successful.

mclemson's picture

What about simple scripts, like the DIR Pause sample?  If you have a job that Reboots to WinPE, runs that script, then Reboots to Prod, does the script succeed?

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

boonet's picture

mclemson:

I receive the following error on the NS when I launch the same DIR Pause script:

Status: Failed
Return code: -1
 
Start time: 2/4/2013 8:09:48 AM
End time: 2/4/2013 8:09:58 AM
Total run time: 9 seconds

 

An error occurred while attempting to launch the script.

 

mclemson's picture

Did you check 'require HTTPS' when configuring Altiris?  If so, HTTPS will not work in automation until 7.5, so you should remove that requirement in IIS and reconfigure agents to use HTTP.

Are any updates available in SIM?  If so, when logged on locally as the application identity, run SIM and install those updates.  Are any solutions listed with a Reconfigure.. button when you go through the list and select each?  If so, click Reconfigure.. to reconfigure that solution/platform/suite, or run 'cmd' as an Administrator and then run aexconfig.exe /reconfigureall.

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

boonet's picture

mclemson...in IIS, it looks like "Require HTTPS" is unchecked.  I also opened the PECTAgent log on a client device and verified that it is connecting to the NS with http:// and not https://.

I will look into your other suggestion.  As of right now, I am using 6.9 to image our devices.

boonet's picture

In addition, it looks like SIM 7.5.92 is available, but I am not sure if that would make a difference.

 

Also, no Reconfigure buttons appear, just the usual Repair and Uninstall buttons.

 

Thanks for your help.

mclemson's picture

I'd run the command specified in my above post, to make sure everything is installed properly.

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

Thomas Baird's picture

Script tasks all fail if you mark the advanced option to capture script output.  That option will NOT work in automation.  No matter what script type you choose (at this time).  It has been broken since the release of SP2.

My guess is that a quick call to support would resolve this BTW.

That said, an agent sitting in automation should be able to receive a task without issue.  Here's a test for you.

1) in the SMP console remove ALL MiniNT computers (right-click | delete) so there are absolutely none.

2) Clear all the files in the SBS Store folder (all the SBS files - historical only anyway)

3) Restart the PXE server service (SBS server).  Wait for 3 or 4 SBS files to appear in the SBSStore folder so you know the service is ready.

4) Boot to PE.  Wait for a record to appear in the console with a MiniNT name.  You'll have to refresh it occasionally to find it (I like to switch from tasks to computers back and forth.  This should be the computer you just started.

5) assign a task to the system, like a script task (remember to NOT do that advanced option) using VBScript that reads:

msgbox "hi"

6) see if you get a popup box on the system.

 

If that works, you're well on your way.  There still may be some mysteries, but at least you know it is "functional".

Thomas Baird
Private Consultant & open to full-time opportunities.
That means I CAN help beyond the forum (directly).