SHARE: Post New Thread Similar Threads Anyone have an MSI for a PDF creator.I have managed to setup a one site SCCM deployment..LinkBack LinkBack URL About LinkBacks Bookmark Share Digg this Thread Add Thread to del.icio.us Bookmark in Technorati Tweet this thread Share on Facebook Reddit Thread Tools Search Thread Advanced Search 27th August 2014, 05:45 PM 1 Sh500 Join Date Aug 2014 Posts 11 Thank Post 2 Thanked 0 Times in 0 Posts Rep Power 0 Uninstalling PDF Creator- running a cmd script Hi all, New to this forum and indeed SCCM.Application deployments seem to be working fine and as expected.
2011 Black List Scripts Creator Manual Scripted MethodI have installed this via a manual scripted method as an Application. 2011 Black List Scripts Creator .Exe Verysilent SUPPRESSMSGBOXESAs far as I am aware there is no official MSI for this program, so I thought Id try to uninstall the software, via the following.cmd script: C:Program Files (x86)PDFCreatorunins000.exe verysilent SUPPRESSMSGBOXES NORESTART This works fine when run manually but I cannot seem to get it working via SCCM. I have searched the net and there has been discussion about batch scripts and system rights, etc. 2011 Black List Scripts Creator Full And ProperPerhaps its something to do with what folder the script needs to execute Can someone please let me know, the full and proper procedure using SCCM 2012 to uninstall this program. Many thanks. 27th August 2014, 06:19 PM 2 free780 Join Date Sep 2012 Location Leeds,UK Posts 2,983 Thank Post 262 Thanked 463 Times in 374 Posts Rep Power 194 In the path to the uninstall exe (within the deployment type) make sure you enter its as it would be on a 32 bit is. Then tick the box that says this is a 32 bit program on a 64 bit is. Sorry I cant remember the exact wording. August 2014, 08:05 AM 3 macshinobi Join Date Aug 2005 Posts 10,312 Thank Post 3,835 Thanked 1,181 Times in 1,071 Posts Rep Power 400 Arthur wagnerk SYNACK Found some articles via google but then found the uninstall string for PDF Creator which shows the same as what Sh500 is already using and when I tried to use msiexec uninstall or similar I kept getting error messages Just wondering if you could shed some light on how to remove PDF Creator. Yep, I have that boxed checked already. August 2014, 10:47 AM 5 free780 Join Date Sep 2012 Location Leeds,UK Posts 2,983 Thank Post 262 Thanked 463 Times in 374 Posts Rep Power 194 Is the path to c:program files or programfiles 28th August 2014, 11:12 AM 6 Sh500 Join Date Aug 2014 Posts 11 Thank Post 2 Thanked 0 Times in 0 Posts Rep Power 0 Ive tried both of them, as well as C:Program Files (x86) 28th August 2014, 11:17 AM 7 Sh500 Join Date Aug 2014 Posts 11 Thank Post 2 Thanked 0 Times in 0 Posts Rep Power 0 I am guessing I am missing out something fundamental in deploying a batch script via SCCM in general. Like I say, the uninstall.cmd script that I have works fine when executed manually on the client PC. Originally Posted by macshinobi would it make any difference if it is a.bat instead of a.cmd Extremely unlikely. Originally Posted by Sh500 I thought Id try to uninstall the software, via the following.cmd script: Code: C:Program Files (x86)PDFCreatorunins000.exe verysilent SUPPRESSMSGBOXES NORESTART If your batch file consists of just that command, you would be better off avoiding using batch files altogether and put the entire command in the Uninstall program box (similar to what is shown below). You can make sccm ignore behaviour based on exit code in the deployment type. August 2014, 06:13 AM 12 Arthur Join Date Feb 2007 Location 52.989247,-1.888549 Posts 20,497 Thank Post 936 Thanked 8,059 Times in 5,411 Posts Rep Power 2349 Originally Posted by Sh500 Entering the command directly does seem to remove the software - but the client has a Removal Failed as the status: Error 0x87D00325 seems to be caused by the PDF Creator uninstaller (unins000.exe) launching another executable ( TEMPiu14D2N.tmp ) and then quiting. The second process is then used to remove everything in the ProgramFiles(x86)PDFCreator folder (including unins000.exe). Originally Posted by InnoSetup Because Windows doesnt allow programs to delete their own EXEs, the uninstaller creates and spawns a copy of itself in the TEMP directory. This clone performs the actual uninstallation, and at the end, terminates the original uninstaller EXE (at which point you get an exit code back), deletes it, then displays the uninstall complete message box (if it hasnt been suppressed with SILENT or VERYSILENT). SCCM thinks the uninstaller has completely finished when in fact it hasnt. The easiest solution is probably what free780 suggested. August 2014, 06:27 AM 13 free780 Join Date Sep 2012 Location Leeds,UK Posts 2,983 Thank Post 262 Thanked 463 Times in 374 Posts Rep Power 194 Either that or it needs sp- SUPPRESSMSGBOXES as well. Also it may be the detection rule you have in place for the application. HKEYLOCALMACHINEsoftwaremicrosoftwindowspiec eofsoftware This entry should be deleted when the application is. August 2014, 02:25 PM 14 Sh500 Join Date Aug 2014 Posts 11 Thank Post 2 Thanked 0 Times in 0 Posts Rep Power 0 Originally Posted by free780 Its probably the error code at the end of the uninstall. I have just tried adding the extra suppress code and changing the detection rule to a reg value. On general note: Why is it that my.cmd script did not work and entering the code directly does Is it something to with the script trying to run from a UNC path I ask because, I tested a simple batch file that maps a network drive and that script also did not actually execute.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |