locked
Exchange 2003 Standard / Server 2008 R2 Forest RRS feed

  • Question

  • I recently installed Exchange 2003 Standard on a Server 2003 SP2 server.  The Domain Controller is Server 2008 R2.  The domain was already up and operational prior to installing Exchange.  I ran through ALL of the prerequisite checks, including DCDiag, the Network test, forest prep, etc. and I did not receive any errors.  I did receive a note about an incompatibility, but upon looking up the KB it did not apply.  Upon completion of the installation, I do not have any mailboxes existing in AD for current users.  I have never installed Exchange before, so I don't know if that is normal but it would seem to me that it is.  I have gone into AD and accessed a user and right-clicked, expecting to see the options to create a new mailbox.  I do not see any Exchange options at all.  Was this supposed to have occurred during the forest prep and subsequent installation of Exchange?  I do not have Exchange System Manager installed on the server, and I'm not sure if I need it.  Nonetheless, I don't see a download version for Server 2008.  I have read mixed reviews about the support for Exchange 2003 in a 2008 AD, and the conclusion I came to is that it does work so long as DC is writeable:

    As in more details

    It states quite clearly that read only 2008/2008R2 domain controllers are not supported; standard (i.e. writable) DCs are supported.

    It also states that 2008/2008R2 domain and forest functional levels are supported.

    What is not supported is running Exchange 2003 on a 2008/2008R2 server.

    Regards.

    Shafaquat Ali.

     

    How do I know if my DC is writeable?  If all of this is going to be a dead end, can I simply perform an in-place upgrade of Exchange 2003 to 2007?

    Regards,
    Scott

    Thursday, January 26, 2012 10:38 PM

Answers

All replies

  • The Options you are expecting to Create new mailbox is can be done only on Window Server 2003

    So Open Active Directory Users and Computers in the Exchange Server

    And Try Creating a Mailbox.

     

     

     

     


    Satheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in
    • Proposed as answer by Fiona_Liao Friday, January 27, 2012 3:24 AM
    Friday, January 27, 2012 12:48 AM
  • @Satheshwaran

    The server running Exchange is only a domain member, not a domain controller and is not running AD.

    Friday, January 27, 2012 3:00 AM
  • Hi Spickles,

    You should be able to find the ADUC tool in the Exchange server. If no, run dsa.msc.

    By the way, why not install Exchange 2010 for a new environment? Exchange 2003 is out of support.

    Refer to:

    http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=exchange+server&Filter=FilterNO


    Fiona Liao

    TechNet Community Support

    • Proposed as answer by Fiona_Liao Friday, January 27, 2012 3:31 AM
    • Marked as answer by spickles Saturday, January 28, 2012 2:16 AM
    Friday, January 27, 2012 3:30 AM
  • Hi Spickles,

    You can Run dsa.msc as Fiona Said.

    You Should find one for sure !!


    Satheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in
    Friday, January 27, 2012 3:30 PM
  • @Fiona & @Satheshwaran - 

     

    Thanks, I'll look into it later this evening.  The reason for the Exchange 2003 is that it's my first time doing this, and I spent the $$ on my DC so I could run Server 2008 - my Server 2003 box won't support anything higher than Exchange 2003 due to hardware requirements.

    Friday, January 27, 2012 3:55 PM
  • Okay !!

    I understand your Situation ,


    Satheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in
    Friday, January 27, 2012 5:39 PM
  • Had a chance to try adding a mailbox.  Although I can't install the System Management tools on the domain controller, as indicated by Fiona, running 'DSA.MSC' allowed me to access Active Directory Users and Computers, and the Exchange tasks were there.  So I've added a mailbox, and now I have to test and set it up for receiving mail on two different domains.

    Regards,
    Scott 

    Friday, January 27, 2012 8:29 PM
  • Great !!

    Good to Hear that !!

     


    Satheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in
    Friday, January 27, 2012 8:47 PM
  • Test using OWA worked.  I added a Security Group to AD for an outside domain and created a new Recipient Policy and setup the filter to match that group.  I have my firewall set to allow SMTP in and I'm NAT'ing to the mail server.  However, when I run 'portqry -n <my domain> -p tcp -e 25' I get 'NOT LISTENING'.  There is no firewall turned on on the server, and the SMTP virtual service is running as well as the SMTP service.  Other tests using 'portqry' and similar NAT rules and ACLs show that my webserver is fine.  What now?
    • Edited by spickles Friday, January 27, 2012 9:33 PM
    Friday, January 27, 2012 9:23 PM
  • Also, based on the Recipient Policy I created, should I see multiple email addresses listed for the specified user(s) in AD that belong to the Security Group I created?  As of right now I don't.  Do I have to delete the mailbox and re-create it so that there is a box for both email addresses?
    • Edited by spickles Friday, January 27, 2012 10:05 PM
    Friday, January 27, 2012 9:30 PM
  • On the Exchange server, 'netstat -ano -p tcp | find ":25" returns

    TCP    0.0.0.0:25             0.0.0.0:0              LISTENING       1680

    I can't see anything running in taskmgr with a PID of '1680', and I don't know how to tell if a particular service is using that PID.  So at this point I can't determine if there is anything else tying up the port.  Also, from the list of services running, it appears to me that everything that should be running for Exchange is running.  I would think that if the server wasn't operating properly that my internal tests for email would fail.  Should inbound email for this external domain be coming in on SMTP or POP3?  Do I need to run the POP3 virtual server and port forward it?  If no, then I bet my damn ISP is blocking 25, and they keep telling me that they don't block anything inbound (yeah right).  My MX record is pointing where it should, too.


    • Edited by spickles Friday, January 27, 2012 9:43 PM
    Friday, January 27, 2012 9:42 PM
  • All Will Be receving in Port 25 Only Spickles.
    Satheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in
    Friday, January 27, 2012 11:02 PM
  • Yes , You should See 2 Email addresses.

    For example.

    user1@domain.local

    User1@domain.com

     

    To Reflect Right Away - Update your RUS - Recipient Update Services


    Satheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in
    Friday, January 27, 2012 11:04 PM
  • I performed all of the steps in this guide, including the RUS, and no difference.  I'm going to attempt to remove and re-add the mailbox.

     

    http://www.petri.co.il/configure_specific_email_addresses_for_exchange_users.htm

    Saturday, January 28, 2012 12:57 AM
  • Make Sure your Filter is good for your Email address policy

     

    If RUS is not Stamping - Update your RUS , Check you get any errors in your events ?

    I don't think adding and readding your Mailbox would work

     

    For the Meanwhile .

    You can add smtp address manually if you have less users.

     



    Satheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in
    Saturday, January 28, 2012 1:07 AM
  • Looks like you can't use an AD OU for policies:

    http://support.microsoft.com/default.aspx?scid=kb;en-us;296112

    Saturday, January 28, 2012 1:08 AM
  • Oopz.. It doesn't work on Legacy version

    It won't work until you remove legacy versions.

    Cause I was working with Address book policies in Exchange 2010 . with the Same problem

     

    Never Thought Your filter was OU.

    Great you found that !


    Satheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in
    Saturday, January 28, 2012 1:09 AM
  • I don't understand why I can't use an OU according to the previous post I made when I see this:

     

     

    Is it because it can't find users INSIDE the OU?

    Saturday, January 28, 2012 1:20 AM
  • I would quickly test on my lab

    Give me 2 mins


    Satheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in
    Saturday, January 28, 2012 1:21 AM
  • I tested on my lab 100% sure.

    Its not Stamping for OU.

    Use someother Filter Rules !!


    Satheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in
    Saturday, January 28, 2012 1:26 AM
  • Wow, really Microsoft?  All of that structure in AD and I can't do something as simple as add people to an OU and create a filter against it.  I was able to add a custom attribute and search against that - which means that if I were the admin of a domain of hundreds or thousands of people, I'd be really P.O.'d to have to touch each user to add that custom attribute.  I could only hope that AD would be structured in such a way that I'd be able to script it and be selective about whom I'd set that custom attribute for - then again, if the filter policy could just look up an OU and grab the users inside of it ...
    Saturday, January 28, 2012 1:36 AM
  • I'm happy to report that email is working!  Now I have to figure out how to automate all of this when I register a new email address from a web form.  Also, how can I change which email address is primary?  I edited my username and selected the internal domain as primary, but then I went back and looked it had changed back to the external domain.
    Saturday, January 28, 2012 1:46 AM
  • Bingo!  Figured out the primary email address issue.  I didn't realize policies were similar to those in IAS/NPS in that once a policy matches, no other policies are evaluated.  Therefore, I modified my custom policy to include both the internal and external domains, and then I was able to set the primary.  In this way, only users that match my custom attribute in AD match this policy, get both email addresses, and correctly sets the primary and secondary.  For those that don't match it just get the default single email address for the internal domain.  Thanks for all of your help!

    Edit: I also appreciate the post from Fiona (which I marked as the answer to my initial question on the thread).  Funny thing, I learned from other internet searches that the AD plugin was provided as a short cut right from the START MENU under MICROSOFT EXCHANGE.  I couldn't have been more blind ...

    • Edited by spickles Saturday, January 28, 2012 2:18 AM
    Saturday, January 28, 2012 2:15 AM
  • We have good tools like admodify. where you you can edit and add almost everything in bulk @@

    Hope you had a good weekend !!


    Satheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in
    Monday, January 30, 2012 2:53 PM