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
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Could you add permissions by User's SID? I'd be suprised if it was a different SID.
Answered 08/13/2007 by: schieb
Purple Belt

Please log in to comment
0
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.
Answered 08/13/2007 by: AngelD
Red Belt

Please log in to comment
0
This is our commercial package going around the world for both corperates and home users.

Is there a sure fire way of setting permissions to cater for international installations of Windows, I want to steer clear from applyling local policy templates and would love to use Lock Perms.

Paul
Answered 08/14/2007 by: HotSpot
Orange Senior Belt

Please log in to comment
0
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 :)
Answered 08/14/2007 by: deploy.no
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity