Exchange 2013 – Creating SEND Connector

Here is another very common post on the Exchange forum by many new Exchange Admin that they have setup/installed the Exchange but they can’t send the emails. The reason is simple that you need to setup a very first send connector for your outbound email flow

Open the Exchange Admin Center —goto Mail Flow — Send Connector



Click the PLUS + button to create a ‘new send connector’



Give a suitable name to the connector – in my case it is INTERNET



Click Next and the screen below show that you need to type the name of FQDN. We will set it up as *  so it can send out email to any domain on the internet.  Then SAVEsend3


Below select the source server- I have two servers in this case and i’m going to add both of them



and here it is when you are done with creating the send connector – it is time to test your outbound emails.send5





Fixing Exchange 2013 Website Security Cert

A typical Exchange Website right after you install the Exchsnge Server 2013 or legacy version. This post will show you how to fix it. If you  look at the address it has server name and the domain name i.e. I do a Godaddy cert for and I will show in this post how to fix this issue and as well set the other Exchange Virtual directories for OWA ECP and Autodiscover to replicate a production environment.


Once we are done with configuration it will appear as HTTPS://MAIL.WINDOWSITADMINC.COM/ECP & HTTPS://MAIL.WINDOWSITADMIN.COM/OWA AND also AutoDiscover

Let’s begin – (it is assumed that you have already installed or imported the certificate – check out my previous blog post)

First step is being with setting up the virtual directories


Existing default default setup/virtual directories




This is a pull using Powershell fro server ex2013-mbx1 server of the same above OWA  virtual directoryVDir2


Another pull fro ECP Virtual DirectoryVDir3

Now I am going to set all the Virtual Directories to



Same way I will setup the OAB Powershell EWS and Microsoft ActiveSync Virtual Directories for both Internal and External URL depending on the requirement.

Now moving on setting up the Autodiscover Uri for Outlook



 Now accessing the Outlook Web Access



Benefits of using Outlook Anywhere Outlook Anywhere

Outlook Anywhere offers the following benefits to clients that use Outlook 2013, Outlook 2010, or Outlook 2007 to access your Exchange messaging infrastructure:
Users have remote access to Exchange servers from the Internet.
You can use the same URL and namespace that you use for Outlook Web App and Microsoft Exchange ActiveSync.
You can use the same Secure Sockets Layer (SSL) server certificate that you use for both Outlook Web App and Exchange ActiveSync.
Unauthenticated requests from Outlook can’t access Exchange servers.
You don’t have to use a virtual private network (VPN) to access Exchange servers across the Internet.
If you already use Outlook Web App with SSL or Exchange ActiveSync with SSL, you don’t have to open any additional ports from the Internet.
You can test end-to-end client connectivity for Outlook Anywhere and TCP-based connections by using the Test-OutlookConnectivity cmdlet.

Exchange 2013 Integration with SharePoint 2013 – Free Workshop

Join the team of experts to know learn about the new wave of Microsoft product on unified communication platform. This month July 18th we will have two MS PFE who will discuss the integration of Exchange and SharePoint 2013. The event is free



  • Exchange and SharePoint Integration

    Exchange Server 2013 and SharePoint Server 2013 Integration
    Microsoft Exchange Server 2013 includes many features that integrate with Microsoft SharePoint 2013. Discuss solutions for deploying Exchange Server 2013 and SharePoint Server 2013 together, including e-Discovery, high-resolution user photos, unified contact store, site mailboxes, Exchange task synchronization. Learn tips and tricks on configuring and taking advantage of the integration between the products.



    6:15-6:45 PM – Socializing
    6:45-7:00 PM – Sponsor Introduction
    7:00-8:30 PM – Topic of the day
    8:30-9:00 PM – Q&A and door closes at 9:00 PM



    Sowmyan Soman Chullikkattil– Premier Field Engineering, Microsoft
    “Sowmyan is one of the few SharePoint experts who achieved the Microsoft Certified Solutions Master (MCSM) title. He has been working with Microsoft Technologies for about seven years. He  joined  Microsoft Corporation as a support engineer in SharePoint developer support team. He has been working as SharePoint Premier Field Engineer in New York since the last 3 years . Under this role, he has taken up several proactive and reactive engagements with premier customers across USA.”


    Kamal Abburi – Premier Field Engineering, Microsoft
    Kamal Abburi is a Premier Field Engineer for Microsoft based in the New York/New Jersey region supporting customers improve their IT health, drive successful deployments, improve service availability by delivering Proactive Services like Workshops, Health Checks, Risk Assessments and Reactive Services like on-site support, troubleshooting and Problem Prevention. He worked in the IT Industry for 14 years on various Microsoft Technologies primarily helping Enterprise customers with Exchange deployments, migrations and training.


    Microsoft Premier Field Engineering
    TechNet Blog: MSPFE on TechNet
    Blog: MSPFE on MSDN
    Facebook: PFE on Facebook
    Twitter: #MSPFE
    MS Certified Solution Master



Secure Messaging Exchange 2013 and Previous Versions

Microsoft Exchange Server 2013 provides administrative functionality and other enhancements that improve the overall management of Transport Layer Security (TLS). As you work with this functionality, you need to learn about some TLS-related features and functionality. Some terms and concepts apply to more than one TLS-related feature.

What is the difference between Exchange 2010 and Exchange 2013 TLS?
There is NO difference , it works the same. It uses the same Opportunistic TLS mechanism.

So what is Opprtunitics TLS by definition from TechNet?
Opportunistic TLS In earlier versions of Exchange, you had to configure TLS manually. In addition, you had to install a valid certificate, suitable for TLS usage, on the server running Exchange. In Exchange 2013, Setup creates a self-signed certificate. By default, TLS is enabled. This enables any sending system to encrypt the inbound SMTP session to Exchange. By default, Exchange 2013 also attempts TLS for all remote connections.

My previous post about MS Exchange 2010 TLS

Resource URLS
Exchange 2013 TLS Functionality
Exchange 2010 TLS Functionality

Secure messaging is simple too.