Keith & Jon,
Every time I change a setting in Options I get the "thank you for registering" dialog - rather irritating. This was in 3.0. and still in b1. I have code in HKLM by the way.
Pete

Keith,
See attachments.
Pete

See attached.
Note I have currently 10 machines setup with the registry code set in HKLM. I tend to run FileSeek as local administrator.
These all do same. These are all upgrades from 2 to 3 to this beta.

Keith,
Any update on a fix for this issue - it is a little irritating?
Pete

Keith the test build seems to have fixed this problem.

Keith,
One thing I have noticed is that if the license is in HKLM the installer UI "doesn't show it" while installing.
I think the installer should look in HKLM and HKCU for the license.
However I can see a design rational that says if it is in HKLM don't show the code but just state it is registered. If it is in HKLM then and end user shouldn't see the code - don't want an easy way for them to copy it.
Pete

Thanks Keith.

So following on with this discussion regarding the license I have the following points:
1) Do you intended to add this functionality to the installers for the other products?
2) The next point is that in the UI the license code is visible to any user - so someone logging on to one of our machines could just copy the code and install on their own personal system. I do not think that this should be possible in any enterprise capable application. I think you need to add this to a todo list and fix it moving forward for all you apps. Something like if the license is in HKLM it is not visible in the UI at all.

Keep up the good work,
Pete

Keith thanks again.
Re the ADMX templates; have you reorganized the structure (single BFS entry point) as per my previous suggestion?
Pete

Keith - any update on 3.1.1 as I don't want to deploy until these features are available?
Pete

Keith,
Thanks - lets call this thread closed.
Pete