I've seen it done a number of ways. I'll stick to the pleasant ones. :) Put them on their own network, and even own domain, and setup a schedule for patch management that works for both IT and Development.
In one place, we segmented the dev team and further segmented their virtualized development environment. Some of them were given additional rights to regulate AV on their local machines, but anyone who got infected was made less privileged the next time around. We only had 3 repeat offenders, including one guy who wrecked a portion of the dev environment and earned the wrath of his colleagues. We simply locked him down, recovered the environment from snapshots and moved on. :) *ASB *(My XeeSM Profile) <http://XeeSM.com/AndrewBaker> *Exploiting Technology for Business Advantage...* * * On Fri, Sep 17, 2010 at 2:03 PM, David Lum <[email protected]> wrote: > For those of you in software development companies – how do you handle > development machines vs. normal employee use machines as far as managing > patches, AV, level of local user permissions, etc. you don’t have them on a > separate subdomain or anything do you? > > *David Lum** **// *SYSTEMS ENGINEER > NORTHWEST EVALUATION ASSOCIATION > (Desk) 971.222.1025 *// *(Cell) 503.267.9764 > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
