strange issue with permissions

[NewsArchive]

Hi all,

I recently posted a question regarding ACL and SB. I've made those
changes which appear to be fine, however, here is a new problem that has
been happening and it either has to be related to changes in the core
operating system (ie windows), recent changes to SetupBuilder OR the
possibility of a file in use during the install process.

Here is the problem; We are running an application under Terminal
Services. If we install a new copy of the application in a new folder,
a person can login and run the application without problems. If
however, we update an existing application and reboot, people logging in
through TS will not be able to run the app. The reason is that many of
the DLL's in the losing BUILTIN\Users security descriptor.

I can reset the permissions from the command line with cacls, however, I
was curious if there was any way to determine exactly why this is
being caused. I'm leaning toward people in the app at the time of
update, but wanted to get other people's opinion.

Cheers!
ken

[NewsArchive]

Hi Ken,

When a file is "replaced" in Windows, security attributes for the existing
file are not copied to the "new" file. So if you do not reset the
permissions, then they are lost.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Thanks Friedrich,

My confusion with the above comments is that when we first install the
software it has "Builtin\users" automatically set and this is something
that we are not programatically or manually doing, however, when we
update that same folder the "builtin\users" is removed. Any ideas on
why that would be happening?

I could understand if it were a case of we manually added a specific
group or user to the permissions.

Thanks,
Ken

[NewsArchive]

Ken,

> My confusion with the above comments is that when we first install the
> software it has "Builtin\users" automatically set and this is something
> that we are not programatically or manually doing, however, when we update
> that same folder the "builtin\users" is removed. Any ideas on why that
> would be happening?
>
> I could understand if it were a case of we manually added a specific group
> or user to the permissions.

You mentioned a "reboot" in your first message. Are you replacing a
"locked" file and then a reboot is required?

In this case, a MoveFileEx() Windows function copies the file to a temporary
folder and (after the reboot), Windows copies the file to the target
location to replace the previously locked file. Perhaps this causes such a
permission situation?

Friedrich