e was local admins.
-Original Message-
From: Charlie Kaiser [mailto:charl...@golden-eagle.org]
Sent: Friday, 12 February 2010 12:37 AM
To: NT System Admin Issues
Subject: RE: Non-local admin for developers, etc
VMWare or a second machine. "Primary corporate PC" does not get admi
orkstation. They can use that account for
priv escalation as needed. Auditing is turned up on the workstations.
-sc
From: David Lum [mailto:david@nwea.org]
Sent: Thursday, February 11, 2010 9:02 AM
To: NT System Admin Issues
Subject: Non-local admin for developers, etc
For those of
Enforce standards and good practices on where in the registry and
local drives the corporate developed software can write. Give them
permissions to those locations.
That solves the problem for most of our software. We do have some
people working at the driver level and those work in a lab.
On 2
org
Kingman, AZ
***
> -Original Message-
> From: David Lum [mailto:david@nwea.org]
> Sent: Thursday, February 11, 2010 7:02 AM
> To: NT System Admin Issues
> Subject: Non-local admin for developers, etc
>
> For those of you who have adopted the
VMWare Workstation on some
Delegated admin rights to virtual test systems on others
Liberal use of RunAs feature
On 11 February 2010 14:02, David Lum wrote:
> For those of you who have adopted the “no login as local administrator”
> and have software developers, how do you handle the develope
For those of you who have adopted the "no login as local administrator" and
have software developers, how do you handle the developers?
David Lum // SYSTEMS ENGINEER
NORTHWEST EVALUATION ASSOCIATION
(Desk) 971.222.1025 // (Cell) 503.267.9764
~ Finally, powerful endpoint security that ISN'T a res
