Lock Permissions for international "USERS"
Hi guys,
I've had a guy in Holland try out my installer, he report that he's getting Error 1609,:
Error1609: An error occured while applying security settings. Users is not a valid user or group. This could be a problem with the package or a problem connecting to a domain controller on the network.Check your network connection and Retry, or Cancel to end the install.
It looks like "Users" is not an internationally known local group, is this correct? Marvelous if it is'nt but a right pain if it is true!!!
I suppose if it is true "Everyone" is an option...
Paul
I've had a guy in Holland try out my installer, he report that he's getting Error 1609,:
Error1609: An error occured while applying security settings. Users is not a valid user or group. This could be a problem with the package or a problem connecting to a domain controller on the network.Check your network connection and Retry, or Cancel to end the install.
It looks like "Users" is not an internationally known local group, is this correct? Marvelous if it is'nt but a right pain if it is true!!!
I suppose if it is true "Everyone" is an option...
Paul
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
schieb
16 years ago
Posted by:
AngelD
16 years ago
It looks like "Users" is not an internationally known local group, is this correct?
Yes, that's correct.
I suppose if it is true "Everyone" is an option...
Sorry, but it's not possible as it's not a "real" group.
Is this package being installed in an corporate environment or is it a vendor package?
I guess you're using the LockPermissions table, if you don't know the negative sideaffect of it please search the forum for this table. There's alot of information for other solutions to change/add security permissions instead.
Yes, that's correct.
I suppose if it is true "Everyone" is an option...
Sorry, but it's not possible as it's not a "real" group.
Is this package being installed in an corporate environment or is it a vendor package?
I guess you're using the LockPermissions table, if you don't know the negative sideaffect of it please search the forum for this table. There's alot of information for other solutions to change/add security permissions instead.
Posted by:
HotSpot
16 years ago
Posted by:
deploy.no
16 years ago
We have used the SIDLookup merge module by Andreas Magnusson for some projects in the past without trouble. Even so, this was because we had a very special requirement that all security related information were to be stored directly as msi tables for some automated reporting tools to work.
http://www.installsite.org/pages/en/msi/tips.htm#SIDLookup
For other, more common projects we don't use the LockPermissions table because its too inflexible. If you look around, "setacl" is an appdeploy long-time favourite, it seems :)
http://www.installsite.org/pages/en/msi/tips.htm#SIDLookup
For other, more common projects we don't use the LockPermissions table because its too inflexible. If you look around, "setacl" is an appdeploy long-time favourite, it seems :)
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.