We had no luck with SP2 and IE6 until we ran it on the workstation container GPO.  Double-check the permissions of those workstations (or just DOMAIN COMPUTERS or whatever it's called) into the directories you're storing the files in.  Our IE6/SP2 only rebooted once.  (The other funny thing was that it applied them in the order it wanted, didn't matter which we told to go first)  We told everyone to restart their computers at night when they left, warning them that the update would take some time on next reboot.  Had one user that didn't listen and shut his machine off during the update.  I imagine you could also do it with a logoff script, but we didn't look into that.

For the security updates, use HFNETCHK and QCHAIN.EXE.  There's also a sweet HTML interface for HFNETCHK at http://www.maximized.com/freeware/hotfixreporter/
 
 
 
 
-----Original Message-----
From: Blair, James [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 11, 2001 06: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

Reply via email to