Wondering if anyone has come across the following issue:
When packaging Autodesk Design Review Active Setup fails to run the hkcu.reg
This file is placed in eg. C:\Program Files\Autodesk and it doesn't run via active setup?
If i create a folder on C:\Autodesk it works fine.
Any other location Active setup fails to run the hkcu.reg
I have tried all sorts of permissions to no avail......
Any ideas?

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{450063AA-643B-417C-8CF5-405BA3F4EF40}]
"Version"="1,0,0,0"
@="Autodesk Design Review"
"StubPath"="regedit /s C:\\Program Files\\Autodesk\\Design Review\\HKCU.reg"

REGEDIT4
[HKEY_CURRENT_USER\Software\Autodesk\Design Review\Preferences\User Interface]
"Default File Type"=dword:00000001
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
Try this instead:
"StubPath"="regedit /s \"C:\\Program Files\\Autodesk\\Design Review\\HKCU.reg\""
Answered 05/12/2008 by: AngelD
Red Belt

Please log in to comment
0
seems a little odd to use this to add registry.

why not at the HKCU to the package and use self healing to deploy it.

regedit could be disabled by policy regardsless if the user has access to the registry location
Answered 05/13/2008 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
I was always had the understanding that HKCU repair was a last resort and not common practice.
The user experience should be "quiet" with no repairs?
I'm not quite sure what best practice should be?
On this occasion the appropriate answer seems to be HKCU repair.

re: AngelD StubPath didn't work either.
Answered 05/13/2008 by: Conapps
Senior Yellow Belt

Please log in to comment
0
I was always had the understanding that HKCU repair was a last resort and not common practice.
Who told you that?

The user experience should be "quiet" with no repairs?
As quiet as possible with repairs.
You need to make sure the repair doesn't take longer then necessary.
John (jmcfadyen) has posted a nice article regarding CurrentUser feature and its position so search for that, HINT: top-feature.
Answered 05/13/2008 by: AngelD
Red Belt

Please log in to comment
0
The only time you wouldn't want a repair is if your installing on a citrix server. Then it pays to use active setup (only if your publishing a full desktop)
Answered 05/14/2008 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
You correct timmsie as a user is not allowed to trigger a repair. In that case you need to make sure every HKCU registry is written by the shadow registry. Files located in the userprofile should be handled by Active Setup that do NOT use the windows installer to write the files but instead an EXE, VBSCRIPT or similar.
Answered 05/14/2008 by: AngelD
Red Belt

Please log in to comment
0
Exactly, although Active setup is not run if you only publish an application and not a full desktop.
Answered 05/14/2008 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0

The articles on HKCU confirm what other packagers have said to do, as apposed to what is taught by Altiris Wise in Australia.
I will follow the use of msi HKCU self repair under a CurrentUser feature to ensure a quick repair for the end user.

Thanks to all for the info
Answered 05/14/2008 by: Conapps
Senior Yellow Belt

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