Export Mailbox to PST

To export a mailbox to PST is relatively a simple process but there are a few steps to do before you jump into this. Here are the steps:

  1. Grant the User access to the Role as by default there are not users assigned to the Import/Export Management role.
  2. Create a Network Share and Grant the Exchange Trusted Subsystem Read/Writes.
  3. Exporting the Mailbox
  4. Monitoring the Export

Granting Access to the Role:

  • New-ManagementRoleAssignment –Role “Mailbox Import Export” –User User

Granting Access to the Share:

granting access

Exporting the Mailbox:

  • New-MailboxExportRequest -Mailbox User -FilePath \\fileserver\pst\User.pst

Monitoring the Mailbox Export:

  • Get-MailboxExportRequest | Get-MailboxExportRequestStatistics

If you want to Export a Users Mailbox Archive you need to include the “-IsArchive” option at the end of the command:

  • New-MailboxExportRequest -Mailbox User -FilePath \\fileserver\pst\User.pst -IsArchive

Hope it helps.

Lync 2013 frontend – Event ID 32042

You might see the following 2 Event ID’s on your server if your have certificates in the wrong store:

  • Event ID 32042 LS User Services
    Invalid incoming HTTPS certificate
    cause: This can happen if the HTTPS certificate has expired or is untrusted



Open up Lync Management Shell and run the following command:

  • Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} | Format-List * | Out-File “c:\computer_filtered.txt”

If the text file lists certificates then you know which ones to remove/move. After you have cleaned up, reboot your server and all should be fine.

One thing to also take note of, your Lync client will show other users status as “Updating”. Once the server is rebooted it changes to there current status.

Hope it helps.

Full Lync 2013 Installation Guide – Coming Soon

Full Lync 2013 Installation Guide

I will be creating a step-by-step document on how to setup your Azure environment but also setup Lync 2013.

This test environment is built on Microsoft Azure, below are the outlined sections that will be covered in detail with screen shots.


Software required:

  • Windows Server 2012 R2
  • Lync Server 2013
  • Office Web Application Server
  • Office 2013

Server Names & I.P’s used in this test environment:


Server Name I.P Role
Aetodc02 Primary Domain Controller
Aetodc03 Secondary Domain Controller
Aeteclyncapp1 Primary Lync Frontend 1
Aeteclyncapp2 Primary Lync Frontend 2
Aeteclyncapp3 Primary Lync Frontend 3
Aeteclyncapp4 Persistent Chat Server
Aeteclyncapp5 Web Access Server
Aeteclyncedge1 Lync Edge Server
Aetecsql1 Primary SQL Server
Aetecsql2 Secondary SQL Server
Aetecsql3 SQL Witness Server


Section A: Azure Setup

Section A1

  • Azure Virtual Network Setup
    • P Address Setup
    • DNS Server

Section A2

  • Azure Storage Setup

Section A3

  • Server setup and Installation:
  • Windows Server 2012 R2 (Primary Domain Controller)
  • Windows Server 2012 R2 (Secondary Domain Controller)
  • Windows Server 2012 R2 (Primary Lync Frontend 1)
  • Windows Server 2012 R2 (Primary Lync Frontend 2)
  • Windows Server 2012 R2 (Primary Lync Frontend 3)
  • Windows Server 2012 R2 (Persistent Chat Server)
  • Windows Server 2012 R2 (Web Access)
  • Windows Server 2012 R2 (Lync Edge)
    • Edge Server setup with Multiple NICS – Azure PowerShell
  • Windows Server 2012 R2 (Primary SQL Server)
  • Windows Server 2012 R2 (Secondary SQL Server)
  • Windows Server 2012 R2 (SQL Witness Server)


Section B: Configuration of Domain Controllers

Section B1

  • Domain Controller Setup
  • Install AD Services on both Domain Controllers
  • Promote Primary Domain Controller
  • Promote Secondary Domain Controller

Section B2

  • Internal DNS Setup
  • External DNS Setup

Section B3

  • Certificate Authority Setup

Section B4

  • User Account Setup

Section C – Configuration of SQL Servers

Section C1

  • Joining SQL Servers to domain

Section C2

  • Installing SQL Server 2012 Enterprise


Section D – Configuration of Lync Servers (Excluding Edge in this section)

Section D1

  • Joining Lync Servers to domain

Section D2

  • Installing Lync Server Frontend Prerequisites

Section D3

  • Installing Lync Server 2013
  • Install Core Components
  • Install Administrative Tools
  • Create Topology (Topology Builder)
  • Prepare Active Directory
  • Publish Topology
  • Install Lync Server System
  • Adding additional Frontend Lync Servers to the Lync Pool

Section D4

  • Web Access Server Installation
  • PowerShell Execution Policy Setup
  • Installing Lync WAC Server Prerequisites
  • WAC Software Installation
  • WAC Server Language Pack Installation
  • Topology Builder – Add in Office Web Apps Server

Section D5

  • Archiving and Monitoring Setup
  • Topology Builder Loading
  • Archiving SQL Server Setup
  • Monitoring Server Setup
  • Publish Topology
  • Monitoring Report Installation

Section D6

  • Persistent Chat Setup
  • Server Prerequisites Setup
  • Topology Builder Loading
  • Create new Persistent Chat Pool
  • SQL Server Store Setup
  • Install Lync Server System
  • Persistent Chat Configuration – Lync Control Panel


Section E – Configuration of Lync Edge Server

Section E1

  • Edge Server Installation
  • Add DNS Suffix (reboot required)
  • Install Server Prerequisites
  • DNS Setup
  • Topology Builder – New Edge Pool
  • Publish Topology
  • Export-CsConfiguration File
  • Permission Setup Lync Control Panel
  • Install Lync Server System


Error accessing mailbox that was re-connected

If you disable a user’s mailbox in Exchange 2010 it moves to the Disconnected Mailbox Container under Recipient Configuration in Exchange. Now when you re-connect the mailbox to the AD user and you try send an email to the account you get the following error:

#554-5.2.1 mailbox disabled 554 5.2.1 STOREDRV.Deliver.Exception:AccountDisabledException.MapiExceptionMailboxDisabled; Failed to process message due to a permanent exception with message Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group.


Run the following command from Exchange powershell:

  • Clean-MailboxDatabase “databasename”

After this you should be able to send mails to the user and login to the mailbox.

Hope it helps.

The Web Conferencing Server failed to send health notifications to the MCU factory at

After patching my Lync 2013 servers to November Updates I started getting flooded with the following errors:

  • LS MCU Infrastructure 61035

You can follow this KB to sort this out:

  • http://support.microsoft.com/kb/2901554/en-us
  • Click Start, type regedit in the Start search box, and then click regedit.exe in the results list.
  • Locate the following registry subkey: HKLM\System\CurrentControlSet\Control\SecurityProviders\Schannel
  • Right-click Schannel, and then click New DWORD (32-bit) value.
    Type EnableSessionTicket, then press Enter.
  • Right-click EnableSessionTicket, and then click Modify.
  • Change the existing value to 2, and then press Enter.
    Exit Registry editor.
  • Open the Lync Server Management Shell.
  • Run the following Lync Server PowerShell commands in the given order:

After that the errors should be gone.

Hope it helps.

Lync Server 2013 Error – Lost Connection to all Web Conferencing Edge Services

Recently I started seeing the following event IDs 41026 and 41024 logged on my 3 front end servers every 15-30 min.

As this is a test environment I experienced a problem with one of my internal CA servers and created a new one.

I then re-issued certs for my front end from the new CA and the events stopped being logged.

Hope it helps.

Event ID 14584 – LS Protocol Stack – Connection attempt to at least one service in a pool failed.

I have seen the warning/error below logged on my Lync Servers:

  • “Connection attempts to the following services have failed. Another attempt will be made for each service every 10 minutes.
    Service Address:; Pool FQDN: LyncPool1.domain.com; Down Time: 0:15
    Service Address:; Pool FQDN: LyncPool1.domain.com; Down Time: 0:14

    Cause: The specified service(s) are unavailable.
    Check the servers in the pool(s) on which the service(s) are installed.”

From what I have seen these have no impact on the server. My servers are fully patched and up-to-date.

Hope it helps.