How to do custom command line?

Topics: Misc.
Jul 23, 2015 at 6:02 PM
I'm very familiar with WSUS itself, but a newbie for WPP. I've successfully deployed several basic self-contained updates using WPP.

But how do I create and update for an exe that requires a custom command line parameters to make it run silently?

I've searched and I find lots of posts that talk about using custom command lines, but I can't find anything that tells me specifically how to create a custom command line.

I did check into using the "Custom Update" wizard in WPP, which looks like it will do what I need to do. But is that the only way to create an update to use a custom command line? Is there no way to just add command line parameters to a normal update?

Also, if I use the Custom Update wizard, or if there is indeed another easier way for normal updates, are there any caveats to be aware of regarding quote characters on the command line? My command line does require quotes.

One other idea I had... I do have a license for WinZip self-extractor full version where I can create packages "for software installation" (where it extracts the self-extracting .exe to the TEMP directory, runs a command line, then deletes the extracted contents from TEMP). I could encapsulate my program installer .exe inside the WinZip self-extractor and publish the WinZip .exe file. So WSUS would just run the WinZip .exe file which would still require no extra parameters and run silently, and the WinZip .exe would then extract the actual software install .exe and run the custom command line. Is there any reason that wouldn't work?

Thank you!
Jul 23, 2015 at 7:38 PM
You can have a look at this documentation (page 3) : TightVNC Deployment with Custom Settings
Marked as answer by DCourtel on 7/23/2015 at 2:25 PM
Jul 23, 2015 at 8:29 PM
Ha! Thanks! I really appreciate your reply. Now I feel really stupid though (through entirely my own fault). :) Somehow I totally missed seeing that Command Line field. Duh!
Jul 28, 2015 at 1:56 PM
Follow-up on this. Is there any special handling of quotes on the command line? My command line isn't working.

This is one of those things where the installer is an .msi encapsulated inside a setup.exe. So the parameter I need to add to the command line for the setup.exe is:
/v”/qn REBOOT=ReallySuppress”

This works fine when I run that command line manually to install the product, but it's not working when deploying through WSUS with WPP. The WindowsUpdate.log file on the workstation PC says it's installing the update, but it's not actually installed. I'm thinking that maybe the quotes are the issue, but I don't know for sure.

Thank you.
Jul 28, 2015 at 4:39 PM
You can make multi try. Just revise the update and change the command-Line
Jul 28, 2015 at 7:19 PM
I'm sorry, but I don't know what you mean by multi try. And in what way would I revise the command line?

I will say, WSUS does re-detect that the update is not installed on the next detection, and does try to install it again, and again, and again.
Jul 28, 2015 at 8:43 PM
Right click on the update in WPP and choose 'Revise'. Then change the Command-Line until you find the right one.
Jul 28, 2015 at 9:05 PM
I know HOW to change the command line. I don't know what I'd change it to. That IS the correct the command line that I posted in the my original post.

I'm still not sure what you mean by "make multi try" in your earlier reply today. can you please explain that?

Since you didn't address this question in your earlier replies, am I correct that I don't need to do anything special for having quotes in the command line? I don't need to "escape" the quotes, or make them double quotes, or anything else special?

Thanks again.
Jul 29, 2015 at 6:57 PM
Well, I figured out my problem. Darn "autocorrect" and copy & paste! :)

It was indeed the quotes that were the issue, but not in the way I thought.

I had copied and pasted the command line into WPP from an Outlook email message. Outlook had "autocorrected" the quote characters to fancy "open" and "close" quote characters instead of just plain standard quotes. So that's what I pasted into WPP.

Once I manually typed in the quote characters on the command line field in WPP so they were true quote characters, the install worked just fine.
Marked as answer by DCourtel on 7/29/2015 at 1:32 PM