Re: Impersonating a domain user for debugging purposes
From: Steve Thompson (stevethompson_at_nomail.please)
Date: 06/22/04
- Next message: Steve Thompson: "Re: configuring antivirus"
- Previous message: ed: "configuring antivirus"
- In reply to: Raterus: "Impersonating a domain user for debugging purposes"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 22 Jun 2004 14:17:06 -0400
"Raterus" <raterus@spam.org> wrote in message
news:%23uCRFd9VEHA.716@TK2MSFTNGP11.phx.gbl...
<<I'd like to debug these scripts at the comfort of my workstation, and not
rely on the end-users interaction in this process, except for the initial
error report. My problem is that since I have Domain Admin rights,
everything works fine for me. It usually boils down to a simple permission
somewhere, but that's hard to track when I don't have any errors I can see
at my workstation..
So my question is:
Is there some way I can impersonate a specific users login, in order that I
can test what exactly happened on their end? I'd prefer not to have to
change their password.>>
In addition to Dan's suggestion, another technique that I've used, create a
test account with equivelent permissions to your end users. Drop a shortcut
to Query Analyzer on the desktop. Right click, the QA shortcut and choose
RunAs, enter the domain\testname & password. You are now runnin the QA
session in the context of your test account.
Steve
- Next message: Steve Thompson: "Re: configuring antivirus"
- Previous message: ed: "configuring antivirus"
- In reply to: Raterus: "Impersonating a domain user for debugging purposes"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
