Re: Windows Server 2008 w/Exchange 2007 Authentication on Active D

Alright, sounds good,

Here's my first question. Server #2 and #3 are truly going to be placed
into production, eventually. Server #1 is not. I was just using server #1
for this test.

So, my question is, if I setup Sever #1 as the 2nd DC with DNS, as you said,
if once this test phase is complete, can i remove Server #1 from the
equation, and replace it with another server, and just setup that server as
we did with Server #1? Or will there be conflicts doing it that way?

I definitely agree and will setup 2 DC's, anything to help with failover, or
reducing IT time spent on fixing issues during production is a major plus.


My 2nd Question is,
Can I re-install the active directory service and fix the name of the
server? To something such as:

Server #2 (glv-dc-01) - primary AD/DC/DNS server
Server #1 (glv-dc-02) - secondary DC/DNS server
Server #3 (glv-mx-01) - exchange server

Because, I would rather fix the naming issues now, while these servers are
in their testing phase and not in production.

I will be working on this all this week, so I will be posting a lot, I thank
you both for all your help, and hope that I can complete this soon..

Thanks,
MIKE











"Ace Fekay [MVP Direcrtory Services]" wrote:

In news:C6C87653-DF07-4DAF-9AA5-C1969946A6D8@xxxxxxxxxxxxx,
netadmin07 <netadmin07@xxxxxxxxxxxxxxxxxxxxxxxxx> requesting assistance,
typed the following:
Ok.

Current status:
I removed server #1, because the other rep (Meinolf Weber),
recommended running our DNS on the same server our Active Directory
is running on. So, this is the route I took. I started from
scratch, reinstalled the OS's and at this time I have DNS, DHCP and
Active Directory all running on server #2. We don't really care about
the DHCP server, because we can run that separately, if need be. But
if it will work on the same server, then that is fine too.

I have only installed the OS on server #3, i have not started the
Exchange installation yet.

We are now using the Integrated DNS domain recommended by the other
rep.
We are planning on have 2 DCs, but we were planning on using a
different server for the 2nd DC. Can this 2nd DC be installed at a
later time? Or will that not work?

Server #3 will be solely for Exchange. Yes.





Should we move forward now with the NetDiag... And complete the
install??? Thanks.

MIke


Hi Mike,

Sure, I would always run a "netdiag /v /fix > c:\netdiag.txt" and review the
outpuyt file at that location for any errors. On a DC, I would suggest
"dcdiag /v /fix > c:\dcdiag.txt" and look at that file for any errors.

I'm glad you followed Meinolf's recommendations. In many cases we all try to
collaborate to work together.

Here are my suggestions:

Rename the server you will be using for Exchange to something more
descriptive of it's role, such as (just a suggestion) change it from
WIN-1OP2FOIXLI1 to glv-mx-01. Of course 'glv' is descriptive of the
organization, "mx" I like to use to describe it as a mail server, and '01'
to signify that it is the first of many. Not that you will ever install
another one, but this is a matter of choice on my part because I handle many
clients and knowing their names and such, the machine will come to mind in a
split second. It also adds continuity to your organization's machine naming
structure. For example, desktops would be (suggestion) glv-dafekay (d for
desktop, and my username), and a laptop would be glv-lafekay. You can also
use the machines asset tag, which in a larger org with lease swaps, machine
upgrades, and increased security, would be more appropriate. These are just
suggestions.

As for server1, I would *definitely* recommend this guy to be a domain
controller. Why? It is highly recommended in any domain to have a minimum of
two DCs. This way if you lose one, you still have your domain config and all
user, group and other objects and the company can continue to move on while
fixing the other one. If you only have one, you will have a huge headache
and will drastically cut into your drinking time. ;-)

I would also suggest to rename server1 to glv-dc-01. You can't rename
server2 because it is already a DC.

That said, I would then procede to run dcpromo on server1 and make it a DC.
Make sure DNS is installed. Make sure DNS is pointed to only server2 until
completed. Once completed and after it's been restarted, change the DNS
entries so server 1 will have server2's IP in the first DNS spot, and itself
as second. Same goes with server2. Make server1 first, and itself second.
Since this is only one domain, I would make both DCs GCs.

You can run DHCP on either DC if you want without problems.

Then I would join server3 to the domain. Once joined, follow Meinolf's
instructions to install Exchange. Keep in mind it will be running a
domainprep in the background, so it must be run with elevated privledges
using the domain administrator account.

Oh, and on server1 and server2, if there are additional NICs, if you do not
plan on teaming them, disable the unused one or it will cause additional
errors and headaches with Active Directory. Same with the Exchange server.
Only use one unless you plan on teaming. Teaming requires the NIC
manufacturer's drivers. You can look into this later if you want.

Ace


.

Relevant Pages

  • Re: AD/DNS/DHCP - Upgrading Windows 2000 to Windows 2003
    ... Exchange is a member now and in total we got 2 DCs. ... exchange ios on a DC to install it on a member server? ... On the old server open DNS management console and check that you ... Install the new machine as a member server in your existing ...
    (microsoft.public.windows.server.migration)
  • Re: AD/DNS/DHCP - Upgrading Windows 2000 to Windows 2003
    ... Exchange is a member now and in total we got 2 DCs. ... exchange ios on a DC to install it on a member server? ... On the old server open DNS management console and check that you ... Install the new machine as a member server in your existing ...
    (microsoft.public.windows.server.migration)
  • Re: E2K3 SP2 + IMF -> SMTP Outbound reports errors if no smart host is set
    ... the mail could queue at the smarthost server. ... > install IMF v1 after you have installed SP2, your IMF may break and yes, I ... >> I have an Exchange 2003 server running SP2. ... >> 2) I've manually walked the DNS queries that Exchange should be executing ...
    (microsoft.public.exchange.connectivity)
  • Re: Urgent question about 2 domains/5.5-2003 migration!!!!
    ... Make sure you have DNS, ... Your 5.5 server and W2k3 DC point ... Run through the Exchange Deployment Tools To Install and move to the new ...
    (microsoft.public.exchange.setup)
  • Re: Exchange on VMWare
    ... controller is using itself for DNS resolution. ... Check to be sure that your virtual member server is also using your vm dc ... However when i install exchange on the member server it cannot find the ...
    (microsoft.public.exchange.setup)
Loading