all groups > sql server msde > september 2005 >
You're in the

sql server msde

group:

MSDE BUILTIN\Administrator lock down


MSDE BUILTIN\Administrator lock down Sam
9/18/2005 6:21:45 PM
sql server msde:
After purposefully removing the builtin\administrator from sql server on my
msde (msm based) installation I get the following error:

SQLServerAgent could not be started (reason: Unable to connect to server
'SERVER\INSTANCENAME'; SQLServerAgent cannot start).


Everything goes through well with the install but I cant start the sql
server agent service unless Builtin\Administrator. I've tried the following
manually ( didn't even work) and would love to avoid having to do it
programatically:

http://support.microsoft.com/default.aspx?scid=kb;en-us;283811&sd=tech

Basically has anyone been successfult at locking down msde by removing
builtin\administrator? I don't want users tampering with or viewing the
design of the application we are deploying. The installation went through
perfectly. But I get the following error when I let the sql service agent
auto start:

SQLServerAgent could not be started (reason: Unable to connect to server
'SERVER\INSTANCENAME'; SQLServerAgent cannot start).

Some one please help. I went through so much on getting MSDE to install and
configuring it to Autostart the service. I would appreciate other options
anyone may have on locking down MSDE and not having anyone with Windows
admin rights be able to get through to the MSDE install with Enterprise
Manager.

Re: MSDE BUILTIN\Administrator lock down Andrea Montanari
9/19/2005 12:43:40 PM
hi Sam,
[quoted text, click to view]

I was successfull with sp3, but, as you already pointed out, unfortunately
this article is no longer alligned with modifications applied with sp4.. and
you will no longer be able to start and run SQL Server and
the Agent only using the reported info..
I'm still trying troubleshooting it..
try "propagating" file permissions to all sub folders as described, as long
as assigning registry permissions as
HKLM\Software\Microsoft\MSSQLServer\Setup (READ)
HKLM\Software\Microsoft\MSSQLServer\MSSQLServer (FULL CONTROL)
for the account running SQL Server and
HKLM\Software\Microsoft\MSSQLServer\SQLSERVERAGENT (FULL CONTROL)
HKLM\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib\LastConnect
(FULL CONTROL)
HKLM\Software\Description\Microsoft\Rpc\UuidTemporaryData (FULL CONTROL)
HKLM\Software\Microsoft\MSSQLServer\Setup (READ)
HKLM\Software\ODBC\ODBC.INI (FULL CONTROL)
for the account running the Agent...
make those accounts member of the local sysadmins WinNT role

feedback is welcome :D:D

but i definitevely hope kb article 283811 get updated..
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply

AddThis Social Bookmark Button