Been working with @xrobx99 on this one. We had a request for TweetDeck to be installed on a couple of user’s machines. We feared that word would get out and everyone would have to have it. So we have been looking into deploying TweeDeck silently through SCCM. Using my SCCM PowerShell install script (which is basically just a wrapper for the msi commands) we have observerd the following issues below:
When run silently with the command: msiexec /i TweetDeck.msi /q /norestart /l c:\Temp\TweetDeck.log
- Short-cuts don’t get created
- TweetDeck does not show up in Add Remove programs
Other Non-enterprise ready issues that we have observed:
- No way to know the current version number without installing first (shouldn’t it be in the MSI properties?)
- Web site does not show the current version number
- Is there a way to NOT check/prompt for update on close? This is annoying for non-administrators (they get a UAC prompt)
- Twitter’s registry entry in HKCU\Software is not with a capitol “T” (I know, weak, but that kind of stuff drives me crazy)
It is entirely possible that I am doing something wrong, but those are my findings.
UPDATE I realized that I can use the ALLUSERS=1 parameter and the program will be installed for all users, then the Icons and Add remove programs will be correct. Maybe the packagers need to include ALLUSERS=1 in their packaging software? Updated install string:
msiexec /i TweetDeck.msi ALLUSERS=1 /q /norestart /l c:\Temp\TweetDeck.log
Thanks for the hint regarding “ALLUSERS=1”! Saved my morning! 🙂
A lot of other interesting – bookmarking-worthy – scripts and pieces on your site! Keep up the good work.
Greetings from Germany
Wolfgang
Thanks for taking the time comment!
Very helpful, thanks 🙂
i try it with the Version 2.1.0 msi file and doesn’t work with msiexec /i TweetDeck.msi ALLUSERS=1 /q /norestart /l c:\Temp\TweetDeck.log
* no Short-cuts created
* TweetDeck does not show up in Add Remove programs
* Tweetdeck is installed ind the x86 folder and run it.
🙁
I have not had much luck with this package. I tried to reach out to the vendor, but they didn’t reply to my request for better enterprise deployment support. Sorry I couldn’t help.