Software Deployment

Does the HP setup executable allow you to pass parameters to it? If so, have it create a verbose log of its install. Then do the same for your MSI and then compare the 2 logs. Make sure you do this using the same image or VM.

Failing that, you could run your MSI, then take a 'Before' snapshot using a lightweight snapshot tool like Ziff-Davis's In Control. Next, run HP's installer, then take an 'After' snapshot. That will highlight any differences.

The second step is one I *always* take with my MSIs anyway, just to ensure it reproduces exactly what the vendor's install does, within the boundaries of my client's standards, of course.

The exe does not allow me the parameters.One thing I have come to know there are 3 kernel services and 4 signed devices.The 3 kernel services are (1) HPZipr12 image path is( [SystemFolder]DRIVERS\HPZipr12.sys)
(2)HPZius12 image path is ( [SystemFolder]DRIVERS\HPZius12.sys) (3)HPZid412 image path is ( [SystemFolder]DRIVERS\HPZid412.sys).These are not at all running but when the source is installed these services are running. The 4 signed devices are HP LaseJet M9040MFP [DOT4], HP LaserJet M9040 MFP [DOT4PRT], HP LaserJet M9040 MFP [DOT 4USB] and HP LaserJet M9040 MFP [DOT 4USB] PCL6 for which the inf files are oem38, oem40, oem42 and oem43 respectively.These signed devices are not visible when the msi is installed but visible when source is installed. The oem files as well as the corresponding sys files are present in the msi.If these are working fine then the msi is working fine.Could you please help me out.

How are you installing these services? With 'Rundll32 printui.dll (etc, etc)' or with DifXApp?

Have you seen http://juice.altiris.com/article/1079/how-to-package-a-signed-device-driver-using-wise-studio?

I am installing the services through the registries.Not through Run Dll32 or any thing.The corresponding registries are already present in the msi.The system services which are present are running after a reboot but not the kernel services.

Sorry, it's my fault for not editing my post properly. I meant to ask how the printer driver was being installed. You have, however, answered the question. Clearly, you have captured the installation into your own MSI. This is to be avoided, as it leads to precisely the problems you are experiencing.

Use either RunDLL32 or the DifXApp methods.

Hi,
I could able to get the kernal drivers run, but the signed drivers are not getting signed. When i check the properties of the drivers I am seeing " Driver Signer --Not digitally signed.Could you please let us know how to get these digitally signed.

ORIGINAL: VinayVS
I could able to get the kernal drivers run, but the signed drivers are not getting signed. When i check the properties of the drivers I am seeing " Driver Signer --Not digitally signed.Could you please let us know how to get these digitally signed.
Why not send me the package as you have it now and I'll complete it for you?

Come on, my friend! Do at least SOME of the work: use Google.

To get the signed drivers we have not used Rundll32 printui.dll (etc, etc)' or with DifXApp.It is done all by ourselves not using what u have provided.You could have just told its not possible from my side.Google its a prime duty of any packager who wants troubleshooting in any of his application.Any way thanks for asking the package for you to complete.

ORIGINAL: VinayVS
Any way thanks for asking the package for you to complete.Vinay, you should probably learn to recognise sarcasm when you see it. :)