Thanks All - I ended up using a Task Sequence and it appears to be working fine. -
From: [email protected] [mailto:[email protected]] On Behalf Of Marcum, John Sent: Wednesday, October 07, 2015 2:17 PM To: [email protected] Subject: [mssms] RE: Custom Package Install Via SCCM With CM07 I'd use a task sequence for this. ________________________________ John Marcum MCITP, MCTS, MCSA Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ [H_Logo] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Enley, Carl Sent: Wednesday, October 7, 2015 11:56 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Custom Package Install Via SCCM Hi I am hoping that some folks on this board may be able to help me out or offer some suggestions with a task that I have been assigned. I need to upgrade about 3500 computers with a new Websense Endpoint Client using SCCM 2007. The machines are a mix of desktops and laptops and the users do not have Admin permissions on the machines. We generally try to take care of most of our installs under the radar without the end user being nagged or prompted but I have run into some challenges with this install as I will outline below: Challenges: Old client requires a reboot - this means we have to notify our users of this before it happens and allow time for them to save documents etc... 50% of our machines are Laptops and may be traveling or at home during the evening hours and only available during normal business hours Desktops can install during Maintenance Windows but I am unsure how to setup the package so that after the reboot another install takes place immediately following Requirements: Remove old end point client Reboot Computer Install new end point client Minimize the amount of time that a machine is unprotected between the reboot and the install of the new client If anyone has any thoughts or suggestions I would love to hear them, I have been concentrating on making the uninstall / install not require a reboot but I have failed. I tried editing the .msi with Orca to remove the pending reboot check, deleting the registry key for pending file renames etc.....I have come to the conclusion that I need to reboot the systems and I need a way to warn the users, reboot and then run the installer all under the system context. Thanks ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
