PGomersall
229 discussion posts
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
May 9, 2013 (modified May 10, 2013)
•
#1
I haven't been able to reproduce this here, even with the license key in the HKLM\Software\Binary Fortress Software\FileSeek key.
Could you export your HKCU\Software\Binary Fortress Software\FileSeek key and attach it so that I can restore your settings on a test machine and try to reproduce this bug?
Thanks!
PGomersall
229 discussion posts
Keith,
See attachments.
Pete
• Attachment [protected]: FileSeek.reg [780 bytes]
• Attachment [protected]: Thanks.png [7,526 bytes]
PGomersall
229 discussion posts
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.
• Attachment [protected]: FS-HKCU.reg [19,362 bytes]
May 10, 2013 (modified May 10, 2013)
•
#5
Thanks Pete! I've found the issue, so we'll hopefully have it fixed up for the next beta.
PGomersall
229 discussion posts
Keith,
Any update on a fix for this issue - it is a little irritating?
Pete
PGomersall
229 discussion posts
Keith the test build seems to have fixed this problem.
PGomersall
229 discussion posts
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
May 30, 2013 (modified May 30, 2013)
•
#10
Good point! I'll investigate this to see if we can make those changes to the installer.
FileSeek 3.1 is now available, and fixes the License Key error in the settings. The installer will also now hide the license key box if the key has been specified by an administrative policy.
Thanks!
PGomersall
229 discussion posts
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
PGomersall
229 discussion posts
Keith thanks again.
Re the ADMX templates; have you reorganized the structure (single BFS entry point) as per my previous suggestion?
Pete
Sure have! If you want to try them out, I've attached them here. Note that the "Disable License Key" tab won't work until FileSeek 3.1.1 is released.
I'll be posting new DisplayFusion ADMX templates up to the site today as well to move them into the Binary Fortress Folder as well.
Jun 7, 2013 (modified Jun 7, 2013)
•
#16
PGomersall
229 discussion posts
Keith - any update on 3.1.1 as I don't want to deploy until these features are available?
Pete
I'm actually not sure on the ETA for 3.1.1 but I'll check into it and keep you posted.
PGomersall
229 discussion posts
Keith,
Thanks - lets call this thread closed.
Pete
