ImgBurn
Hi,
I'am trying to install ImgBurn sillent, I found the install switch for the app. setup.exe /S, but somehow when I deploy it through SMS it does not make an shoortcut on userse desktop, then I attached /ALLUSERS=2 to the command line, but this did not work out for me, is there anybody hwo knows to get this right.
http://www.imgburn.com/
Thanks
Henrik
I'am trying to install ImgBurn sillent, I found the install switch for the app. setup.exe /S, but somehow when I deploy it through SMS it does not make an shoortcut on userse desktop, then I attached /ALLUSERS=2 to the command line, but this did not work out for me, is there anybody hwo knows to get this right.
http://www.imgburn.com/
Thanks
Henrik
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
Posted by:
dkelle
16 years ago
Posted by:
anonymous_9363
16 years ago
...probably because *your* Setup stub doesn't support that switch. Use the policy .REG advice instead. Remember that, being a machine policy, it will log *all* MSI activity so you'll want to turn it off once you're done.
Because the log files are named randomly, there's no clue as to which belongs to which MSI. I normally use DOS's FIND command to quickly locate the one I'm interested in. Use the MSI name as the unique text to search for:
FIND /C /I [unique_text_to_search_for] %temp%\MSI*.LOG
Because the log files are named randomly, there's no clue as to which belongs to which MSI. I normally use DOS's FIND command to quickly locate the one I'm interested in. Use the MSI name as the unique text to search for:
FIND /C /I [unique_text_to_search_for] %temp%\MSI*.LOG
Posted by:
nheim
16 years ago
Posted by:
cipher
8 years ago
This is an old thread, I know, but age is irrelevant for default searches from search engines. This article pops up at the top.
So I did my own research and answered this question. Those looking to install ImgBurn silently have two options...
So I did my own research and answered this question. Those looking to install ImgBurn silently have two options...
- Use the two case-sensitive switches /S and /NOCANDY. This is important, since you don't want to install the adware "OpenCandy" which ImgBurn deploys these days. Example: setupimgburn_2.5.8.0.exe /S /NOCANDY
- Use compression software (ie: 7Zip) to extract the installer file into a new folder. You'll get the executable along with its plugins all by itself. You can make your own deployment from there, but be sure to delete the file "OCSetupHlp.dll" from the "$PLUGINSDIR" folder since that's the OpenCandy software you don't want.
I deployment ImgBurn 2.5.8.0 on systems successfully with the option #1 above. I'm using Microsoft Deployment Toolkit 2013 Update 1, but should work fine with other tools and applicances like Dell KACE 2000. Good luck!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.