It wouldn't be too hard to control this remotely with PowerShell, Orchestrator, or lots of other means.
Daniel Ratliff From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of it's mike Sent: Friday, October 18, 2013 12:51 PM To: scripting@lists.myitforum.com Subject: RE: [scripting] Temporary Local Admin rights We've had to do this, but the time window was measured in hours - admin access required for the afternoon to allow installation of some software or something like that. We had to rely on obfuscation - eg bury the sched task deep inside the scheduled tasks tree under an unlikely name. Still, as below, a tricky admin is hard to wall up completely. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com]<mailto:[mailto:listsad...@lists.myitforum.com]> On Behalf Of Kennedy, Jim Sent: Friday, October 18, 2013 9:28 am To: scripting@lists.myitforum.com<mailto:scripting@lists.myitforum.com> Subject: RE: [scripting] Temporary Local Admin rights Or the user could add another local admin account for later use. I would do it with restricted groups and set a calendar appointment for myself, if this is a one off. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of christopher.catl...@us.sogeti.com<mailto:christopher.catl...@us.sogeti.com> Sent: Friday, October 18, 2013 12:22 PM To: scripting@lists.myitforum.com<mailto:scripting@lists.myitforum.com> Subject: RE: [scripting] Temporary Local Admin rights ....... but realize that if you have admin rights you can just delete the task ;) The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
