I found some systems where WMI was broken and needed a way to test if this was the case. Unfortunately the WMIC command doesn't set errorlevel, so it got a bit tricky.
We had issues with the SCCM client causing Windows Updates to fail, so rather than push a solution through SCCM, I pushed it through PSEXEC. Here's the batch file solution.
This utility application to provides a friendly way to manage rebooting a user's machine. It supports delays and hides while waiting for the delay to end.
Just like it sounds. Remove FileZilla in AutoIT
just like it sounds. Install FileZilla in AutoIT
This batch file looks for key Office 2010 components, and if it finds them it aborts. It writes activity to a time-stamped log - see below for example. If it decides to remove Office 2010, it write a CONFIG.XML file first, then calls the Setup /uninstall routine and then finally checks for success by looking for a .LNK file as a marker.