Exchange 2013 Step by Step Configuration

fonte: http://www.techieshelp.com/exchange-2013-step-by-step-configuration/

Written by Allen White on. Posted in Exchange 2013

exchang 2013 install guide
This guide is a combination of all the Exchange 2013 guides already on the site but in the order I wouldconfigure Exchange 2013 in. From out of the box installation through to spam configuration and setting up an SSL cert in Exchange 2013.Treat this article as your main Exchange 2013 configuration guide. All the pages will open in a new window.

Deployment Scenario

This solution is based on a new Exchange 2013 environment, no previous Exchange servers have been installed on this domain previously. If you are migrating from Exchange 2010 then the version of Exchange 2013 you will need is Exchange 2013 Cu2 at minimum find that here http://www.microsoft.com/en-us/download/details.aspx?id=39609 and your exchange 2010 will need to be at service pack 3 before you install Exchange 2013 into your organization , find that here http://www.microsoft.com/en-us/download/details.aspx?id=36768 . This deployment is greenfield and will work on Server 2008 R2 or as Ive wrote it for Server 2012.

First we need to actually install Exchange 2013, this is on Server 2012. This article is located here

How Do I Configure Exchange 2013?

Once Exchange 2013 is installed we then need to enter the product key for Exchange 2013 to enable certain features and be licensed correctly.

Now that the Exchange 2013 product key is entered we are ready to configure Exchange 2013, we will firstsetup the Send Connector so we cant send mail out.

If you decided you want to put a limit on the size of email you send out on the send connector then use this guide.

Once that is done we need to configure and check that Exchange 2013 is ready to accept mail for your domain the receive connector is set to receive mail by default from external domains, we now need to tell Exchange 2013 what domains to accept mail for.

As we are sending and receiving mail now we should really think about anti-spam measures, lets now setup Exchange 2013 anti spam to stop users getting lots of junk mail.

Now that our email is secure and safe we can add users to Exchange 2013 so they can start to send a receive mail. First so Outlook or your email client can connect to Exchange and configure automatically create an A record called Autodiscover in DNS and point it to the IP address of the Exchange server with the CAS role. Then use the guide below to create your users.

As users are sending email now to and from the domain we realy should add a disclaimer to Exchange 2013.

So email is now flowing, we are protected from spam and we also issue a disclaimer when sending email out. Lets think about when users attach through owa, we need to secure exchange 2013 with an SSL certificate.

Now you have followed all the Exchange 2013 guides you will have a fully functioning Exchange 2013 enviroment. If you want to optimize Exchange 2013 even more then check out the Exchange 2013 category for more articles such as catch all mailboxes and many more. Hope this helps.

FINALLY!..for much more information on what you can and cannot do in Exchange 2013 check out the whats new section for Exchange 2013 from Microsoft.
Whats new in Exchange 2013.

How To Migrate Windows Server 2008 R2 Active Directory Domain Services To Windows Server 2012

fonte: http://www.elmajdal.net/WindowsServer/How_To_Migrate_Windows_Server_2008_Active_Directory_Domain_Services_To_Windows_Server_2012.aspx

To perform the below steps, you will need to use a domain account which is member member of Domain Admins and Enterprise Admins Groups and member of the Schema Admins group. I will be using the domain Administrator account which is already a member of all these groups.

Migrating your Domain Controller from Windows Server 2008 to Windows Server 2012 undergoes a few major steps, which are discussed in details below :

Step 1 : Check Forest and Domain Functional Level

  1. The Forest Functional level and Domain Functional Level must be at least Windows Server 2003

  2. To Check The Functional Levels, read my article : How to Raise the Forest and Domain Functional Levels in Windows Server 2008/R2

Step 2 : Preparing Active Directory Schema

The schema has to be upgraded and prepared for Windows Server 2012. To do this you have to run the adprep command.

  1. Insert the Windows Server 2012 /R2 DVD into the DVD drive of the Windows Server 2008 / R2 Domain Controller

  2. Open command prompt in administrative mode, and type adprep /forestprep and press enter.

  3. Open the Directory of the DVD drive and navigate to adprep directory and then type : adprep /forestprep

    You will receive a warning that all active directory domain controllers in the forest must be running at least windows server 2003. click c  andEnter to confirm and continue.

    Adprep will successfully update the forest

  4. Then type adprep /domainprep and press enter

Step 3 : Install Windows Server 2012 and join it to the Windows Server 2008 Domain

  1. For Installing Windows Server 2012, read this article :  How To Install Windows Server 2012

  2. For Joining Windows Server 2012 to the domain of Windows Server 2008, read this article : How To Join Windows Server 2012 to a Domain

Step 4 : Setting Up Additional Active Directory Domain Controller With Windows Server 2012

By now you already have your Windows Server 2008 Domain Controller, and you have installed Windows Server 2012 and is now a domain member. Now we need to introduce our first Windows Server 2012 domain controller in our network. This has been discussed in a previous article, read it here :Setting Up Additional Active Directory Domain Controller With Windows Server 2012

Step 5 : Transferring the Flexible Single Master Operations (FSMO) Role

You have your Windows Server 2008 Domain Controller ( in my lab its called : ELMAJDAL-DC ) and have an additional Windows Server 2012 domain controller ( in my lab its called : ELMAJDAL-DC13). To complete the migration , we need to transfer 5 FSMO roles to the new domain controller.

The five FSMO roles are:

  • Schema Master

  • Domain Naming Master

  • Infrastructure Master

  • Relative ID (RID) Master

  • PDC Emulator

To check who is currently holding FSMO, run the following command : netdom query fsmo

The FSMO roles are currently with the Windows Server 2008 R2 domain controller : ELMAJDAL-DC

The FSMO roles are going to be transferred, using the following three MMC snap-ins :

  • Active Directory Schema snap-in : Will be used to transfer the Schema Master role

  • Active Directory Domains and Trusts snap-in : Will be used to transfer the Domain Naming Master role

  • Active Directory Users and Computers snap-in : Will be used to transfer the RID Master, PDC Emulator, and Infrastructure Master roles

Lets start transferring the FSMO roles.

  • Using Active Directory Schema snap-in to transfer the Schema Master role

You have to register schmmgmt.dll in order to be able to use the Active Directory Schema snap-in

  1. Open Command Prompt in administrative mode and type regsvr32 schmmgmt.dll

  2. Open Microsoft Management Console , mmc

  3. Click File > then click Add/Remove Snap-in…


  4. From the left side, under Available Snap-ins, click on Active Directory Schema, then click Add > and then click OK

  5. Right click Active Directory Schema, then click Change Active Directory Domain Controller…


  6. From the listed Domain Controllers, click on the domain controller that you want to be the schema master role holder and then click on OK

    You will receive a message box stating that the schema snap-in is not connected to a schema operations master. That is for sure, as we have not yet set this Windows Server 2012 domain controller as a Schema Master role holder. This will be done in the next step. Click OK


  7. In the console tree, right click Active Directory Schema [DomainController.DomainName], and then click Operations Master…


  8. On the Change Schema Master page, the current schema master role holder will be displayed ( ex. ELMAJDAL-DC.ELMAJDAL.COM) and the targeted schema holder as well (ex. ELMAJDAL-DC13.ELMAJDAL.COM). Once you click Change, the schema master holder will become
    ELMAJDAL-DC13.ELMAJDAL.COM
    , click Change

    Click Yes to confirm the role transfer

    The role will be transferred and a confirmation message will be displayed. Click OK

    Then click Close, as you can see in the below snapshot, the current schema master is ELMAJDAL-DC13.ELMAJDAL.COM which is the Windows Server 2012 DC


  • Using Active Directory Domains and Trusts snap-in to transfer the Domain Naming Master Role

  1. From the Start Screen, open the Active Directory Domains and Trusts

  2. Right click Active Directory Domains and Trusts, then click Change Active Directory Domain Controller…


  3. From the listed Domain Controllers, click on the domain controller that you want to be the Domain Naming master role holder and then click onOK


  4. Right click Active Directory Domains and Trusts, then click Operations Master…


  5. On the Operations Master page, we are going to change the Domain Naming role holder from ELMAJDAL-DC.ELMAJDAL.COM toELMAJDAL-DC13.ELMAJDAL.COM, Click Change

    Click YES to confirm the transfer of the Domain Naming role. The role will be transferred and a confirmation message will be displayed. ClickOK , then click Close


  • Using Active Directory Users and Computers snap-in to transfer the RID Master, PDC Emulator, and Infrastructure Master Roles

  1. From the Start Screen, open the Active Directory Users and Computers console

  2. Right click your domain and select Operations Masters

  3. In the Operations Masters window, ensure the RID tab is selected.

    Click the Change button. Select Yes when asked about transferring the operations master role. Once the operations master role has successfully transferred, click OK to continue.

  4. Ensure the Operations Master box now shows your new Windows Server 2012

  5. Repeat steps 4 to 6 for the PDC and Infrastructure tabs.

    >>
    >>

    Once completed, click Close to close the Operations Masters window.

If you would like to check if the roles were properly transferred, open command prompt and type: netdom query fsmo. If you see your new server listed in each role, you have successfully transferred all of your FSMO roles to the new server

Related Articles

How To Join Windows Server 2012 to a Domain

How to Raise the Forest and Domain Functional Levels in Windows Server 2008/R2

Setting Up Additional Active Directory Domain Controller With Windows Server 2012