Export (0) Print
Expand All

Verify the Permission Settings for Remote Debugging (Windows Embedded Standard 2009)

4/23/2012

When you perform remote debugging, you must configure both local and remote systems to meet the minimum permission requirements. You must have the minimum permissions on the device where the application is being debugged.

  • Managed code debugging permission requirements
    To debug managed code that is running under your own account, you must be a member of either the Administrators group or the Debugger Users group.
    To debug managed code that is running under another user account, such as the local SYSTEM account, you must be a member of the Administrators group.
  • Native code debugging permission requirements
    To debug native code that is running under your own account, you must be a member of either the Administrators group or the Debugger Users group.
    To debug native code that is running under another user account, such as the local SYSTEM account, you must be a member of the Administrators group or the Debugger Users group, and you must have the SE_DEBUG_NAME permission in the local security policy. By default, the Administrators group has this permission.
    Bb521312.note(en-US,WinEmbedded.51).gifNote:
    When you perform remote debugging of native Microsoft Visual C or Microsoft Visual C++ applications with Remote Debug Monitor (Msvcmon.exe), the remote computer user does not have to be a member of the Debugger Users group. However, this method is not secure.

On the local computer, where the Visual Studio .NET debugger is installed, you must be an administrator or a member of the Debugger Users group to run the debugger successfully.

Bb521312.note(en-US,WinEmbedded.51).gifNote:
Remote debugging requires extra configuration if you are using DCOM or Machine Debug Manager (MDM). For more information, visit the following Microsoft Web site.

Community Additions

ADD
Show:
© 2014 Microsoft