Infrastructure migration to a new Domain. Joining TS and SQL
Posted on 2007-03-31
I need some expert help with some Infrastructure migration.
I have a client that refuses to spend money on there Network. They have a Break/Fix mind set. The only time they spend money on there network is when it breaks and production stops. That mind set has led to a Patch work style network held together with gum, and super glue. 
Well something has broken, and now they need to fix it. I want to use this opportunity to improve there Network Infrastructure as much as possible.
Here is what they currently have.
• Win03 server. Function: Exchange03, File Server, Domain Controller, FSMO holder. This is the only server in this domain.
• Win2K server. Function: Terminal server, Domain Controller
• Win2K server. Function: Domain controller, FSMO holder, This is where a Trust Relationship is setup In-between the 2 domains.
• Win03 server. Function: Member server running SQL only. All the workstations (and terminal server) have a MAS500 client software installed.
I want to get all the servers on to one Domain and dissolve the other domain. All of the workstations are joined to DOMAIN1. They have there computers and desktops setup how they want it.
The Terminal server is broken and needs to be rebuilt from scratch. The SAGE (MAS500) software people have convinced my client that it’s not there software that is broken, and that the Terminal server needs to be rebuilt. I don’t fully agree with this, but the decision has been made and Ill use this opportunity to upgrade them to Win03 with the proper TS CAL’s.
Please critique my migration plan.
• On DOMAIN2 win2K Terminal Server: make this the FSMO holder. Setup a trust relationship in-between the 2 domains from here.
• Take the second Win2K server offline, format, install Win03, Join to DOMAIN1, configure as a New Terminal Server.
• Join SQL to the other domain
• Point the Firewall to the New Win03 Terminal Server.
• At this point The old Win2K terminal server will be the only server in DOMAIN2. Run DCpromo and dissolve this domain completely.
I know nothing about SQL. What risks are there in joining the SQL server to another domain? It will change the name of the server ( from sql.company.local to sql.BlaBlacompany.local) what impact will that have. Will that affect the MAS500 clients?
I know this may have been long but I wanted to be through.
Thank you for any help you can offer.