Software Deployment

ORIGINAL: jimmyx
This is only happening when I use the /qb switch. Working fine as a standard install.


Then that suggests that there are actions in the InstallUISequence that are not present in the InstallExecute sequence or that certain actions have conditions on them based on UILevel.

Regards,

Spartacus

Could you give us some examples of such registry entries?

Thanks for the replies guys

Spartacus: Can't spot anything missing in the Install Execute sequence or any conditons that might be upsetting things

AngelID: Here are the values I am have difficulties with

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_MCHINJDRV]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_MCHINJDRV\0000]
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"ConfigFlags"=dword:00000000
"DeviceDesc"="mchInjDrv"
"Legacy"=dword:00000001
"Service"="mchInjDrv"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_MCHINJDRV\0000\Control]
"*NewlyCreated*"=dword:00000000
"ActiveService"="mchInjDrv"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_PHAROS_SYSTEMS_COMTASKMASTER]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_PHAROS_SYSTEMS_COMTASKMASTER\0000]
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"ConfigFlags"=dword:00000000
"DeviceDesc"="Pharos Systems ComTaskMaster"
"Legacy"=dword:00000001
"Service"="Pharos Systems ComTaskMaster"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_PHAROS_SYSTEMS_COMTASKMASTER\0000\Control]
"*NewlyCreated*"=dword:00000000
"ActiveService"="Pharos Systems ComTaskMaster"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_MCHINJDRV]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_MCHINJDRV\0000]
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"ConfigFlags"=dword:00000000
"DeviceDesc"="mchInjDrv"
"Legacy"=dword:00000001
"Service"="mchInjDrv"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_MCHINJDRV\0000\Control]
"*NewlyCreated*"=dword:00000000
"ActiveService"="mchInjDrv"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_PHAROS_SYSTEMS_COMTASKMASTER]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_PHAROS_SYSTEMS_COMTASKMASTER\0000]
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"ConfigFlags"=dword:00000000
"DeviceDesc"="Pharos Systems ComTaskMaster"
"Legacy"=dword:00000001
"Service"="Pharos Systems ComTaskMaster"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_PHAROS_SYSTEMS_COMTASKMASTER\0000\Control]
"*NewlyCreated*"=dword:00000000
"ActiveService"="Pharos Systems ComTaskMaster"

As Kim probably suspected, you're trying to write to registry entries which you really ought not to.

There's a good article here http://blogs.msdn.com/astebner/archive/2004/10/13/242122.aspx about what the CurrentControlSet etc. registry keys are about.

Anyway, as this is a driver install, you will save yourself HOURS of grief by using one of the driver installation methods, probably DifX.http://www.microsoft.com/whdc/driver/install/difxtools.mspx

Include entries related to your application under HKLM\SYSTEM\CurrentControlSet and not under ControlSet001 or ControlSet002.

VBScab: Thanks for that info, the applictaion is not a pure driver install. A bit of background: the printing server creates it own set of .exe's, which do not support a silent uninstall switch so hence the need for an MSI for AD!

Strange thing is the same keys are used on our re-packaged previous version and that works fine on a silent install.

Looking a bit deeper at the /System/CurrentControlSet/Enum keys it looks as though only the SYSTEM account has full control.
Excuse my ignorance (I'm on a bit of a learninng curve here!) but i'm guessing that when you use the /qb switch it will use the admin account, and the SYSTEM account is used with no swtiches?
If that is the case is there somewhere I can change to make sure the SYSTEM account is always used when installed

AnegelD: Thaks for that, and yes I am now only using CurrentControlSet entries.
Thanks again for any help

ORIGINAL: jimmyx
Excuse my ignorance (I'm on a bit of a learninng curve here!) but i'm guessing that when you use the /qb switch it will use the admin account, and the SYSTEM account is used with no swtiches?No, the /Q argument controls the UI presentation i.e. whether you get one or not and, if so, what level that UI is.

To ensure that the System account is used depends on how the package is deployed and/or under which context any Custom Actions in the package are set to run. CA context is something that can only be set in the Execute Deferred sequence.

Thanks as always for your prompt response Ian.

Does a machine install via GP use the system account per chance?

Yup, it sure does...