nhughes122
Member
- Messages
- 5
- Reaction score
- 1
- Points
- 3
Good morning! Shockwave has reached end of life and I'm trying to work on getting it uninstalled across our business.
My batch file works, when run as admin on a test computer to uninstall Shockwave, but when I created an application in SCCM and deployed it to my computers, it doesn't look like the file is getting ran. If it is, it looks like it is being ran without administrative privileges.
The batch file is simple:
wmic product where "name like '%%Shockwave%%'" call uninstall /nointeractive
pause
My questions:
My batch file works, when run as admin on a test computer to uninstall Shockwave, but when I created an application in SCCM and deployed it to my computers, it doesn't look like the file is getting ran. If it is, it looks like it is being ran without administrative privileges.
The batch file is simple:
wmic product where "name like '%%Shockwave%%'" call uninstall /nointeractive
pause
My questions:
- When I have a batch and I build it into an applications, in this case the application is "Adobe Shockwave Uninstaller", does it get installed and ran with admin privileges or is it being ran as the user?
- Can I specify the rights it runs under or do I need to do that in the script?
- Is building a application for the batch the best way to handle scripts with SCCM or is there a general "best practice" for batch files and such?
- Does anyone have a different suggestion on how to remove Shockwave from the environment that isn't this uninstall process?
