Debug view :: remote use requires admin rights :: BizTalk 2004

[BA]

Hello,

We use the Debug View from sysinternals for BizTalk development and testing.

The remote feature is very useful since you can login to any server and see
the debugging statements. Unfortunately this requires administrative
rights.

Its the stated policy of my client not to allow admin rights, and because of
this we cant use the debug view for the testers. It is slowing them down.

Has anyone had this problem or does anyone know a way to use the debug view
remotely without having to grant testers administrative rights on the
server?

Thanks,

BA

[Nicholas Paldino [.NET/C# MVP]]

BA,

I know it is the "stated policy" (which I find amounts to nothing when
put up against a deadline and going over budget) of your client, but you
might want to let them know of the situation, and how it will impact your
timeline and budget. While I do understand the reasons why such policies
are made, exceptions need to be made (supervised, and not often, of course),
in exceptional situations (which I am sure you would agree, this would be
one).

I know it's not the answer you were looking for, but it might help.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"BA" <bi***************@gmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

Hello,

We use the Debug View from sysinternals for BizTalk development and
testing.

The remote feature is very useful since you can login to any server and
see
the debugging statements. Unfortunately this requires administrative
rights.

Its the stated policy of my client not to allow admin rights, and because
of
this we cant use the debug view for the testers. It is slowing them down.

Has anyone had this problem or does anyone know a way to use the debug
view
remotely without having to grant testers administrative rights on the
server?

Thanks,

BA

[BA]

Nicholas,

I tried that road already and its a dead end street. Their certification by
some accounting board has things like this (believe it or not) on their list
of requirements for certification.

I couldnt agree more though. These sorts of policies secure very little and
end up costing lots of money in lost productivity.

BA
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
message news:uT**************@TK2MSFTNGP09.phx.gbl...

BA,

I know it is the "stated policy" (which I find amounts to nothing when
put up against a deadline and going over budget) of your client, but you
might want to let them know of the situation, and how it will impact your
timeline and budget. While I do understand the reasons why such policies
are made, exceptions need to be made (supervised, and not often, of course), in exceptional situations (which I am sure you would agree, this would be
one).

I know it's not the answer you were looking for, but it might help.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"BA" <bi***************@gmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

Hello,

We use the Debug View from sysinternals for BizTalk development and
testing.

The remote feature is very useful since you can login to any server and
see
the debugging statements. Unfortunately this requires administrative
rights.

Its the stated policy of my client not to allow admin rights, and because of
this we cant use the debug view for the testers. It is slowing them down.
Has anyone had this problem or does anyone know a way to use the debug
view
remotely without having to grant testers administrative rights on the
server?

Thanks,

BA