Share via

Exchange 2013 on Windows Server 2012 (Stand Alone DC)

  • Article

In this article I have explained step by step installation of Exchange 2013 on windows server 2012 standalone server (DC server: Though not recommended) its just a Lab environment, following steps will save a lot of time and error free installation.

*"Exchange Server 2013 is bringing a lot of exciting new features which deserve several articles to describe each one of them in detail.
*

  1. New Architecture
    There are only two roles now: Mailbox and Client Access. The new Mailbox role will contain all components of CAS/HUB/Mailbox and UM comparing with Exchange Server 2010 roles and it will handle all processes for any given mailbox. The new CAS will proxy, authenticate and redirect requests. Just by doing this change the future upgrades will be easier, since there is no translation work being done at CAS. The NLB is much simpler as well, because we need only Layer 4 level on our Load Balancers.
  2. Management Tools
    Exchange Management Console is gone, the two ways that we have to manage the product is using either Exchange Management Shell or the web interface EAC (Exchange Admin Center).
  3. Outlook client
    Because of the architectural change, the product has changed how the clients will connect to the server. The decision was to remove MAPI and use only Outlook Anywhere (RPC over HTTP).
  4. Public Folders and Collaboration
    They are back and with cool new features, such as: new replication method using a single-master replication model. In this new release we will also have a Site Mailbox which is a feature that will integrate Mailbox and SharePoint information in a single location for the end-user." [msexchange.org (part1)]

whatever the size of your VMware machine, but for production you need atleast 8 GB RAM,

  After prereqs... Installing windows server 2012 on your test machine (hyper v or VMware machine), ADDS, and then promoting as a DC (not recommended by MS), static Ip, Update and a domain.

Exchange Setup (extract to a folder) and then follow step by step:

Prepare Schema:

Prepare AD & Organization Name *(in this case PirExchange)

Accept License agreement Always

Preparing domain

installing feature in windows Power shell (Tip: use  cd.. )

Installing Windows Features using Exchange Server 2013 Setup Wizard

"If you don’t want to type in too much information in PowerShell, you can use this lazy approach that will have the same result:

  1. Install Desktop Experience on the server by running the following cmdlet:
    Add-WindowsFeature Desktop-Experience (figure below)
    Note: This feature is a requirement to install Microsoft Unified Communications Managed API 4.0"    *** [msexchange.org (part 1)]***

Simple next next done:

Microsoft Filter Pack and Exchange Server 2013…

"Finally, we have the Microsoft Filter pack dilemma and it has changed in this new version. Exchange Server 2013 uses a new search engine however the Filter Pack is still required when you want to use Transport Rules for either Office OneNote or Publisher files.

It’s up to you as it doesn’t hurt to install it. I would recommend going ahead and installing it on Exchange Server 2013 that will have the Mailbox server role deployed.

The installation is a straight forward process and the only decision making is during the license agreement portion of the package which is not challenging at all."** **[msexchange.org (part 1)]

**

**

User Account Settings and Exchange Server 2013 deployment…

*"Just a follow up in this area, if you use UAC (User Account Settings) make sure that you right-click on the setup.exe installation from Exchange and run it as Administrator (Figure below)." *** **[msexchange.org (part 1)]


if you have internet click connect else dont check updates right now.

accept agreement and click next on introduction page and setup will start \ (GUI mode)

"On the Malware Protection Settings page (Figure below). That is a new feature of Exchange Server 2013, where we have Malware protection and this option can be managed through Exchange Administration Center or Exchange Management Shell afterwards. Let’s leave the default settings and click Next." [msexchange.org (part 2)]

Since as I mentioned earlier MS doesn't recommend installing exchange 2013 on DC, however I have done and its work fine for me in LAB environment ) but mind you in production environment it may create headaches in administration.

Click Install


there you go restart & now you will see Exchange Management Shell & Exchange toolbox

Post configuration tasks are coming soon.
Cheers!