SetFileOwner

sliceofpie · 20th July 2011, 23:34

Hi,
I'm running into an issue with AccessControl::SetFileOwner.

I've created a script that sets the ownership of a file to the current logged in user:

code:


  AccessControl::GetCurrentUserName "" "$0"

  Pop $0

  AccessControl::SetFileOwner "$INSTDIR\myfile.txt" $0

This works well in workgroups but does not work in a domain environment

. In a domain, it actually assigns the local admin, instead of the logged in user. Im not sure if this is due to "RequestExecutionLevel admin".

Anyhow Id like it to assign the actual user that is logged on. I've tried to use UserMgr::GetCurrentDomain in conjuction with AccessControl::GetCurrentUserName but I believe my syntax was wrong.. (I'm new to NSIS so couldn't figure out the format

)

Any ideas? Any help is greatly appreciated !!!

Anders · 21st July 2011, 01:27

If you are using RequestExecutionLevel admin then you can't really get the user.

sliceofpie · 21st July 2011, 16:07

I see. Is it possible to switch the RequestExecutionLevel back down then take ownership of the file? not sure if that would be appropriate in my scenario.

Any examples would really help.

MSG · 21st July 2011, 16:39

As far as I know it's not possible to downgrade access level in Windows. But if it is possible, the only way to do it is to use shellexecuteas or runas.exe to start a new process. And for that you need to know the username, which you don't.

So, the best option is probably to use the UAC plugin to get two instances of your installer, one at userlevel and one at adminlevel. You can then get the username in the outer (userlevel) instance, and do all adminny stuff in the inner (admin) instance. Not recommended for beginners.

sliceofpie · 21st July 2011, 17:24

MSG thank you for suggestion.

I thought about something else. What if I run the dos command "takeown.exe" from the installer. Is that possible to do?

20th July 2011, 23:34	#1
sliceofpie Junior Member Join Date: Jul 2011 Posts: 3	SetFileOwner Hi, I'm running into an issue with AccessControl::SetFileOwner. I've created a script that sets the ownership of a file to the current logged in user: code: AccessControl::GetCurrentUserName "" "$0" Pop $0 AccessControl::SetFileOwner "$INSTDIR\myfile.txt" $0 This works well in workgroups but does not work in a domain environment . In a domain, it actually assigns the local admin, instead of the logged in user. Im not sure if this is due to "RequestExecutionLevel admin". Anyhow Id like it to assign the actual user that is logged on. I've tried to use UserMgr::GetCurrentDomain in conjuction with AccessControl::GetCurrentUserName but I believe my syntax was wrong.. (I'm new to NSIS so couldn't figure out the format ) Any ideas? Any help is greatly appreciated !!!

21st July 2011, 01:27	#2
Anders Moderator Join Date: Jun 2002 Location: ${NSISDIR} Posts: 2,810	If you are using RequestExecutionLevel admin then you can't really get the user. IntOp $PostCount $PostCount + 1

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

21st July 2011, 16:07	#3
sliceofpie Junior Member Join Date: Jul 2011 Posts: 3	I see. Is it possible to switch the RequestExecutionLevel back down then take ownership of the file? not sure if that would be appropriate in my scenario. Any examples would really help.

21st July 2011, 16:39	#4
MSG Major Dude Join Date: Oct 2006 Posts: 1,847	As far as I know it's not possible to downgrade access level in Windows. But if it is possible, the only way to do it is to use shellexecuteas or runas.exe to start a new process. And for that you need to know the username, which you don't. So, the best option is probably to use the UAC plugin to get two instances of your installer, one at userlevel and one at adminlevel. You can then get the username in the outer (userlevel) instance, and do all adminny stuff in the inner (admin) instance. Not recommended for beginners.

21st July 2011, 17:24	#5
sliceofpie Junior Member Join Date: Jul 2011 Posts: 3	MSG thank you for suggestion. I thought about something else. What if I run the dos command "takeown.exe" from the installer. Is that possible to do?