Server migration -NT to AD domain

pts.
Tags:
Microsoft Windows
I have a windows 2000 production server that is still hanging around in our old windows NT domain. I will have to migrate this server to win2k3 domain before I decommission the domain. The server hosts production web (business objects)it runs IIS5.0. The vendor has advised us to go ahead with the migration as there is no issue with business objects. I would like to know if there is a general checklist (microsoft point of view)that I should know before I migrate the server. All users are in AD and there is a trust between NT and AD domain. Thank you

Answer Wiki

Thanks. We'll let you know when a new response is added.

I’m not aware of any MS checklist, but since the server is not a domain controller and your web application vendor will support it under W2K3 AD domain, I don’t see any problems with migrating it to AD.
However, as a pre-cautionary measure, if possible, I would image the server (using Ghost, etc.) and get some type of guarantee in writing from your application vendor.

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Invisflare
    The scenario looks relatively safe to me. Just make sure all service accounts are from new domain (if not local System). Your business objects vendor said it's OK; that probably only means their stuff supports 2003 AD. It's still up to you to make sure not a single authentication is based on the old domain in all settings. Otherwise you may have a breakdown after migrating. MS has a ADMT for domain migration/upgrading. That's mainly for moving users and groups, which looks unnecessary for your case.
    0 pointsBadges:
    report
  • Petroleumman
    Hello, I would say your biggest concerns are going to be with IP. Your going to need to assign new IP addressing to the website, update DNS records (internal and external) etc. I would make a list of my current settings and pre-configure as much as possible ahead of time to try to limit downtime. The rest is pretty striagt forward, just add it to the new domain as you would a new server and turn it on. Good luck!
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following