Software Deployment

Hi everyone,

I am trying to repackage the UltraVNC Mirror Driver 1.00.22 with Wise Package Studio 7.0 SP3. I am following the guidance from these URLs:

• http://www.symantec.com/connect/articles/how-package-signed-device-driver-using-wise-package-studio
• http://itninja.com/question/how-do-you-roll-out-new-machines?0873

However, I'm confused if the driver is signed or unsigned. I downloaded the drivers from http://sc.uvnc.com/drivers.zip. Inside the 'xp\driver' folder path (XP is the target platform I'm repackaging for), there are 4 files:

• mv2.cat
• mv2.dll
• mv2.inf
• mv2.sys

Since a .cat file is already present with a digital signature embedded from GlobalSign, I would have thought this means the driver is signed:





However, if I try to install the driver manually using devcon.exe for testing:
[blockquote][font="courier new"]devcon.exe install mv2.inf mv_hook_display_driver2
[/blockquote]... I get this warning message, which suggests that the driver is unsigned:



Can anyone explain what is happening here? Is it because it's not signed by Microsoft themselves (i.e., when I inspect .cat files on my own computer, they all seemed to be signed by Microsoft Windows Hardware Compatibility Publisher)? If so:

• Does this mean that the vendor provided .cat file is essentially useless?
• How does creating and self signing your own your own .cat file (as suggested in http://itninja.com/question/how-do-you-roll-out-new-machines?0873) get around this?

Thanks in advance.

Asked 14 years ago 5008 views