All posts by jaapwesselius

Purge deleted users in Office 365

When deleting users in the Microsoft Online Portal these deleted users are moved to the Recycle Bin where they will be retained for another 30 days. You can see this when selecting Deleted Users in the Portal:

image

In the Portal it is not possible to permanently remove users, or purge deleted user accounts. This can only be done using Remote PowerShell. Please note that the Azure Active Directory Module for Windows PowerShell need to be installed. Click here to install this PowerShell module. Continue reading Purge deleted users in Office 365

Exchange Server 2013 CU7

On Tuesday December 9, 2014 Microsoft released Exchange Server 2013 Cumulative Update 7 and the UM Language Packs for Cumulative Update 7, 105 days after the release of the previous CU6 update. This release is a little overdue because of a last minute issue that was found moments before the original release date of CU7. As long as it improves the quality of the release this shouldn’t be a problem though.

CU7 contains fixes for issues reported by customers, including the Russian Time Zone issue and fixes for issues identified in MS14-075. Updates for MS14-075 are also available for Exchange Server 2013 Service Pack 1 and Exchange Server 2013 Cumulative Update 6. Because of the Microsoft (N-1) support policy this hotfix won’t be available for CU5.

Continue reading Exchange Server 2013 CU7

Health Manager does not start on Exchange 2013 Edge Transport Server

After installing an Exchange 2013 Edge Transport Server (CU6) I noticed the Microsoft Exchange Health Manager was not running. When trying to start this service the following error occurred:

Windows could not start the Microsoft Exchange Health Manager service on Local Computer.

Error 1075: The dependency service does not exist or has been marked for deletion.

image

Continue reading Health Manager does not start on Exchange 2013 Edge Transport Server

Can’t verify domain

Recently I configured a new Office 365 E3 tenant for my lab environment and one of the domains I use (and had in mind for configuring Federation) was exchangelabs.nl.

When adding a domain to a tenant Microsoft has to verify if you’re the owner of the domain being added and this is achieved by you adding a TXT record to public DNS. Microsoft checks for this TXT and thus knows you’re the one and only owner.

After adding the TXT record the verification wizard failed with the following error:

Can’t verify domain

Exchangelabs.nl was already added to a different Office 365 account exchangelabs.onmicrosoft.com.
Sign in to that account as ad admin, and remove domain <domain>. Then come back here and try adding <domain> to this account again.
If you can’t sign in to exchangelabs.onmicrosoft.com as an admin, try resetting your admin password. Continue reading Can’t verify domain

Shared Mailboxes in Office 365

In Exchange 2013 there are regular Mailboxes and there are Shared Mailboxes. The latter are user independent Mailboxes and have common email addresses, for example info@contoso.com or sales@contoso.com. These Mailboxes don’t have a specific user account but are mostly shared between a number of users.

The interesting part is that you don’t need a license to implement a Shared Mailbox (or a Resource Mailbox for that matter) but the users that access the Shared Mailbox need to be licensed though.

There used to be a 10 GB size limit on Shared and Resource Mailboxes, but this was changed recently (November 2014) and all Shared and Resource mailboxes are now restricted to 50GB, just as regular Mailboxes. You can check this on the Exchange Online Limits page on Technet.

Continue reading Shared Mailboxes in Office 365