I am going to be upgrading an old NT4 Network to a new windows server 2003. We have already decided that we will not upgrade the NT4 box but just install the server as a new server and new accounts to save transferring any remaining faulty issues from the old NT4 box. So what we are going to do is install as a new domain and then migrate the 20 or so users all XP based to the new domain.
One thing that has given pause for thought reading the Microsoft associated articles and sites is what we call this domain. the exisiting NT4 domain is basically called COMPANY [as an example] on a box named ntserver. Now Micrososft claims that it should be a FQDN and so would suggest COMPANY.COM, but have been told that this could lead to problems.
The server acts as basically receiving emails run on mailenable, domain controller, anti virus updates, and file server. I have been told I should name it COMPANY.LOCAL but that could throw a few spanners re the MAC's we have, or can I just call it COMPANY, or do I have to work this out a bit more logically, ie COMPANY.OFFICE, or just plain COMPANY1 because of the NT4 box.
Pause for thought.