XP Patch via Alteris software...

[ddeleaumont]

Hey all,

I mistakenly posted this in the Win 2K Pro forum so please forgive me for the duplicate post.

We have a computer lab with about 20 XP stations in it. We pushed the MS Patch last month to these machines via the Alteris software. For some reason, only HALF of the machines showed having the patch dated 7/5/03 and the other half actually got hit with the Welchia Worm. There was never any indication that only half of the machines took that patch.

My question is: Is there a reason that only half the machines took hte patch and is Alteris just not a good way to install MS Patches and Service Packs? If not, what does everyone else use?

Thanks,
Don
PC Technician

"If you want to make a difference, you have to be different. That's the deal."
-Kevn Kinney

 

[bcastner]

As a guess it is not the Alteris push that failed, but other issues.

1. Permission issues. Only administrator users would be able to apply the Hotfix if it came from outside the Windows Update Service running on the workstation. The advantage of the service is that it runs with elevated priviliges.

It might be better to package the pushed Hotfix(es) in this form for deployment:

. Use the Dynamic Update deployment tool (new):

http://support.microsoft.com/default.aspx?scid=kb;EN-US;312110

. See these instructions for creating the Hotfix package:

http://support.microsoft.com/default.aspx?scid=kb;en-us;296861&FR=1&PA=1&SD=HSCH

2. The workstations may be missing antecedent Hotixes. I do not recall this being an issue with the msblast/RPC Hotfix, but it is an issue with many. Run Qfecheck on a test troubled workstation:

http://support.microsoft.com/?kbid=282784

3. Look in the logs in c:\windows. For example, if the dahotfix.log shows MDAC versioning errors, you might apply the MDAC 2.7 RTM download from Microsoft.

4. Search here for the many links detailing Windows Update problems. Generally you should at least rename c:\windows\system32\catroo2 to something else, and clear any existing c:\WUTemp directories. The Microsoft Troubleshooter should be examined for additional hints, such as re-registering some .dlls:

http://v4.windowsupdate.microsoft.com/troubleshoot/

5. You might consider using the (free) SUS server from Microsoft for this particular chore.


4.