4 Replies Latest reply on Jul 25, 2012 1:48 AM by ffazzi

    LaunchPad Link

    ffazzi Rookie

      Hello,

       

      We are moving from Novell ZEN/ZCM to LanDesk. Now the clients are used to launch some applications from NAL (Launchpad is very similar concept). The problem is that often the link we create and associate to the client it isn't in the LaunchPad. I have the task "successful" anyway the client can't see that app. Sometimes I need to reinstall the landesk agent and/or launch a refresh. And sometimes the link is not ready anyway. We have the latest LanDesk client and Console. Thank you!

        • 1. Re: LaunchPad Link
          Phil.Lambert Apprentice

          Check to see that the user has access to the executable.  If the program that the Launchpad link points to does not exist or the user cannot see the executable, the Launchpad shortcut won't appear.

           

          Check to see if the shortcut appears in the %ALLUSERSPROFILE%\Application Data\LANDesk\ManagementSuite\LaunchPad\XXXXX.  Check the security of the shortcut file.  If the launchpad task is assigned to the machine, All Users will have access.  If just assigned to one user, only that user has access to the shortcut.

           

          Another thing to verify is the icon of the shortcut.  If the executable does not have an icon. Try assigning one.  If the shortcut file does appear in the above mentioned directory, check to see if the assigned icon appears in the properties.

           

          Occasionally we have to run a clean-up script on a device when a shortcut dissappears and then refuses to re-appear.  It usually happens when the task is started multiple times.  The client db will show the task successful and the inventory shows the Launchpad link, and the client ignores future attempts to distribute the link.  (let me know if you want the script, which is slightly modified from the one supplied by LANDesk support)

          1 of 1 people found this helpful
          • 2. Re: LaunchPad Link
            ffazzi Rookie

            Hi Phil,

             

            thank you for your answer. I would appreciate very the script. I'll do some test in the folders you wrote about. Thanks again...

            • 3. Re: LaunchPad Link
              Phil.Lambert Apprentice

              This is local version that you can copy to a machine and run remotely or create a package to distribute.  If you create a package, use a PUSH delivery method and not a Policy.

               

              ========================================================

              Rem Stop Policy service....................
              net stop "LANDesk Policy Invoker"

              REM Delay..................................
              ping -n 10 localhost


              REM  Delete local Database and all task files........................
              DEL /f /q "%LDMS_LOCAL_DIR%\..\sdclient.tasks.xml"
              DEL /f /q ""%LDMS_LOCAL_DIR%\..\..\Shared Files\cbaroot\alert\queue\internal*.xml"
              DEL /s /f /q "%ALLUSERSPROFILE%\Application Data\LANDesk\ManagementSuite\*.*"
              DEL /s /f /q "%ProgramData%\LANDesk\ManagementSuite\*.*"


              rem Delay ...................................
              ping -n 10 localhost


              rem Rebuild Database...............................
              "%LDMS_LOCAL_DIR%\..\clientdbutil.exe" /create

              rem Delay .........................................
              ping -n 10 localhost

              rem Restart Policy Service.........................
              net start "LANDesk Policy Invoker"


              rem Delay .........................................
              ping -n 10 localhost

              rem Policy Sync ......................................
              "%LDMS_LOCAL_DIR%\..\policy.sync.exe"

              ===============================================================

               

              This the Script in "Manage Scripts"

              =================================================================

              ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
              ; MACHINES - This section is run once for each machine in the target set. 
              ; Commands in this section will be processed in the order they are listed
              ; in the custom script.  This section supports both local (LOCxxx) and remote
              ; (REMxxx) commands.

              [MACHINES_NT]
              REMEXEC1=cmd /c net stop "LANDesk Policy Invoker"
              REMEXEC2=cmd /c ping -n 10 localhost
              REMEXEC3=cmd /c DEL /f /q "%LDMS_LOCAL_DIR%\..\sdclient.tasks.xml"
              REMEXEC4=cmd /c DEL /f /q ""%LDMS_LOCAL_DIR%\..\..\Shared Files\cbaroot\alert\queue\internal*.xml"
              REMEXEC5=cmd /c DEL /s /f /q "%ALLUSERSPROFILE%\Application Data\LANDesk\ManagementSuite\*.*"
              REMEXEC6=cmd /c DEL /s /f /q "%ProgramData%\LANDesk\ManagementSuite\*.*"
              REMEXEC7=cmd /c ping -n 10 localhost
              REMEXEC8="%LDMS_LOCAL_DIR%\..\clientdbutil.exe" /create
              REMEXEC9=cmd /c ping -n 10 localhost
              REMEXEC10=cmd /c net start "LANDesk Policy Invoker"
              REMEXEC11=cmd /c ping -n 10 localhost
              REMEXEC12="%LDMS_LOCAL_DIR%\..\policy.sync.exe"
              REMEXEC13=cmd /c ping -n 10 localhost
              =========================================================================

              • 4. Re: LaunchPad Link
                ffazzi Rookie

                Hi Phil,

                 

                thank you very much! It worked for a couple of computer, mine included. Ciao! F.