SMBKitchen: Discovery phase

Using this as a guide - http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part2.html

Using these we'll make sure we understand the Exchange environment we have

The Exchange Management Console

  • The Exchange Management Shell for basic data collection and export
  • Exchange Environment Report Script
  • Exchange Profile Analyser
  • Exchange Best Practices Analyser
  • IIS Log Analysis
  • Windows Server Update Services reporting
  • I'll begin by following this guidance:

    "We'll begin by using the Exchange Management Console (EMC) to collect information about Internal and External URLs for Outlook Web App, The Offline Address Book and ActiveSync. For each service, navigate to the relevant tab within Server Configuration>Client Access then double click the listed Virtual Directory:"

    Click on Start, then on the Exchange Management console, then on the UAC prompt

    Go to client access, then to Outlook Web access tab.

    Note the Internal URL as well as the External url

    In our example it's both https://remote.sbs2essentials.com/owa for both

    Then go to the Offline Address book tab, right mouse click on properties

    it's https://remote.sbs2essentials.com/OAB

    "Next, we'll collect the value used for Outlook Anywhere. Right click the Server Name in the EMC, and choose Properties"

    In the case of a SBS 2008 it should be the same, but it's wise to double check.  remote.sbs2essentials.com

    Next up some PowerShell:

    "There's a couple for URL values we aren't able to collect from the EMC, so we'll need to open the Exchange Management Shell and use a couple of commands to return the information we need. First, lets grab the Internal URL and External URL for Exchange Web Services:

    Get-WebServicesVirtualDirectory | fl Name, InternalURL, ExternalURL  "

    Click on PowerShell for Exchange, don't forget to right mouse click and run as admin

    Now copy and paste the command

    Get-WebServicesVirtualDirectory | fl Name, InternalURL, ExternalURL 

    Remember over a HyperV you can click on clipboard and then it will copy over the commands

     

    The result will come back when you hit enter

     

    In our case it's

    InternalUrl : https://remote.sbs2essentaisl.com/EWS/Exchange.asmx

    ExternalUrl: https://remote.sbs2essentaisl.com/EWS/Exchange.asmx

    "We'll also need to retrieve the Service Connection Point value used for the Exchange Server. This value (or values for multiple servers) is the AutoDiscover URL that is provided to Outlook clients that are domain joined:"

    Get-ClientAccessServer | fl Server,*URI

    "Finally we'll examine the SSL certificates and subject alternative names in use. You can if you wish view these details by accessing the server directory, or simply by visiting the Internal and External URLs from the LAN and externally examining the Subject Alternative Names recorded on the certificate:"

    In our example we just have our domain name.

    In our example our autodiscover is up at our DNS hoster as a srv record.

    "Record the names listed on the certificates, and then verify the names listed are actually in DNS. If they aren't listed in either internal or external DNS then that means the names aren't actually in use and we can consider ignoring them. For example, to check internal Active Directory-integrated DNS, we'll access a Domain Controller and open DNS Management. Navigate to the domain and verify each Subject Alternative Name (and FQDN) listed."

    Click on start, administrative tools, then DNS and review the setup

    In the case of SBS we have a split DNS

    We have a DNS setting for our domain name - remote.sbs2essentials.com

    and then we have our internal domain name of .local

     

    as you can see here:

    "Finally we'll revisit the Exchange Management Console and view the name used - if any - for services including POP and IMAP. Navigate to Server Configuration, then select the respective IMAP and POP tabs and select the properties for each service. Record the x509 certificate subject name from the Authentication tab as shown below."

    Again it's our remote.sbs2essentials.com.

    And if anyone is still using the pop connector and they are migrating to ON PREMISES Exchange... honey we need to talk.  You should long ago have killed that off.

    "To determine whether you need to consider either IMAP or POP namespaces, we'll check the service startup settings for both. Open the Services Management Console via Start>Run then entering services.msc and scroll down to find the Microsoft Exchange POP3 and Microsoft Exchange IMAP services as shown below."

    In our case we're not using IMAP or POP3.

    After collection the namespaces, we'll record them as shown below:

    Service

    Internal URL

    External URL / FQDN

    OWA

    https://remote.sbs2essentials.com/OWA

    https://remote.sbs2essentials.com/OWA

    OAB

     https://remote.sbs2essentials.com/OAB

     https://remote.sbs2essentials.com/OAB

    EWS

    https://remote.sbs2essentials.com/EWS/Exchange.asmx

    https://remote.sbs2essentials.comEWS/Exchange.asmx

    Outlook Anywhere

    N/A

    remote.sbs2essentials.com

    POP3

    N/A

    remote.sbs2essentials.com

    SCP

    https://autodiscover.remote.sbs2essentials.com/Autodiscover/Autodiscover.xml

     

     

    Next up the Exchange Environment Report

    Blogging my way (starting over) through a proof of concept migration from SBS 2008 to Essentials 2012 R2 series will be a SMB kitchen project whitepaper.  More about the SMBKitchen project at - http://www.thirdtier.net/enterprise-solutions-for-small-business 

    About the Author

    Susan is just a wacko SBSer who started down her path by hanging out in the SBS newsgroup community. She's not a Microsoft employee or affiliated with Microsoft. Get a feel of the SBS “vibe” and join in the SBS community!