Re: Protecting Administrator Account Concern.
From: Daniel (idaniel99_at_hotmail.com)
Date: 11/16/04
- Next message: Frank McCallister SBS MVP: "Re: Migrating SBS2003 to new server hardware"
- Previous message: Frank McCallister SBS MVP: "Re: Installation problems -please help"
- In reply to: Michael Jenkin [SBS-MVP]: "Re: Protecting Administrator Account Concern."
- Next in thread: Henry Craven: "Re: Protecting Administrator Account Concern."
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 15 Nov 2004 21:31:43 -0800
Thank you both for your replies. Michael if you remember the link to that
site pls let me know.
Regards,
Daniel
"Michael Jenkin [SBS-MVP]" <michael.jenkin@mvps.org> wrote in message
news:eD9bxPvyEHA.2876@TK2MSFTNGP12.phx.gbl...
> Hello,
>
> My expeariance is the SQL admin tools need access to specific registry
> keys and files during the run time. I saw a great demo where you can run
> SQL as a guest. You run regmon from sysinternals to see what registry
> keys are accessed and then regedt32 to allow the SQL product access to
> these keys. Then run filemon from sysinternals and make sure the ntfs
> permissions on the files is ok to run as guest. You can then start the
> SQL services and restart as guest and then actually administer the
> server without being an admin.
>
> I don't have a link to a site where someone explains this full process
> but hopefully this will jog someones mind and they will show you to an
> article relating to this.
>
> Thanks
>
> Daniel wrote:
>
>> An SBS2k3 Premium has been successfully configured for one of our clients
>> that is in a process of upgrading from NT4. This company has an SQL
>> database, therefore another instance was created (SharePoint already on
>> SQL2k) to which the company's developer has full rights under a domain
>> power
>> user account. He was given even the SA password and registries edited for
>> Network Client Utility
>> http://sqljunkies.com/Newsgroups/microsoft.public.sqlserver.security/2004/4/22/184292.aspx
>>
>> The Developer demands administrative rights over the SBS server to be
>> able
>> to work with his SQL instance, but that's against Microsoft's
>> recommendations for Security Best Practice. Obviously we are concerned
>> about the other SBS technologies, and the entire network integrity as he
>> already managed to bring down TrendMicro (the server is not in production
>> yet).
>>
>> As I'm not an SQL expert, is there a need for the developer to have
>> administrative rights over the server just because of this SQL instance?
>>
>>
>>
>> Your input is very much appreciated.
>>
>> Daniel
>>
>>
>>
>>
>
> --
> Michael J. Jenkin MVP - SBS, Senior Systems Engineer
> Visit http://www.mickyj.com
>
> Microsoft Most Valued Professional, Microsoft's Windows Server Systems -
> Small Business Server
> MVP's do not work for Microsoft. If this email was generated in a
> newsgroup, please reply only to the newsgroup.
> Note: The contents of my postings and responses here represent my
> personal opinions and do not necessarily reflect the views, thoughts or
> feelings of Microsoft or any of its employees.
> http://mvp.support.microsoft.com
>
>
- Next message: Frank McCallister SBS MVP: "Re: Migrating SBS2003 to new server hardware"
- Previous message: Frank McCallister SBS MVP: "Re: Installation problems -please help"
- In reply to: Michael Jenkin [SBS-MVP]: "Re: Protecting Administrator Account Concern."
- Next in thread: Henry Craven: "Re: Protecting Administrator Account Concern."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
