Domain Name Change: What will happen?

  • Our NT domain was set up years ago, and incorrectly named (companyName_NT). We are preparing to correct this so we can upgrade our Exchange and other servers. The new name will be companyName, with no _NT.

    Our SQL servers are set up to use NT authentication, and permissions and db ownerships are all based on the domain name which is going to change.

    My question is, what will happen when the name change takes place? I can re-assign permissions, but I'm concerned that the db's which have ownership using the old domain will not see my new domain account as the owner of the db's.

    E.g. the ownership is currently companyName_NT\mylogin, and my account will change to companyName\mylogin.

    Any assistance would be greatly appreciated, as they're planning on doing the change this coming weekend.

    Thanks.

  • quote:


    Our SQL servers are set up to use NT authentication, and permissions and db ownerships are all based on the domain name which is going to change.


    1. Set SQL Server authentication mode SQL server and Windows.

    2. Change SQL Server service accounts to local system account.

    3. Change the ownership of all your database to 'sa'.

    4. Create database role and assign proper permissions to access database. Once domain name chaged, you only need to add new domain logins to the role.

    5. Review all DTS packages, Jobs, SQL Server mail and SQL Agent Mail, Linked servers, log shipping and replications if they are owned by a domain login.

  • Allen,

    Thanks, sounds like I'll be busy after all this weekend....

  • Are they renaming the domain (using the KB article) or are they doing a side-by-side move to a domain with the proper name?

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    K. Brian Kelley
    @kbriankelley

  • Brian,

    I am in the process of finding out. What difference, if any, would this make?

    Thanks

  • If they renamed the domain (there's a KB article, it's at your own risk, etc), the SIDs I believe remain the same. If they go the other route, they're probably going to create a full trust (2-way trust) relationship between the two, which means user accounts and resources can go back and forth. That buys you some time.

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    K. Brian Kelley
    @kbriankelley

  • They're planning on renaming the domain (kb article 178009)

  • Allen's checklist is your only safe path, then. It's a lot of work, but absolutely necessary.

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    K. Brian Kelley
    @kbriankelley

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply