Exchange

Address Book Policy using Exchange Online (Office 365)

The question were raised a couple of times and I couldn’t find any related articles besides the official TechNet articles, so I decided to write one myself.

Some organizations have the need of separating people from seeing each other in the global address list (GAL), this is known as GAL segmentation and have been on the surface for a long time.

However, when it comes to do a segmentation in Office 365 and Exchange Online, it can be challenging and difficult, so I decided to write this article and provide an example of how this can be done.

 

Scenario – segmentation between school (students & teachers) and others (teachers, admin personnel and managers).

In detail the teachers and the students should be able finding each other in the address lists, while the administrators shouldn’t be able finding the students in their lists. However, administrators and teachers should be able to reach out through the address lists.

 

ABP

 

RBAC

By default the global administrator DON’T have access to manage the address lists, so either add the Address List Management permissions into the Organization Management role group or create a new role group with the role Address List Management and add the appropriate user into the group.

 

Attributes

One way of making sure the segmentation is working they way it is expected is to make it possible grouping the users using the extensionAttribute/CustomAttribute values in AD/Exchange.
These should be configured in the on-premise Active Directory (AD).

In this example all students and teachers has a value of “EDU” in their extensionAttribute15/CustomAttribute15, while the others have a value of “ADM” in their extensionAttribute14/CustomAttribute14 so they can easily be filtered.

With the attribute values in place, we need to configure address lists, global address list, offline address book, address book policy and finally apply it to the mailboxes.

This is done using PowerShell for Exchange Online running the following cmdlets..

 

Configuration for students and teachers


New-AddressList -Name "AL-EDU-Users-DGs" -RecipientFilter {((RecipientTypeDetails -eq 'UserMailbox') -or (RecipientTypeDetails -eq "MailUniversalDistributionGroup") -or (RecipientTypeDetails -eq "DynamicDistributionGroup")) -and (CustomAttribute15 -eq "EDU")}

New-AddressList -Name "AL-EDU-Rooms" -RecipientFilter {((Alias -ne $null) -and ((RecipientDisplayType -eq 'ConferenceRoomMailbox') -or (RecipientDisplayType -eq 'SyncedConferenceRoomMailbox'))) -and (CustomAttribute15 -eq "EDU")}

New-GlobalAddressList -Name "GAL-EDU" -RecipientFilter {(CustomAttribute15 -eq "EDU")}

New-OfflineAddressBook -Name "OAB-EDU" -AddressLists "GAL-EDU"

New-AddressBookPolicy -Name "ABP-EDU" -AddressLists "AL-EDU-Users-DGs","AL-EDU-Rooms" -OfflineAddressBook "\OAB-EDU" -GlobalAddressList "\GAL-EDU" -RoomList "\AL-EDU-Rooms"

Get-Mailbox | Where {$_.CustomAttribute15 -eq "EDU"} | Set-Mailbox -AddressBookPolicy "ABP-EDU"

 

Configuration for administrator personnel, managers and teachers


New-AddressList -Name "AL-ADM-Users-DGs" -RecipientFilter {((RecipientTypeDetails -eq 'UserMailbox') -or (RecipientType -eq "MailUniversalDistributionGroup") -or (RecipientType -eq "DynamicDistributionGroup")) -and (CustomAttribute14 -eq "ADM")}

New-AddressList -Name "AL-ADM-Rooms" -RecipientFilter  {((Alias -ne $null) -and ((RecipientDisplayType -eq 'ConferenceRoomMailbox') -or (RecipientDisplayType -eq 'SyncedConferenceRoomMailbox'))) -and (CustomAttribute14 -eq "ADM")}

New-GlobalAddressList -Name "GAL-ADM" -RecipientFilter {(CustomAttribute14 -eq "ADM")}

New-OfflineAddressBook -Name "OAB-ADM" -AddressLists "GAL-ADM"

New-AddressBookPolicy -Name "ABP-ADM" -AddressLists "AL-ADM-Users-DGs","AL-ADM-Rooms" -OfflineAddressBook "\OAB-ADM" -GlobalAddressList "\GAL-ADM" -RoomList "\AL-ADM-Rooms"

Get-Mailbox | Where {$_.CustomAttribute14 -eq "ADM"}  | Set-Mailbox -AddressBookPolicy "ABP-ADM"

 

Configuration for teachers (“Everyone”)

The configuration for the teachers is a bit different since they should be able to see all users, in my example I do configure the policy to include all address lists, this can be configured so it matches your requirements.


New-AddressBookPolicy -Name "ABP-Teachers" -AddressLists "AL-ADM-Users-DGs","AL-ADM-Rooms","AL-EDU-Users-DGs","AL-EDU-Rooms","All Groups","All Contacts","All Distribution Lists","All Rooms","All Users" -OfflineAddressBook "\Default Offline Address Book" -GlobalAddressList "\Default Global Address List" -RoomList "\All Rooms"

Get-Mailbox | Where {$_.CustomAttribute1 -eq “teachers”} | Set-Mailbox -AddressBookPolicy "ABP-Teachers"

 

Ps. In the example for applying the policy to teachers, I’ve filtered the users using extensionAttribute1/CustomAttribute1 with the value of “teachers”.

 

The final result is shown below..

Students – able to find students and teachers in GAL

2014-09-30 13-51-27

Admins – able to find admins, managers and teachers in GAL

2014-09-30 13-53-06

Managers – able to find admins, managers and teachers in GAL

2014-09-30 13-54-05

Teachers – able to find everyone in GAL

2014-09-30 14-00-11

 

I hope this gave a more clear picture of the configuration to you, feel free to comment or give any feedback!

 

More information:

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

Content Indexing failed using Exchange 2013 RTM

Content Indexing failed using Exchange 2013 RTM

I just found a bug in my lab environment and wanted to share the information with you.
My lab environment is a small environment that consists of one domain controller (Windows 2008 R2) and two Exchange 2013 RTM servers (based on Windows 2012 Server), these holds both the Mailbox and the CAS role.

I found this issue when I was about to do a failover of one of the mailbox databases.
It couldn’t be done (without using any additional parameters) because the content indexing was in failed state.

When I did run: Get-MailboxDatabaseCopyStatus –Server tlex01 it did show me that the index was in failed state.

image

I tried to update it using the Update-MailboxDatabaseCopy –CatalogOnly cmdlet, but after a while it was still in failed state. Some posts on the forums stated to remove the indexing files, which is the standard procedure when having these kind of issues. However, it was done as a step 2 but it didn’t solve the issue for me.

Finally I came over some information that a group should be created called “ContentSubmitters”, I did create this group in the Microsoft Exchange Security Groups OU as a Universal – Security Group.
I also granted “Builtin\Administrators” and “NetworkServiceFull Control to this group.

After this was done I stopped the Microsoft Exchange Search and Microsoft Exchange Search Host Controller service and removed the content indexing files. Then started up the services again, after a while the index was rebuilt and was in a healthy state.

I have tried to find information if this issue is solved by using CU1, but I haven’t found any information yet.

Regards,
Jonas

A summary of year 2012

A summary of year 2012

It has been an amazing year for me in many ways, both private and work related things.
But this post keeps the focus on the work related things..

I’ve been involved in a couple of really interesting projects such as a large coexistence between Domino and Exchange (45-50k users), coexistence between Domino and Office 365. Also migrated lots of mailboxes from Domino to Exchange. Besides the “complex” migration projects, I’ve also been involved in a large Exchange transition and storage design with 25-30k users for a customer.

Together with all these projects I was one of the lucky people that were sent to Orlando in September for attending the MEC 2012, which was really good. Lots of great new contents to me and lots of interesting people.

Regarding the community related things, I’m not active anymore at the TechNet forum because I want to spend that time of sharing articles with you out there instead. The forum is a great place to ask questions or search for issues. This post is written the 27th and the 28th of December, at that time I can look back and see that lots of people have found my blog and hopefully you find it attractive. The blog have had around 90k visitors and 130k pageviews year 2012, compared with 2011 which had 40k visitors and 50k pageviews, which is an amazing growth!

I did write a couple of new fresh posts about Exchange 2013, when it still was in a preview version.
I’m really happy that I did post these and shared them with you, in the end I got an offer from Packt Publishing to write an update on a book that Mike Pfeiffer wrote for Exchange 2010 SP1, called “Microsoft Exchange 2010 PowerShell Cookbook” which is a true honor to me that I’m really proud of. So you might have wondered why I haven’t posted so much this autumn, there’s the answer 🙂

Now, I just want to say thanks to all of you out there that keeps reading my blog and comment on posts! Happy new year everyone! See you out there in 2013 🙂

Complete guide on configuring KEMP VLM load balancer for Exchange 2013

Complete guide on configuring KEMP VLM load balancer for Exchange 2013

Introduction

Published: 2012-11-02
Updated: 2013-04-24
Version: 1.1

Update:
Made some updates regarding the health check for the OWA and Outlook Anywhere service.

Since Exchange Server 2013 reached RTM the 11th of October, and finally it was published to MSDN the 24th of October. This post is based on the RTM version of Exchange 2013.

I decided to write a post that included both the KEMP configuration together with the Exchange 2013 configuration. I’ve also seen that Jaap Wesselius have posted an article regarding this topic already, it’s my hope that I can fill the gap regarding the complete configuration of both Exchange and the load balancer.

For illustrating my lab environment, see the picture below.

On the left side is the “client” which tries to connect, in the middle is the load balancers and to the right are my two Exchange 2013 servers.

Drawing1

I did decide to have one namespace per service for having a better flexibility, however this is NOT required. But the advantage for having it like this is that the load balancer can check the health of each component. If one component is not working, it’s just disabling that service from the corresponding server, and not the whole server.
But an disadvantage is a increased cost for the certificate and the load balancer get’s a bit more complex.

I’m using the Virtual LoadMaster which resides in different versions (in the end of my post I will provide some links regarding versions etc).

Initial configuration

My configuration is a two-leg load balancer, where the first leg is placed into the client network segment and the other leg (NIC) is placed into my server segment.

The initial configuration is done by providing a license key.

image

Go to System Configuration –> Interfaces –> eth0 for configuring the IP address of the first network card.

image

System Configuration –> Local DNS Configuration –> Hostname configuration for giving the VLM a hostname.

image

System Configuration –> Local DNS Configuration –> DNS configuration for configuring the VLM with a domain and DNS server.

image

System Configuration –> Route Management –> Default Gateway for configuring the VLM with a default gateway.

image

Often it’s required to have the VLM understand other networks and can route traffic to them, for configuring additional route go to System Configuration –> Route Management –> Additional Routes.

image

Don’t forget to configure the date and time on the VLM, go to System Configuration –> System Administration –> Date/Time. I’ve configured to use “ntp.lth.se” as my NTP server, it’s recommended to use the NTP option.

image

When the configuration is done, a good tip is to take a backup of it, go to System Configuration –> System Administration –> Backup/Restore.

image

High Availability configuration

Kemp is providing a high availability cluster of two load balancing nodes, where one is active and one is passive (standby). I’ve been playing around with it and it works really good. The passive kicks in right away when the active one is broken or restarted/shutdown.

During a restart of the active node the passive becomes the active node.

In general, they share a cluster IP/name where the configuration is done and on each LB node the local settings can be done such as configuring date/time, IP addresses etc.

Start with the first node, for configuring this go to System Configuration –> Miscellaneous Options –> HA Parameters. Set it to “HA Mode: HA (First) Mode”.

image

Go to System Configuration –> Interfaces –> eth0. Give the load balancer cluster a IP address and also provide the IP address for the second node. Don’t forget to press the “Set Shared address” and “Set Partner address” buttons for saving the configuration. Then go back to System Configuration –> System Administration –> System Reboot. Restart the first node.

When the first node is back online, continue with the second node. Go to System Configuration –> Miscellaneous Options –> HA Parameters. Set it to “HA Mode: HA (Second) Mode”.

image

Example of my first node.

image

Example of my second node.

image

Creating and configuring load balancing services

I will create two examples for load balancing services, one for OWA and one for Outlook Anywhere.
Using these examples, you can easily creating services by yourself for the other ones.

OWA

Go to Virtual Services –> View/Modify Services –> Add New.

image

Type in the IP address for the service in the Virtual Address field, together with port, protocol and name.
Press “Add this Virtual Service”.

image

Make sure that “Force L7” is checked, but the “L7 Transparency” is unchecked.
Since Exchange 2013 doesn’t require persistence anymore, make sure that the option is set to “None”.
For the load method/Scheduling method, I’m using Round-Robin which is pretty much spreading the load on all servers.

image

Update:
Under “Real Servers”, let’s configure the health checks. Make sure it’s set to use HTTPS protocol. This together with Checked Port: “443” and URL: “/owa/healthcheck.htm”. Don’t forget to press the “Set URL” button for saving the settings. Check the option “Use HTTP/1.1” and select GET as the HTTP Method.

image

Let’s press the “Add New…” button under “Real Servers”. Add your Exchange 2013 Client Access servers. When all servers are added, press the Back button. (I’m using multirole servers, so all of them are added)

image

When everything is setup it should look like the figure below.

image

When you’re satisfied with the configuration, press the Back button. The services should then show up as green if the protocols are available.

image

Outlook Anywhere

Go to Virtual Services –> View/Modify Services –> Add New.

image

Type in the IP address for the service in the Virtual Address field, together with port, protocol and name.
Press “Add this Virtual Service”.

image

Make sure that “Force L7” is checked, while the “L7 Transparency” is unchecked.
Since Exchange 2013 doesn’t require persistence anymore, make sure that the option is set to “None”.
For the load method/Scheduling method, I’m using “Round-Robin” which is spreading the load to the servers.

image

Update:
Under “Real Servers”, let’s configure the health checks. Make sure it’s set to use HTTPS protocol. This together with Port: 443 and URL: “/rpc/healthcheck.htm”. Don’t forget to press the “Set URL” button for saving the settings. Also check the option “Use HTTP/1.1” and select GET as the HTTP Method.

image

Let’s press the “Add New…” button under “Real Servers”. Add your Exchange 2013 Client Access servers. When all servers are added, press the Back button.

image

Everything is now setup for load balancing the Outlook Anywhere function.

image

In the services console, it should look like below if the health is successfully verified.

image

Note: In my lab environment I’ve decided to not use L7 transparency since I don’t have any use for it. It is used when the Client Source IP address needs to show up at the CAS Servers. This can sometimes be important when using SMTP filters. So for proper load balancing, the traffic needs to flow through the load balancer, both back and forth. Therefore you need to change the Default Gateway settings of your servers, when you are activating the L7 Transparency.

Final tests

Let’s start with testing the load balancing functions so that Outlook is able to connect and that the connections are spread throughout the servers.

Here’s my final configuration, for clarifying that I’m using five different VIP’s, one for each service.

image

The figure below shows that Outlook 2013 profile is getting connected, I was using the autodiscover feature for configuring the Outlook profile. Both the InternalHostname and the ExternalHostname is configured to: outlook.testlabs.se in my scenario, on both my servers. For authentication I’m using NTLM.

image

Since Outlook 2013 was worked fine, it’s up to OWA to show up.
I reached the form-based authentication page and put in my credentials and finally got to the Inbox.
Did this a couple of times, together with login into the Admin Center for getting some more sessions in the load balancer.
This for checking so that the VLM spreads the load between the servers in a good way.

image

image

Below are two figures that shows how the sessions are spread between the servers.
To me this looks really good!
The first figure shows the servers and how the sessions are spread between them.
The second figure does show the services instead of the servers, this together with the total amount of connections last minute and up to the last hour.

These two figures together shows how the load is spread, since this is just a lab environment I don’t have an large amount of connections. It would be really interesting to see in a large enterprise environment how the load is spread between the servers.

image

image

Helpful links

General documentation
http://www.kemptechnologies.com/documentation

Sizing tool for load balancer (Exchange 2010)
http://www.kemptechnologies.com/emea/loadmaster-sizing-for-ms-exchange-2010.html

Deployment guide
http://www.kemptechnologies.com/fileadmin/content/pdf/KEMP_Exchange_2010_Deployment_Guide_5_1_v1.6.pdf

Compare Load Balancer models
http://www.kemptechnologies.com/emea/products/server-load-balancing-internet-router-load-balancer.html

Exchange Load Balancers
http://www.kemptechnologies.com/emea/loadbalancingresource/ms-exchange-2010.html

Virtual Load Balancers
http://www.kemptechnologies.com/emea/products/virtual-load-balancers/vlm-overview.html

Multi-Site Load Balancers
http://www.kemptechnologies.com/emea/products/multi-site-load-balancers/overview.html

Thanks for reading!
I hope that this was informative and interesting to read, please feel free to provide feedback

Regards,
Jonas Andersson

Exchange Server 2013 Preview – Part 3: How to configure site URL’s, Databases and Outlook Anywhere

Exchange Server 2013 Preview – Part 3: How to configure site URL’s, Databases and Outlook Anywhere

I suppose you already have, but if you haven’t read my previous parts in this Exchange 2013 serie, have a look at the links below.

Part 1: Complete guide of how to perform the installation
Part 2: How to do the Basic configuration

This part will include details on how the configuration could be made for Site URL’s/Virtual Directories, Databases, Outlook Anywhere and MAPI vs RPC over HTTPs together with connecting using Outlook 2013.

In the previous part we did install the certificate which included the following names, so we can use these names in the site configuration. (If using HTTPS, the configured name needs to be included into the certificate.)

  • mail.testlabs.se
  • autodiscover.testlabs.se
  • tlcas01
  • tlcas01.testlabs.se
Sites / URL’s

Let’s go through the steps for configuring the sites with the ExternalURL and other settings.
I’ll go through both the EAC and the PowerShell, so you have the opportunity to select which method you prefer.

Let’s start..

In EAC: Go to Servers, select Virtual Directories.

image

Select the server in the menu and which type you want to show. Then press Edit.

image

Let’s start with Autodiscover.

image

By default, Integrated Windows Authentication and Basic authentication is enabled. Press Save.

image

Next, select Exchange ActiveSync (EAS). Press Edit.

image

General settings shows the URL’s, I did type in the ExternalURL like the pic below. Press Authentication.

image

Make sure that Basic authentication is enabled. Press Save.

image

Next, select ECP. Press Edit.

image

General settings shows the URL’s, I did type in the ExternalURL like the pic below. Press Authentication.

image

Authentication default settings is “Use forms-based authentication” enabled. Press Save.

image

A warning, make sure to change all virtual directions. Press OK.

image

Next, select EWS. Press Edit.

image

General settings shows the URL’s, I did type in the ExternalURL like the pic below. Press Authentication.

image

Authentication settings, Integrated Windows authentication is enabled by default. Press Save.

image

Next, select OAB. Press Edit.

image

I did type in the ExternalURL in this setting, the InternalURL was already configured. I did also change the Polling interval from 480 minutes to 60. For having a faster update of the OAB. Press Save.

image

Next, select OWA. Press Edit.

image

General settings shows the URL’s, I did type in the ExternalURL like the pic below. Press Authentication.

image

Forms-based authentication is selected, I did select the Logon format: User name only and did select my domain by the browsing button. Press Features.

image

Showing the default settings. Press File Access.

image

Showing the default settings. Press Save.

image

Next, select PowerShell. Press Edit.

image

General settings shows the URL’s, I did type in the ExternalURL like the pic below. Press Authentication.

image

Both Integrated Windows authentication and Basic authentication was selected by default. Press Save.

image

Using PowerShell

Start the Exchange Management Shell (EMS) and the following commands will do the same work that’s done in EAC.

Autodiscover:
Get-ClientAccessServer | fl *uri*
Set-ClientAccessServer –Identity TLCAS01 –AutoDiscoverServiceInternalUri https://autodiscover.testlabs.se/Autodiscover/autodiscover.xml

image

Exchange ActiveSync (EAS):
Get-ActiveSyncVirtualDirectory | fl *url*, ide*
Set-ActiveSyncVirtualDirectory –Identity “TLCAS01\Microsoft-Server-ActiveSync (Default Web Site)” –ExternalUrl https://mail.testlabs.se/Microsoft-Server-ActiveSync
image

Exchange Control Panel (ECP):
Get-EcpVirtualDirectory | fl *url*, ide*
Set-EcpVirtualDirectory –Identity “TLCAS01\ecp (Default Web Site)” –ExternalUrl https://mail.testlabs.se/ecp

image

Exchange Web Services (EWS):
Get-WebServicesVirtualDirectory | fl *url*, ide*
Set-WebServicesVirtualDirectory –Identity “TLCAS01\EWS (Default Web Site)” –ExternalUrl https://mail.testlabs.se/EWS/Exchange.asmx

image

Offline Address Book (OAB):
Get-OabVirtualDirectory | fl *url*, ide*,pol*
Set-OabVirtualDirectory –Identity “TLCAS01\OAB (Default Web Site)” –ExternalUrl https://mail.testlabs.se/OAB –PollInterval 60

image

Outlook Web App (OWA):
Get-OwaVirtualDirectory | fl *url*, ide*
Set-OwaVirtualDirectory –Identity “TLCAS01\OWA (Default Web Site)” –ExternalUrl https://mail.testlabs.se/OWA

image

PowerShell:
Get-PowerShellVirtualDirectory | fl *url*, ide*
Set-PowerShellVirtualDirectory –Identity “TLCAS01\PowerShell (Default Web Site)” –ExternalUrl https://mail.testlabs.se/powershell

image

Databases

Let’s go through the steps that’s required for renaming the default database, dismount and mount. Also creating new databases. Let’s start with the EAC and then do it in PowerShell.

Let’s start..

In EAC: Go to Servers, select Databases.

Select the default database, named “Mailbox Database 0883045..”. Press Edit.

image

General settings is shown. Press Cancel.

image

Select the database, Dismount it by pressing the … icon and press Dismount database.

image

It does show a warning, that mailboxes being on this database now will be unavailable. Press Yes.

image

Select the database. Press Edit.

image

Give the database a friendly name, example: DB01. Press Maintenance.

image

Maintenance settings is shown. Press Limits.

image

Mailbox limits are shown, these are the default values. Press Client Settings.

image

By default, no Offline address book was selected. Press Browse and make sure to select the address book. Press Save.

image

What about if you want to create a new database?

Let’s start in EAC

Press the Add button (+).

image

Give the database a friendly name, example: DB02. Browse for a mailbox server. And also put in the database path and log path. Press Save.

image

During the creating of the database, there is not option for associate the database with the offline address book. When the database is created, press Edit. Then go to Client Settings and select the Offline address book.

image

Using PowerShell

Start the Exchange Management Shell (EMS) and the following commands will do the same work that’s done in EAC.

Retrieve database information
Get-MailboxDatabase
Get-MailboxDatabase | fl name,*path*

Dismount Database
Dismount-Database –Identity DB01

After the default database is renamed to DB01, I want to move the database file and the logs to another drive. It’s done by the commands below:

Move-DatbasePath –identity DB01 –EdbFilePath “E:\Database\DB01\DB01.edb” –LogFolderPath “F:\Logs\DB01”

Mount-Database DB01

image

Get-OfflineAddressBook

For creating a new database (DB02), we have the opportunity in PowerShell to specify all parameters that’s needed for having all options configured.

New-MailboxDatabase -Name DB02 -EdbFilePath “E:\Database\DB02\DB02.edb” -LogFolderPath “F:\Logs
\DB02” -OfflineAddressBook “\Default Offline Address Book” -Server TLMB01

Mount-Database DB02

image

Note that the OfflineAddressBook is specified during the creation of the database.

Outlook Anywhere

Configuration of the feature Outlook Anywhere can also be done from both the EAC and EMS, in various ways.

Let’s start with the EAC:

Go to the servers menu, and select Servers. Press Edit.

image

Then go to the “Outlook Anywhere” option, type in the external name, example: mail.testlabs.se.
I’m using Basic authentication for Outlook Anywhere. Press Save.

image

And the Configuration is completed.

Using PowerShell

Start the Exchange Management Shell (EMS) and the following commands will do the same work that’s done in EAC.

Enable Outlook Anywhere:
Enable-OutlookAnywhere –Server TLCAS01 –ExternalHostname mail.testlabs.se –InternalHostname tlcas01.testlabs.se –ExternalClientAuthenticationMethod Basic –InternalClientAuthenticationMethod Ntlm –IISAuthentication Ntlm –SSLOffloading:$false

Get-OutlookAnywhere –Server TLCAS01

image

MAPI and RPC

The MAPI/RPC (RPC over TCP) traffic is now gone and  replaced with RPC over HTTP/s instead. With that said no more load balancing of static RPC ports, as far as I know this will make both the Firewall team and the Load Balancer teams work easier, less ports is used together with the requirement of load balancing affinity/sticky session settings is not required anymore. This because of there is no need anymore to have the affinity settings, it can now be load balanced based on IP addresses. Just make sure that the load balancer verifies the Exchange services before sending traffic to it.

Outlook instead will use port 443 (HTTPS) or port 80 (HTTP). I think (and hope) most of you will use RPC over HTTPS, with this said I’ll show you the new Outlook 2013 Preview/beta and how it connects and also the traffic it’s using.

Outlook 2013 Preview, connects to my mailbox in Exchange 2013. It’s using HTTPS to initiate the connection, using port 6001 by default for it’s connection, using RPC over HTTPS.

image

A small picture from Network Monitor when the connection initiated by Outlook 2013.

image

More information around What’s new in Exchange 2013 can be found here.

Next parts will cover Public Folders, Client Access Server Array, Database Availability Groups and more.
Next part can be found here.

Thanks for reading, I hope it helped you guys/girls out there.
If you want me to cover anything special around Exchange 2013, leave a comment.

Exchange Server 2013 Preview – Part 2: How to do the Basic configuration

Exchange Server 2013 Preview – Part 2: How to do the Basic configuration

If you haven’t read it already, I did post a complete guide for installing Exchange 2013, it can be found here. That was part 1, now it’s time for part 2. Which of course is the configuration of the server setup.

We have lots of changes between how you configured Exchange 2007/2010 and 2013.
First thing is that Exchange Management Console is gone and replaced by a refreshed ECP called Exchange Admin Center (EAC), built on Silverlight (I suppose). The “old” Exchange Management Shell (EMS) is still there, so I suppose lots of us geeks will use more PowerShell in the near future.

The fact that EMC is replaced will make the administration easier and more portable, but I still like the EMC better. I will like the EAC better after used it for a while. This portable administration together with Remote PowerShell will be awesome.

I will use both methods for the configuration steps, both EAC and PowerShell.

The easiest way to find the URL path to the EAC is to start the Exchange Management Shell and run the command below:

Get-EcpVirtualDirectory | fl *url*

The picture below is my output from my lab environment

image

So let’s get things started..

Start up an Internet browser and go to the URL output from the command above

image

Mail Flow

Let’s get the mail flow configured first so we can receive mails from external senders.

In EAC: on the left side (menu) press “Mail Flow”.

image

Accepted Domains

Ensure sure that your domains that should be used for SMTP is listed in here for making Exchange able to receive mails for these domains. More info about Accepted Domains can be found here.

In EAC: After selecting “Mail Flow” to the left, press “Accepted Domains” at the top menu in the middle.

image

If your domain is not listed and you need to add it, press the plus mark and fill in the information, like my example below.

image

image

Using PowerShell: Since I’m a geek I like to use PowerShell because it gives you the advantage of see what happens, have the full control and easily build scripts.

For listing and adding a domain like above in PowerShell you should write:

Get-AcceptedDomain
New-AcceptedDomain –Name testlabs.com –DomainName testlabs.com –DomainType Authoritative

image

Email Address Policies

These policies are used to stamp each user mailbox object with an email address/SMTP address.
These policies does not remove any addresses used previously, it just adds new addresses to mail objects.

In EAC: By default after the installation we only have one policy, called Default Policy.

I want to edit this one, by selecting the “Default Policy” and pressing the “pen” icon.

image

The Default Policy is showing up, in the left menu, press “Email Address Format”.

image

Since I live in Sweden and we have some special characters that I want to get rid of, I’m using the custom policy, Address type: SMTP and the Email address parameters:

%råa%räa%röo%g.%råa%räa%röo%s@testlabs.se

%r means it replaces the character after, in this case åäö. Which it replaces with aao.

When you have done the change press the “Save” button at the bottom of the page.

image

Check so that the change is correct, then press the “Save” button.

image

After the changes have been saved, it needs to be applied. This is done by pressing the “Apply” text/button down in the right menu.

image

image

Using PowerShell: Let’s start with listing the Policy and the settings in it. As a final step let’s do the same configuration to the “Default Policy” that we did using EAC.

If you want to create more than just alias@domain.com to your policies, then this is done by comma separation. For setting the Primary SMTP address, use capital letters for SMTP, and for additional addresses use small letters for smtp. See the example below:

Get-EmailAddressPolicy

Get-EmailAddressPolicy | fl

Get-EmailAddressPolicy | Set-EmailAddressPolicy –EnabledEmailAddressTemplates “SMTP: %råa%räa%röo%g.%råa%räa%röo%s@testlabs.se”,”smtp: %m@testlabs.se”

Set-EmailAddressPolicy –identity “Default Policy” –EnabledEmailAddressTemplates “SMTP: %råa%räa%röo%g.%råa%räa%röo%s@testlabs.se”,”smtp: %m@testlabs.se”

Get-EmailAddressPolicy | Update-EmailAddressPolicy

It can easily be checked if the policy has been applied, it will show a True or False value. For checking the value run the command below:

Get-EmailAddressPolicy | fl *appl*

Note: Don’t forget to update the Policy, or else the new addresses won’t be pushed out to the recipients.

image

Receive Connectors

Since the HUB Transport server role now is gone and the HUB role is placed together with the CAS role, this is the server you should be looking at.

After the SMTP domains have been added into the Accepted Domain tab, some settings could be of value to have a look at before starting to use the servers.

A change has been made to the new version, the default connector now named “Default Frontend servername”. It now allows traffic from Anonymous users by default. I suppose this is due to that the Edge Transport Role also is removed.

In EAC: Go to the “Receive Connectors”, found under “Mail Flow”. Make sure to select your CAS server(s) and the “Default Frontend servername”. Then press the “pen” icon for Edit the selected connector.

image

The only thing I did change was the “Maximum receive message size” to 30 MB.
When you have done your changes for the connector, press the Save button.

image

Using PowerShell: Start the Exchange Management Shell, lets view the receive connectors and then make the changes like above.

Get-ReceiveConnector

Get-ReceiveConnector | fl

Set-ReceiveConnector –Identity “TLCAS01\Default Frontend TLCAS01” –MaxMessageSize 30MB

Note: The size can be configured between 64KB up to 2GB.

Verify that the settings was correctly set, using the command below
Get-ReceiveConnector | fl ide*,maxmes*

image


Send Connectors

When the HUB server role now is gone and after the default installation of Exchange we don’t have any send connectors. So… for being able to send out mails to external recipients, let’s create a Send Connector on the CAS server.

In EAC: Go to the “Send Connectors”, found under “Mail Flow”. Press the “plus” icon for Creating a new send connector.

image

Give the send connector a friendly name and select what type it should be. Since this one I’m creating now is for sending to external recipients I’m selecting “Internet”. (Seems like we have a typo, see picture below). Press Next.

image

Select how to route those mails, either by using MX records or through a smart host(s). If you have a mail gateway then you should select smart host and type in it’s IP address. My server is just sending them directly to Internet so I’m using the MX method. Then press Next.

image

Press the “plus” icon for adding the address space this connector should use. In my case it will be “*”. Then it takes care of all domains. Press Save.

image

Then Press Next for accepting the settings you’ve just made.

Next screen will show you which source servers that should be used. Let’s add these into the connector by pressing the “plus” icon and selecting the Mailbox servers.

image

Press Finish button so the connector get’s created.

Note: By default the connector has a maximum message size of 10MB. You can’t configure the maximum send message size when creating the connector, but this can be done by editing the created connector.

Using PowerShell: Start the Exchange Management Shell, lets view the send connectors and then make the changes like above.

Get-SendConnector

Get-SendConnector| fl

This creates a new send connector using the DNS/MX method
New-SendConnector –Name “Outbound” –AddressSpaces ‘*’ –SourceTransportServers TLMB01 –MaxMessageSize 30MB

This creates a new send connector using the smarthost method

New-SendConnector –Name “Outbound” –AddressSpaces ‘*’ –SourceTransportServers TLMB01 –MaxMessageSize 30MB –DNSRoutingEnabled:$false –SmartHosts “10.10.10.10”

This creates a new send connector using the smarthost method together with using the CAS server as a proxy server for sending the mails

New-SendConnector –Name “Outbound” –AddressSpaces ‘*’ –SourceTransportServers TLMB01 –MaxMessageSize 30MB –DNSRoutingEnabled:$false –SmartHosts “10.10.10.10” –FrontEndProxyEnabled:$True

Note: The size can be configured between 0 Bytes up to 2TB.

Verify that the settings was correctly set, using the command below
Get-SendConnector| fl ide*,maxmes*

image

Certificates

As most of you already know we need to request and import a certificate for Exchange. This for having a fully working OWA, ActiveSync etc. certificates needs to be configured so let’s get started.

In EAC: Go to the “Certificates”, found under “Servers”. Select the server and press the “plus” icon for Creating a new certificate request.

image

I’m using an Internal PKI solution, so in this case I want to “Create a request for a certificate from a certificate authority”. Press Next.

image

Type in a friendly name for the certificate. Press Next.

image

If you want to create the request for a wildcard certificate, this is the checkbox you should use.
I don’t want a wildcard certificate, so I just let it be unchecked. Press Next.

image

Press Browse and select which server you want to store it on. Press Next.

image

For each service you can here type in the address, and the request will generate the names in the end. When you’re done press Next.

image

Go through the names in the list and make sure that all names that’s needed are included. Press Next.

image

Fill in Organization name, Department, Country, City and State. Press Next.

image

In my example I did type in the path to a share on my domain controller, which also is my Internal CA. Press Finish.
Example: \\tldc01\certificates\certreq.req

image

When the request is completed, it shows up with the friendly name, together with the status “Pending request”. When the certificate is issued, press the “Complete” button below the status.

image

Type in the URL path to the .cer file, my file is saved on my DC. Press OK.
Example: \\tldc01\certificates\certnew.cer

image

It’s now time for assigning the services to the certificates. This is done by selecting the certificate and press the Edit button.

image

Go to “Services” and add the one’s that should be used. Press Save.

image

Press OK.

image

Check so that the services is assigned to the certificate.

image

Using PowerShell: Start the Exchange Management Shell, lets view the existing certificates and then make a new cert request like above. Finally import the issued certificate.

Get-ExchangeCertificate

Get-ExchangeCertificate | fl

This creates a new certificate request and saves it to a share
New-ExchangeCertificate –Server TLCAS01 –GenerateRequest –FriendlyName Exchange2013-PS –PrivateKeyExportable $true –SubjectName “c=SE, s=Skane, l=Malmo, o=Testlabs, ou=Testlabs, cn=mail.testlabs.se” –DomainName  mail.testlabs.se,autodiscover.testlabs.se –RequestFile “\\tldc01\certificates\test.req”

image

Import-ExchangeCertificate –Server TLCAS01 –FileName “\\tldc01\certificates\certnew-ps.cer” –PrivateKeyExportable $true –FriendlyName Exchange2013-PS

Enable-ExchangeCertificate –Thumbprint A2E6649A22A99BEAB2654BEB403C92BB9D34B404 –Services “IIS, SMTP, POP, IMAP” –Server TLCAS01

Get-ExchangeCertificate

image

Note: Make sure to specify –Server, or else you can have difficulties finding our created request. Mine landed at my Mailbox server even if I did it on the CAS server.

If you haven’t read it already, have a look at Part 1: Complete guide of how to perform the installation

Thanks for reading, I hope that it’s informative and great reading for most of you. It would be awesome if you guys leave some comments, what do you think about Exchange 2013? Maybe you have already installed the Preview/Beta? Which new feature is the best one?

Next part will cover Databases, Outlook Anywhere, Outlook 2013 and MAPI/RPC etc.

Part 3 can be found here

Exchange Server 2013 Preview – Part 1: Complete guide of how to perform the installation

Exchange Server 2013 Preview – Part 1: Complete guide of how to perform the installation

Since Exchange Server 2013 beta was released yesterday I’m glad to announce that my first installation is done and here’s a complete walkthrough.

My setup is basic, using one server as domain controller, Windows 2008 R2.
Initially for Exchange I’m using 3 servers, 1 server for the CAS role and 2 servers for the Mailbox role.

There are some prerequisites that need to be installed/removed before the installation of Exchange can take place.

Note: It’s now recommended to install the Mailbox server first. So I’m starting with that server.

Step 1. Install the administration pack using the commands below, make sure to restart the server before proceeding to step 2.

Import-Module ServerManager
Add-WindowsFeature RSAT-ADDS

image

Step 2. Install the Windows features that Exchange uses, for Mailbox and CAS server use the command below:

Import-Module ServerManager
Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, 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-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI

image

Step 3. When the feature is completed. Continue with the installation of the required components, use the links below to download the components.

.NET Framework 4.5 RC

Windows Management Framework 4.0

Unified Communications Managed API 4.0, Core Runtime 64-bit

Office 2010 Filterpack x64

Office 2010 Filterpack SP1 x64

KB 974405 (Windows Identity Foundation)

KB 2619234 (RPC over HTTP)

KB 2533623 (Remote code execution)

Note: Make sure to uninstall the Visual C++ 11 Beta Redistributable (x64) before starting the Exchange 2013 installation.

You can have a look at the setup.exe parameters using

setup.exe /?
setup.exe /help:install

image

Step 4. Start the installation using unattended installation for the Mailbox server role

setup.exe /mode:install /roles:Mailbox, ManagementTools /IAcceptExchangeServerLicenseTerms /InstallWindowsComponents /OrganizationName:Testlabs /TargetDir:"D:\Program Files\Microsoft\Exchange Server\V15"

The installation process starts up and prepare the organization for Exchange 2013, install the necessary Windows components. The schema prep can also be done manually using setup.exe /preparead, I’ve chosen to go with the default behavior.

When for the Mailbox server role installation is successfully finished it will tell you to restart the server.

image

Step 5. Start the installation of the Windows features for the CAS server role

Import-Module ServerManager
Add-WindowsFeature RSAT-ADDS
Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, 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-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI

Make sure to restart the server after the Windows features got installed.

Step 6. Start the installation of the CAS server role

setup.exe /mode:install /roles:ClientAccess, ManagementTools /IAcceptExchangeServerLicenseTerms /InstallWindowsComponents /OrganizationName:Testlabs /TargetDir:"D:\Program Files\Microsoft\Exchange Server\V15"

Since this is the second server, the schema prep is already done so the installation will skip that step.

When it’s finished it will look like the picture below, a restart of the server is required.

image

The installation of both servers are now completed.

Next blog post will be around how to configure Exchange 2013.

Thanks for reading, looking forward to your comments about the post and also about Exchange 2013 in general.

More information about the prerequisites can be found here.

What’s new in Exchange 2013

Next blog post, Part 2: How to do the Basic configuration

#Office15 Wave Whats new

#Office15 Wave Whats new

outlook-2013-icon

I did listen to Microsoft’s announcement for Wave 15
Here are some short directly from the webcast

Office 2013 will integrate directly with Skydrive and Skype, it looks really interesting at Windows 8 and all those really nice integrations if you ask me.

Lync Server 2013 is available for preview download here

Exchange Server 2013 is available for preview download here
Exchange Server 2013 What’s new online help

Exchange 2013 will not support a coexistence between Exchange 2003 and 2013, so all customers that has Exchange 2003 really needs to upgrade.
It does seem like we have really done a totally rebuild of the Exchange architecture.

Keep updated and follow the news on twitter at #MSExchange #ucoms #Lync #Office365
Some blog posts that also have posted new about the upcoming versions:

Exchange:
http://www.pro-exchange.be/blogs/exchange2013/archive/2012/07/16/a-first-look-at-what-s-new-in-exchange-server-2013-and-what-s-still-the-same.aspx
http://paulrobichaux.wordpress.com/2012/07/16/exchange-2013-preview-ships/

Lync:
http://ucken.blogspot.ca/2012/07/whats-new-in-lync-2013.html

 

Be aware, the information above is for the beta products and there might be changes before it’s RTM.

Leave comments of what you think about it

Exchange 2010 Restore to Recovery Database using EMC Networker

Exchange 2010 Restore to Recovery Database using EMC Networker

Published: 2012-07-05
Updated: –
Version: 1.0

Here’s a complete step-by-step guide for doing restore using EMC Networker for Exchange 2010.
Personally I’ve used these steps when doing restore of end user mailbox and/or items that has been lost.

Start up “Networker User for Microsoft Applications”, right click Recover and select “Exchange 2010 Recover Session” and select “Database Recover”.

Make sure that the Client selection is pointed to the DAG or specific server.

After a while it will show Microsoft Exchange 2010 and the databases below, right click the database you want to restore and select “Versions”.

image

Select the date you want to restore from and put a checkbox in “Use selected item backup time as new browse time”. Press OK.

image

Check so that the database and logs are selected and press “Advance Recover..”

image

Control so that the source database is correct and that “Recovery Database (RDB) Recovery” is selected. Press Next.

image

Press the Create button.

image

Make sure that you have sufficient amount of free disk space before starting the restore.
Save the edb/database file in a folder and give it a friendly name. Press Save.

image

Give the RDB a friendly name and press Create.

image

RDB is created successfully.

image

When the RDB is created, mount it by pressing Mount button.

image

Mounted successfully.

image

Press the “RDB Overwrite” button for making sure that Networker is allowed to overwrite the RDB.

image

Press Next.

image

Check the summary and press “Start Recover”.

image

You can monitor the restore process by going to “Monitor” on the left side. It will show information about the restore.

image

When the restore is completed, it will notify with a window like this.

image

The last step before everything is restored is to merge/copy the data from the RDB into a mailbox.
I’m using the command “Restore-Mailbox”

The command below is an example from my restore, it restores the mailbox called “LostMailbox” into my mailbox called “Jonas” and puts the contents into a folder called “Recovery”:

Restore-Mailbox –Identity Jonas –RecoveryDatabase RDB –RecoveryMailbox LostMailbox –TargetFolder Recovery

Then it’s pretty easy to use Outlook and move the contents to the correct mailbox, or else put the contents directly into the right mailbox. It’s up to you!

Source: http://technet.microsoft.com/en-us/library/bb125218.aspx

C#.NET – Configure Exchange 2010 Tool

C#.NET – Configure Exchange 2010 Tool

======

Updated the code again, this time a minor bug in code.
Version is now 0.93.

======

Thanks to John A Cook @JohnACook, who found the issue. It’s now resolved, the tool is now updated and working in my lab environment.
It was a compilation issue, found out that it was compiled as a x86 tool. Sorry for that folks! Thanks a lot for helping me out

======

Download

ChangeLog:
0.93 – Updated minor bug in code
0.92 – Fixed the compile issue.
0.91 – The tool has now been updated to version 0.91, this update fixed if URL’s was not configured/null.

Description:

A while ago I was having this idea of creating a tool that configure the most common things on the Exchange server(s).

It took about 3-4 weeks to complete the application with all coding, which includes around 3000 lines in total.

The tool should be used locally on the server, since it’s using the Exchange PowerShell snapin when doing the query’s and configuring parts.

Besides the smaller parts that uses PowerShell the application is built on C#.NET.

Before going into detail, at the moment it’s version 0.9 since I’m about to optimize the code a bit more. I will update the blog post when it’s done.
Until then, use it as much you want and feel free to give any feedback (it’s great to get feedback).

The debugging of the application has been done on Exchange 2010 SP2, that’s the version it’s built for. But most likely it will work on RTM newer.

Description:

The tool will give you the opportunity to configure the following Exchange features:

Autodiscover, Outlook Web App, Active Sync, Web Services, Control Panel, Offline Address Book, POP/IMAP and Outlook Anywhere.

Check the screenshots below:

imageimageimage

All functions are built upon a query is done first and then it’s possible the change the current settings using the “Set” button.

The first tab is for configuring the Autodiscover SCP settings (Get-ClientAccessServer).
Press the Query button for requesting the current setting, and then you’re able to change it by editing the text and press “Set” button.

The second tab it for set the Internal and ExternalUrl for Outlook Web App, and also for the Logon format.

Third tab is used for Exchange ActiveSync, it’s possible to set the Internal and ExternalUrl and also set the Basic Authentication setting.

Fourth tab is for Exchange Web Services, Internal and ExternalUrl is about to be configured.

Fifth, Exchange Control Panel settings; Internal and ExternalUrl.

Sixth, Offline Address Book settings; Internal and ExternalUrl.

Seventh, POP and IMAP settings, it’s possible to change the Logintype, X509 name and set the Service to Automatic and Start it.

Eighth and final tab, Outlook Anywhere configuration, External hostname and what authentication setting is possible to change here.

About tab, it speaks for it self. Information about the small application

Note: The first query take some time, since it’s loading the snapin. Have some patience, but after the first one it should be pretty fast.

Download the application from here

Like I initially said I will do some code optimization, and will be updating this blog post when it’s done.
Feel free to leave comments, it’s always a pleasure to read them!

Ps. Use the application/code/scripts at your own risk. Test in lab environment first.

Thanks for reading

Load More