At.exe Service Account - scripted or registry?
From: ATarasul@SpencerStuart.com
Date: 01/24/03
- Previous message: matthew patton: "RE: Bypass Traverse Checking?"
- Next in thread: ATarasul@SpencerStuart.com: "RE: At.exe Service Account - scripted or registry?"
- Maybe reply: ATarasul@SpencerStuart.com: "RE: At.exe Service Account - scripted or registry?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 24 Jan 2003 12:36:06 -0600 From: <ATarasul@SpencerStuart.com> To: <focus-ms@securityfocus.com>
There is a trick to set "AT Service Account" to existing account , but
wrong dummy password - front end validation validate only account name.
In this case jobs scheduled with "at" - assuming attacker managed to run
at - will not be able to execute.
Any idea how to do this in script or by writing to registry to
distribute through template/policy?
Thanks
Alexander
Microsoft How-to is:
Open Control Panel and double-click Scheduled Tasks.
In the Scheduled Tasks window, open the Advanced menu and then choose AT
Service Account.
Click This Account and specify a particular user and password. Click OK.
- Next message: Hall, Randy: "RE: Bypass Traverse Checking?"
- Previous message: matthew patton: "RE: Bypass Traverse Checking?"
- Next in thread: ATarasul@SpencerStuart.com: "RE: At.exe Service Account - scripted or registry?"
- Maybe reply: ATarasul@SpencerStuart.com: "RE: At.exe Service Account - scripted or registry?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|