[duxhelp] Re: Unable to emboss
- From: "Peter Sullivan" <peter@xxxxxxxxxx>
- To: <duxhelp@xxxxxxxxxxxxx>
- Date: Fri, 11 Jun 2004 15:12:19 -0400
Kevin,
I'll address your last point first. It would take a day or two to write &
test the registry fixup program you suggest. That's more time than we have
to dedicate to the task.
It appears that Mark's suggestion is the one we could all live with best.
Current installations will be patched up, but you'll still have the
opportunity to add durable customizations to the registry permissions;
you'll just need to be sure to flip the "Customized" setting.
- Peter
-----Original Message-----
From: duxhelp-bounce@xxxxxxxxxxxxx [mailto:duxhelp-bounce@xxxxxxxxxxxxx] On
Behalf Of Loeffler, Kevin J.
Sent: Friday, June 11, 2004 3:09 PM
To: duxhelp@xxxxxxxxxxxxx
Subject: [duxhelp] Re: Unable to emboss
I don't know that I have a preference. I would think it best to NOT require
a registry hack to remove anything. This will be complicated for some of
the regular users and they probably shouldn't be in the registry for their
systems'
own good. Having administrators edit a key manually to prevent overwriting
the settings sounds like it may be the best option. Regular users can
always make the needed changes to their registry. Systems managed by
administrators can be locked down with the registry key set to 1 instead of
the default 0.
So I
guess I do prefer one over the others - your final alternative seems like it
would cause the least disruption for ALL parties involved, not just systems
administrators.
If you go with the first option you suggested, how hard would it be to post
a registry edit file to undo settings from a previous build of DBT?
You'll
only have one to start with, and if you update the reg files as new builds
come out, users could use the reg file to remove the registry branch from
older builds without getting into the registry by hand. The new build could
then be installed and it could create the new branch as needed.
Kevin--
-----Original Message-----
>OPTION 1:
>But one question remains: at what point shall we set rights to the
registry
>branch? I suggest setting them only as the branch is created. This
>prevents DBT overwriting any customizations that you may have to set by
>hand. However, it also means that current installations won't be fixed
when
>we post a new build of DBT. Rather, you would have to remove the
registry
>branch (using regedit) and then re-create all of your embosser
>configurations.
>
>
>Another alternative would be to overwrite rights settings always, if we
can,
>unless we find a specific value (e.g. PermissionsCustomized=1) in the
>registry branch. You would then want to add this value if you
customize
>permissions for some reason.
>
>A final alternative would be similar. We could overwrite right
settings
>always, if we can, unless we find a specific value (e.g.
>PermissionsInitialized=1) in the registry branch. We would ourselves
write
>this value, so that your customizations would be preserved unless you
>eliminate the setting.
>
* * *
* This message is via list duxhelp at freelists.org.
* To unsubscribe, send a blank message with
* unsubscribe
* as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also
* subscribe, unsubscribe, and set vacation mode and other subscription
* options by visiting //www.freelists.org. The list archive
* is also located there.
* Duxbury Systems' web site is http://www.duxburysystems.com
* * *
* * *
* This message is via list duxhelp at freelists.org.
* To unsubscribe, send a blank message with
* unsubscribe
* as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also
* subscribe, unsubscribe, and set vacation mode and other subscription
* options by visiting //www.freelists.org. The list archive
* is also located there.
* Duxbury Systems' web site is http://www.duxburysystems.com
* * *
Other related posts:
