repair only works for non-admin users...
I know I've stumbled across links in the past describing fixes for this issue but now that I'm actually dealing with it myself I cannot seem to find them...
I'm attempting to package BeyondCompare 3. The install includes some HKCU keys and 3 files that need to exist in each user's profile. All files and regkeys are created for the installer and self-repair works fine for basic user accounts. But for admins (local or domain) self-repair only creates the regkeys; the user profile files are not created.
I know this has something to do with the fact that admins have access to all files on the system and therefore the self-repair sees that the files exist (albeit in the wrong profile!!!) and do not recreate them but I do not know how to overcome this issue.
Any help would be greatly appreciated.
I'm attempting to package BeyondCompare 3. The install includes some HKCU keys and 3 files that need to exist in each user's profile. All files and regkeys are created for the installer and self-repair works fine for basic user accounts. But for admins (local or domain) self-repair only creates the regkeys; the user profile files are not created.
I know this has something to do with the fact that admins have access to all files on the system and therefore the self-repair sees that the files exist (albeit in the wrong profile!!!) and do not recreate them but I do not know how to overcome this issue.
Any help would be greatly appreciated.
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
mekaywe
14 years ago
The components which contain User Files should have HKCU key as keypath, then you will be able to get User files in Admin as well.
Posted by:
anonymous_9363
14 years ago
I know this has something to do with the fact that admins have access to all files on the systemWell, you can stop "knowing" that right away, because it's completely wrong. :)
The simple expedient of taking a verbose log of both installs will highlight what's going on.
Posted by:
mturman
14 years ago
mekaywe, I had already created 3 new components under a new top-level feature, then added 1 file to each component, then created HKCU dummy keys for each of the components which are set as keyfiles. I also tried adding all 3 files to one component with a single HKCU dummy key.
In both cases, as stated previously, if the app is launched for the first time as a basic user, repair works perfectly. If launched with admin privilages, only the HKCU keys are created.
VBScab you're always great at making suggestions but not so much so about explaining them. How exactly would one go about setting verbose logging?
In both cases, as stated previously, if the app is launched for the first time as a basic user, repair works perfectly. If launched with admin privilages, only the HKCU keys are created.
VBScab you're always great at making suggestions but not so much so about explaining them. How exactly would one go about setting verbose logging?
Posted by:
mekaywe
14 years ago
you will find ICE errors/warnings regarding those files, give a try to resolve them and test
Posted by:
spartacus
14 years ago
How exactly would one go about setting verbose logging?
You'll need to use the following link because you need to log self-repair activity rather than installation activity.
http://itninja.com/question/wpsclient---silent-install7
Regards,
Spartacus
Posted by:
anonymous_9363
14 years ago
How exactly would one go about setting verbose logging?Send me your work address and I'll come round and complete the job for you, shall I?
The best way to learn is as I did: read, experiment, break stuff, fix it, read some more, etc., etc. I have no intention of spoon-feeding anybody, especially when the information asked for can be found in less than 3 seconds.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.