Possible back door?

Hi I'm new to SQL and I've been asked to help my company with this server
(Windows 2003). Some history of what is going on is that the company is not
happy with their current tech situation and are in the process of getting
rid of their current tech and he knows it. This is where I come in like I
said have been asked to help with this situation. But I'm located at
different location so one of the first things the company wanted me to do is
setup an link between My loction and the other location using the internet.
So my first steps before opening up the the company was to try and secure th
e
system. But what I found is that the current tech is login in to the system
with an account called "sqlagentcmdexec" and on this account there is no
password (In my mind a big problem becauce I think this account was setup
with admin privileges). So when I was checking out the current user list and
their privileges this account in question was not there with all of the othe
r
accounts. I found a coulpe of articles that tells me a little about the
account but not a whole lot. So with all of that in mind what should I try t
o
do? Can I add a password to this account? Can I Find out what the account
privileges are and lower them if the are admin? If it is possible to lower
the account privileges what might be some of the side effects? Could there
be similar hiden accounts on this system and finally what would the best
thing to do in this situation?
Thank you for your time and help!What SQL Server version is used at this company?
I don't think such an account is created in the last two versions of SQL
Server : 2000 and 2005. It might be left from an older SQL Server
installation.
The following KB article has some information on this account:
http://support.microsoft.com/?id=264155
You could also ask for more information on the SQL Server Tools forum:
http://forums.microsoft.com/MSDN/Sh...ID=84&SiteID=1. You can
find answers about SQL Agent topics there.
Thanks
Laurentiu Cristofor [MSFT]
Software Design Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"josh" <josh@.discussions.microsoft.com> wrote in message
news:F389E9E2-9716-4C26-8DC3-BADBFFFE810B@.microsoft.com...
> Hi I'm new to SQL and I've been asked to help my company with this server
> (Windows 2003). Some history of what is going on is that the company is
> not
> happy with their current tech situation and are in the process of getting
> rid of their current tech and he knows it. This is where I come in like I
> said have been asked to help with this situation. But I'm located at
> different location so one of the first things the company wanted me to do
> is
> setup an link between My loction and the other location using the
> internet.
> So my first steps before opening up the the company was to try and secure
> the
> system. But what I found is that the current tech is login in to the
> system
> with an account called "sqlagentcmdexec" and on this account there is no
> password (In my mind a big problem becauce I think this account was setup
> with admin privileges). So when I was checking out the current user list
> and
> their privileges this account in question was not there with all of the
> other
> accounts. I found a coulpe of articles that tells me a little about the
> account but not a whole lot. So with all of that in mind what should I try
> to
> do? Can I add a password to this account? Can I Find out what the account
> privileges are and lower them if the are admin? If it is possible to lower
> the account privileges what might be some of the side effects? Could
> there
> be similar hiden accounts on this system and finally what would the best
> thing to do in this situation?
> Thank you for your time and help!|||To add to Laurentiu's response, the local SqlAgentCmdExec account is created
during a SQL 7 install for use as the SQL Agent Proxy account. The password
should not be blank and is managed entirely by SQL Server. You can reset
the account password from Enterprise Manager per the article link Laurentiu
provided.
Hope this helps.
Dan Guzman
SQL Server MVP
"josh" <josh@.discussions.microsoft.com> wrote in message
news:F389E9E2-9716-4C26-8DC3-BADBFFFE810B@.microsoft.com...
> Hi I'm new to SQL and I've been asked to help my company with this server
> (Windows 2003). Some history of what is going on is that the company is
> not
> happy with their current tech situation and are in the process of getting
> rid of their current tech and he knows it. This is where I come in like I
> said have been asked to help with this situation. But I'm located at
> different location so one of the first things the company wanted me to do
> is
> setup an link between My loction and the other location using the
> internet.
> So my first steps before opening up the the company was to try and secure
> the
> system. But what I found is that the current tech is login in to the
> system
> with an account called "sqlagentcmdexec" and on this account there is no
> password (In my mind a big problem becauce I think this account was setup
> with admin privileges). So when I was checking out the current user list
> and
> their privileges this account in question was not there with all of the
> other
> accounts. I found a coulpe of articles that tells me a little about the
> account but not a whole lot. So with all of that in mind what should I try
> to
> do? Can I add a password to this account? Can I Find out what the account
> privileges are and lower them if the are admin? If it is possible to lower
> the account privileges what might be some of the side effects? Could
> there
> be similar hiden accounts on this system and finally what would the best
> thing to do in this situation?
> Thank you for your time and help!