The third method: On the Foxit screen, press down Ctrl + F11 shortcut keys to show or hide the ribbon bar.įor versions prior to V81, please do one of the following ways to show or hide the ribbon toolbar. The second method: Right-click toolbar and uncheck the Minimize the Ribbon option to have the ribbon displayed. The first method: Click on one of the tabs in Foxit application.In the following figure, I Choose HOME tab.Click the pushpin icon located on the lower-right corner of the ribbon. please do one of the following ways to show or hide the ribbon toolbar. Hopefully it will help someone else.The following describes how to stop ribbon toolbar from auto hiding in different versions of Foxit PhantomPDF.įor version 8.x to V10.x. My VB skills aren’t great so there might be a cleaner way of doing this, but I added the lines below to the subroutine “FixupUninstallString” and works great. Ran into an issue with a program where it called an executable in the uninstall string, but had a space in the path so I would always get “file not found” when executing the script. Jason, First off thanks for putting this together as I use it all the time. Uninstall Software Script (v 1.10): Get it on GitHub Configure the setting check to check for a value equal to zero for the item to be compliant as anything else is non-compliant and that’s when we want the remediation script to kick in. Then use the script as both the detection and remediation script in the compliance item (each modified slightly differently per the notes in the script itself). This is because we can’t pass parameters to scripts used in compliance items. To do use the uninstall software script in this way, first modify lines 64, and 66-68. It is also possible to use this script in a compliance item - you will have to increase the compliance item timeout however for it to successfully uninstall anything (). Deploy as an Uninstall optionally hiding it from the Software Center completely (as it would look awkward to the user if they see it there).Set the detection method to run the script changing the lines in the script as if it were a compliance item (see below and the comments in the script itself for this).Use a noop for the install command line, something like the following:.Specifying one of the above command lines as the Uninstall command line in the deployment type.Create the application and a deployment type.You can also use this script in an application by using the following guidelines: cscript.exe Uninstall-Software.vbs /product:"Quicktime" /uninstall.cscript.exe Uninstall-Software.vbs /product:"Adobe Acrobat Reader" /uninstall.cscript.exe Uninstall-Software.vbs /product:"Adobe Reader" /uninstall.The following are examples successfully used in a large production environment and deployed using a package and program in ConfigMgr CB (1602): If you need to modify the uninstall string fix-ups applied, simply edit the FixupUninstallString subroutine that starts on line 175. This will cause the log entries to be output to the console in addition to the log file. /hwinv - if specified (and the ConfigMgr agent is installed on the system) runs a hardware inventory at the endįor testing purposes, simply don’t specify the uninstall switch./uninstall - if specified actually runs the uninstall string.The uninstall software script presented here takes one parameter (without which the script does almost nothing): Creates (or appends to) a log file (called Uninstall-Software.log) in the temp directory of the user running the script or the ConfigMgr logs folder if the ConfigMgr agent is detected.Outputs the number of matching products found to the console/stdout.Runs the fixed up uninstall string to uninstall the product. Adds /norestart if it’s not there already.Fixes up the uninstall string if needed.Grabs the Uninstall string from the entry.Finds and loops through entries by DisplayName that contain a specified substring.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |