Tag: Exchange 2013

MS16-010: Security update in Microsoft Exchange Server to address spoofing: January 12, 2016

This security update resolves a vulnerability in Microsoft Exchange Server that could allow information disclosure if Outlook Web Access (OWA) doesn’t handle web requests, sanitize user input and email content correctly.

To learn more about the vulnerability, see Microsoft Security Bulletin MS16-010.

Download:
Microsoft Exchange Server 2013 Service Pack 1 (3124557)

Microsoft Exchange Server 2013 Cumulative Update 10 (3124557)

Microsoft Exchange Server 2013 Cumulative Update 11 (3124557)

Microsoft Exchange Server 2016 (3124557)

Cumulative Update 11 for Exchange Server 2013

Cumulative Update 11 for Microsoft Exchange Server 2013 was released on December 15, 2015. Several nonsecurity issues are fixed in this cumulative update or a later cumulative update for Exchange Server 2013.

This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles:

This update also includes new daylight saving time (DST) updates for Exchange Server 2013. For more information about DST, go to Daylight Saving Time Help and Support Center.

 

Download Cumulative Update 11 for Exchange Server 2013 (KB3099522) now.

The given key was not present in the dictionary while installing Exchange 2013 CU10

I wanted to install Exchange 2013 CU10 on my lab. But i get the following error.

[09-22-2015 11:31:09.0224] [2] Saving object “My Marketplace Apps” of type “ExchangeRole” and state “Unchanged”.
[09-22-2015 11:31:09.0240] [2] Used domain controller DC01.wardvissers.local to read object CN=My ReadWriteMailbox Apps,CN=Roles,CN=RBAC,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=wardvissers,DC=local.
[09-22-2015 11:31:09.0271] [2] [ERROR] The given key was not present in the dictionary.
[09-22-2015 11:31:09.0271] [2] [WARNING] An unexpected error has occurred and a Watson dump is being generated: The given key was not present in the dictionary.

CU10 Error

At this moment i found no solution for it.

Cumulative Update 10 for Exchange Server 2013

Exchange Team has released Cumulative Update 10 for Exchange Server 2013.

From the Microsoft Exchange Team blog:

The release includes fixes for customer reported issues, minor product enhancements and previously released security bulletins, including MS15-103.

Cumulative Update 10 does not include updates to Active Directory Schema, but does include additional RBAC definitions requiring PrepareAD to be executed prior to upgrading any servers to CU10. PrepareAD will run automatically during the first server upgrade if Setup detects this is required and the logged on user has sufficient permission.

The updates released today are important pre-requisites for customers with existing Exchange deployments who will deploy Exchange Server 2016.Cumulative Update 10 is the minimum version of Exchange Server 2013 which will co-exist with Exchange Server 2016.

For the full list of fixes check: KB3078678

Cumulative Update 10 is available for download here.

CalCheck Powershell Script to fix Calander Issues the Easy Way

I created a handy script to fix a Exchange calender the easy way.

I does the following:
– Ask for the username
– Gives full access to user mailbox and disable automapping
– Export Name,LegacyExchangeDN from the user to list.txt
– Run CalCheck
– Remove Full Access Permissions

Put CalCheck.ps1 in de same folder where calcheck.exe exsist.

Download CalCheck

You can find the script the Microsoft Script Libary:
https://gallery.technet.microsoft.com/scriptcenter/CalCheck-Powershell-Script-c419c10e

ExchangeLyncAdminScript.ps1 Script to Manage Exchange & Lync & Active Directory

Exchange & Lync Admin Script created by Ward Vissers
www.wardvissers.nl

Tool to Manage Active Directory & Exchange & Lync

THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK
OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER

    Please select the admin area you require

        1. Active Directy Users Tasks
        2. Active Directy Computers Tasks
        3. Active Directy Groups Tasks
        4. Active Directy Protected From Accidental Deletion Tasks
        5. Active Directy FSMO Tasks
        6. User Profile Tasks
        7. Exchange Tasks
        8. Lync Tasks
        9. Quit and exit
    Enter Menu Option Number:

Download: https://gallery.technet.microsoft.com/scriptcenter/Exchange-Lync-Script-c079133e

Configure your Exchange 2013 server with Configure-Echange2013.ps1 Updated to V3.1

Updated to V3.1

Change List:

# V1.0 Begin
# V1.1 Added Some New Options 12-10-2014
# V1.2 Added Hyper-V Best Practise & NTFS Partition Offset
# V1.3 Added KB2995145 .NET Framework 4.5 garbage collector heap Fix
# V1.4 Added Set Minimum Disk Space Warning level (180GB Default CU6 200GB CU5)
# V1.5 Added Some new features
# V1.6 Changed the Layout & Add Move Arbitration Mailbox
# V1.7 Added PST Export & KB2990117
# V1.8 Added Full backup, Database in GB and Mailbox Size in GB Export CSV
# V1.9 Added Outlook AnyWhere & SafetyNetHoldTime
# V2.0 Added Check DatacenterActivationMode, Get-DatabaseAvailabilityGroupNetwork, Add Static Route, Disable Replation Network on DAG, Database Copies Per Volume (AutoReseed)
# V2.1 Added Edge Subscription
# V2.2 Added Check Transaction Log Growth
# V2.3 Changed the Menu to Submenu’s
# V2.4 Added Check Database White Space
# V2.5 Added MAPI HTTP External URL
# V2.6 Fixed OWA Virtual URL & HTTP URL
# V2.7 Added Fixes & Mountpoints & Changed Set Minimum Disk Space Warning Level from REG to GlobalOverride
# V2.8 Maintaince Added
# V2.9 Set Power to Highperformance
# V3.0 Check of Microsoft.Exchange.Management.PowerShell.SnapIn is loaded
# V3.1 Added Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.domain.com & Set-OutlookProvider -Identity EXCH -CertPrincipalName msstd:*.domain.com

Download: https://gallery.technet.microsoft.com/scriptcenter/Configure-Exchange-2013-e0ffb2a6

Exchange 2013 OWA Error: StoragePermanentException

Error: SDServerErr;Microsoft.Exchange.Data.Storage.StoragePermanentException
SDServerErr;Microsoft.Exchange.Data.Storage.StoragePermanentException
 
Delete the meeting reminders by using the MFCMAPI editor

These steps help you remove a meeting reminder that still appears even though the original meeting was removed. This typically occurs if the meeting reminder is corrupted.

Note: Although the MFCMAPI editor is supported by Exchange Online, use caution when you make changes to mailboxes by using this tool. Using the MFCMAPI editor incorrectly can cause permanent damage to a mailbox.
Note The exact steps may vary, depending on the version of MFCMAPI that you’re using.

  1. Install MFCMAPI editor. It’s available from the following Microsoft CodePlex MFCMAPI website:

    http://mfcmapi.codeplex.com 

  2. In Outlook, click the Send/Receive tab.
  3. n the Preferences group, click Work Offline, and then exit Outlook.
  4. Double-click the MFCMapi.exe file to start the MFCMAPI editor.
  5. On the Session menu, click Logon and Display Store Table.
    A screen shot of MFCMAPI x86 Build windows, showing the Sessio tab and Logon and Display Store Table option
  6. Right-click the mail profile that you want to change, and then click Open Store.
    A screen shot of mail profiles
  7. Expand Root-Mailbox, expand Finder, and then double-click Reminders.
    A screen shot after expanding Root - Mailbox
  8. Locate the recurring appointment by sorting the Subject column or the To column.
  9. Right-click the appointment, and then click Delete Message.
    A screen shot of appointment, showing the Delete Message
  10. In the Delete Item dialog box, select one of the permanent deletion options, and then click OK.
  11. Click Start, type outlook.exe /cleanreminders in the search box, and then press Enter.
  12. If you’re prompted, select your profile to start Outlook.

KB2503266

new CMDlet parameters missing in Exchange 2013 CU9 KB3075700

When you upgrade your Exchange 2013 server to CU9 some command are missing.

These you need wen you want more control over Sent Items when using shared mailboxes.

Whether a mailbox is used by multiple users as a communication tool, a shared mailbox remains an important business requirement.
Early releases from Exchange 2013 there was a no way to configure this behavior.

In Office 365 and Exchange 2013 CU9, this feature on shared mailboxes is disabled by default.

If you mis it run:
setup.exe /preparead /iacceptexchangeserverlicenseterms

Get-Mailbox -RecipientTypeDetails Shared | Set-Mailbox -MessageCopyForSentAsEnabled $True
Get-Mailbox -RecipientTypeDetails Shared | Set-Mailbox -MessageCopyForSendOnBehalfEnabled $True

https://support2.microsoft.com/kb/3075700/

Cumulative Update 9 for Exchange Server 2013

Exchange Team released Cumulative Update 9 for Exchange Server 2013

Fixes:

Translate »