Office 365

Office 365 – How to migrate contacts from Exchange

During an Office 365 migration from an Exchange on-premises, it can be usefull to migrate contacts information. For some reasons, if you can not do a Active Directory synchronization, contacts information needs to be imported manually.

You can easily do that by running two scripts, one in your Exchange environnement which creates an csv file, and the other into the Office 365 Powershell.

Continue reading

Exchange-1

Exchange – Disable access for a mailbox

Sometimes, it can be usefull to disable access to the Exchange server for a specific mailbox. For exemple, in order to forbid Outlook Web App (Outlook on the Web for Exchange 2016) but you do not want to disable the user account. Or you can prestage the mailbox and only allow access to a specific date/ time.

This can also be used during a migration to another mail system: when the user is migrated, you can disable all access to force the user on the new messaging system. And prevent any email sent by the old Exchange.

Exchange Disable access

Exchange Disable access

Let’s see how to disable all access for a mailbox using ECP or Exchange Powershell:

Continue reading

Exchange-1

Exchange 2013 – Powershell No Mapping Unicode WinRM

Microsoft released the Cumulative Update 11 for Exchange 2013 and Exchange 2016 CU1 in December 2015. With these new packages, they changed the behavior of Exchange Management Shell, (Exchange Powershell).

Prior to 2013 CU11 and 2016 CU1, when you start the EMS, it will connect by default to the local Exchange Server. But with CU11, Exchange Powershell will be proxy to the server where the user’s mailbox is located. It means that when you start the EMS console, it will probably try to connect to another server.

When all your servers are up to date, in some circonstances, you can get an error when launching the EMS: “No mapping for the Unicode character exists in the target”:

Mapping Unicode error

Mapping Unicode error

If you get this error, do not panic and stay calm :). You can find some posts where you need to rebuild the powershell virtual directory, but do not do this! Let’s see how to resolve this issue easily.

Continue reading

Exchange-1

Exchange 2013 – Restart all services with Powershell

When you want to fully restart Microsoft Exchange Services, you can not do this by restarting a single service. You have to stop and start each Exchange Service :

Exchange All Services

Exchange All Services

Powershell

Fortunately, we can restart each service using Powershell script:

#Get List of Microsoft Exchange Services
$services = Get-Service | ? { $_.name -like "MSExchange*" -and $_.Status -eq "Running"}
 
#Restart each service
foreach ($service in $services)
{
	Restart-Service $service.name -Force
}
Exchange Powershell Restart Services

Exchange Powershell Restart Services

Exchange-1

Exchange 2013 – VSS backup does not clean logs 800423f3

In Exchange Server 2013, I got one backup issue with Veeam Backup, but the problem occurs with all VSS backup solutions. I was able to reproduce the issue with Windows Server backup role.

In fact, when I checked the mailbox database folder, all transactions logs were not deleted after the backup, even if the backup is reported as successful.

VSS Backup logs not deleted

VSS Backup logs not deleted

Continue reading

Exchange-1

Exchange 2013 – Web Management Service doesn’t start

With Exchange 2013, you can have an issue where the service “Web Management Service” can not be started. Without it, you can’t install any Cumulative Update and some Exchange functionality are no more available.

Service not started

If you try to install a new CU, you get this error:

Error:
The following error was generated when "$error.Clear();
if (Get-Service WMSVC* | ?{$_.Name -eq 'WMSVC'})
{ Set-Service WMSVC -StartupType Automatic
Start-SetupService -ServiceName WMSVC
}
" was run: "Service 'WMSVC' failed to reach status 'Running' on this server."

When you look into the Service mmc and try to start manually the service, you get the error code -2147483640 :

Web Management Service Error

Web Management Service Error

Continue reading