Monthly Archives: January 2014

You are browsing the site archives by month.

SMBKitchen: Configure Exchange 2013 external URLs

Configure Exchange 2013 external URLs


 

Estimated time to complete: 10 to 15 minutes


There are several settings that you need to configure on the Exchange 2013 virtual directories, which include Outlook Anywhere, Exchange ActiveSync, Exchange Web Services, Offline Address Book (OAB), Outlook Web App, the Exchange admin center, and the availability service.


Learn more at: Virtual Directory Management




  1. Open the EAC by browsing to the URL of your Client Access server. For example, https://Ex2013CAS/ECP.
  2. Enter your user name and password in Domain\user name and Password, and then click Sign in.
  3. Go to Servers > Servers, select the name of the Internet-facing Exchange 2013 Client Access server and then click Edit Edit Icon.


  4. Click Outlook Anywhere.
  5. In the Specify the external hostname field, specify the externally accessible FQDN of the Client Access server. For example, mail.contoso.com.
  6. While you’re here, let’s also set the internally accessible FQDN of the Client Access server. In the Specify the internal hostname field, insert the FQDN you used in the previous step. For example, mail.contoso.com.
  7. Click Save.

 


I think we change that internal domain name to match the external one?


 



 


If this is wrong I’ll clarify in a new post and edit this one.


Hit save and you’ll get a warning which is okay



  1. Go to Servers > Virtual directories and then click Configure external access domain Configure icon.

 



  1. Under Select the Client Access servers to use with the external URL, click Add Add Icon.

 


  1. Select the Client Access servers you want to configure, and then click Add.

 


 


  1. After you’ve added all the Client Access servers you want to configure, click OK.
  2. In Enter the domain name you will use with your external Client Access servers, type the external domain you want to apply. For example, mail.contoso.com. Click Save.


  3. noteNote:
    Some organizations make the Outlook Web App FQDN unique to protect users against changes to underlying server FQDN changes. Many organizations use owa.contoso.com for their Outlook Web App FQDN instead of mail.contoso.com. If you want to configure a unique Outlook Web App FQDN, do the following after you completed the previous step. This checklist assumes you have configured a unique Outlook Web App FQDN.
    1. In Select server, choose your Exchange 2013 Client Access server.
    2. Select owa (Default Web Site) and click Edit Edit Icon.
    3. In External URL, type https://, then the unique Outlook Web App FQDN you want to use, and then append /owa. For example, https://owa.contoso.com/owa.
    4. Click Save.
    5. Select ecp (Default Web Site) and click Edit Edit Icon.
    6. In External URL, type https://, then the same Outlook Web App FQDN that you specified in the previous step, and then append /ecp. For example, https://owa.contoso.com/ecp.
    7. Click Save.
  4. Click Save.


To verify that you have successfully configured the external URL on the Client Access server virtual directories, do the following:

  1. In the EAC, go to Servers > Virtual directories.
  2. In the Select server field, select the Internet-facing Exchange 2013 Client Access server.
  3. Select a virtual directory and then, in the virtual directory details pane, verify that the External URL field is populated with the correct FQDN and service as shown below:





  4.  
  5. Virtual directory External URL value

    Autodiscover

    No external URL displayed

    ECP

    https://owa.contoso.com/ecp

    EWS

    https://mail.contoso.com/EWS/Exchange.asmx

    Microsoft-Server-ActiveSync

    https://mail.contoso.com/Microsoft-Server-ActiveSync

    OAB

    https://mail.contoso.com/OAB

    OWA

    https://owa.contoso.com/owa

    PowerShell

    http://mail.contoso.com/PowerShell


Blogging my way 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

SMBKitchen: Create a mailbox

Create an Exchange 2013 mailbox


 

To simplify configuration of Exchange 2013 and to help test your new server later on, you need to create an Exchange 2013 mailbox. We’ll make this new mailbox a member of the Organization Management role group and you’ll use this mailbox when you configure Exchange 2013.


Later on in the checklist you’ll need to log into your Exchange 2013 servers. Log in using the Exchange 2013 mailbox you’ll create in this step. This will make sure you have the correct permissions to perform each of the steps and that the EAC opens correctly.


How do I do this?


  1. Open the EAC by browsing to the URL of your Client Access server. For example, https://Ex2013CAS/ecp?ExchClientVer=15.
    importantImportant:
    You need to include ?ExchClientVer=15 in the URL when you want to open the EAC with a user that doesn’t have an Exchange 2013 mailbox.
  2. Open the EAC by browsing to the URL of your Client Access server. For example, https://Ex2013/ecp?ExchClientVer=15.

In my case https://Exchange/ecp?ExchClientVer=15 which resolves to



 


importantImportant:
You need to include ?ExchClientVer=15 in the URL when you want to open the EAC with a user that doesn’t have an Exchange 2013 mailbox.


  1. Enter the user name and password of the account you used to install Exchange 2013 in Domain\user name and Password, and then click Sign in.
  2. I used the domain account so we’ll log in with the domain user account.

 


 



 


 



  1. Go to Recipients > Mailboxes. On the Mailboxes page, click Add Add Icon and then select User mailbox.

 


  1. Provide the information required for the new user and then click Save.

Note, I placed this Exchange user in the SBS Organizational unit under SBSUsers 



  1. Go to Permissions > Admin Roles. On the Admin Roles page, select Organization Management and click Edit Edit Icon.
  2. (the edit is the pencil icon

 


  1. Under Members, click Add Add Icon.

 



  1. Select the Exchange 2013 mailbox you just created, click Add, then click OK. Then click Save.

How do I know this worked?

To verify that you’ve successfully created an Exchange 2013 mailbox and added it as a member of the Organization Management role group, do the following:

  1. In the EAC, go to Permissions > Admin Roles. On the Admin Roles page, select Organization Management.
  2. In the details pane, view the Members list. If the Exchange 2013 mailbox has been successfully added as a member of the Organization Management role group, the mailbox will be listed here.

 


 



 


 


Blogging my way 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

Enough is Enough Microsoft, stop making it hard for me to support you like this

http://techverse.net/download-windows-7-iso-x86-x64-microsofts-official-servers/
UPDATE : 1/30/2014 : It seems Microsoft has stopped providing Windows 7 ISO images. The Windows 7 links provided below are discontinued

When we have to do a repair install and the person has no media, these are the links I would post.

Now that you’ve pulled these, you’ve effectively crippled all operating systems.

The reality of Windows 7 is that it gets component based servicing stack issues that no fixit will fix and ONLY a non destructive repair install will fix.


UPDATE : 1/31/2014 : The links provided for Windows 7 ISO images are not working currently. It seems to be a temporary issue with Digitalriver. According to Microsoft the problem should be resolved in the next couple of days.

http://techverse.net/download-windows-7-iso-x86-x64-microsofts-official-servers/

Thank goodness.

SMBKitchen: More checking on our deployment

http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2284-W-DgBEAgAAQACACAEAAQAAAA%7e%7e


Review the setup log file




You can also learn more about the installation and configuration of Exchange 2013 by reviewing the setup log file created during the setup process.


During installation, Exchange Setup logs events in the Application log of Event Viewer on computers that are running Windows Server 2008 R2 with Service Pack 1 (SP1) and Windows Server 2012. Review the Application log, and make sure there are no warning or error messages related to Exchange setup. These log files contain a history of each action that the system takes during Exchange 2013 setup and any errors that may have occurred. By default, the logging method is set to Verbose. Information is available for each installed server role.


You can find the setup log file at <system drive>\ExchangeSetupLogs\ExchangeSetup.log. The <system drive> variable represents the root directory of the drive where the operating system is installed.



The setup log file tracks the progress of every task that is performed during the Exchange 2013 installation and configuration. The file contains information about the status of the prerequisite and system readiness checks that are performed before installation starts, the application installation progress, and the configuration changes that are made to the system. Check this log file to verify that the server roles were installed as expected.


We recommend that you start your review of the setup log file by searching for any errors. If you find an entry that indicates that an error occurred, read the associated text to figure out the cause of the error.


Early on in my hyperV test I didn’t have the second server set to look at the SBS box for it’s DNS settings.  When you are in a test situation sometimes your networking isn’t a great as it could be. So if you set static nics and have the second server have as it’s DNS settings the main server, it will find the main domain controller and be happy.


What you see in my event logs is just that early whoopsie where I didn’t have the DNS set and the second server couldn’t find the DC



 


Blogging my way 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

SMBKitchen: Checking that it worked

How do I know this worked?




Run Get-ExchangeServer

To verify that Exchange 2013 installed successfully, run the Get-ExchangeServer cmdlet in the Exchange Management Shell. A list is displayed of all Exchange server roles that are installed on the specified server when this cmdlet is run.

For detailed syntax and parameter information, see Get-ExchangeServer

And there’s our SBS 2008/Exchange 2007 and our 2013 Exchange server showcasing we have the two chugging along nicely.

and may I just say that hitting the swipe/charm thingy on a Server 2012 over a HyperV manager window is not easy lemme tell ya.

SMBKitchen: Are we insane?

Right about now in this stage of the process I am questioning my sanity.  I honestly have never installed Exchange before.  So while I want to go through the methodical step by step gui process to understand what is going on, to make this feasible from a business deployment standpoint we either need to script it or PowerShell this deployment in the future to make it repeatable.  While the TechNet Essentials instructions have a script for Exchange 2010 (see http://technet.microsoft.com/en-us/library/jj200172.aspx) , they do not have one for 2013.


What you can do when it’s your first is to obviously test.  Or hire the folks at www.thirdtier.net to do it for you and then you hang over their shoulder (virtually that is) and pepper them with questions.  And review the current script info posted on Exchange 2013 – http://technet.microsoft.com/en-us/library/aa997281%28v=exchg.150%29.aspx



At this point remember to back up your SBS box because we are making changes to Active Directory…. and here we go….



Now copying files




 


 


We’re getting mailboxes installed…



 


Client access role



Next step 10



Next step



 


Right about now you see we need more automation and a script if we’re going to be doing this over and over again for clients



 


We’re onto step 13



Step 14



And we’re done



  1. On the Completion page, click Finish.

  1. noteNote:
If you didn’t separate your Active Directory schema preparation from the installation of Exchange 2013, the amount of time this takes is dependent upon your Active Directory site topology. It might take some time for the changes to replicate across your organization.


  1. Restart the computer after Exchange 2013 has completed.

SMBKitchen: Installing Exchange via GUI

I’m going to use this as an exercise in trying out installing Exchange via the gui (no PowerShell script).  Honestly, the most efficient way is to install this via a script but I’m doing this the slow step by step way to see what happens.


Up next in our install is the prereq check where we see that the system needs to do certain things (IIS setups)



It will actually do these IIS items and at this point need a reboot.



Don’t do anything but reboot at this point and then  have the prereq checker check again



When you reboot all these items are installed



We start again



And we check for mailbox and client access role



Again I check for malware



This time there is a much smaller item of things missing, this time it’s downloads.


We need the Unified Communications Management 4.0 API and two Office 2010 Filter packs.  To make your life easier you may want to download these ahead of time.


http://www.microsoft.com/en-us/download/details.aspx?id=34992


http://www.microsoft.com/en-us/download/details.aspx?id=17062&fwLinkID=191548


http://www.microsoft.com/en-us/download/details.aspx?id=26604&fwLinkID=262358


 

SMBKitchen: Installing Exchange begins

http://technet.microsoft.com/en-US/exdeploy2013/PrintChecklist?state=2284-W-DQBEAgAAQACACAEAAQAAAA%7e%7e


Next up we start the process of extracting the download and installing Exchange



I always runas admin when I extract the file to ensure that they extract.



Now in hindsight I’d put this file in a subfolder as Exchange spits files all over the place.



When you go to install ensure you either do command line run as administrator, or do a run as administrator



I don’t like checking for updates as it adds to the install and introduces possibilities of change.



it goes to copy the files



It starts the install



While I’m installing this I tend to enable network discovery on the server.  Also make sure you move the Exchange server from the computersOU to the ServersOU in the MyBusiness OU up on the SBS box




And now the install is ready to go…well …sorta



Use the recommended settings



Choose both mailbox and client access role



Don’t install it on the C drive, this is only for testing purposes.  Place this on an appropriate drive location.



I don’t want to disable malware scanning so I’ll enable that


 


 


 

SMBKitchen: Watching paint dry


We’re in the step of ‘watching paint dry’ as the full download comes down.


 


 

SMBKitchen: Deploying Exchange 2013

At this step you want to download the latest version of Exchange 2013 (each CU is a complete build) and use that to download the copy of Exchange to the server.


http://technet.microsoft.com/en-US/Library/jj907309


So whatever the latest one is, is what you want to download.