Software Deployment

Ok Ninjas,I've been fighting a problem for several days, now and for the life of me I cannot find a solution. I'm hoping someone has come across this...We have a PACS software that we install on Radiology PCs. This software includes a "fat" client, as well as ActiveX controls for using a web-based client. The "fat" client is working fine. However, the ActiveX control will not load. The web interface just prompts us to download and install the software again. This is an EXE installer, not a standard ActiveX install prompt. This is on Windows 7 SP1 with IE9. It happens on both 32-bit and 64-bit.A little bit of background - We had previously been using a master image built on the Dell OEM install DVD. On that image, this software works perfectly. However, we just recently had to change over to an image built from Volume License install DVD. It's only on PCs built from this new image that have the problem. I prepared the images the exact same way, but I think I must have missed something.I have done all the usual ActiveX troubleshooting - site is in Trusted Sites zone, all the security for that zone is set to low - signed and unsigned ActiveX controls are pretty much all allowed. Scripting of controls is allowed, etc. The ActiveX is 32-bit only, so I've also made sure we're loading the site in the 32-bit browser.Here's where it gets strange, though... If I load up my pre-sysprep'd version of this image and install the software, the ActiveX controls work fine, even using the default settings for Security zones. Of course, with default settings, I get prompted to allow the control to run. I thought maybe something was getting changed by the sysprep process, so I again reverted back to the pre-sysprep snapshot (I used a VM to build it), sysprep'd it, then rebooted and allowed it to go through the process of booting. Once done, I again installed the software, and again it worked fine.The problem only seems to occur once I've captured and re-imaged from the K2000. Even just a basic deployment with only the minimal tasks of creating partitions.One clue as to what might be the cause on the deployed image is, after installing the software, the Allow prompt now shows it as "Control name is unavailable" from "Unavailable" insted of the actual control name and publisher name. The previous image, as well as my pre-sysprep'd new image show the control name and publisher just fine.EDIT: Thanks to PressAnyKey for suggesting running regsvr32 on the ocx file. As usual I was just overthinking the problem. However, from that comes a new question... why can't the installer register the OCX on it's own, as it clearly was able to do on my previous image, and also the pre-deployed version of my new image?