Windows Server 2008 w/Exchange 2007 Authentication on Active Direc

  • Thread starter Thread starter netadmin07
  • Start date Start date
N

netadmin07

Guest
> We are setting up a new test LAN. These are brand new servers, and brand
> new
> installations of OS, AD, and Exchange, as well as, we are setting up a
> test
> DNS box for this test LAN.
>
> The main problem we are facing is:
>
> We install DNS on 1 box, then on another box we setup Active Directory
> with
> the Domain. We then create an Admin user and assign that user all the
> rights
> needed to administer the Exchange installation and management for
> Exchange.
> (member of the domain admin and schema admin groups in AD)
>
>
> However, it appears to be a permission issue, because when I try to run
> the
> setup utility to install Exchange with the account we setup - it errors
> out
> saying "Setup has encountered an error and has to close". But, if we use
> the
> local Administrator account, we do not get that error, and it starts
> installing, but fails at the prerequisite checks saying, "the account has
> to
> be logged onto the domain." "Unable to contact the domain" and so on. I
> have given the account we created on the domain full admin rights locally,
> as
> well as at the domain level, and added to all the necessary groups, but we
> still get the same issue.
>
> Server specs:
>
> Windows Server 2008 Enterprise (Exchange 2007), Dell 2950
> Windows Server 2003 Enterprise (Active Directory), Dell 1950
> Windows Server 2003 Enterprise (DNS, DHCP), Test Server
>
>
> At this point, I was planning on re-installing both OS's (the exchange and
> AD OS) and starting over.
>
> Thanks for any help,
> Mike
 
Re: Windows Server 2008 w/Exchange 2007 Authentication on Active Direc

Hello netadmin07,

For the installation part you have to run the setup from exchange with "run
as administrator", even if the account you created is in the domain admin
group. To install this you need elevated priviliges.

Just to get your setup correct:
1x 2003 member server as DNS server
1x 2008 Domain controller without DNS installed, personally i prefer to have
DNS installed with AD integrated zones on all my DC's
1x 2008 member server for exchange 2007, it has to be 2007 with SP1 to run
correctly on 2008.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


>> We are setting up a new test LAN. These are brand new servers, and
>> brand
>> new
>> installations of OS, AD, and Exchange, as well as, we are setting up
>> a
>> test
>> DNS box for this test LAN.
>> The main problem we are facing is:
>>
>> We install DNS on 1 box, then on another box we setup Active
>> Directory
>> with
>> the Domain. We then create an Admin user and assign that user all
>> the
>> rights
>> needed to administer the Exchange installation and management for
>> Exchange.
>> (member of the domain admin and schema admin groups in AD)
>> However, it appears to be a permission issue, because when I try to
>> run
>> the
>> setup utility to install Exchange with the account we setup - it
>> errors
>> out
>> saying "Setup has encountered an error and has to close". But, if we
>> use
>> the
>> local Administrator account, we do not get that error, and it starts
>> installing, but fails at the prerequisite checks saying, "the account
>> has
>> to
>> be logged onto the domain." "Unable to contact the domain" and so
>> on. I
>> have given the account we created on the domain full admin rights
>> locally,
>> as
>> well as at the domain level, and added to all the necessary groups,
>> but we
>> still get the same issue.
>> Server specs:
>>
>> Windows Server 2008 Enterprise (Exchange 2007), Dell 2950 Windows
>> Server 2003 Enterprise (Active Directory), Dell 1950 Windows Server
>> 2003 Enterprise (DNS, DHCP), Test Server
>>
>> At this point, I was planning on re-installing both OS's (the
>> exchange and AD OS) and starting over.
>>
>> Thanks for any help,
>> Mike
 
Re: Windows Server 2008 w/Exchange 2007 Authentication on Active D

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

What is the first step I should take? Install Exchange? OR Install Active
Directory?

I already have DNS and DHCP setup on the 1st server, but I have now
reinstalled the OS's on the 2nd and 3rd servers (Exchange and AD servers).

I assume, I will install Active Directory first.
Then I will install Exchange.

What about Prepare Active Directory and Domains? I read the article, but am
running the prepare/AD function on the Exchange server or the Active
Directory server?

I just need a start to finish guide or something... But every article I find
on Technet, or Microsoft says I have to follow some other article... I just
want to make sure I take the right steps in the right order.



Let me clear that up for you:

1st Server
DNS server - Win Svr 2003 Ent

2nd Server
Active Directory server - Win Svr 2003 Ent

3rd Server
Exchange 2007 sp1 server - Win Svr 2008 Ent x64





"Meinolf Weber" wrote:

> Hello netadmin07,
>
> For the installation part you have to run the setup from exchange with "run
> as administrator", even if the account you created is in the domain admin
> group. To install this you need elevated priviliges.
>
> Just to get your setup correct:
> 1x 2003 member server as DNS server
> 1x 2008 Domain controller without DNS installed, personally i prefer to have
> DNS installed with AD integrated zones on all my DC's
> 1x 2008 member server for exchange 2007, it has to be 2007 with SP1 to run
> correctly on 2008.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> >> We are setting up a new test LAN. These are brand new servers, and
> >> brand
> >> new
> >> installations of OS, AD, and Exchange, as well as, we are setting up
> >> a
> >> test
> >> DNS box for this test LAN.
> >> The main problem we are facing is:
> >>
> >> We install DNS on 1 box, then on another box we setup Active
> >> Directory
> >> with
> >> the Domain. We then create an Admin user and assign that user all
> >> the
> >> rights
> >> needed to administer the Exchange installation and management for
> >> Exchange.
> >> (member of the domain admin and schema admin groups in AD)
> >> However, it appears to be a permission issue, because when I try to
> >> run
> >> the
> >> setup utility to install Exchange with the account we setup - it
> >> errors
> >> out
> >> saying "Setup has encountered an error and has to close". But, if we
> >> use
> >> the
> >> local Administrator account, we do not get that error, and it starts
> >> installing, but fails at the prerequisite checks saying, "the account
> >> has
> >> to
> >> be logged onto the domain." "Unable to contact the domain" and so
> >> on. I
> >> have given the account we created on the domain full admin rights
> >> locally,
> >> as
> >> well as at the domain level, and added to all the necessary groups,
> >> but we
> >> still get the same issue.
> >> Server specs:
> >>
> >> Windows Server 2008 Enterprise (Exchange 2007), Dell 2950 Windows
> >> Server 2003 Enterprise (Active Directory), Dell 1950 Windows Server
> >> 2003 Enterprise (DNS, DHCP), Test Server
> >>
> >> At this point, I was planning on re-installing both OS's (the
> >> exchange and AD OS) and starting over.
> >>
> >> Thanks for any help,
> >> Mike

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

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

Hello netadmin07,

Install the domain controller first, again i would make this one DNS server
with AD integrated zones. If the DC is up and running use dcdiag and netdiag
to check for errors. If no errors, add the 2008 as a member server to the
domain and just insert the exchange disk. During the setup you have just
to follow the installation disk, it will start doing the complete domain
preparation for the exchange schema additions.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> What is the first step I should take? Install Exchange? OR Install
> Active Directory?
>
> I already have DNS and DHCP setup on the 1st server, but I have now
> reinstalled the OS's on the 2nd and 3rd servers (Exchange and AD
> servers).
>
> I assume, I will install Active Directory first.
> Then I will install Exchange.
> What about Prepare Active Directory and Domains? I read the article,
> but am running the prepare/AD function on the Exchange server or the
> Active Directory server?
>
> I just need a start to finish guide or something... But every article
> I find on Technet, or Microsoft says I have to follow some other
> article... I just want to make sure I take the right steps in the
> right order.
>
> Let me clear that up for you:
>
> 1st Server
> DNS server - Win Svr 2003 Ent
> 2nd Server
> Active Directory server - Win Svr 2003 Ent
> 3rd Server Exchange 2007 sp1 server - Win Svr 2008 Ent x64
>
> "Meinolf Weber" wrote:
>
>> Hello netadmin07,
>>
>> For the installation part you have to run the setup from exchange
>> with "run as administrator", even if the account you created is in
>> the domain admin group. To install this you need elevated priviliges.
>>
>> Just to get your setup correct:
>> 1x 2003 member server as DNS server
>> 1x 2008 Domain controller without DNS installed, personally i prefer
>> to have
>> DNS installed with AD integrated zones on all my DC's
>> 1x 2008 member server for exchange 2007, it has to be 2007 with SP1
>> to run
>> correctly on 2008.
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>> We are setting up a new test LAN. These are brand new servers, and
>>>> brand
>>>> new
>>>> installations of OS, AD, and Exchange, as well as, we are setting
>>>> up
>>>> a
>>>> test
>>>> DNS box for this test LAN.
>>>> The main problem we are facing is:
>>>> We install DNS on 1 box, then on another box we setup Active
>>>> Directory
>>>> with
>>>> the Domain. We then create an Admin user and assign that user all
>>>> the
>>>> rights
>>>> needed to administer the Exchange installation and management for
>>>> Exchange.
>>>> (member of the domain admin and schema admin groups in AD)
>>>> However, it appears to be a permission issue, because when I try to
>>>> run
>>>> the
>>>> setup utility to install Exchange with the account we setup - it
>>>> errors
>>>> out
>>>> saying "Setup has encountered an error and has to close". But, if
>>>> we
>>>> use
>>>> the
>>>> local Administrator account, we do not get that error, and it
>>>> starts
>>>> installing, but fails at the prerequisite checks saying, "the
>>>> account
>>>> has
>>>> to
>>>> be logged onto the domain." "Unable to contact the domain" and so
>>>> on. I
>>>> have given the account we created on the domain full admin rights
>>>> locally,
>>>> as
>>>> well as at the domain level, and added to all the necessary groups,
>>>> but we
>>>> still get the same issue.
>>>> Server specs:
>>>> Windows Server 2008 Enterprise (Exchange 2007), Dell 2950 Windows
>>>> Server 2003 Enterprise (Active Directory), Dell 1950 Windows Server
>>>> 2003 Enterprise (DNS, DHCP), Test Server
>>>>
>>>> At this point, I was planning on re-installing both OS's (the
>>>> exchange and AD OS) and starting over.
>>>>
>>>> Thanks for any help,
>>>> Mike
 
Re: Windows Server 2008 w/Exchange 2007 Authentication on Active D

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

Ok.
I followed your steps, we received the following errors while running dcdiag:

Starting test: systemlog
An Error Event occured. EventID: 0x00000411
Time Generated: 09/18/2008 13:59:53
Event String: The DHCP service is not servicing any clients
An Error Event occured. EventID: 0x825A0011
Time Generated: 09/18/2008 14:03:12
Event String: Time Provider NtpClient: An error occurred during
An Error Event occured. EventID: 0x825A0011
Time Generated: 09/18/2008 14:03:31
Event String: Time Provider NtpClient: An error occurred during
An Error Event occured. EventID: 0xC25A001D
Time Generated: 09/18/2008 14:03:31
Event String: The time provider NtpClient is configured to
An Error Event occured. EventID: 0x825A0011
Time Generated: 09/18/2008 14:05:55
Event String: Time Provider NtpClient: An error occurred during
An Error Event occured. EventID: 0x00000423
Time Generated: 09/18/2008 14:22:27
Event String: The DHCP service failed to see a directory server
An Error Event occured. EventID: 0x00000416
Time Generated: 09/18/2008 14:22:27
Event String: The DHCP/BINL service on the local machine,
An Error Event occured. EventID: 0x00000423
Time Generated: 09/18/2008 14:22:27
Event String: The DHCP service failed to see a directory server
An Error Event occured. EventID: 0x00000416
Time Generated: 09/18/2008 14:38:51
Event String: The DHCP/BINL service on the local machine,
An Error Event occured. EventID: 0x00000416
Time Generated: 09/18/2008 14:45:08
Event String: The DHCP/BINL service on the local machine,
......................... GLV07 failed test systemlog


We are waiting on your resposne to run the netdiag.. only because we are not
sure if these errors need to be resolved first or not.

It appears this error is the only one possibly applicable to our issue:

An Error Event occured. EventID: 0x00000423
Time Generated: 09/18/2008 14:22:27
Event String: The DHCP service failed to see a directory server



Thanks,
Mike



"Meinolf Weber" wrote:

> Hello netadmin07,
>
> Install the domain controller first, again i would make this one DNS server
> with AD integrated zones. If the DC is up and running use dcdiag and netdiag
> to check for errors. If no errors, add the 2008 as a member server to the
> domain and just insert the exchange disk. During the setup you have just
> to follow the installation disk, it will start doing the complete domain
> preparation for the exchange schema additions.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > What is the first step I should take? Install Exchange? OR Install
> > Active Directory?
> >
> > I already have DNS and DHCP setup on the 1st server, but I have now
> > reinstalled the OS's on the 2nd and 3rd servers (Exchange and AD
> > servers).
> >
> > I assume, I will install Active Directory first.
> > Then I will install Exchange.
> > What about Prepare Active Directory and Domains? I read the article,
> > but am running the prepare/AD function on the Exchange server or the
> > Active Directory server?
> >
> > I just need a start to finish guide or something... But every article
> > I find on Technet, or Microsoft says I have to follow some other
> > article... I just want to make sure I take the right steps in the
> > right order.
> >
> > Let me clear that up for you:
> >
> > 1st Server
> > DNS server - Win Svr 2003 Ent
> > 2nd Server
> > Active Directory server - Win Svr 2003 Ent
> > 3rd Server Exchange 2007 sp1 server - Win Svr 2008 Ent x64
> >
> > "Meinolf Weber" wrote:
> >
> >> Hello netadmin07,
> >>
> >> For the installation part you have to run the setup from exchange
> >> with "run as administrator", even if the account you created is in
> >> the domain admin group. To install this you need elevated priviliges.
> >>
> >> Just to get your setup correct:
> >> 1x 2003 member server as DNS server
> >> 1x 2008 Domain controller without DNS installed, personally i prefer
> >> to have
> >> DNS installed with AD integrated zones on all my DC's
> >> 1x 2008 member server for exchange 2007, it has to be 2007 with SP1
> >> to run
> >> correctly on 2008.
> >> Best regards
> >>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >>>> We are setting up a new test LAN. These are brand new servers, and
> >>>> brand
> >>>> new
> >>>> installations of OS, AD, and Exchange, as well as, we are setting
> >>>> up
> >>>> a
> >>>> test
> >>>> DNS box for this test LAN.
> >>>> The main problem we are facing is:
> >>>> We install DNS on 1 box, then on another box we setup Active
> >>>> Directory
> >>>> with
> >>>> the Domain. We then create an Admin user and assign that user all
> >>>> the
> >>>> rights
> >>>> needed to administer the Exchange installation and management for
> >>>> Exchange.
> >>>> (member of the domain admin and schema admin groups in AD)
> >>>> However, it appears to be a permission issue, because when I try to
> >>>> run
> >>>> the
> >>>> setup utility to install Exchange with the account we setup - it
> >>>> errors
> >>>> out
> >>>> saying "Setup has encountered an error and has to close". But, if
> >>>> we
> >>>> use
> >>>> the
> >>>> local Administrator account, we do not get that error, and it
> >>>> starts
> >>>> installing, but fails at the prerequisite checks saying, "the
> >>>> account
> >>>> has
> >>>> to
> >>>> be logged onto the domain." "Unable to contact the domain" and so
> >>>> on. I
> >>>> have given the account we created on the domain full admin rights
> >>>> locally,
> >>>> as
> >>>> well as at the domain level, and added to all the necessary groups,
> >>>> but we
> >>>> still get the same issue.
> >>>> Server specs:
> >>>> Windows Server 2008 Enterprise (Exchange 2007), Dell 2950 Windows
> >>>> Server 2003 Enterprise (Active Directory), Dell 1950 Windows Server
> >>>> 2003 Enterprise (DNS, DHCP), Test Server
> >>>>
> >>>> At this point, I was planning on re-installing both OS's (the
> >>>> exchange and AD OS) and starting over.
> >>>>
> >>>> Thanks for any help,
> >>>> Mike

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

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

Hello netadmin07,

Check the event viewer system log for the DHCP and Time errors. If the server
is not DHCP server i think you can ignore them, just make sure the DHCP client
is running, needed for DNS registration. And the time errors will occur because
you didn't configure the DC with an external time source.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Ok.
> I followed your steps, we received the following errors while running
> dcdiag:
> Starting test: systemlog
> An Error Event occured. EventID: 0x00000411
> Time Generated: 09/18/2008 13:59:53
> Event String: The DHCP service is not servicing any clients
> An Error Event occured. EventID: 0x825A0011
> Time Generated: 09/18/2008 14:03:12
> Event String: Time Provider NtpClient: An error occurred during
> An Error Event occured. EventID: 0x825A0011
> Time Generated: 09/18/2008 14:03:31
> Event String: Time Provider NtpClient: An error occurred during
> An Error Event occured. EventID: 0xC25A001D
> Time Generated: 09/18/2008 14:03:31
> Event String: The time provider NtpClient is configured to
> An Error Event occured. EventID: 0x825A0011
> Time Generated: 09/18/2008 14:05:55
> Event String: Time Provider NtpClient: An error occurred during
> An Error Event occured. EventID: 0x00000423
> Time Generated: 09/18/2008 14:22:27
> Event String: The DHCP service failed to see a directory server
> An Error Event occured. EventID: 0x00000416
> Time Generated: 09/18/2008 14:22:27
> Event String: The DHCP/BINL service on the local machine,
> An Error Event occured. EventID: 0x00000423
> Time Generated: 09/18/2008 14:22:27
> Event String: The DHCP service failed to see a directory server
> An Error Event occured. EventID: 0x00000416
> Time Generated: 09/18/2008 14:38:51
> Event String: The DHCP/BINL service on the local machine,
> An Error Event occured. EventID: 0x00000416
> Time Generated: 09/18/2008 14:45:08
> Event String: The DHCP/BINL service on the local machine,
> ......................... GLV07 failed test systemlog
> We are waiting on your resposne to run the netdiag.. only because we
> are not sure if these errors need to be resolved first or not.
>
> It appears this error is the only one possibly applicable to our
> issue:
>
> An Error Event occured. EventID: 0x00000423
> Time Generated: 09/18/2008 14:22:27
> Event String: The DHCP service failed to see a directory server
> Thanks,
> Mike
> "Meinolf Weber" wrote:
>
>> Hello netadmin07,
>>
>> Install the domain controller first, again i would make this one DNS
>> server with AD integrated zones. If the DC is up and running use
>> dcdiag and netdiag to check for errors. If no errors, add the 2008 as
>> a member server to the domain and just insert the exchange disk.
>> During the setup you have just to follow the installation disk, it
>> will start doing the complete domain preparation for the exchange
>> schema additions.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> What is the first step I should take? Install Exchange? OR Install
>>> Active Directory?
>>>
>>> I already have DNS and DHCP setup on the 1st server, but I have now
>>> reinstalled the OS's on the 2nd and 3rd servers (Exchange and AD
>>> servers).
>>>
>>> I assume, I will install Active Directory first.
>>> Then I will install Exchange.
>>> What about Prepare Active Directory and Domains? I read the
>>> article,
>>> but am running the prepare/AD function on the Exchange server or the
>>> Active Directory server?
>>> I just need a start to finish guide or something... But every
>>> article I find on Technet, or Microsoft says I have to follow some
>>> other article... I just want to make sure I take the right steps in
>>> the right order.
>>>
>>> Let me clear that up for you:
>>>
>>> 1st Server
>>> DNS server - Win Svr 2003 Ent
>>> 2nd Server
>>> Active Directory server - Win Svr 2003 Ent
>>> 3rd Server Exchange 2007 sp1 server - Win Svr 2008 Ent x64
>>> "Meinolf Weber" wrote:
>>>
>>>> Hello netadmin07,
>>>>
>>>> For the installation part you have to run the setup from exchange
>>>> with "run as administrator", even if the account you created is in
>>>> the domain admin group. To install this you need elevated
>>>> priviliges.
>>>>
>>>> Just to get your setup correct:
>>>> 1x 2003 member server as DNS server
>>>> 1x 2008 Domain controller without DNS installed, personally i
>>>> prefer
>>>> to have
>>>> DNS installed with AD integrated zones on all my DC's
>>>> 1x 2008 member server for exchange 2007, it has to be 2007 with SP1
>>>> to run
>>>> correctly on 2008.
>>>> Best regards
>>>> Meinolf Weber
>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>> and
>>>> confers
>>>> no rights.
>>>> ** Please do NOT email, only reply to Newsgroups
>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>>> We are setting up a new test LAN. These are brand new servers,
>>>>>> and
>>>>>> brand
>>>>>> new
>>>>>> installations of OS, AD, and Exchange, as well as, we are setting
>>>>>> up
>>>>>> a
>>>>>> test
>>>>>> DNS box for this test LAN.
>>>>>> The main problem we are facing is:
>>>>>> We install DNS on 1 box, then on another box we setup Active
>>>>>> Directory
>>>>>> with
>>>>>> the Domain. We then create an Admin user and assign that user
>>>>>> all
>>>>>> the
>>>>>> rights
>>>>>> needed to administer the Exchange installation and management for
>>>>>> Exchange.
>>>>>> (member of the domain admin and schema admin groups in AD)
>>>>>> However, it appears to be a permission issue, because when I try
>>>>>> to
>>>>>> run
>>>>>> the
>>>>>> setup utility to install Exchange with the account we setup - it
>>>>>> errors
>>>>>> out
>>>>>> saying "Setup has encountered an error and has to close". But,
>>>>>> if
>>>>>> we
>>>>>> use
>>>>>> the
>>>>>> local Administrator account, we do not get that error, and it
>>>>>> starts
>>>>>> installing, but fails at the prerequisite checks saying, "the
>>>>>> account
>>>>>> has
>>>>>> to
>>>>>> be logged onto the domain." "Unable to contact the domain" and
>>>>>> so
>>>>>> on. I
>>>>>> have given the account we created on the domain full admin rights
>>>>>> locally,
>>>>>> as
>>>>>> well as at the domain level, and added to all the necessary
>>>>>> groups,
>>>>>> but we
>>>>>> still get the same issue.
>>>>>> Server specs:
>>>>>> Windows Server 2008 Enterprise (Exchange 2007), Dell 2950 Windows
>>>>>> Server 2003 Enterprise (Active Directory), Dell 1950 Windows
>>>>>> Server
>>>>>> 2003 Enterprise (DNS, DHCP), Test Server
>>>>>> At this point, I was planning on re-installing both OS's (the
>>>>>> exchange and AD OS) and starting over.
>>>>>>
>>>>>> Thanks for any help,
>>>>>> Mike
 
Re: Windows Server 2008 w/Exchange 2007 Authentication on Active D

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

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.





Unedited ipconfig /all

-------------------------------------------------
Server #2
Active Directory server - Win Svr 2003 Ent
-------------------------------------------------
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : glv07
Primary Dns Suffix . . . . . . . : glovill.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : glovill.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE
(NDIS
VBD Client)
Physical Address. . . . . . . . . : 00-1E-C9-FD-00-D3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.1.5
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 172.16.1.1
DNS Servers . . . . . . . . . . . : 172.16.1.5

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE
(NDIS
VBD Client) #2
Physical Address. . . . . . . . . : 00-1E-C9-FD-00-D5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.236.7
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

C:\Documents and Settings\Administrator>


----------------------------------------------------------
Server #3
Exchange 2007 sp1 server - Win Svr 2008 Ent x64
----------------------------------------------------------
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : WIN-1OP2FOIXLI1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE
(NDIS
VBD Client) #2
Physical Address. . . . . . . . . : 00-22-19-01-5A-AF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE
(NDIS
VBD Client)
Physical Address. . . . . . . . . : 00-22-19-01-5A-AD
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::58ae:8b13:aed9:8c92%10(Preferred)
IPv4 Address. . . . . . . . . . . : 172.16.1.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 172.16.1.1
DNS Servers . . . . . . . . . . . : 172.16.1.5
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{8C864CB6-4927-41DF-9BCB-401891356
4B1}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{54E30539-054E-496E-849A-E02957571
92F}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Users\Administrator>
--------------------------------------



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

MIke











"Ace Fekay [MVP Direcrtory Services]" wrote:

> In news:1DE3E52A-8AB7-43D8-9924-2F57DF37AE62@microsoft.com,
> netadmin07 <netadmin07@discussions.microsoft.com> requesting assistance,
> typed the following:
> > What is the first step I should take? Install Exchange? OR Install
> > Active Directory?
> >
> > I already have DNS and DHCP setup on the 1st server, but I have now
> > reinstalled the OS's on the 2nd and 3rd servers (Exchange and AD
> > servers).
> >
> > I assume, I will install Active Directory first.
> > Then I will install Exchange.
> >
> > What about Prepare Active Directory and Domains? I read the article,
> > but am running the prepare/AD function on the Exchange server or the
> > Active Directory server?
> >
> > I just need a start to finish guide or something... But every article
> > I find on Technet, or Microsoft says I have to follow some other
> > article... I just want to make sure I take the right steps in the
> > right order.
> >
> >
> >
> > Let me clear that up for you:
> >
> > 1st Server
> > DNS server - Win Svr 2003 Ent
> >
> > 2nd Server
> > Active Directory server - Win Svr 2003 Ent
> >
> > 3rd Server
> > Exchange 2007 sp1 server - Win Svr 2008 Ent x64

>
> AD has to be installed first prior to Exchange. It appears you have AD
> installed on server2. Are you planning on making server 1 a DC as well? It's
> recommended to have a minimum of two DCs per domain.
>
> I am assuming server 3 will be solely for Exchange, and not AD. AD on 2008
> is another dimension to handle at this point.
>
> Considering the errors you posted that you are getting, to get a better idea
> of your configuration, can you post an unedited ipconfig /all from all three
> servers please? That will help us determine if the basics are correct prior
> to moving forward.
>
> Thanks,
>
> --
> Regards,
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
> MVP Microsoft MVP - Directory Services
> Microsoft Certified Trainer
>
> For urgent issues, you may want to contact Microsoft PSS directly.
> Please check http://support.microsoft.com for regional support phone
> numbers.
>
> Enter into an artificial quantum singularity lined with fermions and
> neutrino scatterings depicted by electrons smashing into protons and
> neutrons like billiard balls moving at warp 9 exposing quarks, mesons
> and baryons, the essentials of their existence, that are spinning off
> in half scatters. You have now entered the Twilight Zone.
>
 
Re: Windows Server 2008 w/Exchange 2007 Authentication on Active D

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

In news:C6C87653-DF07-4DAF-9AA5-C1969946A6D8@microsoft.com,
netadmin07 <netadmin07@discussions.microsoft.com> 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
 
Re: Windows Server 2008 w/Exchange 2007 Authentication on Active D

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

Hello netadmin07,

See inline.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> 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.


It will work without any problem.

> 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?


Having at least 2 DC's is always the best solution, in case of failures you
have still the complete database with all users etc. running and your users
can work. You can install the second one whenever you like.

> Server #3 will be solely for Exchange. Yes.


Also good solution.

> Unedited ipconfig /all
>
> -------------------------------------------------
> Server #2
> Active Directory server - Win Svr 2003 Ent
> -------------------------------------------------
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
> C:\Documents and Settings\Administrator>ipconfig/all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : glv07
> Primary Dns Suffix . . . . . . . : glovill.net
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : glovill.net
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II
> GigE
> (NDIS
> VBD Client)
> Physical Address. . . . . . . . . : 00-1E-C9-FD-00-D3
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 172.16.1.5
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . : 172.16.1.1
> DNS Servers . . . . . . . . . . . : 172.16.1.5
> Ethernet adapter Local Area Connection 2:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II
> GigE
> (NDIS
> VBD Client) #2
> Physical Address. . . . . . . . . : 00-1E-C9-FD-00-D5
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> Autoconfiguration IP Address. . . : 169.254.236.7
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . :


Unused NIC's just disable, so they will not register in DNS with the APIPA
address. If your hardware vendor supports teaming for the NIC's you can also
use both NIC', but only with teaming software, HP for example has it.

> C:\Documents and Settings\Administrator>
>
> ----------------------------------------------------------
> Server #3
> Exchange 2007 sp1 server - Win Svr 2008 Ent x64
> ----------------------------------------------------------
> Microsoft Windows [Version 6.0.6001]
> Copyright (c) 2006 Microsoft Corporation. All rights reserved.
> C:\Users\Administrator>ipconfig/all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : WIN-1OP2FOIXLI1
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> Ethernet adapter Local Area Connection 2:
>
> Media State . . . . . . . . . . . : Media disconnected
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II
> GigE
> (NDIS
> VBD Client) #2
> Physical Address. . . . . . . . . : 00-22-19-01-5A-AF
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II
> GigE
> (NDIS
> VBD Client)
> Physical Address. . . . . . . . . : 00-22-19-01-5A-AD
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . :
> fe80::58ae:8b13:aed9:8c92%10(Preferred)
> IPv4 Address. . . . . . . . . . . : 172.16.1.3(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . : 172.16.1.1
> DNS Servers . . . . . . . . . . . : 172.16.1.5
> NetBIOS over Tcpip. . . . . . . . : Enabled
> Tunnel adapter Local Area Connection* 8:
>
> Media State . . . . . . . . . . . : Media disconnected
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . :
> isatap.{8C864CB6-4927-41DF-9BCB-401891356
> 4B1}
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> Tunnel adapter Local Area Connection* 9:
>
> Media State . . . . . . . . . . . : Media disconnected
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . :
> isatap.{54E30539-054E-496E-849A-E02957571
> 92F}
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> C:\Users\Administrator>
> --------------------------------------
> Should we move forward now with the NetDiag... And complete the
> install??? Thanks.


Same as above for the NIC, will be the same. If you have later on a second
DC/DNS do not forget to set the secondary DNS. For the naming of your servers
Ace gave you a really good explanation, this will make your live more easier.

The diagnostics tool's, dcdiag /v, netdiag /v, dnslint /ad /s "ip address
of your dc", and if you have more then one DC repadmin /showrepl you should
run at least once a week and ofcourse after any kind of new installation
or changing/adding new roles to a server.
 
Re: Windows Server 2008 w/Exchange 2007 Authentication on Active D

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

"Meinolf Weber" wrote in message
news:ff16fb667b288cae98fa8bef569@msnews.microsoft.com...
> Hello netadmin07,
>
> See inline.
>
> Best regards
>
> Meinolf Weber


I hope all this helps him. I have a feeling Exchange questions are coming up
next!

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

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

Hello Ace Fekay [MVP Direcrtory Services],

Maybe you're feelings will be right. We will see. :-)

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> "Meinolf Weber" wrote in message
> news:ff16fb667b288cae98fa8bef569@msnews.microsoft.com...
>
>> Hello netadmin07,
>>
>> See inline.
>>
>> Best regards
>>
>> Meinolf Weber
>>

> I hope all this helps him. I have a feeling Exchange questions are
> coming up next!
>
> Cheers!!
> Ace
 
Re: Windows Server 2008 w/Exchange 2007 Authentication on Active D

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@microsoft.com,
> netadmin07 <netadmin07@discussions.microsoft.com> 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
>
>
 
Re: Windows Server 2008 w/Exchange 2007 Authentication on Active D

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

Hello netadmin07,

For removing a DC you only have to keep in mind, that you have to demote
it and do some additional steps, to get it correct out of the domain.

See here how to:
http://technet.microsoft.com/en-us/library/cc755937.aspx

If this was done you can use ofcourse another machine and configure it the
same way.

No.2
Ofcourse you can rename a DC, you have two options:

moving FSMO roles to another DC, demoting it to member, wait/check for replication
in AD/DNS and rename it, wait/check again for replication in AD/DNS.

Or use the netdom tool, which requires domain functional level of at least
windows server 2003 or windows server 2008:
http://technet.microsoft.com/en-us/library/cc794951.aspx

http://technet.microsoft.com/en-us/library/cc816601.aspx

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> 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@microsoft.com,
>> netadmin07 <netadmin07@discussions.microsoft.com> 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
>>
 
Re: Windows Server 2008 w/Exchange 2007 Authentication on Active D

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

"netadmin07" <netadmin07@discussions.microsoft.com> wrote in message
news:4DB89BEC-73A9-4C15-A443-21549ACBE74A@microsoft.com...
> 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



Meinolf responded to all your questions. Good that you are doing it now!

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

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

Well,

I feel like I'm getting way off track on this... which started to be a very
simple install, now is seeming more and more complex.

This is just a test, I don't care what the names are of the servers, I only
need 1 DC for this test, that is required, from my understanding...

Is that right?

If so, I would like to move forward with the AD installation, which where we
left off, was here,

">> Install the domain controller first, again i would make this one DNS
>> server with AD integrated zones. If the DC is up and running use
>> dcdiag and netdiag to check for errors. If no errors, add the 2008 as
>> a member server to the domain and just insert the exchange disk.
>> During the setup you have just to follow the installation disk, it
>> will start doing the complete domain preparation for the exchange
>> schema additions."



So, i now have the integrated dns domains, and i pasted the results from the
dcdiag, so I will go ahead and run the netdiag one,

Does this sound right?
Thanks,
MIKE

"Ace Fekay [MVP Direcrtory Services]" wrote:

> "netadmin07" <netadmin07@discussions.microsoft.com> wrote in message
> news:4DB89BEC-73A9-4C15-A443-21549ACBE74A@microsoft.com...
> > 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

>
>
> Meinolf responded to all your questions. Good that you are doing it now!
>
> Ace
>
>
 
Re: Windows Server 2008 w/Exchange 2007 Authentication on Active D

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

Alright,

Current Status:

I have run the netdiag on the AD server, and it has now passed all tests.
So, the next part that is failing is when I attempt to run the

setup /preparealldomains

I have tried different variations, but it pops up an error, stating, "Go to
control panel and install components"

Which ones do I install, and where are they located?
Thanks...




"netadmin07" wrote:

> Well,
>
> I feel like I'm getting way off track on this... which started to be a very
> simple install, now is seeming more and more complex.
>
> This is just a test, I don't care what the names are of the servers, I only
> need 1 DC for this test, that is required, from my understanding...
>
> Is that right?
>
> If so, I would like to move forward with the AD installation, which where we
> left off, was here,
>
> ">> Install the domain controller first, again i would make this one DNS
> >> server with AD integrated zones. If the DC is up and running use
> >> dcdiag and netdiag to check for errors. If no errors, add the 2008 as
> >> a member server to the domain and just insert the exchange disk.
> >> During the setup you have just to follow the installation disk, it
> >> will start doing the complete domain preparation for the exchange
> >> schema additions."

>
>
> So, i now have the integrated dns domains, and i pasted the results from the
> dcdiag, so I will go ahead and run the netdiag one,
>
> Does this sound right?
> Thanks,
> MIKE
>
> "Ace Fekay [MVP Direcrtory Services]" wrote:
>
> > "netadmin07" <netadmin07@discussions.microsoft.com> wrote in message
> > news:4DB89BEC-73A9-4C15-A443-21549ACBE74A@microsoft.com...
> > > 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

> >
> >
> > Meinolf responded to all your questions. Good that you are doing it now!
> >
> > Ace
> >
> >
 
Re: Windows Server 2008 w/Exchange 2007 Authentication on Active D

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

Hello netadmin07,

No components are listed in the message?

Did you follow this way for installing exchange:
http://technet.microsoft.com/en-us/library/bb125224(EXCHG.80).aspx

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Alright,
>
> Current Status:
>
> I have run the netdiag on the AD server, and it has now passed all
> tests. So, the next part that is failing is when I attempt to run the
>
> setup /preparealldomains
>
> I have tried different variations, but it pops up an error, stating,
> "Go to control panel and install components"
>
> Which ones do I install, and where are they located? Thanks...
>
> "netadmin07" wrote:
>
>> Well,
>>
>> I feel like I'm getting way off track on this... which started to be
>> a very simple install, now is seeming more and more complex.
>>
>> This is just a test, I don't care what the names are of the servers,
>> I only need 1 DC for this test, that is required, from my
>> understanding...
>>
>> Is that right?
>>
>> If so, I would like to move forward with the AD installation, which
>> where we left off, was here,
>>
>> ">> Install the domain controller first, again i would make this one
>> DNS
>>
>>>> server with AD integrated zones. If the DC is up and running use
>>>> dcdiag and netdiag to check for errors. If no errors, add the 2008
>>>> as a member server to the domain and just insert the exchange disk.
>>>> During the setup you have just to follow the installation disk, it
>>>> will start doing the complete domain preparation for the exchange
>>>> schema additions."
>>>>

>> So, i now have the integrated dns domains, and i pasted the results
>> from the dcdiag, so I will go ahead and run the netdiag one,
>>
>> Does this sound right?
>> Thanks,
>> MIKE
>> "Ace Fekay [MVP Direcrtory Services]" wrote:
>>
>>> "netadmin07" <netadmin07@discussions.microsoft.com> wrote in message
>>> news:4DB89BEC-73A9-4C15-A443-21549ACBE74A@microsoft.com...
>>>
>>>> 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
>>> Meinolf responded to all your questions. Good that you are doing it
>>> now!
>>>
>>> Ace
>>>
 
Re: Windows Server 2008 w/Exchange 2007 Authentication on Active D

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

Yes, I know... It just said

Go install the windows components in the control panel...

If it told me which ones, I probably would have found them...

And yes, I am following that article, and one of the "assumptions" on that
article, states to run the setup prepare AD on the AD server....

That's where I'm stuck.... However, I currently connected the AD server to
the internet, because it did not have all the latest updates from Microsoft
(sp2) and so I figure I will try again once it is up to date.


Please let me know what I'm missing on the setup prepare AD.
thanks...



"Meinolf Weber" wrote:

> Hello netadmin07,
>
> No components are listed in the message?
>
> Did you follow this way for installing exchange:
> http://technet.microsoft.com/en-us/library/bb125224(EXCHG.80).aspx
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Alright,
> >
> > Current Status:
> >
> > I have run the netdiag on the AD server, and it has now passed all
> > tests. So, the next part that is failing is when I attempt to run the
> >
> > setup /preparealldomains
> >
> > I have tried different variations, but it pops up an error, stating,
> > "Go to control panel and install components"
> >
> > Which ones do I install, and where are they located? Thanks...
> >
> > "netadmin07" wrote:
> >
> >> Well,
> >>
> >> I feel like I'm getting way off track on this... which started to be
> >> a very simple install, now is seeming more and more complex.
> >>
> >> This is just a test, I don't care what the names are of the servers,
> >> I only need 1 DC for this test, that is required, from my
> >> understanding...
> >>
> >> Is that right?
> >>
> >> If so, I would like to move forward with the AD installation, which
> >> where we left off, was here,
> >>
> >> ">> Install the domain controller first, again i would make this one
> >> DNS
> >>
> >>>> server with AD integrated zones. If the DC is up and running use
> >>>> dcdiag and netdiag to check for errors. If no errors, add the 2008
> >>>> as a member server to the domain and just insert the exchange disk.
> >>>> During the setup you have just to follow the installation disk, it
> >>>> will start doing the complete domain preparation for the exchange
> >>>> schema additions."
> >>>>
> >> So, i now have the integrated dns domains, and i pasted the results
> >> from the dcdiag, so I will go ahead and run the netdiag one,
> >>
> >> Does this sound right?
> >> Thanks,
> >> MIKE
> >> "Ace Fekay [MVP Direcrtory Services]" wrote:
> >>
> >>> "netadmin07" <netadmin07@discussions.microsoft.com> wrote in message
> >>> news:4DB89BEC-73A9-4C15-A443-21549ACBE74A@microsoft.com...
> >>>
> >>>> 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
> >>> Meinolf responded to all your questions. Good that you are doing it
> >>> now!
> >>>
> >>> Ace
> >>>

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

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

Hello netadmin07,

On the C:\exchangesetuplogs folder check the exchangesetup.log for additional
errors about the components. When i did my first exchange 2007 install i
just choose the wizard from the disk and did not do any step by hand and
it works fine.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Yes, I know... It just said
>
> Go install the windows components in the control panel...
>
> If it told me which ones, I probably would have found them...
>
> And yes, I am following that article, and one of the "assumptions" on
> that article, states to run the setup prepare AD on the AD server....
>
> That's where I'm stuck.... However, I currently connected the AD
> server to the internet, because it did not have all the latest updates
> from Microsoft (sp2) and so I figure I will try again once it is up to
> date.
>
> Please let me know what I'm missing on the setup prepare AD. thanks...
>
> "Meinolf Weber" wrote:
>
>> Hello netadmin07,
>>
>> No components are listed in the message?
>>
>> Did you follow this way for installing exchange:
>> http://technet.microsoft.com/en-us/library/bb125224(EXCHG.80).aspx
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Alright,
>>>
>>> Current Status:
>>>
>>> I have run the netdiag on the AD server, and it has now passed all
>>> tests. So, the next part that is failing is when I attempt to run
>>> the
>>>
>>> setup /preparealldomains
>>>
>>> I have tried different variations, but it pops up an error, stating,
>>> "Go to control panel and install components"
>>>
>>> Which ones do I install, and where are they located? Thanks...
>>>
>>> "netadmin07" wrote:
>>>
>>>> Well,
>>>>
>>>> I feel like I'm getting way off track on this... which started to
>>>> be a very simple install, now is seeming more and more complex.
>>>>
>>>> This is just a test, I don't care what the names are of the
>>>> servers, I only need 1 DC for this test, that is required, from my
>>>> understanding...
>>>>
>>>> Is that right?
>>>>
>>>> If so, I would like to move forward with the AD installation, which
>>>> where we left off, was here,
>>>>
>>>> ">> Install the domain controller first, again i would make this
>>>> one DNS
>>>>
>>>>>> server with AD integrated zones. If the DC is up and running use
>>>>>> dcdiag and netdiag to check for errors. If no errors, add the
>>>>>> 2008 as a member server to the domain and just insert the
>>>>>> exchange disk. During the setup you have just to follow the
>>>>>> installation disk, it will start doing the complete domain
>>>>>> preparation for the exchange schema additions."
>>>>>>
>>>> So, i now have the integrated dns domains, and i pasted the results
>>>> from the dcdiag, so I will go ahead and run the netdiag one,
>>>>
>>>> Does this sound right?
>>>> Thanks,
>>>> MIKE
>>>> "Ace Fekay [MVP Direcrtory Services]" wrote:
>>>>> "netadmin07" <netadmin07@discussions.microsoft.com> wrote in
>>>>> message news:4DB89BEC-73A9-4C15-A443-21549ACBE74A@microsoft.com...
>>>>>
>>>>>> 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
>>>>> Meinolf responded to all your questions. Good that you are doing
>>>>> it now!
>>>>>
>>>>> Ace
>>>>>
 
Re: Windows Server 2008 w/Exchange 2007 Authentication on Active D

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

Interesting.... So, you didn't run the setup prepare AD manually??

Well, once these updates are complete, I will just try to run the Exchange
disc..

Oh, one more thing,


I believe i will need to create a user on the AD server (exchange admin)....
Which rights should i assign this user... Because I think I have to login
with that user on the Exchange box, prior to the exchange installation...??

Is that correct?
Thanks.









"Meinolf Weber" wrote:

> Hello netadmin07,
>
> On the C:\exchangesetuplogs folder check the exchangesetup.log for additional
> errors about the components. When i did my first exchange 2007 install i
> just choose the wizard from the disk and did not do any step by hand and
> it works fine.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Yes, I know... It just said
> >
> > Go install the windows components in the control panel...
> >
> > If it told me which ones, I probably would have found them...
> >
> > And yes, I am following that article, and one of the "assumptions" on
> > that article, states to run the setup prepare AD on the AD server....
> >
> > That's where I'm stuck.... However, I currently connected the AD
> > server to the internet, because it did not have all the latest updates
> > from Microsoft (sp2) and so I figure I will try again once it is up to
> > date.
> >
> > Please let me know what I'm missing on the setup prepare AD. thanks...
> >
> > "Meinolf Weber" wrote:
> >
> >> Hello netadmin07,
> >>
> >> No components are listed in the message?
> >>
> >> Did you follow this way for installing exchange:
> >> http://technet.microsoft.com/en-us/library/bb125224(EXCHG.80).aspx
> >> Best regards
> >>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >>> Alright,
> >>>
> >>> Current Status:
> >>>
> >>> I have run the netdiag on the AD server, and it has now passed all
> >>> tests. So, the next part that is failing is when I attempt to run
> >>> the
> >>>
> >>> setup /preparealldomains
> >>>
> >>> I have tried different variations, but it pops up an error, stating,
> >>> "Go to control panel and install components"
> >>>
> >>> Which ones do I install, and where are they located? Thanks...
> >>>
> >>> "netadmin07" wrote:
> >>>
> >>>> Well,
> >>>>
> >>>> I feel like I'm getting way off track on this... which started to
> >>>> be a very simple install, now is seeming more and more complex.
> >>>>
> >>>> This is just a test, I don't care what the names are of the
> >>>> servers, I only need 1 DC for this test, that is required, from my
> >>>> understanding...
> >>>>
> >>>> Is that right?
> >>>>
> >>>> If so, I would like to move forward with the AD installation, which
> >>>> where we left off, was here,
> >>>>
> >>>> ">> Install the domain controller first, again i would make this
> >>>> one DNS
> >>>>
> >>>>>> server with AD integrated zones. If the DC is up and running use
> >>>>>> dcdiag and netdiag to check for errors. If no errors, add the
> >>>>>> 2008 as a member server to the domain and just insert the
> >>>>>> exchange disk. During the setup you have just to follow the
> >>>>>> installation disk, it will start doing the complete domain
> >>>>>> preparation for the exchange schema additions."
> >>>>>>
> >>>> So, i now have the integrated dns domains, and i pasted the results
> >>>> from the dcdiag, so I will go ahead and run the netdiag one,
> >>>>
> >>>> Does this sound right?
> >>>> Thanks,
> >>>> MIKE
> >>>> "Ace Fekay [MVP Direcrtory Services]" wrote:
> >>>>> "netadmin07" <netadmin07@discussions.microsoft.com> wrote in
> >>>>> message news:4DB89BEC-73A9-4C15-A443-21549ACBE74A@microsoft.com...
> >>>>>
> >>>>>> 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
> >>>>> Meinolf responded to all your questions. Good that you are doing
> >>>>> it now!
> >>>>>
> >>>>> Ace
> >>>>>

>
>
>
 
Back
Top