SQL Agent won't start after sysprep

[Zoran]

Hi All,

after sysprep of an SQL 2005 the SQL Server Agent won't start as any other
account but Local System.

I did change the server's name to mach the windows server name:
check servername
select @@servername,serverproperty('machinename')
if both values are different then you need to
exec sp_dropserver 'oldservername'
exec sp_addserver 'newservername','local'

After that I did a restart of the whole server, no help.

If I add a domain account to the local admins group, and make the SQL
Server Agent run as that account, then it works. But I don't like idea of
having that account as the local admin.

Any ideas?

Any good articles on sysprep'ping the SQL 2005 and 2008?

Thank you in advance!

Regards
Zoran

[Uri Dimant]

What error? SQL Server Agent account should have an appropriate permissions
to perform different tasks such as for example BACKUP DATABASE to remote
comupter...

I have NOT seen offten users./clients have a SQL Server account member of
non-admin group

"Zoran" <ms....@pantic.dk> wrote in message
news:e1kWImbb...@TK2MSFTNGP04.phx.gbl...

[Zoran]

Hi Uri,

thank you for your input!

The error is:
        WMI Provider Error
        The process terminated unexpectedly. [0x8007042b]

 

I tried googling this, but there are a lots of inputs, related both to Windows Cluster and SQL. I tried something related to SQL (like changing the SAL server name), but there is obviously more to be done.

In Application Log I can see the following:
        Login failed for user 'OurDomain\sqlservice'. [CLIENT: <local machine>]
(but that is not the case, since the other SQL services are running under that account!)

There is also this one:
        SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).

 

Microsoft's Princip of Least Privilege is against logons being local admins on the server. In SQL 2008 by default the local admins aren't having admin rights in SQL server. And on the original server (the one that I cloned and sysprepped to get this new machine) everything works fine without the domain service account being local admin.

Regards,
        Zoran

"Uri Dimant" <ur...@iscar.co.il> skrev i en meddelelse news:eYcPTScb...@TK2MSFTNGP04.phx.gbl...

[Erland Sommarskog]

Zoran (ms....@pantic.dk) writes:
> In Application Log I can see the following:
> Login failed for user 'OurDomain\sqlservice'. [CLIENT: <local
> machine>]
> (but that is not the case, since the other SQL services are running under
> that account!)

But are both services configured with the same password?

Then again, that does not look like an error message from Windows, but
SQL Server. That is, the service account is not able to log into
SQL Server.

Log in to Windows as OurDomain\SqlService and try to connect to
SQL Server with Windows Authentication. My guess is that this will
fail.

--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx