taartero
asked on
Create SCCM package that can remain in control of the PC through several reboots
I am planning on running an uninstall utility to remove an AntiVirus/Firewall suite. This utility will force the PC to reboot. but I want SCCM to remain in control of the PC to install the newer suite. Then I want SCCM to reboot after the new install.
So there will be a total of 3 reboots.
1) I want the system to reboot before the uninstall utility (to ensure all applications are closed.
2) the uninstall utility will case another reboot (is a bat file)
3) the install of the new suite does not require the reboot (but I want it to reboot once more)
I can manuever through SCCM but am not the SME. I know I need a collection/package/adverti
actually accomplishing each of those steps would be helpful.
So there will be a total of 3 reboots.
1) I want the system to reboot before the uninstall utility (to ensure all applications are closed.
2) the uninstall utility will case another reboot (is a bat file)
3) the install of the new suite does not require the reboot (but I want it to reboot once more)
I can manuever through SCCM but am not the SME. I know I need a collection/package/adverti
actually accomplishing each of those steps would be helpful.
ASKER
so the question I have about your pre-req package is. the uninstall for SAV would require a reboot. How am I going to be sure that the user isn't able to log on after that reboot when the (in your example, NOD32) has not been installed yet.
I want to be sure that after the reboot from the uninstall, that the user will not be able to interact with the system until the replacement app is installed and the system rebooted after the new install.
I want to be sure that after the reboot from the uninstall, that the user will not be able to interact with the system until the replacement app is installed and the system rebooted after the new install.
Actually, we suppressed the reboot for Symantec with the "ReallySupress" option and chained NOD32 right after wards, again surpressing the reboot. NOD32 wasn't fully installed until a reboot. I was able to live with that.
Back to your last question....it's just something SCCM is not able to do, because it is based on pull (not push) technology. You are at the mercy of the CCM client and when it checks in with the server to finish the install. You can leverage Group Policy to "install on login" and the PC will sit at the login screen installing the software before letting the user login. However, the only way to ensure the users wouldn't "get in the way" is to leverage the Wake-on-LAN and maintainence window features in SCCM to schedule the update during non-business hours.
You probably wouldn't want computers rebooting multiple times in the middle of the day anyways....at least I wouldn't! :)
Back to your last question....it's just something SCCM is not able to do, because it is based on pull (not push) technology. You are at the mercy of the CCM client and when it checks in with the server to finish the install. You can leverage Group Policy to "install on login" and the PC will sit at the login screen installing the software before letting the user login. However, the only way to ensure the users wouldn't "get in the way" is to leverage the Wake-on-LAN and maintainence window features in SCCM to schedule the update during non-business hours.
You probably wouldn't want computers rebooting multiple times in the middle of the day anyways....at least I wouldn't! :)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
In each program, you can say Run Program X first and within Program X, you can run Program W first and so on. I did something something similar for the removal of Symantec Antivirus and the install of NOD32. I just make an install package for NOD32 and in the pre-req package, I called another program that fired msiexec to uninstall Symantec.
If the uninstall package failed, the 2nd program wouldn't run.