[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


migrate files from one domain to another

Posted on 2005-04-25
Medium Priority
Last Modified: 2012-06-21
I fully configured and built a fresh new Window Server 2003 standard on brand new hardware.  It is a domain controller with a domain name of ultranew.com.  I need to migrate files to this new server from an NT 4.0 file server that resides in a NT4 domain called box.com.  

Active Directory and DNS are running on the ultranew.com 2003 server, I did not install DHCP nor did I set a default gateway in the network card's TCP/IP Properties.  The old NT domain "box.com" has DHCP, DNS and users running.  My question is if I connect the new 2003 domain controller to the network so that I can migrate files will this cause problems for my users?

I'm assuming it wouldn't because all the user computers are part of the box.com domain and dhcp points them to box.com.  But I just want to make sure my users can't accidently connect to the new server's domain until it's ready.  Is there any way this could happen?
Question by:bboy77
  • 3
  • 2

Accepted Solution

JimsZ earned 1400 total points
ID: 13860501
you shouldn't have any issues.  The only issues you should have would be for the users to have open files, etc while you were trying to copy them.

Author Comment

ID: 13860796
Thanks for the reply. I also realized something else.  The old NT domain "box.com" does not run DNS services.  It uses the ISPs DNS servers.  The problem is we have a web site on the Internet with a dns record of "ultranew.com" also.  When I run ipconfig /all on one of the client's connected to the box.com domain I get something like this.

 Host Name . . . . . . . . . . . . : computer3   ----> this client is part of the box.com domain
 Primary Dns Suffix  . . . . . . . :
 Node Type . . . . . . . . . . . . : Unknown
 IP Routing Enabled. . . . . . . . : No
 WINS Proxy Enabled. . . . . . . . : No
 DNS Suffix Search List. . . . . . : ultranew.com

t adapter Local Area Connection:

 Connection-specific DNS Suffix  . : ultranew.com
 Description . . . . . . . . . . . : 3Com  1
 Physical Address. . . . . . . . . : 01-01-0c-78-1A-12
 Dhcp Enabled. . . . . . . . . . . : Yes
 Autoconfiguration Enabled . . . . : Yes
 IP Address. . . . . . . . . . . . :   ---> client ip address
 Subnet Mask . . . . . . . . . . . :
 Default Gateway . . . . . . . . . :         ------>router gateway ip address
 DHCP Server . . . . . . . . . . . :      -------> the main windows nt PDC
 DNS Servers . . . . . . . . . . . :           ----> Our ISPs DNS servers

The part that concerns me is the Connection-specific DNS Suffix  portion ultranew.com.  That's actually the name of the new domain on the windows 2003 server that I am migrating to.  Are these DNS settings going to screw things upo when I plug the new server on the network.

I really appreciate  your comment thus far.  If this will work. Itsaves me a lot of time.  I don't have to wait until the weekend to bring the server out of production and then start the migration.

(I'm substituting fake names for the domain names btw).

Expert Comment

ID: 13860913
is the new domain controller running dns then ?  That may be a portion of why it picked up that dns server.  Another thing is do you already have a trust set up, etc ?  With the DNS setup, unless you have users on that domain, there is no way for them to access that domain without some kind of user/trust setup or network shares.

Author Comment

ID: 13860990
The new domain controller is running DNS with the domain name ultranew.com and it's not plugged into the network yet.  I don't have any trusts set up, and I'm pretty sure I don't want to.  All I want to copy over is files.  I don't want to transfer  dns zones, accounts, global catalog etc.  

I think the client picked up the host name dns suffix from the ISPs dns servers.  Our ISP dns servers point to the company website ultranew.com which is hosted by a 3rd party completely separate from the network in question.

thanks again, really helpful info.  I'm thinking this is going to work.

Author Comment

ID: 13869640
Tried it out today, worked like a charm.  Set my windows 2003 server network connections to automatically pick up an IP address and didn't give it a default gateway.  It didn't interfere with users work on the box.com domain.

Migrated all the data without a hitch!!

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I don't know if many of you have made the great mistake of using the Cisco Thin Client model with the management software VXC. If you have then you are probably more then familiar with the incredibly clunky interface, the numerous work arounds, and …
In this article we will discuss all things related to StageFright bug, the most vulnerable bug of android devices.
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…
Hi friends,  in this video  I'll show you how new windows 10 user can learn the using of windows 10. Thank you.
Suggested Courses

834 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question