Software Deployment

That's because Active Setup has no clue what your package is, nor indeed what Windows Installer is. It's a completely different technology.

You could either create the registry entries in an HKLM key and then use a script to copy them to the correct HKCU ones or you could use WI's self-healing. See this afternoon's reply to this http://itninja.com/question/spss-16.0-dialog post.

Hi Sushma,
how do you "install this registries using Active Setup"? A .reg file? with reg.exe?
A solution would be to do it with an MSI. Put the things which go to the profile into its own feature (eg. 'UserSettings').
Make it the top feature and all the existing features subs of it.
Then you reinstall just this single feature on each profile with AS like this:
Stubpath: msiexec /i [ProductCode] REINSTALL=UserSettings REINSTALLMODE=up /qn
Regards, Nick

Hi,

Hey, really nice suggestion Nick and I will surely try this myself and use it in case I come across such a thing.
But on second thoughts, I think [Date] and [Time] etc are generally included in HKLM rather than HKCU. Can anyone think of any other examples for such registries?
One more thing, do you guys think it would be a good idea to exclude such registries from under the HKCU hive? I dont think they would be included under the HKCU for any specific reason unless they are queried for any values (which I think will be less likely)

This is the requirement of the application to keep these registries in HKCU.
I just gave you an example on this keys. It can be anything else than this,
for eg: some data which is set by property within your application or may be some filepath value which may be changed by user at the time of installation.