Deleting LockPermission table
What would be the side effects of removing the LockPermissions table. Can anyone please let me know?
0 Comments
[ + ] Show comments
Answers (11)
Please log in to answer
Posted by:
captain_planet
14 years ago
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?
Posted by:
desert_rose
14 years ago
i want to delete them so that i can install my application on non english OS
Posted by:
captain_planet
14 years ago
Why not delete/amend the relevant rows in the table, as opposed to deleting the whole table?
Posted by:
spartacus
14 years ago
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 :
Regards,
Spartacus
Posted by:
anonymous_9363
14 years ago
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.
EDIT:
Hey, Sparts beat me to it :) Good link, too.
Posted by:
captain_planet
14 years ago
...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. [;)]
Posted by:
desert_rose
14 years ago
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?
Did i missed anything?
Posted by:
eskonar
14 years ago
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[:)]
Posted by:
Jay Am
14 years ago
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.
In our internal packaging guide its not recommended to use the LockPermissions table however it's adviced to use a custom action with secedit.
Posted by:
aogilmor
14 years ago
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.