Deleting BUILTIN\Administrators

From: Martín (marcospaz60@hotmail.com)
Date: 11/28/02 

From: Martín <marcospaz60@hotmail.com>
Date: Thu, 28 Nov 2002 06:29:18 -0800

Sonya,

That it was happened because the SQLServerAgent Service,
it was running with the Loca System Account. If you delete
the BUILTIN login account, and the Agent is running with
some domain account, the service wouldn´t longer.

>-----Original Message-----
>On the advice of "Admin 911 SQL Server 2000"
>(Osborne/McGraw-Hill 2001), I deleted my
>BUILTIN\Administrators account (an alleged security risk),
>and set the SQL Server login account to a domain user
with
>system admininistrator rights. The author warned that
the
>SQL Server Agent would no longer start if the service was
>being started with the sa account, and I made sure that I
>followed his directions to change it to a domain user
with
>sysadmin rights. I stopped and started SQL Server, but
>the SQL Server Agent wouldn't restart. After a short
>panic period and a few different attempts to resolve the
>problem, I was able to get the SQL Server Agent going
>again. I first re-entered the BUILTIN\Administrator
>account, but that still did not allow me to restart the
>SQL Server Agent. I was finally able to restart SQL
Server
>Agent by going into the Services folder and restarting it
>from there. So, I'm back where I started from, but I
>probably aged considerably in the process. :-)
>
>I suspect that the difficulty I encountered was due to
the
>fact that I am operating in Mixed Mode, and, even though
>the Admin 911 author didn't specify, the directions he
>gave were likely for operating in a Windows Only Mode.
>However, I'm not even sure about that theory. I did try
>the process out on my personal edition (which is also set
>up in Mixed Mode)of SQL Server 2000 prior to making the
>change on our standard edition, and the author's
>instructions worked perfectly there.
>
>One other odd thing that I noticed is that, try as I
>might, I was not able to successfully reset the SQL
Server
>login to the desired domain account (with sysadmin
>rights). It would accept the assignment I gave it, but
>upon re-inspection, the account would always bounce back
>to sa.
>
>Any comments would be greatly appreciated.
>
>Thanks,
>
>Sonya
>.
>

Relevant Pages

  • RE: DTS Package fails when Scheduled
    ... Make sure SQL Server Agent account has the correct rights/permissions. ... scheduled job under this context, I still received the error, even though I ...
    (microsoft.public.sqlserver.dts)
  • Re: cant find directory when package scheduled as job
    ... the batch file to map the drive. ... from the DTS designer but fails when it is scheduled as a SQL Server Agent ... under my windows account and the packages executes correctly when run via ...
    (microsoft.public.sqlserver.dts)
  • Re: HELP!! SQL Server Agent not working.
    ... Some things to check - Are you running SQL Server in fiber ... >changed the SQL SERVER SERVICE account to use a Local NT User account ... >configuration for SQL SERVER AGENT was also done in Enterprise Manager. ...
    (microsoft.public.sqlserver.security)
  • Re: Browsing for Publication error message
    ... what is going on with the description you gave previously but I would guess that the subscriber SQL Server Agent service account was somehow added to the publication access list of the publication on the DMZ. ... select from the MSpublication_access table in the distribution database and see if the account for your Subscriber's SQL Server Agent service account shows up. ...
    (microsoft.public.sqlserver.replication)
  • Re: Problems with SQL Srv. Agent and Proxy Account
    ... Windows Account. ... SQL Server Agent, try adding this account to the local ... >Password verification of the 'SQLAgentCmdExec' proxy ...
    (microsoft.public.sqlserver.security)