Hello,
I am attempting to deploy CONNECTION Client v10.00.10.13 silently as per the wiki using the command below and it consistently installs the desktop shortcut.
Silent Install Command: "blg6410001013en.exe BeCheckUpdateOption=3 BeCheckUpdateIsEnabled=0 /q"
It appears to honour this option when installing manually (i.e. same command options without /q); how can I force the installation to respect the do not "Create application shortcut on Desktop" option when performing a silent install?
Is there a complete list of all command line options available for the installation of CONNECTION Client v10.00.10.13?
Thanks
Chris Douglas4DGeotechnics PTY LTD
Sorry for the delay. Use the following "blg6410001013en.exe InstallDesktopShortcutFromParent=0 /q"
Regards,
Tamicca SellarsMicroStation Product Manager
Hi Tamicca,
Thank you for your reply and suggested solution.
I can confirm the "InstallDesktopShortcutFromParent=0" installation switch works for silent installations, but only when initiated from an elevated command prompt within a user session. When installing as the SYSTEM user though (i.e. with a GPO startup script) it continues to create the desktop shortcut.
Is there a known way to silently deploy CONNECTION Client to multiple computers without creating the desktop shortcut?
Hi Chris,
The CONNECTION Client installer should behave the same way for elevated shell and system user. Can you send me the installation log from %temp%? Click the insert button in the editor or drag and drop the log here.
I've just sent the log files from the most recent installation via private message.
I was able to verify the different behaviour today, on my workstation at least, by running the installation from an elevated shell, as the the system user, using psexec.
Also, I observed that the automatic first run immediately after installation is opened within the user context of the elevated user and not the currently logged on standard user. As a result, when the standard user then enters their credentials, they are stored in the user profile of the elevated user and not their own.
Is there a way to prevent this immediate first run from occurring?
For shortcut problem, please try with InstallDesktopShortcutFromParent=1
To prevent launching add command line parameter
PostInstallLaunchApplication=””
Thank you for the "PostInstallLaunchApplication" parameter, it works perfectly.
Still no success with preventing the desktop icon though. I have now resorted to deleting the shortcut as a post install cleanup task.
I know this is an old thread but to stop the installer form installing the DT Shortcut add InstallDesktopShortcutFromParent=2
InstallDesktopShortcut=0
Worked for me, from SCCM command running as system account on desktop.
I've asked the last reviewer to add it to the list in the wiki.