LoadUserProfile failing



Hi all,

MSDN states that starting from XP SP2 and Windows Server 2003 you can
only call LoadUserProfile from within a process that is running with
administrative privileges or as LocalSystem.

Can someone confirm that this is indeed true ? I am running a process as
normal user but with the SeRestoreName and SebackupName privileges
and it indeed does not work. In the UserEnv logging I see very low level
calls failing
with access denied (Inside DropClientContext). Does anyone have a clue
what changed in SP2 that makes non-administrator calls to LoadUserProfile
fail ?

I tried to fix this problem by impersonating an account that does have
Administrative
privileges but even this does not work. Doesn't windows consider the calling
thread's
token but only the calling processes token in this case ?

Thanks a lot,
Jos







.



Relevant Pages

  • LoadUserProfile failing
    ... MSDN states that starting from XP SP2 and Windows Server 2003 you can only ... changed in SP2 that makes non-administrator calls to LoadUserProfile fail? ...
    (microsoft.public.win32.programmer.kernel)
  • Re: LoadUserProfile failing
    ... privileges but even that didnt solve the problem. ... _own_ profile, which strikes me as a bit odd. ... MSDN states that starting from XP SP2 and Windows Server 2003 you can ...
    (microsoft.public.win32.programmer.kernel)
  • Re: how to set admin privilege
    ... TOKEN_ELEVATION_TYPE ptet; ... Elevation is not the same as having administrative privileges. ... The OP asked for administrative privileges and your code simply tells the elevation status of the process token which is not the same thing.For example, if i were to create an account that has the SeImpersonatePrivilege privilege, then I can launch the process with this elevated token. ...
    (microsoft.public.vc.mfc)
  • Re: how to set admin privilege
    ... TOKEN_ELEVATION_TYPE ptet; ... Elevation is not the same as having administrative privileges. ...
    (microsoft.public.vc.mfc)
  • Re: Group policy setting to restrict user access to change
    ... user) it is child's play to elevate privileges and subvert/bypass any ... restrictions whatsoever on the local machine, ... Either Windows Server 2003 or FreeBSD, ... Normal "Task Scheduler" tasks were not ...
    (alt.computer.security)