Scenario: You get the error message below when trying to add a new mail profile in Outlook.
“The profile name you entered already exists”
Solution: Delete an Outlook Mail Profile from the Registry and then Restart
Scenario: You receive the following bounce back when sending to a distribution group that has moderation enabled:
Delivery has failed to these recipients or groups:
The Message can’t be moderated because the approval system is too busy and can’t accept messages now. Please try resending this message later, or contact the recipient directly.
Resolution: The arbitration mailbox that the distribution group is using for moderation is having problems processing the message or located on legacy Exchange servers that is no longer accessible. To resolve this, set the arbitration mailbox to another arbitration mailbox.
To determine the arbitration mailbox that the distribution group is currently using, run this:
get-distributiongroup “All Users” | Select ArbitrationMailbox
To determine the arbitration mailboxes in the organization to choose from:
get-mailbox -arbitration
-or get-mailbox -arbitration -domaincontroller RootDCName
Now set the new arbitration mailbox on the distribution group:
Set-distributiongroup “All Users” -arbitrationmailbox “SystemMailbox”be42da……..02ed2}”
Scenario: You want to find who has delegate permissions to a mailbox and export the users, folders, and access permissions to a CSV File.
Run the following:
$AllUsers = get-mailbox test*
ForEach ($Alias in $AllUsers)
{
$Mailbox = “” + $Alias.Name
Write-Host “Getting folders for mailbox: ” $Mailbox
$Folders = Get-MailboxFolderStatistics $Mailbox | % {$_.folderpath} | % {$_.replace(“/”,””)}
$list = ForEach ($F in $Folders)
{
$FolderKey = $Mailbox + “:” + $F
$Permissions = Get-MailboxFolderPermission -identity $FolderKey -ErrorAction SilentlyContinue
$Permissions | Where-Object {$_.User -notlike “Default” -and $_.User -notlike “Anonymous” -and $_.AccessRights -notlike “None” -and $_.AccessRights -notlike “Owner” }| Select $Mailbox, User, FolderName, AccessRights, *path*
}
}
$list | Export-csv C:delegates.csv
Scenario: If you want to check to see if your Exchange 2013 Anti-malware policies are working, send EICAR virus through email. Its not a actual virus, but Exchange 2013 will treat it as if it was due to the contents of the file.
1. Put the string below in the contents of a text file:
X5O!P%@AP[4PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*
2. Save it as EICAR.txt
3. Attempt to email this file as an attachment to someone and observe the behavior set in your anti-malware policies.
Scenario: When attempting to create an archive mailbox for an Exchange 2013 mailbox, the following error is displayed:
Mailbox ‘user1’ can’t be archive-enabled because it has a managed folder policy assigned. Archives are supported only with a retention policy, the message records management feature introduced in Exchange 2010.
Resolution: Although you can see the ManagedFolderMailboxPolicy property for a mailbox, Exchange 2013 does not support Ex2010 MRM and it ignores its functionality. By attempting to set the managedfoldermailboxpolicy to null, it would not do anything on the mailbox:
set-mailbox user1 -managedfoldermailboxpolicy $null
A work around is to add a temporary retention policy to the mailbox and remove the retention policy:
set-mailbox user1 -retentionpolicy “My Retention Policy”
set-mailbox user1 -retentionpolicy $null
When you add a retention policy to the mailbox, it automatically nulls out the managedfoldermailboxpolicy value. By setting the retention policy back to null, it removes the 2013 retention policy completely as well. You will now be able to create a archived mailbox for that user.
Scenario: Integrate Exchange 2013 OWA and LYNC together. The steps are from the Exchange perspective
Steps:
1. Configure Partner Applications with Exchange and Lync:
“C:Program FilesMicrosoftExchange ServerV15ScriptsConfigure-EnterprisePartnerApplication.ps1 -AuthMetaDataUrl ‘https://atl-cs-001.litwareinc.com/metadata/json/1’ -ApplicationType Lync”
2. Configure OWA Virtual Directories to enable Instant Messaging and to assign OCS as the Instant Messaging Type. Note: InstantMesaging should be enabled but the InstantMessagingType is set to none by default.
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingEnabled $True -InstantMessagingType OCS
3. Copy the Thumbprint of the Certificate you are using for Exchange by running:
Get-ExchangeCertificate -server Srv2013CM1
4. Add the 2 keys under the <appsettings> section of the web.config file located on C:Program FilesMicrosoftExchange ServerV15ClientAccessOWA for each of the backend servers.
<add key=”IMCertificateThumbprint” value=”EA5A332496CC05DA69B75B66111C0F78A110D22d”/><add key=”IMServerName” value=”atl-cs-001.litwareinc.com”/>
5. Recycle the MSExchangeOWAAppPool:
C:WindowsSystem32InetsrvAppcmd.exe recycle apppool /apppool.name:”MSExchangeOWAAppPool”
If you use Outlook Web App Policies:
You will have to enable InstantMessaging and set the InstantMessagingType to OCS. By default, policies are not assigned to any user. Therefore any user will use the settings of the OWA Virtual Directory. OWA Policies override the settings set on the virtual directories.
Get-OwaMailboxPolicy | Set-OwaMailboxPolicy -InstantMessagingEnabled $True -InstantMessagingType “OCS”
Scenario: We were getting alerted that the mount points (1 TB drives) on Exchange were getting low on free disk space. During investigation, we noticed that there was an inconsistency with the size of the files and folders on the drive versus what Disk Management was showing.
Cause: Shadow Copies must have been enabled at some point, and there was a shadow copy of another mount point on the mount point I was investigating. (Open Disk Management –>Right click the drive and go to Properties –> Go to the Shadow Copies Tab and scroll down the list of Hard Drives)
Solution:
From a command prompt, enter the following:
Diskshadow
Delete Shadows All
When you look at the disk space now, the shadow copy was removed and the space is now showing correctly.
Scenario: When you attempt to remove a mobile device from a users mailbox, you receive the error below.
Error: An unexpected error has occurred and a Watson dump is being generated: DeviceId cannot contain hyphens.
Resolution: Remove the mobile device object via ADSI Edit.
1. Open ADSI Edit.
2. Under the Default Naming Context, navigate to the user object of the mailbox that has the mobile device.
3. Expand that user object, and click on the CN=ExchangeActiveSyncDevices.
4. Delete the Mobile Device for this user.
Task: You want to measure your Powershell commands so you can time your commands for efficiency. In the example below, I want to time how fast my results are returned for finding all Mailboxes in our organization.
Resolution: Select from #Start to #End and copy and paste it all into PowerShell. Make sure you paste it all at once. It will execute the start and end time variables and then subtract it. It will then display the $total in these various units of measure; TotalMilliseconds, TotalSeconds, TotalMinutes, TotalHours, TotalDays, and Ticks.
#Start
$Start = Get-Date
Get-Mailbox -resultsize unlimited
$End = Get-Date
$total = $End-$Start
$total
#End
Scenario: You receive the following error in Outlook when trying to Add/Modify Delegates within Outlook:
Error: The Delegates settings were not saved correctly. Cannot activate send-on-behalf-of list. You do not have sufficient permission to perform this operation on this object.
Resolution: Add the IgnoreSOBError with a value of 1 in the registry.
Note: x.0
in the above registry key represents your Outlook version. Please use one of the following values.
Ex-Shell 