Dumb and Dumber

  • Thread starter Thread starter Phillip McClurg
  • Start date Start date
P

Phillip McClurg

I just had VC++ installed by our administrator - when I
tried to debug a test application I discovered I did not
have access because I wasn't in the Debugger User Group.

Geez - I guess I'll call the administrator back up and
have him waste another thirty minutes because Microsoft is
busy creating another industry called "I'm sorry, you
can't use the software you just purchased from us."

By the way, are there any other menu items I need the
administrator to come by and enable?

Get Real Bill - Phil McClurg
 
Phillip said:
I just had VC++ installed by our administrator - when I
tried to debug a test application I discovered I did not
have access because I wasn't in the Debugger User Group.

Geez - I guess I'll call the administrator back up and
have him waste another thirty minutes because Microsoft is
busy creating another industry called "I'm sorry, you
can't use the software you just purchased from us."

By the way, are there any other menu items I need the
administrator to come by and enable?
Click to expand...

Of course the requirement to be a member of the Debugger's group is not a
Visual Studio requirement, it's an operating systrem requirement. Running a
debugger is a potential security risk, since the debugger can attach to
(nearly) any process running on the machine, examine memory, etc. Be glad
that this is something that ordinary users are not allowed to do.

Be unhappy that your IT department hasn't figured out that developers aren't
ordinary users and shouldn't be configured as such!

-cd
 
If you're going to be programming ASP.NET with IIS on your own machine, then
I'd book the system administrator for a couple of days.

Regards,

Jasper Kent.
 
Phillip McClurg said:
I just had VC++ installed by our administrator - when I
tried to debug a test application I discovered I did not
have access because I wasn't in the Debugger User Group.
Click to expand...

There are security issues to be consider when debugging stored procedures
and debugging across the network. This link should explain them:

http://support.microsoft.com/?id=329282
Geez - I guess I'll call the administrator back up and
have him waste another thirty minutes because Microsoft is
busy creating another industry called "I'm sorry, you
can't use the software you just purchased from us."
Click to expand...

FWIW: NT enforces a discretionary security model. Someone with debug
privilege who knows his way around the o/s poses a greater threat than the
garden variety user of Word and Excel hence the check.

Regards,
Will
 
Microsoft said:
And seriously, anybody doing development work *should* be an admin on that
computer. It's just too much of a pain in the rear to not be!!
Click to expand...

But there are an alarmingly large number of I.T. depts who are run by
control freaks. I was at one that periodically scanned our drives to be
sure we only had IE as our browser and went in and uninstalled anything
else they found. Made it beastly difficult for the web developers to be
friendly to anything else. OTOH I would be really smoked if some
developer happily installed something that turned a virus loose on my
network.
 
Back
Top