Tachytelic.net

Office 365

Mail (microsoft outlook 2016) application not found

by 6 Comments

When migrating a customer to Office 365 I had a problem opening the mail control panel applet. It simply showed the error message “Application not found”:

Error message when trying to run the mail applet from Microsoft Outlook 2016 "Application not found"

This seemed to be occurring on 64-Bit machines where we had installed 32-Bit Office 2016 from the Office 365 portal.

I found two workarounds for this:

Workaround One: Run the mail applet directly from the command line

  1. Press Windows Key + R to bring up the run dialog
  2. Paste the following:
    C:\Program Files (x86)\Microsoft Office\root\Office16\MLCFG32.CPL 

Workaround Two: Run the mail applet from Outlook 2016

If you in Outlook you can run the control panel mail applet from within Outlook by going to File and clicking on account settings, at the bottom of the account settings drop down you should see a “Manage Profiles” button, which will take you into the mail applet.
Manage mail profiles from within Outlook 2016

I would like to find a proper solution for why this is happening, so if anyone comes across a solution, I’d appreciate it if you share your solution.

Exclude messages from Clutter in Office 365 using a transport rule

by Leave a Comment

This post shows you create a transport rule to exclude messages from clutter and provides the code for you to do it automatically. Clutter is a handy feature of Office 365, but sometimes you need to see emails even if they don’t really require any attention.

Example: Exclude message from clutter based on the email subject using a transport rule.

New-TransportRule -Name "Tachytelic Test Rule" -SubjectContainsWords "Sample Subject to bypass clutter" -SetHeaderName "X-MS-Exchange-Organization-BypassClutter" -SetHeaderValue "true"

The rule is created using the “New-TransportRule” cmdlet as per the above.

Fill the form below to have the PowerShell code to create a transport rule to exclude your important messages:

PowerShell code to exclude messages from Clutter

 

The above example should result in the following in the Office 365 Admin Centre:

Screenshot showing Office 365 Transport Rule to exclude messages from clutter

You can check if the rule worked by sending an email from an external account to your Office 365 tenant and checking the properties of the message when it has arrived:

Screenshot showing message properties from a message that has bypassed clutter
Look for X-MS-Exchange-Organization-BypassClutter: true in the message header to confirm your rule is working.

If you found this post helpful, please rate it 😀

Setting the primary email address for Office 365 users with PowerShell

by 1 Comment

It’s easy to Set the Primary Email Address on Office 365 with PowerShell using the Set-Mailbox cmdlet. The primary address is defined using “SMTP” in uppercase in the email address. For example:

Set-Mailbox -Identity "test.user" -EmailAddresses SMTP:[email protected],smtp:[email protected]

Note: The Set-Mailbox cmdlet will remove all existing aliases, so include them with the command.

Enter the details of the mailbox to be changed in the form below, and PowerShell code will be generated. It includes the required PowerShell to connect to Office 365.

Set the Primary Email Address on Office 365 using Powershell

 

Screenshot showing how to Set the Primary Email Address on Office 365 with Powershell
Example of the Powershell Code changing the Primary SMTP Address

Set the Primary Email Address on Office 365 when the user is being managed by the local active directory

The steps above will work if the user that you are changing is cloud managed. If your accounts are synchronised from your local active directory, then they will be out of the write scope of Office 365. If that is the case please follow the instructions on this page:

https://www.tachytelic.net/2018/08/office-365-how-to-change-primary-email-address/

Office 365: Outlook crashes when sending an email when ESET NOD32 Antivirus is installed

by Leave a Comment

Just a quick post, had a incident today with a user where Outlook 2013 crashed every time they attempted to send an email.

It turned out that this was caused by the ESET NOD32 installation on the machine. Disabling the email integration in NOD32 immediately fixes the problem.

To disable the email integration right click on the NOD32 icon in the notification area to bring up the options screen. Open out the “Web and email” section and then “Email client integration” and then untick the option “Integrate into Microsoft Outlook”

Eset NOD32 options to stop Outlook crashes when sending an email

 

A quick and easy fix to a pain in the arse problem. 😀

Grant a single user access to access all users calendars in Office 365

by 2 Comments

If you need to Grant a single user access to access all users calendars in Office 365 this can be achieved by using the Add-MailboxFolderPermission cmdlet.

If you are adding permissions to a mailbox where no access rights exist already then this is straightforward, but if there is already some access rights in place then the command will fail, because there is an existing permissions entry in place.

You can check for the presence of existing folder permissions with the use of Get-MailboxFolderPermission cmdlet.

Finally if you find there is any existing permission in place you can remove it by using the Remove-MailboxFolderPermission cmdlet.

I have combined these three steps have been into the PowerShell script below which will check for an existing permission, remove it if it exists and then add the new access right. This is useful if you want to re-run the script on a regular basis so that it captures new users.

PowerShell script to Grant a single user access to access all users calendars in Office 365

  1. Type in the UPN(User Principal Name) of the user that you want to grant calendar permissions.
  2. Select the permissions level you would like them to have.
  3. Copy and paste the code to a Powershell window and the calendar permissions will be assigned.

The various levels of permissions are as follows:

  • None – Has no access to the folder.
  • Owner – Gives full control of the folder. An Owner can create, modify, delete, and read folder items; create subfolders; and change permissions on the folder.
  • Publishing Editor – Has all rights granted to an Owner, except the right to change permissions. A Publishing Editor can create, modify, delete, and read folder items and create sub folders.
  • Editor – Has all rights granted to a Publishing Editor, except the right to create subfolders. An Editor can create, modify, delete, and read folder items.
  • Publishing Author – Can create and read folder items and create subfolders but can modify and delete only folder items that he or she creates, not items created by other users.
  • Author – Has all rights granted to a Publishing Author but cannot create subfolders. An Author can create and read folder items and modify and delete items that he or she creates.
  • Nonediting Author – Can create and read folder items but cannot modify or delete any items, including those that he or she creates.
  • Reviewer – Can read folder items but nothing else.
  • Contributor – Can create only folder items and cannot read items.
  • Availability Only – View only availability data
  • Limited Details – View availability data with subject and location

This should generate output similar to the below:

Image showing how to Grant a single user access to access all users calendars in Office 365