RE: [ActiveDir] Software Deployment:

[Bjelke John A Contr AFRL/VSIO]

James,             unfortunately, the bulk of our experince has been in using SMS to push patches and updates. I really don't think building a new .msi file is the way you want to go. Slip-streaming the patches into the original installs has worked very well for us, and has allowed us to keep an updated version of office 2K, for example, up on a network share. Installing from this directory has eliminated the need for users to keep putting their cd's into the drive every time we patched office for the latest vulnerability, wich was a real pain in the gluteus. Slip-streaming is discussed in depth at http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q271791 , and I imagine one could use RIS to deploy it from a 2K server. You should also be able to set up a policy to force the local machines to run the windows critical updates on a schedule. As for the restart issues, I would send out notice to all the department heads saying "This installation is mandatory. Non-compliance will be reported to upper management" or some such garbage, and instruct them to leave all systems turned on and connected at a specific time. Depending on how you push the updates, you should be able to force a reboot at that time. You should also be able to give users a warning dialogue box telling them to save all work with a count down to reboot. If anything is incorrect here, please feel free to shoot me down! Hope this helps. -John   -----Original Message----- From: Blair, James [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 11, 2001 5:13 AM To: 'ActiveDir ([EMAIL PROTECTED])' Subject: [ActiveDir] Software Deployment: All,   I am looking at rolling out security updates and patches etc. for Windows 2000, Office 2000 etc. I was hoping to utilise Intellimirror to do this but for the life of me can't figure out how to do it correctly. I initially tried an IE 6 rollout to a testbed using WInInstaller LE to create the *.msi file, after failing I then tried out SP2 for the OS, also with no luck. Please could someone out there advise on the best way to do this as third party products seem to be the go but are generally not cheap. Microsoft says that it is trying to lower the total cost of ownership but having to keep investing in third party products is proving quite costly. Also, with the security updates etc. how the hell do you get *.msi's, *.mst's or *.msp's of these the only way to get these seems to be through using the Critical Update Notification...we cannot expect users to do this themselves...One last issue...is there any way to cut down on the shut down and restarts if I roll out IE 6 it will take a reboot also SP2 for W2k requires a reboot, then SR1a for office will as well most likely so will SP2 for Office. It would take at least a week of logins...and if someone is not in on the deployment day!!!!   I know this is probably basic but if anyone can shed light on this please advise, I do not at this stage wish t use SMS 2.0.   James