mst not working through GPO?????
Hey, i have made a mst for acrobat reader 7, however the changes arent being made...
If i install using command line it works fine (msiexec - i.... etc.....) , however through Group Policies it doesnt,
I think it is sort of applying, by this i mean the settings i change in HKLM it applies, such as remove the advertising, BUT the HKCU are not, that is remove the yahoo bit.
has anyone got any ideas to this? i am using installshield.
thanks
If i install using command line it works fine (msiexec - i.... etc.....) , however through Group Policies it doesnt,
I think it is sort of applying, by this i mean the settings i change in HKLM it applies, such as remove the advertising, BUT the HKCU are not, that is remove the yahoo bit.
has anyone got any ideas to this? i am using installshield.
thanks
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
WiseUser
19 years ago
What I'm about to say may be obvious, but it's the only thing that springs to mind.
The HKCU keys can only be written when the user is logged on.
When you run the install from the command line you are logged on?
When it runs using group policy, the user might not be logged on?
The HKCU keys should be written when the user first invokes an advertised entry point (shortcut, association, etc) assuming you have one in your install.
If these registry keys aren't being written when the user runs the shortcut, one of the following might be the problem.
1) Shortcut is not an advertised shortcut
2) The components containing the HKCU keys is not part of the feature that is being used (or a parent feature).
3) The components containing the HKCU keys may have invalid keypaths (possibly non-registry), or keypaths that already exist.
The HKCU keys can only be written when the user is logged on.
When you run the install from the command line you are logged on?
When it runs using group policy, the user might not be logged on?
The HKCU keys should be written when the user first invokes an advertised entry point (shortcut, association, etc) assuming you have one in your install.
If these registry keys aren't being written when the user runs the shortcut, one of the following might be the problem.
1) Shortcut is not an advertised shortcut
2) The components containing the HKCU keys is not part of the feature that is being used (or a parent feature).
3) The components containing the HKCU keys may have invalid keypaths (possibly non-registry), or keypaths that already exist.
Posted by:
antun
19 years ago
Posted by:
$piKeIT
19 years ago
I had the same problem when deploying 6.0 via GPO. Eventually I had to move it to a user based install.
I've since found a handy little reg key that will execute and repair your installer whenever a new user logs on. I haven't tried it in a GPO senario but it definately works when installing Reader 7.0 by using msiexec /i
Add the following string values (assuming this is your product code):
HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{AC76BA86-7AD7-1033-7B44-A70000000000}\StubPath Value=msiexec /fup
HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{AC76BA86-7AD7-1033-7B44-A70000000000}\Version Value=7.0
I've since found a handy little reg key that will execute and repair your installer whenever a new user logs on. I haven't tried it in a GPO senario but it definately works when installing Reader 7.0 by using msiexec /i
Add the following string values (assuming this is your product code):
HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{AC76BA86-7AD7-1033-7B44-A70000000000}\StubPath Value=msiexec /fup
HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{AC76BA86-7AD7-1033-7B44-A70000000000}\Version Value=7.0
Posted by:
antun
19 years ago
Ok i tried the reg keys and it doesnt seem to work.....
HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{AC76BA86-7AD7-1033-7B44-A70000000000}\StubPath
value=msiexec /fup {AC76BA86-7AD7-1033-7B44-A70000000000}
HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{AC76BA86-7AD7-1033-7B44-A70000000000}\Version
Value=7.0
it doesnt work, however if i type msiexec /fup {AC76BA86-7AD7-1033-7B44-A70000000000} in start >>run it works
so it stil not geting executed for some reason, any ideas?
HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{AC76BA86-7AD7-1033-7B44-A70000000000}\StubPath
value=msiexec /fup {AC76BA86-7AD7-1033-7B44-A70000000000}
HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{AC76BA86-7AD7-1033-7B44-A70000000000}\Version
Value=7.0
it doesnt work, however if i type msiexec /fup {AC76BA86-7AD7-1033-7B44-A70000000000} in start >>run it works
so it stil not geting executed for some reason, any ideas?
Posted by:
cdupuis
19 years ago
Posted by:
antun
19 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.