Announcement

Collapse
No announcement yet.

Queistions about exchange domain

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Queistions about exchange domain

    I'm a 100% Unix guy but now am being asked to build an Windows exchange server for a small organization.

    Here's what I have.
    1, Server: PowerEdge T310. It will be Domain controller, DNS and exchange server. (I know someone will argue if it's good idea to install DC and exchange on the same physical box. But keep in mind this is very small organization. Budget is very tight for them).
    2, OS: Licensed Windows 2008 R2
    3, Public DNS: xyz.com has been registered at godaddy and static IP is provided by ISP

    My question:
    1, If the Win2008 R2 is active/licensed, does exchange server (I downloaded Exchange2010-SP2-x64.exe from Microsoft site) still require separate license?

    2, When I try to configure active directory, I was asked to put FQDN of the forest root domain, do I put the public domain xyz.com or it could be any internal domain (say xyz.local). As it clearly says "it is very hard to change it in the future".

    3, After exchange server installation, under Organization Configuration >> Hub Transport >> Accepted domain, should I choose authoritative domain or External relay domain? Again. this is the only exchange server in the whole organization and facing internet.

    Thanks in advance.

  • #2
    Re: Queistions about exchange domain

    1) Yes -- Exchange is a separate product so will require its own license as well as Client Access Licenses. If you will have less than 75 users, SBS2011 may be a better alternative
    2) There is debate but normally domain.local is preferred over domain.com (others may disagree). If you have a public website www.domain.com hosted elsewhere you need to access, using domain.com for your AD name can cause problems
    3) Since you will be handling email, the domain should be authoritative

    Also be aware you will need a public certificate -- GoDaddy will provide
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: Queistions about exchange domain

      if you have two serves.. why not put exchnge on the second ?
      Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

      Comment


      • #4
        Re: Questions about exchange domain

        If the org is very small then you would probably be better off with SBS 2011. It will almost certainly be cheaper than purchasing Exchange 2010 separately even if you write off the Windows 2008 R2 licence that you already have.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment


        • #5
          Re: Queistions about exchange domain

          hopefully these is a better way to bypass the error.

          Comment


          • #6
            Re: Queistions about exchange domain

            Further comments/questions regarding to Ossian's answers.

            1) Yes -- Exchange is a separate product so will require its own license as well as Client Access Licenses. If you will have less than 75 users, SBS2011 may be a better alternative
            The organization has definitely less than 75 users. I'll pass the message about SBS2011 to the manager for sure.


            2) There is debate but normally domain.local is preferred over domain.com (others may disagree). If you have a public website www.domain.com hosted elsewhere you need to access, using domain.com for your AD name can cause problems
            So how to link a public email address (for instance, [email protected]) to the internal one ([email protected])? I'm thinking about mail alias. Just not sure how to achieve it.


            3) Since you will be handling email, the domain should be authoritative
            How do I let exchange server know the public mail relay? Or if it's necessary?


            Also be aware you will need a public certificate -- GoDaddy will provide
            Good to know. Thanks.

            Comment


            • #7
              Re: Queistions about exchange domain

              Originally posted by redstone View Post
              hopefully these is a better way to bypass the error.
              Yes - don't post links.
              In your posting there was no need to put in www.domain.com - you could have easily removed that without changing the way the post read. I will remove the other garbage posts.

              Simon
              --
              Simon Butler
              Exchange MVP

              Blog: http://blog.sembee.co.uk/
              More Exchange Content: http://exchange.sembee.info/
              Exchange Resources List: http://exbpa.com/
              In the UK? Hire me: http://www.sembee.co.uk/

              Sembee is a registered trademark, used here with permission.

              Comment


              • #8
                Re: Queistions about exchange domain

                Please see answers in RED below
                Originally posted by redstone View Post
                Further comments/questions regarding to Ossian's answers.

                1) Yes -- Exchange is a separate product so will require its own license as well as Client Access Licenses. If you will have less than 75 users, SBS2011 may be a better alternative
                The organization has definitely less than 75 users. I'll pass the message about SBS2011 to the manager for sure.


                2) There is debate but normally domain.local is preferred over domain.com (others may disagree). If you have a public website www.domain.com hosted elsewhere you need to access, using domain.com for your AD name can cause problems
                So how to link a public email address (for instance, [email protected]) to the internal one ([email protected])? I'm thinking about mail alias. Just not sure how to achieve it.
                You create domain.com as an accepted domain in Exchange -- this is nothing to do with the Active Directory domain, in fact Exchange can handle multiple accepted domains

                3) Since you will be handling email, the domain should be authoritative
                How do I let exchange server know the public mail relay? Or if it's necessary?
                If it is relaying via an ISP, you set up a "smart host" which tells exchange to pass on emails to the ISPs server. Alternatively you can send directly using DNS

                Also be aware you will need a public certificate -- GoDaddy will provide
                Good to know. Thanks.
                Tom Jones
                MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
                PhD, MSc, FIAP, MIITT
                IT Trainer / Consultant
                Ossian Ltd
                Scotland

                ** Remember to give credit where credit is due and leave reputation points where appropriate **

                Comment

                Working...
                X