We have a few apps (office, acrobat reader etc) which are setup as machine based installs - i.e. they install when the PC starts up before presenting the crtl+alt+del screen.

When a user logs in and runs one of these machine based apps for the first time, it repairs in order to write any HKCU registry keys and user specific files. This is all fine and as expected.

However, when we remove the machine based application and it uninstalls upon next reboot - how do the HKCU reg keys etc get removed from the user profile, or don't they?

Guess they don't get removed but if anyone has any experience with this / best practices etc I'd be grateful.

0 Comments   [ + ] Show 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.


You're right - they don't get removed. We haven't really found a way to properly manage this either, or whether as you say, there are best practices with regards to how they should be managed. I'd be interested to hear someones expert opinion too!
Answered 12/08/2004 by: ab2cv
Orange Senior Belt

Please log in to comment
I've used running an EXE at logon to clean things up with user profiles but that does not work well in an upgrade scenario using AD. I have not tried to clean user profiles up in an upgrade scenario either because if it ain't broken don't go fixin it.
Answered 12/08/2004 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
What you can do it that you IF its possible, remove all HKCU registry entries in the package.... Most program works without then.

When I create msi... The last thing I do is that I save the msi.. then I remove all HKCU and then I save it again under another name.. if the last msi-package works.. I use that.. otherwise I use the one with the HKCU...
Answered 12/29/2004 by: Gastro
Senior Yellow Belt

Please log in to comment
ab2cv and kkaminsk are both right.

They are not removed and unless they pose some sort of issue....don't worry about them.

If they are an issue....you can always create an msi package to remove the offending keys and thats that.
Answered 01/07/2005 by: MSIMaker
Second Degree Black Belt

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