Is "Create Global Objects" privelege necessary to run Windows Forms app ?

[Dmitriy Zakharov]

Hi,

Our .NET application runs fine in a W2K Terminal Server session, but only
when user is a member of Administrators group. Otherwise it creates DRWATSON
log file.

The problem disappeared after Privelege "Create Global Objects" has been
granted to Users in the Local Computer Policy.

Is this privelege required by Windows Forms application or framework ?
Garbage Collector ?

Thanks.
Dmitriy Zakharov.
Tritech Financial Systems, Inc.
(416) 621-2020

 

[Dmitriy Zakharov]

Hi Yanhong,

I've removed the privelege and could not reproduce the problem.

I think maybe system restart that I did earlier fixed something. This box
runs 24/7. It is never restarted without a good reason.

Thanks - I'm impressed by the level of MS Tech Support. I think it has
improved over the time.

Dmitriy.

Hello Dmitriy,

Thanks for posing in the group.

The "Create global objects" user right (SeCreateGlobalPrivilege) is a

Windows 2000 security setting that was first introduced in

Windows 2000 SP4. The user right is required for a user account to create

global objects in a Terminal Services session. Note

that users can still create session-specific objects without being

assigned this user right. By default, members of the

Administrators group, the System account, and Services that are started by

the Service Control Manager are assigned the

"Create global objects" user right. That is why admin could run your application successfully.

So the behavior is not related to .net framework, GC. It should be related to Windows 2000 SP4.

Could you create a simple "Hello World" windows forms application for

testing to confirm whether it is applied to all windows

forms application or just specific to your windows forms app?

For details, please refer to MSDN article: "Overview of the "Impersonate a

Client After Authentication" and the "Create Global