Comodo Silent Installation Of Vlc

Posted on by

Installation has to be silent with no user intervention required. Here’s how this looks before you install VLC and WMP11 handles playback of.avi files. Official download of VLC media player, the best Open Source player. Create skins with VLC skin editor. Install extensions. View all screenshots. Silent installation and uninstallation switches for COMODO Programs Manager 1.3.

Deploying software in the enterprise can be quite complicated, it doesn’t have to but it can be at times. There are tons of people that will just “install” what’s necessary to get them out of trouble (even if it means doing it 100 times over and over!) The same group of people cannot really distinguish between installing and deploying and if you happen to have them on board – you’re in trouble. Now, I don’t even remotely consider myself software packager but when deploying applications I usually follow few simple rules to take care of the basics. Here are the rules: I. Installation has to be silent with no user intervention required. You run the install and usually don’t even know when its done unless you watch out for msiexec processes etc.

II. Once installed you should run it and no popups / random windows / activation, registration dialog boxes etc. Should come up. It simply has to open nice and clean. Again, once installed no extra rubbish should be copied to users desktop / start menu / run once etc. No auto update services should be allowed to start.

No tray icons should be visible etc. If you’re able to achieve all of the above you’re better than most. What we are essentially looking for here to clean and sleek deployment of whatever we need to push out to our client machines. No one likes to login to a machine and see 10 popup windows asking you do to do stuff. Horrible experience before you even start doing anything. Lets get to it! Command line to get VLC installed.

DEL 'C: Users Public Desktop VLC media player.lnk' / S vlcrc and vlc-qt-interface.ini can be downloaded from here: And that’s it! Now simply run vlc.exe and confirm points 1-3 have been taken care of.

Installation

For any questions please leave the comment down below! EDIT – 7th of May 2013 VLC has been updated to version 2.0.6 – please download the latest.exe from here – There is no need to change the vlcrc and vlc-qt-interface.ini files as they work fine. Windows XP and Windows 7 scripts stay as is but the install step needs slightly tweaking to include the version change. • Private Hi Adrian, First of all, thanks for the information you provided.

I got a question regarding your comment here: “Hey Steve, vlcrc is a preference file that’s used by VLC to store options you set in VLC Media Player like full-screen playback, customizations to user interface etc. There is no extension to this file and its being created on per-user basis assuming its not in All Users.” I’m using version 2.0.7 of vlc and I can’t get the configs in the vlcrc file to work for all users.

I’m using Windows 7. Here’s what I did: Installed VLC Changed preferences like Always on top to 1. Closed VLC Verified that the corresponding line in the vlcrc file was modified correctly. Moved the modified vlcrc file to the c: ProgramData vlc folder. Created a new user and logged in with it.

Started vlc Surprisingly, the program was creating a brand new vlcrc file in the c: Users%USERPROFILE% AppData Roaming vlc folder without using the Always on top set to 1 preference that was in the c: ProgramData vlc vlcrc file. Note that I was also using your vlc-qt-interface.ini file and it worked to remove the dialog box on Access Network Policy. But it seems that preferences within the program can’t be controled globaly via a vlcrc file placed in c: ProgramData vlc. Any thoughts on why it doesn’t work and how I could fix that? • Adrian Kielbowicz Post author Hi there, I’m not sure if this is a bug or something but I can replicate the behavior and subsequent issue you’re experiencing. For whatever strange reason vlcrc in C: ProgramData vlc is being ignored when new users are logging in which shouldn’t really be the case.