Deleting BUILTIN\Administrators

From: Ricky Artigas (rya@easycall.com.ph)
Date: 11/29/02


From: "Ricky Artigas" <rya@easycall.com.ph>
Date: Thu, 28 Nov 2002 21:58:46 -0800


Hi, Sonya. Did you say it bounced back to the original
setting? You probably don't have the correct permissions
set on the registry. You can change it from the EM but
when the EM tries to write it to the registry, it
couldn't write it probably due to incorrect permissions
on the registry. Make sure that the sql server account
has permissions to write to the registry, at least on the
sql server section(s).

HTH. ;o)

>-----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: Problems with SQL Srv. Agent and Proxy Account
    ... I have tried with both the sa account and with Use Windows ... Authentication on the SQL Server AGent Connection tab. ... >>rights recording to INF: Reset Proxy and the ...
    (microsoft.public.sqlserver.security)
  • 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: Problems with SQL Srv. Agent and Proxy Account
    ... You need to go to the General Tab of the SQL Server Agent ... >I have tried with both the sa account and with Use Windows ...
    (microsoft.public.sqlserver.security)
  • 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)