exchange and windows 2k3

[goldenboiyaj]

i got a quick question.

installing two seperate servers. each will have server2003. SERVER1 will host ad,dns,dhcp and SERVER2 host file server and exchange 2003.

i've got everything set up on server 1 already. about to start on server2. what do i need to do on server1 to prepare for server2? do i need to do anything in AD, such as adding server2?
i am at the installation point on server2 where it is asking to be part of a domain but it's not seeing server2 when i type in my admin/username of server1, it cannot see the domain and asks if i want to proceed and join it later. I read somewhere that you need to join the domain at the point to make sure everything will work later, is that correct?

i'm am sure my dns and dchp is configured properlly.

any help would be much appreciate.

ky

 

[sharper]

If your installing Windows now you don't need to join the domain. Let the installation finish with it in a Workgroup and once it's rebooted all the times it wants, join it to the domain then. Install the support tools from the Windows 2003 CD when it's finished, you'll need them when you go to install exchange.

As with exchange: Stick the CD in and at eh Exchange 2003 autoplay window click on Exchange Deployment Tools. This will guide you through every step required to install Exchange. It will make all the changes to AD required. Read every page and read every log file generated before moving to the next step. Once you are careful and READ everything It should just work.

 

[dave2korg]

Finish the windows install.
After the install, run windows update and make sure you update to latest service pack.
Join the server to the domain and make sure there is a static address defined with gateway and DNS for the server. (NOTE: since this is going to be an exchange server, you will need to setup a reverse DNS record either through your isp or your dns server).
Under the 'manage server' link in start you will find the role of file server, which will turn on file sharing. Simply setup the shares you want with whatever groups/access etc.

When installing Exchange you should have no issues, as it is next next next, but make sure you follow all prerequisites on the install list before finishing (domain prep, etc).
After the installation, update exchange to sp2 from microsofts site

http://www.microsoft.com/technet/prodtechnol/exchange/downloads/2003/sp2/download.mspx

Make sure you go through almost every option (including SMTP connector) on the Exchange System Manager and configure every setting.
Try sending a test email, if you can send in/out you should have no further problems.
If you want OWA and/or OMA access make sure you install ASP.NET and IIS on the server (again, at the roles screen). Your IIS should point to mail.domain.com

If you have any troubles, post here. I hope you found my chicken scratch helpful.

David McKissic
A+, Net+, i-net+, CCNA, CNE, CNA
Dell, Compaq, IBM, HP
Network Administrator

 

[goldenboiyaj]

Thanks for everything so far. Here is where I am at. got both servers with the latest services packs and critical updates for windows and exhange. got smtp/nntp/wwb..etc..setup on server2. want to use OWA also. both servers can ping eachother and the firewall.

this is some info.
firewall: 10.1.1.1
server1: 10.1.1.10
server2: 10.1.1.11
domain and dns name= domain.local
dhcp scope address pool= 10.1.2.1-254
using domain name for email such as = domain.org

What do i need to configure in DNS and DHCP to make this work?

i know i need to create a zone in DNS for email. what needs to be done in forward, do i make a primary/secondary or stub? i dont know what to select for a couple of the steps in the setup process. what's the steps for doing the reverse?

DCHP is acting weird. I connected a 3rd computer on the network using a switch. the 3rd computer's NIC is set to DHCP but when it tries to connect to the DHCP server on SERVER1, it does not work. It does not get the correct IP address from DHCP. It gives me weird as as 162.x.x.x instead of the 10.1.2.x that i set for the scope on DHCP. Any ideas on my setup of DHCP?


thanks,
ky

 

[sharper]

First off:
What's your netmask?

What do i need to configure in DNS and DHCP to make this work?
In the Scope Options of the scope you created add the following:
003 Router 10.1.1.1
006 DNS Servers <your internal DNS servers' IP addresses>
015 DNS Domain Name domain.local
044 WINS/NBNS Servers <WINS server IP address> !! You need WINS for proper Exchange functionality
046 WINS/NBT node Type 0x8

i know i need to create a zone in DNS for email. what needs to be done in forward, do i make a primary/secondary or stub? i dont know what to select for a couple of the steps in the setup process. what's the steps for doing the reverse?

When you ran DCPROMO did you install DNS from the dcpromo wizard or point it to another Domain Controller running DNS? - if you used the dcpromo wizard to install DNS it should have added the Forward lookup for the DNS domain you created. Reverse lookup zone: just add a primary zone and enter your ip range and it will do the rest.

DHCP Acting wierd
Make sure you only have the one DHCP server on the network.
Try setting the PC that's acting up a static IP address in the correct range and see if you can ping the servers - this will tell you if it's a cable problem or not.

 

[58sniper]

If both servers are in the same location, you don't need WINS for proper Exchange functionality. That's a myth.

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)

 

[sharper]

If both servers are in the same location, you don't need WINS for proper Exchange functionality. That's a myth.

How is this helpful to the problem at hand??? I'm not getting into the WINS/NO WINS argument here but when I'm not given the full specification of the site I think it's best to cover all angles.

oh...

http://support.microsoft.com/kb/837391/en-us

 

[58sniper]

And the 'cause' section says it all:

across different subnets

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)

 

[sharper]

when I'm not given the full specification of the site I think it's best to cover all angles

 

[goldenboiyaj]

ok, SHARPER, those scope things you asked me to entered was already setup in SCOPE OPTIONS in my DHCP.

For DNS setup on SERVER1. DNS was setup when I ran the AD setup from the MANAGE YOUR SERVER wizard when I first got the server up and running.

DHCP is working fine now.

couple more things appeared.

#1. I setup username = testuser with exchange mailbox created on domain. I setup outlook 2003 client on a computer name cpu1. log into cpu1 with new testuser, log out. log back in and setup outlook2k3 client for testuser connecting to exchange server(it works). send an email from HOTMAIL.COM, i get no messages in outlook client.
Why do I not see my emails on outlook client? I also did other way around and send email from testuser account in outlook2k3 to HOTMAIL.com account, I see and I get message in hotmail account from testuser@domain.local. Which i think is wrong because it should be testuser@domain.org. I want ORG as my email name.

#2. Why did cpu1 i added in step get added to my domain.local in DNS forward lookup zones? isnt it only suppose to appear as a computer on the network and DCHP address leases?

 

[sharper]

#1 You probably have @domain.local set as your primary address in your Recipient Policy. In Exchange System Manager expand Recipients - Recipient Policies. Double click on your Recipient Policy (This will be called defaul policy if you haven't added another one) and go to the Email Addresses Policy tab. Highlight the line that says @domain.org and click set as primary (when you closr this screen it should say "Do you want to update blah blah blah....", just go ahead and click Yes. In a bit when you now look at the users properties/Email addresses it should have @domain.org in bold.

#2 CPU1 was added to your local DNS forwatd lookup zone because a) You're DHCP server is set to dynamically update DNS records for new leases b) the machine itself is set to register it's details in DNS. This is normal and good!

S.

 

[58sniper]

If there IS domain.local and domain.org in your recipient policy, change the primary to domain.org as Sharper mentioned, then remove the domain.local address. It's not needed.

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)

 

[goldenboiyaj]

thanks for all help, it helps