/build/static/layout/Breadcrumb_cap_w.png

HKCU repair on first lanch works for admin but not standard user

I've created a transform for Open WorkBench 1.14 to insert some HKCU entries on first run. I've done this using the usual method of making the HKCU reg entry a keypath of a component which belongs to a feature which is a parent of all other features. The shortcut is advertised and belongs to a child feature.

I've tested this as working in my production environment for standard users (on XPPSP2).

A couple of admins at other sites have asked for a copy of the transform and are finding that the transform only works for admins, not standard users.

I've had a look over the transform, and can't see what would be causing the repair not work. Has anyone ever seen a HKCU repair work for admins and not standard users?

0 Comments   [ + ] Show comments

Answers (3)

Posted by: nheim 12 years ago
10th Degree Black Belt
0
Hi Michael,
does installer pop up on a users profile? If yes, only the first time or always?
Please turn on logging on the client and log a repair on a standard users profile.
Regards, Nick
Posted by: jmcfadyen 12 years ago
5th Degree Black Belt
0
usually this happens when your HKCU items are mixed with other items such as HKCU or files in locked down areas.

Are all you HKCU items in a components that are not shared with other locked down items .?
Posted by: meastaugh1 12 years ago
Senior Purple Belt
0
Thank you both for your replies. It turns out a couple of them just hadn't used the advertised shortcut. All is fine now. cheers
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ