Deployment Solution

 View Only
  • 1.  pectagent.ini and thumbprint

    Posted May 06, 2015 02:04 PM

    I have an issue where computers are booting into PE, but unable to register with the SMP.  The errors in the logs are pointing to SSL.

    The computers show up in the console as vm-********************  but never switch over to MINNT-********

     

     

    Does the Pectagent.ini need to have the SSL thumbprint id?

     

    FYI 7.5 HF5 - I've already installed the inventory hot file and re-compiled the PE image.

     

     

     



  • 2.  RE: pectagent.ini and thumbprint

    Posted May 06, 2015 02:09 PM

    Where have you replaced BasicInventory.dll?

    Could you describe the steps you took?

    Because if you replace it in the NS, you will have to wait it until it replaces the site server/PXE server in your location and then you recompile the image.

    Regards



  • 3.  RE: pectagent.ini and thumbprint
    Best Answer

    Posted May 12, 2015 05:14 PM

    Hi,

    please note that "Since Deployment Solution 7.5, computers rebooted to Automation are renamed to their serial numbers rather than "MiniNTxxxx"."

    https://www-secure.symantec.com/connect/blogs/how-find-computer-rebooted-winpe-automation-ds-75

     

    regarding DS and SSL, please make sure your DS environment has been set up for SSL as from documentation:

    http://www.symantec.com/docs/HOWTO95059

     

    Regards,

    Mauro



  • 4.  RE: pectagent.ini and thumbprint

    Posted Jun 04, 2015 02:19 PM

    @ Mauro -  thanks for mentioning that there is no more minint-xxxx naming convention, I was wondering why it wasn't showing up like like 7.1.

    I found that the Extract SSL task failed to run on the site server.  I had to manually run it.  My root cause is something with Task server/IIS.

    FYI -  this is a heavly locked down environment (no SYMC support) only one knows what hardening was placed on the server, permissions, DCOM, and IIS.

    I'm marking the thread as closed.

     

     

    UPDATE:

    The SSL cert only had the shortname in the Subject Alternative Name field.  It was missing the FQDN.