Question : Problem: wsusscn2.cab - How does it get out to clients?

I understand the Microsoft Updates Sync tool checks MS's site and downloads the wsusscn2.cab file.  Can someone tell me or explain the process for how the wssusscn2.cab file ends up under c:\windows\system32\vpcache\PackageID on the clients.  It's not getting updated on several of our servers and I'm trying to figure out which process/package/advertisement/log files to check.

Thanks,
Joe

Answer : Problem: wsusscn2.cab - How does it get out to clients?

thank's for the info.  I ended up figuring this out on my own a few days later.  In case anyone else every comes up with this question - For SMS 2003, it is scanwrapper.exe via the Microsoft Updates Tool program that puts the files into place.  In my particular instance, the program was not authorized to run on R2 servers and all the servers not being updated were R2.  Allowing the Program to run on R2 servers fixed the problem.

Mods - you can close this out.  

Thanks,
Joe