Client Management Suite

I have a managed delivery policy in place to install and upgrade software and everything is working fine. My problem is I am using a batch file to uninstall the old software and I can't find a way to hide the command box that pops up. I don't see a place where I can "uncheck" the option for user input required. In my main managed delivery policy for the new software I've set the option to hidden as well as unchecking the user input required box. It looks like the settings for the uninstall for the old settings are somewhere else and I can't seem to find them. If I go into the properties of the package on the client I can see where are all the settings are listed but I don't know how to adjust them on the server end. Attached is a screenshot if I'm not making any sense.

CMS 7.1 SP1

Software Delivery

with a detection rule and then you can deselect the "Allow user to interact..." box in the Policy Advanced Options.

Yeah I have my detection rule set for the "new" software and I've went in and added my supersede settings so it knows to call the uninstall job when it detects the old software. For my policy it looks like that setting only applies to the "new" software being installed. I would think when you checked the automatically upgrade box you would get options for the old software being uninstalled.

Now that I went through to look at it, I see what you're saying now. So I added a the "old" software job and called the uninstall command and was able to access the options. It would certainly be nice if I didn't have to add the extra step but I guess as long as it works. 

What's weird is once it's added I get two different uninstall tasks and the first one shows that the uninstall task is hidden and the second one shows that it won't be. There must be an xml file or something somewhere that can be edited to change those settings. I'm really just curious at this point.

tool from the support site you can see the XML the client gets but I'm pretty sure it's composed "on the fly" from the database when the Config Update request is made.

To change the behaviour you might be able to find a SQL stored procedure and edit that but it wouldn't be a trvial adjustment and it would probably get overwritten on the next update.

I just live with adding the uninstall explicitly - makes the policy easier to follow for those less familiar with the intricacies of dependencies too,