UCI Housing Network and Cable TV Issues

Here is yet another instance where the CCA client agent doesn't quite work:
A lot of people and organizations who want to avoid having to apply Windows Service Packs or hotfixes manually to new Windows installations turn to slipstreaming Windows. This is a Microsoft-supported way to integrate service packs and other fixes into the core OS on a CD. For a description, see, e.g., Paul Thurrott's page about Slipstreaming.
To quote:

For end users, slipstreaming can also be useful. For example, you can copy the installation directory from your XP CD-ROM to the hard drive, slipstream the XP SP2 files into that installation directory, and [sic]than write it back to a recordable CD, giving you a bootable copy of the XP setup disk that includes SP2 right out of the box (so to speak). That's the process we're going to examine here. And slipstreaming isn't limited to service packs, either: You can also slipstream in various product updates, including hot-fixes.

I have used this method since XP SP1 to create Windows installation CDs that contain SP1 and SP2 already.
The problem the CCA client has with this method is that it doesn't detect that the service packs and hotfixes are already installed. It checks the registry, and slipstreaming obviously can't create registry entries indicating that SP2 and hotfixes are installed, and requires the user to download and install all this again.
So, once again, we have a broken product (CCA) that foils doing the good thing (slipstreaming Windows with service packs and hotfixes already applied.)
Yet another reason why CCA should be abolished.