/build/static/layout/Breadcrumb_cap_w.png
09/10/2019 73 views

I'm having an issue where if I install FileMaker 18 manually it creates shortcuts like it's supposed to but when deploying the same package through SCCM it doesn't create a quick launch shortcut, just the desktop shortcut.  Anyone else having this issue?  It's the same source files and it reads the Assisted Install.txt but no quick launch shortcut.

0 Comments   [ + ] Show comments

Comments


All Answers

0

Most likely it is caused by the execution context. SCCM's agent uses the local SYSTEM account to perform an installation.
As I remember, the quick launch icons are added per-user (in the user's profile folder), so that's why execution in a different context is not able to create them for the user.

To make sure if that's the case, you can install the software manually using PSEXEC -si.

If you provide more details, what is the exact path and target of the quick launch shortcut, what is the operating system version etc. then I will try to dig deeper as for now, I don't recall how it could be handled.

Answered 09/11/2019 by: rad33k
Third Degree Brown Belt

  • Yeah, if I set the Installation Behavior to "Install for system" then it only creates a desktop shortcut. If I set it to "Install for user" then it only creates a quick launch shortcut if that user has admin rights which our users don't so the installation fails. If they have admin rights it does create the quick launch shortcut but giving our users admin rights isn't an option.