asked on

SQL and dcpromo

How is the best way to stage a SQL server that will be a domian controller. In other words, how should I handle the security, since I will be setting it up on a standalone, and making it a DC when it is finished. No, I can't wait until the deployment is finished to load SQL.

miron

For the install / dcpromo it does not matter. Beware, if you allow SQL authentication and run SQL Server under domain admin - what is usually happening, entire domain security will depend on a SQL Server. Using Windows Authentication for this SQL Server exclusively seems a prudent way of action.

jg733

ASKER

Thanks for the reply. If I understand you right, I can set it up for Windows Authentication, create my image of the server, run DCpromo, and then change the SQL servive accounts to report to the domain level?

Forgive me, I'm kinda green at SQL.

miron

Yes, averything you intent todo should be straightfoward. Image though need to be done before you join any domain, to have a sure re - store from it. You would not need to worry about changing account if you set SQL Server to run under account called local system account in services.msc applet, but it is better to take this extra step and set SQL Server to run under domain account. And yes again, try to keep authentication on SQL Server Windows only. When dcpromo finishes, you will re - boot and SQL Server, if left to run under old domain user account will report errors in the event log. If you would like to avoid those ( which is alwais look nice ) set the SQL Server to start manually in the services.msc panel. This way you will have a sure grip on re - starting SQL Server and related services - Distributed Transaction coordinator, SQL Server Agent, and Microsoft SQL Server upon completion of dcpromo and following machine re - start.

ASKER CERTIFIED SOLUTION

miron

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial