Lync Hosting Pack v2 Summit

This week I’m attending the Lync Hosting Pack (LHP) V2 summit in Washington DC. The Lync Hosting Pack is Microsoft’s solution for hosters to offer a fully multi-tenant Lync solution. The summit is a joint development between Microsoft and implement.com.

The solution is based on one Active Directory, but every customer has its own Organizational Unit, fully separated from other OU’s, thus preventing information leakage. LHPv2 itself is based on Lync Server 2013. Continue reading Lync Hosting Pack v2 Summit

Exchange 2013 coexistence, EAC and ECP

When you introduce Exchange 2013 into an existing Exchange 2010 environment and you want to open the Exchange Admin Center (using https://localhost/ecp or using https://webmail.contoso.com/ecp) it ‘fails’ and it opens the Exchange 2010 ECP instead.

image

This is caused by the fact that the administrator mailbox is still on Exchange 2010 and the ECP is tied to the administrator mailbox. You can move the mailbox to Exchange 2013 but instead you can also add the suffix /?ExchClientVer=15, like this https://localhost/ecp/?ExchClientVer=15

This will open the Exchange Admin Center in Exchange 2013 while the administrator mailbox is still on Exchange 2010:

image

Enable POP3 and IMAP4 Logging

For testing purposes it can be useful to enable protocol logging on the POP3 and/or IMAP4 service. In Exchange 2010 this cannot be done using the Exchange Management Console or the Exchange Management Shell like you would do to enable protocol logging on the Send or Receive Connector but needs to be done using a config file.

There’s a Microsoft.Exchange.Pop3.exe.config or similarly a Microsoft.Exchange.Imap4.exe.config file located in the directory C:\Program Files\Microsoft\Exchange Server\ClientAccess\PopImap on the Exchange 2007/2010 Client Access Server.

When you open the file scroll down and locate the “ProtocolLog” key and set its value to “true”, like this:

<add key="ProtocolLog" value="true" />

When changed restart the POP3 or IMAP4 service in the Exchange Management Shell using the following command:

Restart-service MSExchangePop3
Restart-Service MSExchangeImap4

The log files can be found in the directory C:\Program Files\Microsoft\Exchange Server\Logging\Pop3

When you’re finished with troubleshooting don’t forget to disable protocol logging since it will consume a tremendous amount of disk space. Just to give you an idea, this is in the POP3 log file for only one session:

image

In Exchange 2013 it’s a bit different, you can use the Set-PopSettings cmdlet (and Set-ImapSettings cmdlet) to enable logging and set the directory where the log files are stored, for example:

Set-PopSettings -ProtocolLogEnabled $true -LogFileLocation "C:\Pop3Logging"

Released: Exchange 2013 RTM CU1

Today, April 2nd 2013 Microsoft released Cumulative Update 1 (CU1) for Exchange Server 2013 RTM. CU1 is an important release since it offers the possibility to integrate with an existing Exchange Server 2007 or Exchange Server 2010 environment (this was not possible using the original Exchange Server 2013 RTM release). The official version of CU1 is build 620-29.

Furthermore there are many, many bugfixes in CU1 (several thousands, but these also include typo’s and language issues) but also some new additional features:

  • Address Book Policy Routing Agent – especially important for hosting environments. For more information regarding this check out Address Book Policies, Jamba Jokes and Secret Agents;
  • Group membership management by groups – a long awaited feature that was also available in Exchange Server 2007 and earlier;
  • Access to Public Folders via favorites;
  • Exchange Admin Center (EAC) enhancements;
  • Improved probes, monitors and responders (part of managed availability);
  • Optimized Get-HealthReport;
  • Exchange 2013 Management Pack for SCOM;
  • Auto-reseed supports bitlocker encrypted disks;

CU1 is the first update as part of Microsoft’s new servicing model. This means that CU1 is approx. 1.3 GB in size, it is not an update on top of Exchange Server 2013 RTM but it’s a full version. When deploying there’s no need to install Exchange Server 2013 RTM first, you can start directly with deploying CU1.

For more information check out the Release Notes on http://blogs.technet.com/b/exchange/archive/2013/04/02/released-exchange-server-2013-rtm-cumulative-update-1.aspx or download CU1 directly from the Microsoft download site: http://www.microsoft.com/en-us/download/details.aspx?id=38176

Please note that a Cumulative Update is not the same as a Service Pack. Microsoft will release a CU on a regular basis, most likely four times a year (once every quarter). For Exchange Server 2013 Microsoft is planning to release Service Pack 1 (SP1), but no information is available at the time of writing.