NW2468

I'm running a new install of Server 2008 and setting up a completely new domain. When it asks for FQDN, I'm putting in mail.company.com since that is what we have in our current SBS2003 server. (before we had company.local and were getting rejected by some ISPs) At the beginning of the wizard, I thought I remember it asking my to name the domain, which I typed company.local However, at the end of the wizard, it sums up everything and says: "The new domain name is mail.company.com. This is also the name of the new forest" "The NetBIOS name of the domain is MAIL" We want our domain name to be company.local, any idea why it defaults the name to the FQDN that we entered? Putting company.local as the FQDN isn't an option as it creates rejects. As for the NetBIOS name, I'm assuming it just picked that up from mail.company.com since I never typed MAIL anywhere. Any thoughts? Thanks for the help

We currently have a workgroup setup with a Windows 2003 server running SQL. We are moving to Exchange 2007 on Windows 2008 and would like to make that the primary Domain Controller. Can I then make the Windows 2003 (SQL) Server a DC as well? I read something about it would erase all local accounts if I did this - any truth to that? Would we need to do anything with the existing databases prior to making it a DC in the 2008 forest? Thanks for any advice

Bumping up to see if any more advice can be given, thanks for the help.

As far as subdomains go, would you just have abc.com registered with a 3rd party company, then the domain for the server could be server.abc.com but why would you need to give a domain name to both the DC and the Exchange server, are they both on separate domains? In our situation, since Exchange is running on the DC, would we just have a single domain (server.abc.com) and have other servers (i.e. File), printers join that domain?

It was a while ago, but I think the problem was when the laptop was off of the network and the user would try to login, it would say something about not being able to find the domain, so it wouldn't allow them to log into that windows user. So we had to create a second windows user so they could work at home (not dialing in on VPN, over their own network). I'll have to read up on sub domains to see how they work, thanks for the help so far!

Alright, so I have a bunch of issues to bring up and while I search around forums, if anyone can point me in the right direction for some of these things, that'd be great. We're planning a Server 08 install, running Exchange 2007. This will be a single domain controller as well as our single e-mail server. Domain Name We have a domain registered, let's call it company.com with a 3rd party company. My plan was to point the records to the public IP address of our server. Will it matter if the Domain name of the server is company.com as well? During a SBS 2003 Server install, when we tried naming the domain company.com, it wouldn't allow us, so we ended up naming it company.local Should the domain on the server be named the same as the domain we have registered through the 3rd party company, or are the two not related at all? Laptops The last time we attempted to run the company on a domain, we had problems with laptops accessing the domain and then being brought home. Users could not log into the Windows account they used at work, so we ended up having two Windows Accounts, one for work and one for home - which, needless to say, is extremely inconvenient. Can a windows user on a laptop login to the domain at work and login to the same exact id at home? Is there any configuration necessary to accomplish this? Printers We have printers installed throughout the office, some on servers, some on PCs (shared) etc. Would the best practice be to install all network servers on the Server 2008 machine to be authenticated through the domain? Thanks for the help!