How did it get into the cache in the first place? Are you 100% certain that the file has been recognised as being there or did you place it there yourself manually?
Mark Star - MarXtar LANDesk Enhancements
Home of Power State Notifier & Wake-On-WAN for LANDesk
I agree with mark. How did you get the file there? If you copied it manually, you would need to restart the Targeted Multicast Service so the TMC would actually know the file is there. You can verify that TMC is aware of the file by typing the following:
C:\Program Files\LANDesk\LDClient>tmcsvc.exe /f|more
I sent it using a scheduled task using the a multicast delivery method. It does work if I do it as a policy supported push and cancel the job(on the workstation using the package UI) then run it from the portal. But I need it only to install when clicked from portal.
That's the problem. You need to change your delivery method to just a Policy either optional or recommend in order for it show up in the portal.
With a policy supported push LANDesk is going to Push the package first. IF and only If that push fails(IE you canceled it) then that job with be converted to a policy.
I figured a way around which actually works better. I create a policy supported push so it would also cache my package even if the multicast failed. I then created a blank batch file. I added my package as an additional file. after that job finishes I just put them in a seperate policy that tells them to install only from cache.