RE: Occasional local admin needed

2013-01-07 Thread David Lum
Thanks for everyone's replies on this!

Dave

From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org]
Sent: Friday, January 04, 2013 7:53 AM
To: NT System Admin Issues
Subject: RE: Occasional local admin needed

Do a domain account as you describe and set the account to expire tomorrow.  
When they need it you re-enable it and set it to expire again the next day. 
Still manual intervention on your part but the automatic expire solves the 
ongoing access issue.

From: David Lum [mailto:david@nwea.org]
Sent: Friday, January 04, 2013 10:41 AM
To: NT System Admin Issues
Subject: Occasional local admin needed

How would you guys handle this? I have a server that the developers use that 
they occasionally (once a month or so) need local admin access for to 
install/upgrade an app or feature they use. This is a new-ish server that 
previously I have just added a user (it's the same one each time) to the local 
admin group then a week later took them out, but that's cumbersome and I become 
the single point of failure on remembering to back them out.

I could 1. create a special AD account for this user to be local admin, or 2. 
create an  AD group, put this person in it, then GPO that group into local 
admins on that server.

Suggestions?
David Lum
Sr. Systems Engineer // NWEATM
Office 503.548.5229 // Cell (voice/text) 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 
listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com
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 
listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: Occasional local admin needed

2013-01-04 Thread Kennedy, Jim
Do a domain account as you describe and set the account to expire tomorrow.  
When they need it you re-enable it and set it to expire again the next day. 
Still manual intervention on your part but the automatic expire solves the 
ongoing access issue.

From: David Lum [mailto:david@nwea.org]
Sent: Friday, January 04, 2013 10:41 AM
To: NT System Admin Issues
Subject: Occasional local admin needed

How would you guys handle this? I have a server that the developers use that 
they occasionally (once a month or so) need local admin access for to 
install/upgrade an app or feature they use. This is a new-ish server that 
previously I have just added a user (it's the same one each time) to the local 
admin group then a week later took them out, but that's cumbersome and I become 
the single point of failure on remembering to back them out.

I could 1. create a special AD account for this user to be local admin, or 2. 
create an  AD group, put this person in it, then GPO that group into local 
admins on that server.

Suggestions?
David Lum
Sr. Systems Engineer // NWEATM
Office 503.548.5229 // Cell (voice/text) 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 
listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: Occasional local admin needed

2013-01-04 Thread Brian Desmond
How about you create an AD Group, nest the AD group in local admins, and add 
the relevant users? GPOs and extra accounts for a dev box like this sounds like 
substantial unnecessary overhead.

Thanks,
Brian Desmond
br...@briandesmond.commailto:br...@briandesmond.com

w - 312.625.1438 | c - 312.731.3132

From: David Lum [mailto:david@nwea.org]
Sent: Friday, January 4, 2013 9:40 AM
To: NT System Admin Issues
Subject: Occasional local admin needed

How would you guys handle this? I have a server that the developers use that 
they occasionally (once a month or so) need local admin access for to 
install/upgrade an app or feature they use. This is a new-ish server that 
previously I have just added a user (it's the same one each time) to the local 
admin group then a week later took them out, but that's cumbersome and I become 
the single point of failure on remembering to back them out.

I could 1. create a special AD account for this user to be local admin, or 2. 
create an  AD group, put this person in it, then GPO that group into local 
admins on that server.

Suggestions?
David Lum
Sr. Systems Engineer // NWEATM
Office 503.548.5229 // Cell (voice/text) 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 
listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: Occasional local admin needed

2013-01-04 Thread Guyer, Don
I would use an AD account, placed in the local admins group and then 
enable/disable as needed.

Regards,

Don Guyer
Catholic Health East - Information Technology
Enterprise Directory  Messaging Services
3805 West Chester Pike, Suite 100, Newtown Square, Pa  19073
email: dgu...@che.orgmailto:dgu...@che.org
Office:  610.550.3595 | Cell: 610.955.6528 | Fax: 610.271.9440
For immediate assistance, please open a Service Desk ticket or call the 
helpdesk @ 610-492-3839.
[cid:image001.jpg@01CDEA6A.558CB490]

From: David Lum [mailto:david@nwea.org]
Sent: Friday, January 04, 2013 10:40 AM
To: NT System Admin Issues
Subject: Occasional local admin needed

How would you guys handle this? I have a server that the developers use that 
they occasionally (once a month or so) need local admin access for to 
install/upgrade an app or feature they use. This is a new-ish server that 
previously I have just added a user (it's the same one each time) to the local 
admin group then a week later took them out, but that's cumbersome and I become 
the single point of failure on remembering to back them out.

I could 1. create a special AD account for this user to be local admin, or 2. 
create an  AD group, put this person in it, then GPO that group into local 
admins on that server.

Suggestions?
David Lum
Sr. Systems Engineer // NWEATM
Office 503.548.5229 // Cell (voice/text) 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 
listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin
Confidentiality Notice:
This e-mail, including any attachments is the 
property of Catholic Health East and is intended 
for the sole use of the intended recipient(s).  
It may contain information that is privileged and 
confidential.  Any unauthorized review, use,
disclosure, or distribution is prohibited. If you are 
not the intended recipient, please delete this message, and 
reply to the sender regarding the error in a separate email.

~ 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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmininline: image001.jpg

RE: Occasional local admin needed

2013-01-04 Thread Ziots, Edward
Restricted Group GPO or do it via GPP...

 

Z

 

Edward E. Ziots, CISSP, Security +, Network +

Security Engineer

Lifespan Organization

ezi...@lifespan.org

 

From: David Lum [mailto:david@nwea.org] 
Sent: Friday, January 04, 2013 10:40 AM
To: NT System Admin Issues
Subject: Occasional local admin needed

 

How would you guys handle this? I have a server that the developers use
that they occasionally (once a month or so) need local admin access for
to install/upgrade an app or feature they use. This is a new-ish server
that previously I have just added a user (it's the same one each time)
to the local admin group then a week later took them out, but that's
cumbersome and I become the single point of failure on remembering to
back them out.

 

I could 1. create a special AD account for this user to be local admin,
or 2. create an  AD group, put this person in it, then GPO that group
into local admins on that server.

 

Suggestions?

David Lum 
Sr. Systems Engineer // NWEATM
Office 503.548.5229 // Cell (voice/text) 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 listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: Occasional local admin needed

2013-01-04 Thread Tim Vander Kooi
That is what we do for users who have these types of needs.
TVK

From: Brian Desmond [mailto:br...@briandesmond.com]
Sent: Friday, January 4, 2013 9:54 AM
To: NT System Admin Issues
Subject: RE: Occasional local admin needed

How about you create an AD Group, nest the AD group in local admins, and add 
the relevant users? GPOs and extra accounts for a dev box like this sounds like 
substantial unnecessary overhead.

Thanks,
Brian Desmond
br...@briandesmond.commailto:br...@briandesmond.com

w - 312.625.1438 | c - 312.731.3132

From: David Lum [mailto:david@nwea.org]
Sent: Friday, January 4, 2013 9:40 AM
To: NT System Admin Issues
Subject: Occasional local admin needed

How would you guys handle this? I have a server that the developers use that 
they occasionally (once a month or so) need local admin access for to 
install/upgrade an app or feature they use. This is a new-ish server that 
previously I have just added a user (it's the same one each time) to the local 
admin group then a week later took them out, but that's cumbersome and I become 
the single point of failure on remembering to back them out.

I could 1. create a special AD account for this user to be local admin, or 2. 
create an  AD group, put this person in it, then GPO that group into local 
admins on that server.

Suggestions?
David Lum
Sr. Systems Engineer // NWEATM
Office 503.548.5229 // Cell (voice/text) 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 
listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com
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 
listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Occasional local admin needed

2013-01-04 Thread Steve Kradel
The restricted group GPO won't take effect on the regular refresh
schedule, because the GPO itself will not have changed... IIRC it will
take closer to one day to notice that the once-compliant local group
is out of whack.

I think I'd just use a domain group nested into the machine's
builtin\administrators, and make sure to set a reminder to clear that
group after a little while.  Of course that's still assuming the users
won't give themselves extra access in the meantime.

--Steve

On Fri, Jan 4, 2013 at 11:42 AM, Crawford, Scott crawfo...@evangel.edu wrote:
 Better suggestions have already been given, but I’ll throw this out as a
 possibility. Use restricted groups in a GPO to set who should normally be an
 admin. Then when the dev needs admin, add them to the administrators group
 on the local machine.  Once they’re logged in, they’ll have the admin SID in
 their token and will be able to stay logged in as long as necessary.  But,
 within 45 minutes, the GPO refreshes and removes them from the group.



 From: David Lum [mailto:david@nwea.org]
 Sent: Friday, January 04, 2013 9:40 AM


 To: NT System Admin Issues
 Subject: Occasional local admin needed



 How would you guys handle this? I have a server that the developers use that
 they occasionally (once a month or so) need local admin access for to
 install/upgrade an app or feature they use. This is a new-ish server that
 previously I have just added a user (it’s the same one each time) to the
 local admin group then a week later took them out, but that’s cumbersome and
 I become the single point of failure on remembering to back them out.



 I could 1. create a special AD account for this user to be local admin, or
 2. create an  AD group, put this person in it, then GPO that group into
 local admins on that server.



 Suggestions?

 David Lum
 Sr. Systems Engineer // NWEATM
 Office 503.548.5229 // Cell (voice/text) 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 listmana...@lyris.sunbeltsoftware.com
 with the body: unsubscribe ntsysadmin

 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
 ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/  ~


~ 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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin