I've created a some exe's that I'm distributing via Active Setup. They aren't MSI related, just Wise executables that I've created for distribution.

The registry key values I am assigning aren't GUIDs and aren't enclosed by any sort of brackets like some others (Microsoft stuff). The keys are named with alphanumeric characters that I've chosen to help me easily distinguish them from others. If I place more than one of these into the registry, only one runs during the first login after the key is added. The exe runs just as it was designed to but that's it - only one runs. None of the Active Setup keys were present before so there is no chance the current user had already gotten them run.

For example, if I used the following:

HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\ABC-Install
StubPath=C:\Software\Stage\ABCINST\ABCINST.EXE
Version=1

HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\ACME-Install
StubPath=C:\Software\Stage\ACMEINST\ACMEINST.EXE
Version=1

only the first one (alphabetically) runs during the first login after the keys were added. The second item will run but not until the second login.

Because the changes these exe's make require a restart (but not until they're all loaded), I need to be able to have multiple items run via separate Active Setup keys and then force one reboot after all are done.

Does anyone have a clue about what would make the login ignore everything I've placed in Active Setup except the first item?

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
ORIGINAL: sglimke
The registry key values I am assigning aren't GUIDs and aren't enclosed by any sort of brackets like some others (Microsoft stuff). The keys are named with alphanumeric characters that I've chosen to help me easily distinguish them from others.
I can understand your motivation for not using GUIDs but it doesn't seem to work so, if it were me, I'd generate a couple of GUIDs and use them in a test. Here's a QAD script to generate a GUID and copy it to the clipboard.

Set TypeLib = CreateObject("Scriptlet.TypeLib")
strGUID = TypeLib.Guid

Set objIE = CreateObject("InternetExplorer.Application")
With objIE
.Navigate("about:blank")
.document.parentwindow.clipboardData.SetData "text", strGUID
.Quit
End With

Set TypeLib = Nothing
Set objIE = Nothing
Answered 02/27/2008 by: VBScab
Red Belt

Please log in to comment
0
Thanks for the suggestion and the script to create GUIDs. That seemed to be the issue. Do you know if there's some documentation on what all the Active Setup values mean? Specifically, DontAsk and IsInstalled are confusing. Default, ComponentId, Locale, StubPath and Version are fairly straightforward. I've not been able to find a comprehensive description of the others (and if there are other values I'm not aware of).

The script you provided works very well. I'm wondering if there's a way to suppress the "Allow Access" or "Don't Allow" buttons that appear asking about copying to the clipboard. It would be beneficial to be able to use this script within others to auto-generate a GUID for use elsewhere.

Thanks again!!
Answered 02/28/2008 by: sglimke
Yellow Belt

Please log in to comment
0
The answers to both questions revolve around IE. I was punting around the other day looking for a means to log Active Setup activity and came across a bunch of stuff. It would seem AS arose out of the IE v4 project. Enter:

"Active Setup" +log

into Google and have a wander around the MS page hits.

As for the warnings, they're to do with IE "security". Enter:

"internet explorer" +clipboard +"allow access"

into Google and you get a bunch of hits, except teh one that matters, http://msdn2.microsoft.com/en-us/library/bb250473(VS.85).aspx

Make the change shown to the 'Trusted Sites' zone.
Answered 02/28/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity