ICE38 - why does it exist?
Hello all,
Hoping someone can help here.........
Does anyone know why ICE38 exists?
Namely.........
ICE38 - Component <COMP> installs to user profile. It must use a registry key under HKCU as its key path, not a file.
We are using Roaming Profiles on the Project I am currently working on and we have encountered problems with users profiles.
Basically what I want to know is why exactly do you have to make a Current User registry key the keypath for Components installed to the user profile and not a User File?
I have tried a repair with an msi where the User file was set as the keypath and it repaired without a hitch.
Any ideas?
Thanks in advance!
Hoping someone can help here.........
Does anyone know why ICE38 exists?
Namely.........
ICE38 - Component <COMP> installs to user profile. It must use a registry key under HKCU as its key path, not a file.
We are using Roaming Profiles on the Project I am currently working on and we have encountered problems with users profiles.
Basically what I want to know is why exactly do you have to make a Current User registry key the keypath for Components installed to the user profile and not a User File?
I have tried a repair with an msi where the User file was set as the keypath and it repaired without a hitch.
Any ideas?
Thanks in advance!
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
spartacus
18 years ago
Posted by:
mark_holland21
18 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.