Posts tagged: Exchange 2013

Fixing Exchange 2013 Website Security Cert

comments Comments Off on Fixing Exchange 2013 Website Security Cert
By , June 24, 2014 1:48 PM

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. ex2013-mbx1.windowsitadmin.net. I do a Godaddy cert for WindowsITAdmin.com 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.

cert-owaecp1

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

————————————————————————————————————–

VDir1

 

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 WindowsITAdmin.com

setVdir1

setVdir2

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

set-adisc

 

 Now accessing the Outlook Web Access

owa-fixed

 

Benefits of using Outlook Anywhere Outlook Anywhere

comments Comments Off on Benefits of using Outlook Anywhere Outlook Anywhere
By , December 16, 2013 12:40 PM

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.

http://technet.microsoft.com/en-us/library/bb123741(v=exchg.150).aspx

Exchange 2013 Integration with SharePoint 2013 – Free Workshop

comments Comments Off on Exchange 2013 Integration with SharePoint 2013 – Free Workshop
By , June 30, 2013 9:56 PM

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

Audience – IT MANAGERS/ IT DIRECTOR / IT CONSULTANTS / SYSTEMS ARCHITECT / SYSTEMS ENGINEER

 

  • 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.

     

    AGENDA

    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

     

    SPEAKERS

    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.”
    http://blogs.msdn.com/sowmyancs

     

    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
    About: http://blogs.technet.com/b/mspfe/p/mspfe.aspx
    TechNet Blog: MSPFE on TechNet
    Blog: MSPFE on MSDN
    Facebook: PFE on Facebook
    Twitter: #MSPFE
    MS Certified Solution Master

     

    REGISTER HERE

Secure Messaging Exchange 2013 and Previous Versions

comments Comments Off on Secure Messaging Exchange 2013 and Previous Versions
By , April 15, 2013 5:06 PM

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.

Creating Exchange 2013 Certificate – Step by Step

comments Comments Off on Creating Exchange 2013 Certificate – Step by Step
By , March 31, 2013 9:36 PM

njucug1

To create certificate is very simple like previous version except it is web based GUI and you may find different for the first time but it gets very easy. The only thing thing I don’t like is the Import/Export feature because you may find the option unless you clik some option in other words it is not written even on the click to Export/Import the certificate, there are just three four DOT DOT DOT (yes I  mean it and you will see it). Lets begin with creating the certificate

Exchange 2013 Certificates

Exchange 2013 Certificates

ex13-cert2

ex13-cert3

ex13-cert4

ex13-cert5

ex13-cert8

ex13-cert9

ex13-cert10

ex13-cert11

ex13-cert12

ex13-cert13

ex13-cert14

ex13-cert15

That’s it    –  If it was informative then please share it.

 

Exchange 2013-The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure.

comments Comments Off on Exchange 2013-The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure.
By , February 24, 2013 8:34 PM

if you are getting this error on Exchange 2013 CAS below is the fix. I have no idea what went wrong but both my CAS servers (lab environment stopped working). I was lucky enough to find the similar post for Exchange 2010 and soon after

The WinRM client received an HTTP server error status (500), but the remote service did not include any
other information about the cause of the failure.

WinRM1

 

FIX

SERVER MANAGER—–Features——Add Features——-WinRM IIS Extension —- you are done!

 

 

Panorama Theme by Themocracy