The most of you start wander “Where is the EMC (Exchange Management
Console) in Exchange Server 2013?” Well, some things remain the same as login
in the new Exchange Server 2013, and other things change (this is the
technology). Let’s see together which are the things are new in Exchange Server
2013, one of those is the EMC (Exchange Management Console).

Where
is the EMC (Exchange Management Console) and how where we can find it?
Almost everything in new Exchange 2013 is web-based management console, not EMC
(Exchange Management Console) but EAC (Exchange Administration Center), that
allows for ease of use and is optimized for on-premises, online, or hybrid
Exchange deployments. The EAC replaces the Exchange Management Console (EMC)
and the Exchange Control Panel (ECP), which were the two interfaces that were
used to manage Exchange Server 2010. One of the advantages of having the
web-based EAC is that you can partition access from the Internet/Intranet from
within the ECP IIS virtual directory to allow or disallow management features.
This allows you to permit or deny access to users trying to access the EAC from
the Internet outside of your organizational environment, while still allowing
access to an end-user’s Outlook Web App Options.

How can I login to EAC?

If we navigate to IE (Internet Explorer) and type http://server
FQDN/ecp (in my scenario is https://e2013.cloud.com/ecp

and voila, you are now logged in the new EAC old EMC console..

Supported browsers

For the best experience with the EAC, use one of the operating system and browser combinations labeled “Premium”.

• Premium: All functional features are well-supported and fully tested.
• Supported: Has same functional feature support as premium; however, supported browsers will be missing features that the browser and operating system combination doesn’t support.
• Unsupported: The browser and operating system isn’t supported or tested.

As we mention in Part1, Exchange Server 2013 has 2 server roles, Mailbox Server role and Client Access
Server role. We have the option to install either single server role or both the roles on the same computer.
In any case of installation role, CAS Role or both servers roles (CAS and Mailbox), Exchange Management Tools will be
installed together.

After you extract the Exchange-x64.exe file, start the exchange 2013 installation by click on the
setup file available on the installation file. Below window appears up,
check the option “Connect to the Internet and check for Updates” and click next to
continue.

On the Introduction page, read the information and click next to continue. If you plan
to use to Deployment assistant click on the necessary option.

Accept on the License Agreement page and click Next to continue

On the Error Reporting Window, Click Yes and Click Next to continue

Next step will automatically check for the required software if is installed in the
Server, if any issue appear, it will prompt you to fix it. If no error click
Next to Continue

On the Server Role Selection Windows, if it is standalone installation select both the
Mailbox and Client Access Server role and click Next to continue

Installation Space and Location windows will allow an option to change the installation
path, make necessary change or leave the default path and click Next

Type the Exchange Organization name and click Next 

Malware Protection Setting, this option is new in Exchange 2013 which will by default
scan all the emails, if you are using other option disable the option and click
Next to continue

If this Exchange 2013 server is an internet facing client access server then check the
option and enter the internet domain name. If not leave it as it is and click
Next to continiue.

On the Customer Experience Improvement Program, read the information, choose the
required option and click Next to continue

Readiness check windows will check of the all the options prior to install the Exchange
Server 2013. If everything is normal, then the installation will start.

Once the readiness check is completed Exchange Server 2013 installation will happen.
Once it is completed, click finish is complete the installation.

Enjoy..

In this post, we will see step by step the process of Exchange Server 2013 Preview installation in Windows Server 2012. 

The new Exchange Server 2013, split in 2 roles Client Access Server and Mailbox Server (In addition, Exchange 2013 Preview works with the Exchange 2010 Edge server role.)  The Mailbox server includes all the traditional server components found in Exchange 2010: the Client Access protocols, Hub Transport service, Mailbox databases, and Unified Messaging. The Mailbox server handles all activity for a given mailbox. The Client Access server provides authentication, redirection, and proxy services. The Client Access server itself doesn’t do any data rendering. The Client
Access server is a thin and stateless server. There is never anything queued or stored on the Client Access server. The Client Access server offers all theusual client access protocols: HTTP, POP and IMAP, and SMTP.

Before we proceed, we need to check the prerequisites for Exchange Server 2013, let’s see what we need to check before we begin:

• Make sure that the functional level of your forest is at least Windows Server 2003, and that the schema master is
  running Windows Server 2003 with SP1 or later.
• The full installation option of Windows Server 2012 and Windows Server 2008 R2 SP1 must be used for all servers
  running Exchange 2013 Preview server roles or management tools.
• You must first join the computer to the appropriate internal Active Directory forest and domain.
• Some prerequisites require you to reboot the server to complete installation.

To prepare Active Directory for Exchange 2013 Preview, you must install the following software on the computer that will be used to prepare Active Directory:

• Microsoft .NET Framework 4.5
• Windows Management Framework 3.0

After you install the software, open Windows PowerShell and install the Remote Tools
Administration Pack.

On a Windows Server 2012 computer, run the following command:
Add-WindowsFeature RSAT-ADDS

OS prerequisites for both the CAS and Mailbox roles:
Do the following to install the required Windows roles and features:

1. Open Windows PowerShell.
2. Run the following command to install the required Windows components.

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience,NET-Framework-45-Features, RPC-over-HTTP-proxy,
RSAT-Clustering,Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth,Web-Client-Auth,
Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression,Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect,
Web-Http-Tracing,Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase,Web-Mgmt-Console,
Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor,Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth,
Web-WMI, Windows-Identity-Foundation

After you’ve installed the operating system roles and features, install the following
software in the order shown:

1. Microsoft Unified  Communications Managed API 4.0, Core Runtime 64-bit
2. Microsoft Office 2010 Filter Pack 64 bit
3. Microsoft Office 2010 Filter Pack SP1 64 bit

For Exchange 2013 Preview, you must also uninstall Microsoft Visual C++ 11 Beta Redistributable
(x64). This must be done after you’ve installed UCMA, but before you run Exchange 2013 Preview Setup.
To uninstall Microsoft Visual C++ 11 Beta Redistributable (x64), do the following:

1. Open Control Panel > Programs and Features.
2. Select Visual C++ 11 Beta Redistributable (x64) – 11.0.50531 and then click Uninstall.
3. In Microsoft Visual C++ 11 Beta setup, click Uninstall.
4. When Microsoft Visual C++ 11 Beta is uninstalled, click Close.

To be continue….

Wanted to write a quick post about a tool that can help you find and catalogue various PowerShell scripts that are scattered on various online communities or – possibly – your internal company network shares.

The tool is called Microsoft Script Explorer for Windows PowerShell and has entered the public Beta 1 stage now.

• Download Microsoft Script Explorer for Windows PowerShell (pre-release)
• User guide
• Script Explorer Forum

Just to give you a taste of how it looks…

You can search scripts by category, with keywords or various other options. You can also dive directly into categories, which allows you to see scripts by product.

Source: Nino Bilic

Happy New Year 2012 to everyone….

In this Post, will see the step by step installation of Exchange 2010 SP2 and highlighting few things that you should know before installing Exchange Server 2010 SP2 in your production. First thing is to Test it in lab environment before installing in production environment.

What you must know before installing Exchange 2010 SP2:
SP2 includes schema changes

With certain new features, Exchange 2010 SP2 updates the schema. To understand what changes happen when you run Exchange 2010 SP2 read the Exchange Server Active Directory Schema Changes Reference, November 2011

Since, the installer will be requiring modifications to Schema, user account used for installation of SP2 must be a member of Schema Admins group in active directory. As a best practice, make sure that this user account is removed from the group once the schema extension is complete.

Windows Server Features are required for CAS Role

In Exchange Server 2010 CAS is the primary entry point for clients to any Exchange Server 2010 Environment. With this release, a few more features are added in the CAS server role which makes on premise and Office 365 integration a better experience and also an improvement that makes the silent redirection better within cross site CAS roles. A new feature called Mini Outlook Web App now exists that works on no cookies, no scripts model.

Below are Windows Server Role Features that you need to install before installing SP2 on CAS Role.

• IIS 6 WMI Compatibility
• ASP.NET
• ISAPI Filters
• Client Certificate Mapping Authentication
• Directory Browsing
• HTTP Errors
• HTTP Logging
• HTTP Redirection
• Tracing
• Request Monitor
• Static Content

After we finish with adding Windows Server Role Features which required to proceed with SP2 installation we run Setup.

1. Go to the folder which you have download from Microsoft site the Exchange 2010 SP2, unzip the Exchange 2010 SP2 package first, then launch setup program.

2. Follow the wizard, start to install SP2, read through the introduction and click Next button

3. Read through the license agreement, accept it and click Next button.

4. Next step Readiness Checks, Setup wizard finished successfully click Install.

5. Completion and final step is completed successfully, choose Finish.

6. After the installation is complete, we’ll see the following message, which informs us that we need to reboot the system for changes to take effect.

7. After reboot we can see that our Exchange Server was installed successfully SP2, Build number 14.2 (Build 247.5)

Installing Updates on DAG is not a normal exercise

Many of us run DAG because of its proven reliability and ability to make a highly available mailbox database system. Installing updates on a member of a DAG is not a regular installation though, for that reason please visits the link bellow in case you have DAG and you want to upgrade to SP2.

Upgrade Exchange 2010 to Exchange 2010 SP1 or Exchange 2010 SP2
http://technet.microsoft.com/en-us/library/bb629560.aspx

Διαθέσιμο για download το SP2 για τον Exchange Server 2010 στο Download Center της Microsoft.
Κατεβάστε το Exchange 2010 SP2 εδώ.

Overview

Microsoft Exchange Server 2010 SP2 helps IT Professionals achieve new levels of reliability with greater flexibility, enhanced user experiences, and increased protection for business communications.

• Flexible and reliable – Exchange Server 2010 SP2 gives you the flexibility to tailor your deployment based on your company’s unique needs and a simplified way to keep e-mail continuously available for your users.
• Anywhere access – Exchange Server 2010 SP2 helps your users get more done by giving them the freedom to securely access all their communications – e-mail, voice mail, instant messaging, and more – from virtually any platform, Web browser, or device.
• Protection and compliance – Exchange Server 2010 SP2 delivers integrated information loss prevention, and compliance tools aimed at helping you simplify the process of protecting your company’s communications and meeting regulatory requirements.

Important: The SP2 sets new pre-requirements to Windows, to install and upgrade from SP1. It requires an additional Windows role, which was not part of the SP1 pre-requirements. Which is: IIS 6 WMI Compatibility not being installed.
To install this before starting the SP2 install/upgrade, start a PowerShell and run:

· Import-Module ServerManager

· Add-WindowsFeature Web-WMI

This Windows role is required for Mailbox and CAS roles.

Στο σημερινό μας post θα δούμε την εγκατάσταση και την ρύθμιση του Exchange 2010 Edge Transport Server ρόλου. O Edge Transport Role στον Exchange Server 2010 παρέχει ένα υψηλό επίπεδο security μεταξύ external και internal επικοινωνίας. Με λίγα λόγια, ο Edge server σαν «φίλτρο» προστασίας της αλληλογραφίας (εσωτερικής και εξωτερικής). Ο Edge role θα πρέπει να εγκατασταθεί σε ξεχωριστό μηχάνημα « server» από τον server που είναι εγκατεστημένοι οι υπόλοιποι ρόλοι του Exchange Server 2010 HT, CAS, ΜΒ.

Τα προαπαιτούμενα «prerequisites» πριν την εγκατάσταση του Edge Transport Role είναι τα ακόλουθα:

· OS: Windows Server 2008 x64 SP 2 or Windows Server 2008 R2

· Microsoft .NET Framework 3.5

· Windows Remote Management 2.0

· Windows PowerShell V2

· Active Directory Lightweight Directory Services (AD LDS)

Προτού προχωρήσουμε με την εγκατάσταση του Edge Transport Role, αφού έχουμε ήδη ρυθμίσει τον Edge Transport σε DMZ (Demilitarized zone ή αλλιώς perimeter network) θα πρέπει να βεβαιωθούμε ότι το DNS suffix έχει προστεθεί για το “domain. Local”, στην περίπτωση μου είναι “emea.com”.

Μετά την ρύθμιση του DNS suffix θα σας ζητηθεί να επανεκκινήσετε «reboot» τον server. Εφόσον ξεκινήση server θα προχωρήσουμε σε εγκατάσταση του Edge Role, επιλέγουμε από το DVD του Exchange Server 2010 setup.com (Run as administrator).

Ο Wizard της εγκατάστασης ξεκινά..

Step1

Step2

Step3

Θα επιλέξουμε Custom εγκατάσταση για να μπορέσουμε να επιλέξουμε τον Edge Role

Step4

Step5

Η εγκατάσταση συνεχίζετε και το Readiness Checks ολοκληρώνετε, επιλέγουμε Install για να συνεχίσουμε.

Step6

Η διαδικασία εγκατάστασης του Edge Role ολοκληρώνεται με επιτυχία και επιλέγουμε Finish για να ολοκληρωθεί.

Step7

Μετά από την ολοκλήρωση της εγκατάστασης θα μα ζητηθεί να κάνουμε Restart για να εφαρμοστούν όλες οι αλλαγές.

Έφτασε η στιγμή να ρυθμίσουμε τον Edge Role να «μιλάει» με τον HUB Role, πάμε λοιπόν να δούμε την διαδικασία. Παραμένουμε στον Edge Server για να μπορέσουμε να δημιουργήσουμε το the Edge Subscription file μέσω της κονσόλας EMS (Exchange Management Shell) Run as administrator.

Πληκτρολογούμε την εντολή:
New-EdgeSubscription –Filename “C:\edge.xml”

Επόμενο βήμα μας είναι να αντιγράψουμε το xml αρχείο που δημιουργήσαμε στον Edge και να το κάνουμε import στον HUB transport server. Στην δική μου περίπτωση έχω έναν Exchange 2010 multi-role server (CAS/HUB/MBX).

Στον HUB transport server μας θα πάμε να ανοίξουμε την κονσόλα EMC àOrganization Configuration à Hub Transport à Edge Subscriptions και πραγματοποιώντας δεξί κλικ επιλέγουμε New EdgeSubscription.

Επιλέγουμε το AD Site όπου ο Edge θα πρέπει να γίνει subscribed και επιλέγουμε browse για να κάνουμε import το xml file που δημιουργήσαμε πρωτύτερα.

Σημείωση: Για να μπορέσουμε με επιτυχία να συγχρονίσουμε τον Edge server «Edgesync» θα πρέπει η πόρτα 50636 (TCP) να είναι ανοιχτεί στον HUB server(s) προς τον Edge server.
Εξ’ ορισμού ο Edge server ακούει στην πόρτα 50389.

Μόλις η διαδικασία του subscription ολοκληρωθεί με επιτυχία θα πρέπει να εμφανίζετε όπως στην ακόλουθη εικόνα.

Είναι ώρα να ξεκινήσουμε τον συγχρονισμό του Edge server Edgesync, την εντολή θα την εκτελέσουμε από τον Hub Server.

Επιπρόσθετες Πληροφορίες:

· Exchange port reference

· Overview of the Edge Transport Server Role

Microsoft has released Update Rollup 6 for Microsoft Exchange Server 2010 Service Pack 1 (SP1). This update is dated October 27 2011. This article describes the following information about the update rollup:

• The issues that the update rollup resolves
• How to obtain the update rollup
• The prerequisites to install the update rollup

Issues that the update rollup resolves

Update Rollup 6 for Exchange Server 2010 SP1 resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

• 2431609 (http://support.microsoft.com/kb/2431609/ ) An update is available that updates the message of a retention policy in OWA for Exchange Server 2010
• 2449266 (http://support.microsoft.com/kb/2449266/ ) EWS drops the TCP connection to the EWS client application without any error message in a Microsoft Exchange Server 2010 environment
• 2480474 (http://support.microsoft.com/kb/2480474/ ) A Users do not receive quota warning messages after applying SP1 for Exchange 2010
• 2514820 (http://support.microsoft.com/kb/2514820/ ) An incoming fax message is not delivered to the recipient in an Exchange Server 2010 SP1 environment
• 2521927 (http://support.microsoft.com/kb/2521927/ ) Disabling the Exchange ActiveSync Integration feature for OWA does not take effect in OWA Premium clients in an Exchange Server 2010 environment
• 2528854 (http://support.microsoft.com/kb/2528854/ ) The Microsoft Exchange Mailbox Replication service crashes on a computer that has Exchange Server 2010 SP1 installed
• 2535289 (http://support.microsoft.com/kb/2535289/ ) The Microsoft Exchange Information Store service crashes occasionally when you run an antivirus application on an Exchange Server 2010 Mailbox server
• 2536313 (http://support.microsoft.com/kb/2536313/ ) Slow message delivery and mailbox access for journaling mailboxes on an Exchange Server 2010 server
• 2544246 (http://support.microsoft.com/kb/2544246/ ) You receive a NRN of a meeting request 120 days later after the recipient accepted the request in an Exchange Server 2010 SP1 environment
• 2548246 (http://support.microsoft.com/kb/2548246/ ) The Microsoft Exchange Information Store service crashes occasionally when a folder view is corrupted on an Exchange Server 2010 mailbox server
• 2549183 (http://support.microsoft.com/kb/2549183/ ) "There are no objects to select" message when you try to use the EMC to specify a server to connect to in an Exchange Server 2010 SP1 environment
• 2549289 (http://support.microsoft.com/kb/2549289/ ) A RBAC role assignee can unexpectedly run the Add-MailboxPermission command or the Remove-MailboxPermission command on an Exchange Server 2010 server that is outside the role assignment scope
• 2555851 (http://support.microsoft.com/kb/2555851/ ) A mailbox does not appear in certain address lists after you run commands on the mailbox in an Exchange Server 2010 SP1 environment
• 2559814 (http://support.microsoft.com/kb/2559814/ ) A user cannot add or remove delegates from a mailbox by using Outlook in an Exchange Server 2010 environment
• 2561514 (http://support.microsoft.com/kb/2561514/ ) Exchange Server 2003 user cannot view the free/busy information of a user in a different federated organization
• 2563860 (http://support.microsoft.com/kb/2563860/ ) You cannot create a new mailbox database if you already have 1000 mailbox databases in an Exchange Server 2010 environment
• 2567409 (http://support.microsoft.com/kb/2567409/ ) Certain free/busy messages are not replicated from an Exchange Server 2010 server to an Exchange Server 2003 server
• 2571791 (http://support.microsoft.com/kb/2571791/ ) Retention policies are applied to Contact items unexpectedly in an Exchange Server 2010 environment
• 2572052 (http://support.microsoft.com/kb/2572052/ ) Certain properties of a recurring meeting request from external email accounts are missing in an Exchange Server 2010 SP1 environment
• 2575005 (http://support.microsoft.com/kb/2575005/ ) You cannot start the EMC or the EMS in an Exchange Server 2010 Service Pack 1 environment
• 2578631 (http://support.microsoft.com/kb/2578631/ ) Certain users cannot send email messages to a mail-enabled public folder in an Exchange Server 2010 environment
• 2579172 (http://support.microsoft.com/kb/2579172/ ) Items that are deleted or moved still appear in the original folder when you use Office Outlook in online mode to access an Exchange Server 2010 mailbox
• 2579671 (http://support.microsoft.com/kb/2579671/ ) No results returned when you use the ExpandGroup method in EWS to retrieve a list of members of a Dynamic Distribution Group in an Exchange Server 2010 environment
• 2582095 (http://support.microsoft.com/kb/2582095/ ) The SmtpMaxMessagesPerConnection property of a send connector is not replicated to the subscribed Edge Transport server in an Exchange Server 2010 environment
• 2600835 (http://support.microsoft.com/kb/2600835/ ) The RPC Client Access service crashes when you delete an attachment of an item by using Outlook in online mode in an Exchange Server 2010 SP1 environment
• 2601701 (http://support.microsoft.com/kb/2601701/ ) The memory usage of the MSExchangeRepl.exe process keeps increasing when you perform a VSS backup on Exchange Server 2010 databases
• 2616127 (http://support.microsoft.com/kb/2616127/ ) "0x80041606" error code when you use Outlook in online mode to search for a keyword against a mailbox in an Exchange Server 2010 environment
• 2617126 (http://support.microsoft.com/kb/2617126/ ) The Store.exe process crashes when you send an email message that has attachments in an Exchange Server 2010 SP1 environment
• 2627769 (http://support.microsoft.com/kb/2627769/ ) Some time zones in OWA are not synchronized with Windows in an Exchange Server 2010 environment

(KB2608646)

Στο σημερινό post θα δούμε την διαδικασία μεταφοράς ενός Exchange Server 2010 mailbox σε διαφορετική βάση (Database). Στον Exchange Server 2010 υπάρχουν δύο διαδικασίες μεταφοράς mailbox:

• Local Move – Η διαδικασία Local μας παρέχει την δυνατότητα μεταφοράς ενός mailbox από μια database σε μια άλλη (στον ίδιο ή διαφορετικό server, με την προϋπόθεση ο server να βρίσκετε στο ίδιο exchange organization).
• Remote Move – Η διαδικασία Remote μας παρέχει την δυνατότητα μεταφοράς ενός mailbox από μια database σε μια άλλη σε διαφορετικό forest.

Σημείωση: Δεν υποστηρίζετε η δυνατότητα μεταφοράς ενός mailbox από Exchange 2000 και 2007 SP1 σε 2010.

Για να πραγματοποιήσουμε την μεταφορά ενός mailbox από μια database σε μια άλλη στο ίδιο organization ακολουθούμε τα παρακάτω βήματα:

1. Θα μεταβούμε στην κονσόλα EMC (Exchange Management Console)

2. Επιλέγουμε Recipient Configuration και Mailboxes

3. Κάνουμε δεξί κλικ στο mailbox που θέλουμε να μεταφέρουμε και επιλέγουμε “New Local Move Request”.

Στο επόμενο βήμα θα επιλέξουμε την Database που θέλουμε να μεταφέρουμε το mailbox μας (στο παράδειγμα μας επιλέγουμε την MBDB01).

Επόμενο βήμα είναι να επιλέξουμε εάν θέλουμε να κάνουμε skip την διαδικασία μεταφοράς του mailbox σε περίπτωση που υπάρχουν κατεστραμμένα messages ή συνεχίζουμε την διαδικασία επιλέγοντας Next.

Στο επόμενο μας βήμα θα δούμε μία περίληψη του mailbox που προσπαθούμε να μεταφέρουμε. Επιλέγουμε New για να συνεχίσουμε.

Τελευταίο μας βήμα, η διαδικασία Move Request ολοκληρώνεται και επιλέγουμε Finish.

Ο Exchange δεν έχει ολοκληρώσει την διαδικασία μεταφορά του mailbox, απλά έλαβε μονάχα το request για μεταφορά. Για να επιβραβεύσουμε το status της μεταφοράς του mailbox, θα πάμε να το δούμε μέσα από την κονσόλα EMC (Exchange Management Console) στην επιλογή Move Request όπου εμφανίζετε η λίστα και το status της μεταφοράς του mailboxes. Όπως θα παρατηρήσετε και στην εικόνα μας, η διαδικασία ολοκληρώθηκε και το status μας λέει Completing.

Χρήσιμα Link

Managing Move Requests
http://technet.microsoft.com/en-us/library/bb124797.aspx

Microsoft has released Service Pack 2 (SP2) for TMG 2010 Standard and Enterprise editions.

The service pack includes the following new functionality and feature improvements:

New Reports
• The new Site Activity report displays a report showing the data transfer between users and specific websites for any user.

Error Pages
• A new look and feel has been created for error pages.
• Error pages can be more easily customized and can include embedded objects.

Kerberos Authentication
• You can now use Kerberos authentication when you deploy an array using network load balancing (NLB).

To read the release notes, see the Forefront TMG Release Notes (SP2).

Download SP2 here