4 Replies Latest reply on Dec 4, 2014 5:33 AM by martin.gannon

    PXE representative install failure

    mbaney Apprentice

      Hi,

       

      I am having trouble installing the PXE representative.  Like many other posts I’ve read:

      https://community.landesk.com/support/message/75035#75035

      https://community.landesk.com/support/message/67341#67341

       

      It says it installed successfully but in fact it has not.  I’ve also looked at this:

      https://community.landesk.com/support/message/73264#73264

       

      Here are some lines from the osdrep.log file on the machine I am trying to install the PXE rep on:

      MSI (s) (D0:F0) [18:29:24:077]: Product: LANDesk(R) PXE Proxy -- Installation failed.

      MSI (s) (D0:F0) [18:29:24:077]: Windows Installer installed the product. Product Name: LANDesk(R) PXE Proxy. Product Version: 1.0.4. Product Language: 1033. Manufacturer: LANDesk. Installation success or error status: 1603.

      Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action _360D8BE7_4ED6_4312_B447_37B1A0861E4C, location: C:\Program Files (x86)\LANDesk\PXE\System\pxectrl.exe, command: /Install "/svcdir=C:\Program Files (x86)\LANDesk\PXE\System\\"

      Action ended 18:29:23: InstallExecute. Return value 3.

      Action ended 18:29:24: INSTALL. Return value 3.

       

      Here is an entry in the event log is during the install

      Failed to connect to server. Error: 0x800401F0

       

      And another:

      Product: LANDesk(R) PXE Proxy -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action _360D8BE7_4ED6_4312_B447_37B1A0861E4C, location: C:\Program Files (x86)\LANDesk\PXE\System\pxectrl.exe, command: /Install "/svcdir=C:\Program Files (x86)\LANDesk\PXE\System\\"

       

      Here is the CJ-PXE Representative Deployment log file:

      "Machine","CbaStatus","ExitCode","Duration","Begin","End","Command"

      "PXEREP","OK",1605,0:00:00,6/2/2014 6:11:38 PM,6/2/2014 6:11:38 PM,"MsiExec.exe /q /X{F238CE99-6614-4072-9D20-1D2FA7ED951A}"

      "PXEREP","OK",0,0:00:00,6/2/2014 6:11:39 PM,6/2/2014 6:11:39 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\files\bootmenu.1, C:\Program Files (x86)\LANDesk\LDClient\bootmenu.1, TOREMOTE"

      "PXEREP","OK",0,0:00:01,6/2/2014 6:11:40 PM,6/2/2014 6:11:41 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\files\bstrap.0, C:\Program Files (x86)\LANDesk\LDClient\bstrap.0, TOREMOTE"

      "PXEREP","OK",0,0:00:00,6/2/2014 6:11:42 PM,6/2/2014 6:11:42 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\files\dosundi.1, C:\Program Files (x86)\LANDesk\LDClient\dosundi.1, TOREMOTE"

      "PXEREP","OK",0,0:00:00,6/2/2014 6:11:43 PM,6/2/2014 6:11:43 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bootmenu.0, C:\Program Files (x86)\LANDesk\LDClient\bootmenu.0, TOREMOTE"

      "PXEREP","OK",0,0:00:00,6/2/2014 6:11:44 PM,6/2/2014 6:11:44 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\dosundi.0, C:\Program Files (x86)\LANDesk\LDClient\dosundi.0, TOREMOTE"

      "PXEREP","OK",0,0:00:00,6/2/2014 6:11:45 PM,6/2/2014 6:11:45 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bcd.dat, C:\Program Files (x86)\LANDesk\LDClient\bcd, TOREMOTE"

      "PXEREP","OK",0,0:00:00,6/2/2014 6:11:46 PM,6/2/2014 6:11:46 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bcd_x64.dat, C:\Program Files (x86)\LANDesk\LDClient\bcd_x64, TOREMOTE"

      "PXEREP","OK",0,0:00:00,6/2/2014 6:11:48 PM,6/2/2014 6:11:48 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bcd_ia32.dat, C:\Program Files (x86)\LANDesk\LDClient\bcd_ia32, TOREMOTE"

      "PXEREP","OK",0,0:00:00,6/2/2014 6:11:49 PM,6/2/2014 6:11:49 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\boot.sdi, C:\Program Files (x86)\LANDesk\LDClient\boot.sdi, TOREMOTE"

      "PXEREP","OK",0,0:00:02,6/2/2014 6:11:50 PM,6/2/2014 6:11:52 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\boot.wim, C:\Program Files (x86)\LANDesk\LDClient\boot.wim, TOREMOTE"

      "PXEREP","OK",0,0:00:02,6/2/2014 6:11:53 PM,6/2/2014 6:11:55 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\boot_x64.wim, C:\Program Files (x86)\LANDesk\LDClient\boot_x64.wim, TOREMOTE"

      "PXEREP","OK",0,0:00:00,6/2/2014 6:11:56 PM,6/2/2014 6:11:56 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bootx64.efi, C:\Program Files (x86)\LANDesk\LDClient\bootx64.0, TOREMOTE"

      "PXEREP","OK",0,0:00:00,6/2/2014 6:11:57 PM,6/2/2014 6:11:57 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bootia32.efi, C:\Program Files (x86)\LANDesk\LDClient\bootia32.0, TOREMOTE"

      "PXEREP","OK",0,0:00:00,6/2/2014 6:11:59 PM,6/2/2014 6:11:59 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bootmgr.exe, C:\Program Files (x86)\LANDesk\LDClient\bootmgr.exe, TOREMOTE"

      "PXEREP","OK",0,0:00:00,6/2/2014 6:12:00 PM,6/2/2014 6:12:00 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\pxeboot.0, C:\Program Files (x86)\LANDesk\LDClient\startrom.0, TOREMOTE"

      "PXEREP","OK",1603,0:00:09,6/2/2014 6:12:01 PM,6/2/2014 6:12:10 PM,"<qt/>C:\Program Files (x86)\LANDesk\LDClient\sdclient.exe<qt/> /p="http://128.8.118.44/landesk/files/osdrep.msi" /msi /N /An /Ac /g="{F238CE99-6614-4072-9D20-1D2FA7ED951A}" /disableclientqueue"

      "PXEREP","OK",0,0:00:50,6/2/2014 6:12:11 PM,6/2/2014 6:13:01 PM,"<qt/>C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE<qt/> /NTT=128.8.118.44:5007 /S="128.8.118.44" /F /SYNC /NOUI"

      ; "Job Complete","1 Done","0 Failed","0 Off","0 Unknown"

       

      I’ve tried chasing down these various error logs but they quickly become a morass.

        • 1. Re: PXE representative install failure
          Frank Wils ITSMMVPGroup

          is an older version installed maybe? Try to remove using Windows Programs and also check manually to delete the c:\program files (x86)\LANDesk\PXE map.

           

          Then try to reinstall.

           

          Frank

          • 2. Re: PXE representative install failure
            mbaney Apprentice

            No, an older version was no installed.  This was a fresh OS install.  However, it was Server 2012 R2 so that might have been the problem.  I did a fresh install of 2008 R2 and it worked fine.

            • 3. Re: PXE representative install failure
              ecoidan Specialist

              LDMS 9.5 SP2

               

              I am having the same issue with deploying or manually trying to install the PXE Rep on a 2012 R2 server.

               

              Windows Event Log:

              Product: LANDesk(R) PXE Proxy -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action _360D8BE7_4ED6_4312_B447_37B1A0861E4C, location: C:\Program Files (x86)\LANDesk\PXE\System\pxectrl.exe, command: /Install "/svcdir=C:\Program Files (x86)\LANDesk\PXE\System\\"

               

               

              Thoughts?

              • 4. Re: PXE representative install failure
                Expert

                The issue is caused by a missing variable on the 2012 R2 Server that was created during the agent installation.

                 

                To resolve this either install SP3 or follow this procedure:

                 

                Run the following line on the server and create the variable needed.

                SET LDMS_LOCAL_DIR=C:\Program Files (x86)\LANDesk\LDClient\Data

                 

                Once complete ran a full sync scan with the following command line:

                "C:\program files(x86)\LANDesk\LDClient\LDISCN32.EXE" /NTT=(name of core):5007 /S=(name of core) /I=HTTP://(nameofcore)/ldlogon/ldappl3.ldz /V /SYNC /F

                 

                After this has finished redeploy the PXE representative  and this will resolve your issue.