Quantcast
Channel: Symantec Connect - Endpoint Management
Viewing all articles
Browse latest Browse all 7163

WinPE PXE booted machine does not register - PECTAgent issue?

$
0
0
I need a solution

Presently we are running ITMS 7.6 and my WinPE is version 4.0.

The upgrade to 7.6 had its hiccups, but were sorted through easily and all was well. However, I've come across a new problem in the midst of slowly migrating our imaging process from DS6.9 to ITMS 7.6.

We PXE boot our machines into WinPE 4.0 with the x64 setup. This worked before and only when I rebuilt the WinPE did I run into trouble. My first headache was caused by the SYMLINKs being broken that BDC utilizes.

For reference you will see the links in question listed in this location on main NS server: C:\Program Files\Altiris\Notification Server\NSCap\bin\Deployment 

The location will have 2 SYMLINKs and 2 actual directories. The SYMLINKs directories should be BDC & DirversDB. The other two are Installs & Packages.

I corrected that issue alone with ONLY Step 3 in the article: http://www.symantec.com/docs/TECH211409

 
 
The problem:
 
Machines will boot into PXE and load properly and sit idle, like I have the system set to. Normally at this point, a new machine would register and check into the NS with an entry listed as its service tag, but I've also gone so far as to search All Computers via the IP Address with no luck. A little hunting lead me to the below article, which sorta went my direction. However that thread seems to have stalled out.
 
 
WinPE booted systems have properly working DNS, which was a question in the previous noted thread. I can ping servers by hostname alone without issue. I have also been able to manually map drives to copy the below logs off of the system to aid in determination of the issue. What is interesting is that the entries are exactly the same as the other thread. From what I can tell the issue did not crop up until after the 7.6 upgrade, as my original WinPE build worked before I recreated it following changes which were simple add-ons of BGInfo64 and a newer custom WinPE background image. Two things that would not have broken the WinPE instance.
 
WinPE Client - PECTAgent.log
[2015/03/29 15:15:45.288 1416:1420 2] Log File Created.
[2015/03/29 15:15:45.585 1416:1420 2] AgentGlobals.h:139 RegisterLibrary: x:\program files\Symantec\Deployment\Client Task Agent.dll has been registered sucessfully
[2015/03/29 15:15:45.601 1416:1420 2] AgentGlobals.h:139 RegisterLibrary: x:\program files\Symantec\Deployment\AeXNetComms.dll has been registered sucessfully
[2015/03/29 15:15:45.601 1416:1420 2] AgentGlobals.h:112 RegisterLibrary: LoadLibrary Failed to load x:\program files\Symantec\Deployment\AeXBasicInventory.dll
[2015/03/29 15:15:45.601 1416:1420 0] AgentGlobals.h:114 Agent Exception, Could not laod file ErrorCode=0, SystemError=6
[2015/03/29 15:15:45.601 1416:1420 2] PECTAgent.cpp:152 Stopping PECTAgent. Please check for Network configuration or server name resolving problem and try again.
WinPE Client - SMP.log
<event date='03/29/2015 15:15:45.2880000 -08:00' severity='4' hostName='minint-rq4cmo9' source='PectAgent' module='PECTAgent.exe' process='PECTAgent.exe' pid='1416' thread='1420' tickCount='22015'>
  <![CDATA[Version 7.06.1395]]>
</event>
<event date='03/29/2015 15:15:45.6010000 -08:00' severity='1' hostName='minint-rq4cmo9' source='PectAgent' module='PECTAgent.exe' process='PECTAgent.exe' pid='1416' thread='1420' tickCount='22328'>
  <![CDATA[AgentGlobals.h:114 Agent Exception, Could not laod file ErrorCode=0, SystemError=6]]>
</event>
 
 
Not sure where the hangup is. I went so far as to create another WinPE configuration instance in the Settings > Deployment > Preboot Configurations seciton of the NS, with the exact same results. Thoughts?

Viewing all articles
Browse latest Browse all 7163

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>