What would be the side effects of removing the LockPermissions table. Can anyone please let me know?
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
None that I'm personally aware of. Lot's of ropey Autodesk products don't have a LockPermissions table in them. Not sure why you'd want to remove it though?
Answered 01/06/2010 by: captain_planet
Second Degree Brown Belt

Please log in to comment
0
i want to delete them so that i can install my application on non english OS
Answered 01/06/2010 by: desert_rose
Orange Belt

Please log in to comment
0
Why not delete/amend the relevant rows in the table, as opposed to deleting the whole table?
Answered 01/06/2010 by: captain_planet
Second Degree Brown Belt

Please log in to comment
0
ORIGINAL: desert_rose

i want to delete them so that i can install my application on non english OS


Rather than dropping the table, you could investigate making your LockPermissions table language-independent through the introduction of the SIDLookup merge module into your package.

For details see :

http://www.installsite.org/pages/en/msi/tips.htm#SIDLookup

Regards,

Spartacus
Answered 01/06/2010 by: spartacus
Black Belt

Please log in to comment
0
What I think the captain means is, instead of using the account/group names e.g 'Administrators', use their SIDs instead. They never change for the built-in accounts/groups. They're probably documented here on AppDeploy somewhere, they'll certainly be on MSDN if not.

EDIT:
Hey, Sparts beat me to it :) Good link, too.
Answered 01/06/2010 by: VBScab
Red Belt

Please log in to comment
0
...that's the baby. I'm sure Spartacus posted that solution about a year ago for somebody else.....I'll make a note of it this time. [;)]
Answered 01/06/2010 by: captain_planet
Second Degree Brown Belt

Please log in to comment
0
I tried putting the SID for Users and Administrators in the LockPermissions table, but that didnt worked on non english OS.

Did i missed anything?
Answered 01/06/2010 by: desert_rose
Orange Belt

Please log in to comment
0
packager apply permission on the application for proper functionality of the application, if you remove the lock permission table, it might afffect the application in the user mode, hence user may not been able to use the application due to limited access[:)]
Answered 03/24/2010 by: eskonar
Senior Yellow Belt

Please log in to comment
0
Why not using secedit?
In our internal packaging guide its not recommended to use the LockPermissions table however it's adviced to use a custom action with secedit.
Answered 03/25/2010 by: Jay Am
Senior Yellow Belt

Please log in to comment
0
iirc tried that once and got errors, would think you might have to also alter the _valdiation table, but never pursued it. if it doesn't have entries in it, it doesn't do anything.
Answered 03/25/2010 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
Jay AM u r right we can use custom action..... [:)] .
Answered 03/29/2010 by: eskonar
Senior Yellow Belt

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