2 Replies Latest reply: Oct 14, 2010 12:27 PM by LANexpert RSS

    Can LANDesk distribute ThinApp ?

    Rookie

      Hello all !

       

      I recently virtualized applications using VMware Thinapp 4.0.4.

      Then, I tried to push my virtual application to a computer : it failed, with the specific error :

       

      Thu, 14 Oct 2010 10:35:09 processing of package is complete, result -2147467259 (0x80004005 - code 16389)

       

      In the Agent SDMCache, I can see the exe file, but .. he is @@partial@@, with the final size.

       

      Then, I tried to execute the application from the computer, by clicking on the EXE file, stored on my Network Share. It worked.

       

      The questions are:

       

      • Is LANDesk Virtualization Application strictly equivalent to VMware ThinApp ?
      • Does LANDesk includes some kind of  "protections" to prevent the distribution of virtualized apps generated with VMware ThinApp (instead of LANDesk App Virt) ?
      • Does anyone know what is the error I'm getting each time I try to distribute a VMware ThinApp ?

       

      Many thanks for your answer !

        • 1. Re: Can LANDesk distribute ThinApp ?
          Employee

          The questions are:

           

          • Is LANDesk Virtualization Application strictly equivalent to VMware ThinApp ? YES
          • Does  LANDesk includes some kind of  "protections" to prevent the  distribution of virtualized apps generated with VMware ThinApp (instead  of LANDesk App Virt) ? NOT anymoreIn 8.7 and early 8.8 it was.
          • Does anyone know what is the error I'm getting each time I try to distribute a VMware ThinApp ?  You may have a rights issue.  I would place the executable in the ldlogon directory on your core server and try to deploy using HTTP.
          • 2. Re: Can LANDesk distribute ThinApp ?
            Rookie

            I can now confirm that:


            • LANDesk Management Suite is able to distribute VMware ThinApp as well ;
            • There is no limitation ;
            • I had a right problem on my server.

             

            This is now solved.  Many thanks for your help !