All posts by jaapwesselius

Installing MS13-061 breaks CI on Exchange Server 2013

Preliminary information and subject to change! Will update when more information becomes available.

When installing MS13-061 on Exchange Server 2013 CU1 or CU2 issues with the Content Indexing (can) occur. Content Indexing for Mailbox Databases are in a failed state and the existing “Microsoft Exchange Search Host Controller” seems to be missing. Instead there’s a new service called “Host Controller Services for Exchange” on the box.

Right now it looks like it doesn’t affect Exchange Server 2007 or Exchange Server 2010.

There’s a workaround to get this fixed:

Open the Registry Editor and navigate to the following path:

“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search Foundation for Exchange”

Go to the DataDirectory string and give it the following value:

C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data

image

Note. If your Exchange binaries are in a different directory use change the path accordingly.

In the registry navigate to the following location:

“HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HostControllerService”

Change the value of “DisplayName” to “Microsoft Exchange Search Host Controller”

Add a new Multi-String Value named “DependOnService” and specify “http” in Value data.

image

The display name will only be changed after a reboot of the server, but the services can be started at this point.

Unable to delete Lync 2010 Front End Pool after migrating to Lync 2013

After a (successful) migration from Lync 2010 to Lync 2013 I wanted to decommission the old Lync 2010 servers. In my previous blog post I already explained why the CMS didn’t want to move, but the next issue was challenging as well.

Before removing the last Lync front-end server you have to remove all Lync 2010 objects from this front-end server. Well known issue for example is the conference directory that for some reason always stays at the front-end server.

Continue reading Unable to delete Lync 2010 Front End Pool after migrating to Lync 2013

ISE, Remote PowerShell and Exchange 2013

Last TechEd in Madrid I got an interesting question about Exchange 2013 supportability in the PowerShell ISE (Integrated Scripting Environment). This gentleman was using the Remote PowerShell functionality in ISE and was wondering if this was a supported solution.

It took some time to get a confirmation, but these are the supported scenarios:

  • Exchange Management Shell (which is running Remote PowerShell) – supported
  • Regular PowerShell connecting to Exchange via Remote PowerShell – supported
  • Powershell ISE connecting to Exchange via Remote PowerShell – supported

Regular PowerShell or PowerShell ISE simply loading Exchange snapins is not supported unless Technet specifically calls out that you must run local PowerShell for a specific cmdlet.

Remote PowerShell can be activated like this:

$Session = New-PSSession –ConfigurationName Microsoft.Exchange –ConnectionUri http://ams-exch01.contoso.com/PowerShell -Authentication Kerberos
Import-PSSession $Session

This can be done in a normal PowerShell window or in the ISE:

image

A Microsoft knowledgebase article was released recently regarding an issue with Remote Powershell, ISE and Exchange Server 2010 SP3:

http://support.microsoft.com/kb/2859999 – Some cmdlets fail in PowerShell ISE after an upgrade to Exchange Server 2010 SP3

Upgrade to Exchange Server 2013 RTM CU2

Now that Microsoft has released Exchange Server 2013 RTM CU2 it’s time to have a closer look at installing this Cumulative Update.

In contrast with the previous Update Rollups as we’ve seen in Exchange 2007 and Exchange 2010, which were only a set of hotfixes bundled together, a Cumulative Update is a full version of the product. So, it is now possible to install an Exchange 2013 server from scratch using the CU2 download.

Another advantage of a CU is that Microsoft can bundle new functionality into the product, even Schema changes are possible (as a matter of fact CU2 does include a number of Schema changes) but also the Configuration container in Active Directory can be changed.

Continue reading Upgrade to Exchange Server 2013 RTM CU2