Unknown's avatar

About Michel de Rooij

Michel de Rooij, with over 25 years of mixed consulting and automation experience with Exchange and related technologies, is a consultant for Rapid Circle. He assists organizations in their journey to and using Microsoft 365, primarily focusing on Exchange and associated technologies and automating processes using PowerShell or Graph. Michel's authorship of several Exchange books and role in the Office 365 for IT Pros author team are a testament to his knowledge. Besides writing for Practical365.com, he maintains a blog on eightwone.com with supporting scripts on GitHub. Michel has been a Microsoft MVP since 2013.

Exchange 2013 Server Role Requirements Calculator 6.3


Excel-2013[1]The Exchange 2013 Server Role Requirements Calculator received an update to reflect changed incorporated in Exchange 2013 SP1, such as adjusted guidance to accomodate for MAPI/http and its impact on the CAS role, as well as revised pagefile sizing guidance. The new version number is 6.3.

Changes since version 6.1:

  • Fixed Backup Requirements calculations to include greater than 50 databases.
  • Added additional processor core support.
  • Fixed the number of database volumes calculation when disk count is specified.
  • Fixed the database size calculation for A/P scenarios to match A/A scenario calculations.
  • Fixed the calculator to take into account halving database number per volume in non-site resilient scenarios.
  • Fixed conditional formatting errors on transport configuration settings.
  • Fixed transport sizing to take into account mailbox growth.
  • Updated CAS megacycle calculations to align with SP1 guidance.
  • Revised Dispart.ps1 script to create database mount points consistent with JetStress performance counters.
  • Added Calculator version number to record one field three of CSV export files.

You can download the calculator here. For more information, please consult the release notes and read me

Microsoft Exchange Conference 2014 Countdown


imageThe one conference people involved with Exchange and related technologies are looking forward to is now only one week away, the Microsoft Exchange Conference. In fact, this will be the first MEC(*) I will be attending and I am really looking forward to it. Apart from attending sessions and joining discussions that I am sure will be interesting, conferences like these means catching up with peers, some I have not had the pleasure of meeting them in person yet.

With over 100 sessions crammed in a 3 day conference, you can imagine picking sessions is not an easy task, depending on your experience and knowledge you wish to attain. For those still in doubt on which sessions to attend to, Exchange fellow Tony Redmond wrote a helpful list of recommendations here and followed up today with an overview of the MVP sessions here. As you may or may not know, MVPs are recognized people from the community offering independent real-world experience and insights.

Apart from all the learning opportunities, there will also be festivities and parties. I’d like to bring to your attention one of these parties, the ENow sponsored UC Architects party at the rooftop of the Speakeasy on April 1st (no joke). You can request a pass at  http://schedulemymaintenance.com but be quick because the number of passes is limited. To increase your chances, should drawing be required, make sure you listen to The UC Architects episode 35 for a special promo code.

Like with conferences I have attended before, I will be tweeting noteworthy information from the event. If you want to receive MEC-wide information, I suggest you monitor the official hashtag, #IAmMEC.

*) Pronounced by many as  [mek] but according to this Geek Out with Perry – MEC Edition video, Microsoft pronounces it as [em-ee-see]. However, this is insignificant compared to the discussion on how to pronounce Azure.

The UC Architects Podcast Ep35


UC2We’re glad to announce the availability of episode 35 of The UC Architects podcast. This episode is hosted by Steve Goodman who’s joined by Michael van Hoorenbeeck, Dave Stork, Serkan Varoglum, John Cook, Ståle Hansen and yours truly. Editing was done by Andrew Price.

Topic discussed in this episode are:

  • Exchange 2013 Service Pack 1
  • Exchange 2013 SP1 Transport bug
  • Exchange 2010 SP3 UR5
  • Exchange 2007 SP3 UR13
  • Have Public Folder limits changed recently? Let us know!
  • Now Available: GetLogFileUsage.ps1 script
  • Configuring Azure Multi-factor Authentication with Exchange 2013 SP1
  • Exchange 2013 SP1 now includes native ADFS support
  • Windows Server 2012 R2 and Database Availability Groups
  • Certificate Inspector™ by DigiCert
  • Office Web Apps Server 2013 Service Pack 1 (SP1) also available
  • Static IP Addresses for VMs in Windows Azure
  • HA EOP/Office 365 to On-Premises routing
  • SAML 2.0 federation with Office 365
  • Demo Scripts for Remotely managing Office 365 using PowerShell
  • Lync Conference 2014 – Some sessions released
  • Lync Room Systems (LRS) PSA – Update to 15.08
  • Minor update 1.01 to Lync2013 Call Pickup Group Manager Tool.
  • Lync call accounting for user or departmental billing – beta v0.2
  • Office 2013 SP1 fixes annoying UISuppressionMode bug for Lync
  • Using CsClientPolicyEntry for Inband Snom Provisioning
  • Lync 2013 – Masking Information from Monitoring Reports
  • Lync / Powerpoint certificate issue

More information on the podcast including references and a link to download the podcast here or you can subscribe to the podcasts using iTunes, Zune or use the RSS feed.

About
The UC Architects is a bi-weekly community podcast by people with a passion for Unified Communications; our main focus is on Exchange, Lync or related subjects.

Internal Message Classifications visible in Outlook


Ex2013 LogoMessage classifications were introduced with Exchange 2007 which seems like ages ago now. They are a piece of metadata which you can assign to messages, for example the intended audience or sensitivity of messages. These message can then be treated accordingly by the recipient or you can leverage transport rules functionality and Rights Management Services to act on or protect these messages.

Let’s assume you have created a custom message classification using the following cmdlet:

New-MessageClassification –Name ‘InternalUseOnly’ –DisplayName ‘Internal Use Only’ –SenderDescription ‘This message is for internal use only.’

When you retrieve the list of message classifications using Get-MessageClassifications you will notice three additional classifications:

image

Exchange comes with these message classifications which are used by Exchange internally: ExAttachmentRemoved, ExOrarMail and ExPartnerMail. These should not be used by users, let alone be visible. To make them hidden, the PermissionMenuVisible attribute is set to $false for these classifications. This will make them not show up in Outlook WebApp:image

Now, using classifications in Outlook is less admin-friendly and requires exporting of classification information and configuring Outlook to read these classifications from a file. In short, the process described on TechNet TechNet to use message classifications from Outlook is as follows:

From the Exchange Management Shell, run the Export-OutlookClassification.ps1 script from Exchange scripts folder, e.g.

& ‘C:\Program Files\Microsoft\Exchange Server\v15\Scripts\Export-OutlookClassification.ps1’ | Set-Content ‘C:\OutlookClass.xml’

Next, copy the XML file to a location on the client or networked location which is readable by Users. On the client, make the following registry changes:

[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\Policy]
"AdminClassificationPath"="c:\\Classifications.xml"
"EnableClassifications"=dword:00000001
"TrustClassifications"=dword:00000001

Note: For the purpose of this example the XML is stored as C:\Temp\OutlookClass.xml . Note that “15.0” is for configuring Outlook 2013, replace with 14.0 for Outlook 2010 and 12.0 for Outlook 2007.

Restart Outlook so it will use these settings. When composing a message you will now see the message classification options appear under Options > Permission:

image

Apart from the message classification “Internal Use Only” we created, you will also see that Outlook shows the internal classifications by their display name. That should not be happening.

When you open up the Outlook classifications export file, you will spot that it contains all classifications, including the internal ones:image

So, what you can do now and what the documentation seems to fail to mention, is that after exporting message classifications you may want to remove the internal classifications “Attachment Removed” (ExAttachmentRemoved), “Originator Requested Alternate Recipient Mail” (ExOrarMail) and “Partner Mail” (ExPartnerMail) from the XML export file. Downside is that message with these internal classifications will not display the related description in Outlook, but that should not be an issue and a better option than users being able to select them.

When you have removed the three entries from the XML file and restarted Outlook, the built-in options will no longer be on the permission menu:

image

Exchange 2013 SP1 Transport Agent Fix (updated)


Ex2013 LogoAfter installing Exchange 2013 Service Pack 1, people reported issues with Transport Agents. Symptoms are that the Transport service doesn’t start or stops shortly after starting the service or you can’t install the 3rd party product.

Products experiencing the issue are TrendMicro ScanMail, McAfee Email Security (GroupShield), Symantec Mail Security for Exchange, AVG for Servers, ESET Mail Security for Exchange and CodeTwo Exchange Rules. Products from other vendors may be affected as well.

Microsoft is aware of this issue and has published KB2938053 which has a small Exchange2013-KB2938053-FixIt.zip script to fix the issue.

The cause of the issue lies in XML files containing invalid XML markup in the form of “comments” which prevents .NET from loading the XML files, e.g.

<!-- 15.0.847.30 -------------------------------->

The two files containing the invalid XML markup are:

$Env:Windir\Microsoft.NET\assembly\GAC_MSIL\policy.8.0.Microsoft.Exchange.Data.Common\v4.0_15.0.847.30__31bf3856ad364e35\Microsoft.Exchange.Data.Common.VersionPolicy.cfg
$Env:Windir\Microsoft.NET\assembly\GAC_MSIL\policy.8.0.Microsoft.Exchange.Data.Transport\v4.0_15.0.847.30__31bf3856ad364e35\Microsoft.Exchange.Data.Transport.VersionPolicy.cfg

Be advised that the script supplied in the KB article tries to locate and fix various alternate versions of those files. Something you might want to consider as well when fixing it manually, should you be unable to locate the specific files mentioned above.

After running the script you should be able to start the Transport service or install 3rd party containing transport agents..

Update (3/5): Updated blog after official KB article got published. The issue was also blogged on by fellows Jason Sherry, Paul Cunningham while Tony Redmond has additionanal background details here.