SCCM 2007 stumped on proper method
I have been researching a deployment for work, and have been tasked to install IE9 to some client machines. I am stumped on the best method to accomplish what i want. Currently our existing SCCM administrator is using task sequences from OSD menu to deploy software. I believe he is doing this because the task sequences allow us to add exceptions and commands to the package. what i am trying to accomplish is the update IE8 to IE9 but before that package runs, i want to kill any running iexplore.exe processes that are running. So far i have not found a method other than task sequence deployment. I have googled all variations of this, but have come up with little. what would be the proper/best method to do this task.
Answers (3)
You don't *have* to use TSes for this. It's perfectly feasible to create a command file or script to perform the steps required and then use that to deploy via SCCM.
You need to be very careful using TSes to deploy MSI-based installations, as the default behaviour is to copy the files required to a folder in a temporary location on the local hard drive, install from there and then delete the folder. The problem rears its head if the package needs to repair the application, because the MSI's source will have been removed.
I agree with VBScab.. Also, if you want to keep your users from being mad at ya, then do a check for if "iexplore.exe" is (inUse, or Running) to notify the user. If they click OK it will close IE so it can upgrade to a newer version. One place I worked at even had a timer you could set, so they had a 5 min countdown till it would proceed with the install reguardless of their involvement. The last one we Created in AutoIT, normally I use WiseScript thou.
That way you can be sure that IE won't be open.
If you've got WOL configured you could even power them on overnight and run the upgrade. - dunnpy 10 years ago