Deployment Solution

 View Only
  • 1.  Computers with new HDDs will not image - PECTAgent.exe Application Error

    Posted Oct 04, 2016 03:13 PM
      |   view attached

    I'm in the process of upgrading a bunch of computers on my network with SSDs.  I've been installing the SSDs, selecting the old computers names in the Console (MAC addresses match) and scheduling the image job.  I then manually boot the computers into PXE and the image goes.  I've done this for about 100 or so computers but I've just come across an entire hallway worth of computers that will not fully boot to PXE with the new SSD's in them.  I get the attached error message.  I've eliminated this as being a network issue and even so far as plugging them into the same ports as other computers that had just imaged successfully.  Furthermore, if I put a new SSD into the computers that HAVE imaged successfuly, those will work.

    It appears my issue is isolated to only a select group of computers/MAC addresses.  Everything I'm reading about this error points me to the solutions like this but that's not my issue.  I've rebooted my server, restarted services, recreated the PreBoot packages (giving them ample time) and nothing helps me to image this specific group of computers.  Others image just fine after all of this.

    Not sure where to go from here.

    Note : Recently uploaded media files are still processing:

    • IMG_20161004_092515.jpg



  • 2.  RE: Computers with new HDDs will not image - PECTAgent.exe Application Error

    Broadcom Employee
    Posted Oct 10, 2016 06:26 AM

    What is the exact version of DS in use?

    What is the architecture of WinPe we are using on those clients.

    Have you tried both PE arch?



  • 3.  RE: Computers with new HDDs will not image - PECTAgent.exe Application Error
    Best Answer

    Posted Dec 07, 2016 02:12 PM

    Jim,

    If the ssd's from the non-working clients work when placed in the working clients slot then I would say it is an issue with the computer itself.

    Check the bios and make sure the version is updated, older bios versions would not have the correct information for reading SSD's which may be causing the issue.