Retrieve all mailboxes assigned to a specific ActiveSyncMailboxPolicy

Task: Retrieve all mailboxes assigned to a specific ActiveSyncMailboxPolicy.  The ActiveSyncMailboxPolicy we are searching for is labeled “VIP”.

Run the following:

Get-CASMailbox -ResultSize unlimited | Where ActiveSyncMailboxPolicy -like “VIP” | Select SamAccountName, DisplayName,ActivesyncMailboxPolicy,ServerName | Export-csv C:VIP_EASPolicy.csv

Get all messages from all transport servers by a specific sender, starting on a specific day

Get all messages from all transport servers by a specific sender, starting on a specific day and export to CSV

Use this one-liner:

Get-TransportServer | Get-MessageTrackingLog -sender:test@test.com -start 7/15/2014 -resultsize unlimited | export-csv c:export.csv

How to modify distribution list in the GAL using Outlook

How to edit/modify a distribution list in the GAL via Outlook

NOTE: In order to edit a distribution list in the Global Address Listing (GAL), you must be the owner of that list.

STEP 1:  In Outlook, hold down the Control, Shift, and B keys. This will open your address book.

Once the address book is open, verify that “Global Address List” is selected in the Show Names from the: field.

Now, search for the name of the list you would like to edit by entering it into the box located under Type Name or Select from List:.

Once you have located the list you would like to edit, double click it to open the Properties window.

STEP 2:  Click on Modify Members button

STEP 3:  You can add a new member to this list by clicking on the Add button on the right side of the window.

STEP 4:  The Add Users window will now open. Type the name of the user you would like to add and then double click on their name. The name should appear in the field at the bottom of the window. Now click OK.

Note: Repeat STEPs 3 and 4 as many times until you have added all the people you would like to this distribution list.

STEP 5:  Any changes that you have made should now appear. Once you are finished, click OK  to return to your address book. You may now close your address book and continue where you left off.

NOTE:  You must be the owner of the distribution list in order to edit it. If you are not the owner and you try to add a member, you will receive the following error message: changes to the distribution list could not be saved. You do not have sufficient permission to perform this operation on this object. 

Recover Deleted items in Outlook or Outlook Web App

Recover deleted items in Outlook or Outlook Web App


Restore deleted items in Outlook 2013

https://support.office.com/en-US/Article/Restore-deleted-items-in-Outlook-49e81f3c-c8f4-4426-a0b9-c0fd751d48ce?ui=en-US&rs=en-US&ad=US

Restore deleted items or email in Outlook Web App

https://support.office.com/en-US/Article/Recover-deleted-messages-or-items-in-Outlook-Web-App-c3d8fc15-eeef-4f1c-81df-e27964b7edd4


Restore Deleted items in Outlook 2010

https://support.office.com/en-US/Article/Restore-deleted-items-in-Outlook-cd9dfe12-8e8c-4a21-bbbf-4bd103a3f1fe

 

Configuring Message rules for a shared Mailbox

Configuring message rules for a shared mailbox

Scenario: How do I access a shared mailbox and change a rule.  I do have admin rights and full access to this mailbox but when I do a file > open> and try to change the rules, it reverts back to my primary mailbox rules.

Note: Exchange 2010 users cannot modify rules for mailboxes in Exchange 2013, and vice versa

There are several methods to get this to work:

Method 1: Outlook 2010 or Outlook 2013

Configuring Message rules for a shared Mailbox/Service Mailbox

If you are using Outlook 2010 or Outlook 2013 and either have been granted Full Access permissions to the mailbox or have been provided separate credentials for it, then you can also configure this shared mailbox as an additional Exchange account or add it as a secondary mailbox of your own.

How to add an additional mailbox in Outlook 2010:

http://www.groovypost.com/howto/microsoft/add-a-second-additional-mailbox-in-outlook-2010/

How to add an additional mailbox in Outlook 2013

http://www.groovypost.com/howto/add-additional-mailbox-in-outlook-2013/

Once the mailbox has been added, select its Inbox folder and add the rule as you would normally do for your own mailbox.

Method 2: Outlook Web App

When you have been granted Full Access permissions, then you can log on with your own username and password and click on your own name in the top-right corner to get to the option of opening another mailbox.

If you haven’t been granted Full Access permissions but do have separate log on credentials for the additional mailbox, you can use that to log on.

Once logged in, you can create a message rule in the following way:

    For OWA 2013:
    Gears icon (right side of your name)-> Options-> Organize email

    For OWA 2010:
    Options (below your name)-> Create an Inbox Rule…
 

How to Get OutlookAnywhere Configuration Settings from ActiveDirectory

When you type get-outlookanywhere settings, the settings are typically retried from CAS servers. However, those settings can also be retrieved directly from active directory and usually faster than retrieving from CAS servers. To do that, use this PowerShell one liner:

get-outlookanywhere -ADPropertiesOnly | fl identity, *auth*, *hostname

That command will display server name, client authentication method, iisauthentication method and external/internal hostnames

Delegate Installation of Exchange 2013

Delegate Installation of Exchange 2013 Server

Exchange Server 2013 lets you delegate the installation of Exchange servers to people who aren’t members of the Exchange 2013 Organization Management role group.

Notes: Only a member of organization role group can provision a server. Members of delegated setup can install Cumulative updates. Uninstallation of Exchange requires Org role group membership

step 1: There is a built in group for delegating setup of pre-provisioned servers, named the delegated setup role group. Add the installer to this role group. This allows the installer to install provisioned servers

Step 2: If you’re running Setup on the computer that’s being provisioned, run the following command:Setup.exe /NewProvisionedServer /IAcceptExchangeServerLicenseTerms

If you’re running Setup on another computer, run the following command:Setup.exe /NewProvisionedServer:<ComputerName> /IAcceptExchangeServerLicenseTerms

Delegate Installation of Exchange 2010 Server

Exchange Server 2010 allows an administrator to provision a new Exchange server and then delegate the actual setup of that server to another account

Notes: Only a member of organization role group can provision a server. Members of delegated setup can install Cumulative updates and rollups. Uninstallation of Exchange requires Org role group membership

step 1: There is a built in group for delegating setup of pre-provisioned servers, named the delegated setup role group. Add the installer to this role group. This allows the installer to install provisioned servers

Step 2: If you’re running Setup on the computer that’s being provisioned, run the following command:Setup.exe /NewProvisionedServer

If you’re running Setup on another computer, run the following command:Setup.exe /NewProvisionedServer:<ComputerName>

To make sure the server was properly provisioned for Exchange, you can do the following:

Go to Start > Administrative Tools, and then open Active Directory Users and Computers.

Select Microsoft Exchange Security Groups, double-click Exchange Servers, and then select the Members tab.

On the Members tab, check to see if the server you just provisioned is listed as a member of the security group.

If your server is listed as a member of the Exchange Servers security group, it was properly provisioned. Someone who’s a member of the Delegated Setup role group can now install Exchange on that server.

Add a user as the manager of a distribution group without removing existing managers via Exchange PowerShell.

Scenario:  Add a user as the manager of a distribution group without removing existing managers via Exchange PowerShell. If you were to use the Set-DistributionGroup command with the -managedby switch, it would remove the existing managers and set the managers you specified in the switch.  To add the user jdoe1 as a manager and not remove the existing managers from the distribution group ‘HQ-All Employees’, run the following PowerShell commands below.

$Group = Get-DistributionGroup “HQ-All Employees”
$Managers = $Group.ManagedBy
$User = Get-User  jdoe1
$Managers += $User 
Set-DistributionGroup “HQ-All Employees” -Managedby $Managers -BypassSecurityGroupManagerCheck

Excel Magic: If you have an Excel sheet full of groups in Column A and wish to add jdoe1 as the manager to each of those groups, copy the Excel formula below and drag it down for the entire list of groups. The value of each cell will create the Powershell command that you will need for each group.  Copy the cells (the cell values) and Paste it into Exchange PowerShell.  Each command is separated by a ; so the 5 PowerShell commands needed will fit into one Excel Cell and fit on one PowerShell line for each group.

=”$Group= Get-distributiongroup “””&A2&”””; $Managers= $grp.managedby; $User=Get-User jdoe1;$Managers+=$User;Set-DistributionGroup “””&A2&””” -managedby $Managers -BypassSecurityGroupManagerCheck”

A user receives ‘Something went wrong Sorry, we can’t get that information right now. Please try again later. If the problem continues contact your helpdesk’ error message when accessing OWA.

Scenario:  A new mailbox is provisioned and the user is receiving the following error when accessing their mailbox via OWA:

😦something went wrong

Sorry, we can’t get that information right now. Please try again later. If the problem continues, contact your helpdesk.

All normal mail protocols such as OWA and ECP were enabled by default.

Resolution:  I performed a search against the email address for that mailbox and came across two mailboxes that had the same email address  (get-mailbox  jdoe@domain.com). I removed this email alias from the user who was not using it.  The user experiencing the problem could now login to OWA.