IT/Dev Connections 2014 Wrap-Up


Connections 2014 JerseyNote: For those that attended Jaap and my session on Thursday, PowerShell Tips & Tricks for Exchange, and are looking for the scripts used in the demonstrations, they are available here. The slidedeck is available here.

Today I returned from one of the largest, independent conference on Microsoft technologies, as it is not sponsored by Microsoft. Sessions were spread over a 3 day period on popular topics as SharePoint, SQL, developer and Windows, as well as out beloved Exchange. In addition, the conference offered pre and post-conference workshops. The conference was held in the city of Las Vegas, a place which I hadn’t seen after I left it around 1996 when leaving something called Comdex.  The estimated total of attendees was 1,400, of which around 100-200 attended Exchange sessions since people were free to switch between tracks.

With this being my first Exchange Connections, I must confess the community feeling and depth of contents were well-above expectation. Exchange sessions were not only presented by independent Exchange MVP’s and MCSM’s, but there were also sessions hosted by Tim McMichael and Wes Blalock of Microsoft. Greg Taylor, Exchange PM CXP, was also present, but unfortunately didn’t host any session.

The Exchange track was kicked off by an plenary session for those interested in everything Exchange or related topics such as Office 365. I am still waiting for the formal feedback and ratings on the PowerShell Tips & Tricks for Exchange session with Jaap I did on Thursday, but unofficial feedback was overall good which I am happy with since this was my first presentation in front of an international audience and I am somewhat self-critical. The week was closed with a Exchange panel session, wrapping up the week and answering audience questions. It was also when the winners were announced of the trivia contest offered by sponsor ENow. Prizes included an Xbox One and $500 in cash.

When connecting with the community, you get a sense on the current opinion on the product and future plans. It was learned that the majority of the attendees are still running Exchange on-premises and a vast majority still runs Exchange 2007 or Exchange 2010. There were quite a few comments on product quality, mainly referring to the recent issues with Exchange 2013 Cumulative Updates resulting in Hybrid Configuration Wizard issues, issues with Exchange 2013/Exchange 2007 co-existence deployments, or more recently issues experienced when using Chrome with the Exchange Administrative Center.

Connections 2014 VegasI had a blast at Connections, despite a minor inconvenience as my luggage was delayed. There were lots of opportunities to meet up at the conference, receptions, many dinners and the excellent Scheduled Maintenance party. Outside of these formal events, people were also actively looking each other up to exchange musings over a pint. Having experienced my inaugural Exchange Connections this year, I must say I am really looking forward to next year’s event to stay in contact with the community, and catch up with my MVP and MCSM friends. The MVP Summit is next up on the agenda, so I won’t have to miss most of my MVP friends for long.

I was also very pleased with my Huawei E5372, a so-called MiFi device which functions as a mobile WiFi access point, routing traffic to a mobile data provider at a fraction of the roaming mobile data costs. In the end, the amount of mobile data used after this week was rather low, which mainly can be attributed to the excellent WiFi facilities in Aria, the conference hotel.

One final shout out to ENow for the personalized NFL jersey. People attempted pronouncing my last name, and most came up with “The Rouge” which is close enough for me.

Finally, here are some of the other Exchange Connections wrap-ups:

Austrian MVPs Martina Grom (Office 365) and Toni Pohl (Client Development) analysed Twitter data related to IT/Dev Connections 2014, and came up with some nice statistics where they present here. It seems I was a Top 10 Tweeter.

Ready for IT/Dev Connections 2014


imageIt’s almost time to head off to IT/Dev Connections. This year, the conference will take place from September 15-19 in the Aria Resort in Las Vegas, USA. IT/Dev connections is a widely recognized independent, multi-disciplinary conference with tracks for Development, Exchange, SharePoint, SQL Server and Windows related topics.

For the Exchange track, I will be co-hosting a session with long-time Exchange MVP and compatriot Jaap Wesselius, on PowerShell Tips & Tricks for Exchange. In 60 minutes we will show and demonstrate some Exchange-related PowerShell tricks, which are immediately usable in the daily life of Exchange admins.

PowerShell Tips and Tricks for Exchange
When: 9/18/2014, 1:00 PM- 2:15 PM
Room: Bluethorn 1/2

Note that Jaap also has a session earlier that day, Autodiscover – What’s the deal, which starts at 9:00 in Bluethorn 1/2 as well.

Other Exchange MVP fellows as well as members of the Product Group are lined up to provide some great content. Information on the sessions in the Exchange track can be found here. It appears you can still register for the event here, use SOCIAL14 for a $200 discount.

When you are attending IT/Dev Connections, do not hesitate to come up and say hi. 

I hope to see you there!

Ex2013 CU6 & Ex2007 coexistence issue for EAS


Ex2013 LogoA short notice on an issue when you have deployed Exchange 2013 Cumulative Update 6 in coexistence in an Exchange 2007 environment. Exchange fellow Tony Redmond did a write-up on the issue here.

The issue prevents ActiveSync users whose mailbox reside on Exchange 2007 to authenticate properly when their requests are being proxied from Exchange 2013 CU6 to Exchange 2007. It has been identified in KB2997847. Alternatively, you direct Exchange 2007 EAS traffic directly to Exchange 2007 CAS servers when they are internet-facing and published.

Be advised that a previous known issue in this deployment scenario with delegates and dismounting stores has been identified in KB2997209.

Both articles provide links to request these hotfixes.

Another Exchange fellow, Jason Sherry, is keeping track of resolved and open Exchange 2013 CU6 issues here.

Exchange2013-KB2997355-FixIt-v2


Ex2013 LogoAs mentioned earlier, when you have deployed Exchange Server 2013 Cumulative Update 6 in a Hybrid deployment, several Office 365-related mailbox functions will not show up in the Exchange Admin Center (EAC). The issue was identified by Microsoft in KB2997355 and a fix was published.

However, the script to fix the issue looks for the XAML file in the default Program Files folder, using the default Exchange installation folder. Better is to check the actual Exchange installation folder, which can easily be accomplished in Exchange Management Shell using the $exinstall environment variable, or by reading the folder from the registry.

To help those installing Exchange in a non-default installation folder, and I know there are quite a few of you out there, who are hesitant to correcting the installation path in the provided FixIt script, I have create an alternative version of the Exchange2013-KB2997355-FixIt script. This version will read the installation path from the registry. Not disturbing but changed as well is correcting the XAML file in one go, unlike the official script which performs 3 consecutive read/modify/write actions on the same file.

You can download the Exchange2013-KB2997355-FixIt-v2.ps1 script here.

 

Exchange-Processor Query Tool: PowerShell Edition


powershellLast Update: Version 1.2, July 9th, 2018.

Anyone sizing for Exchange Server 2013/2016 or even still Exchange Server 2010, using the Server Role Requirements Calculator, has to determine processor requirements at some point. This is accomplished by looking up the SPECint_rate2006 score of the planned processor configuration and matching that against the calculated number of required megacycles by the calculator. To account for fail-over situations, additional overhead needs to be added to the number of megacycles. The process as part of the overall sizing has been explained in detail by Jeff Mealiffe here.

The Exchange consultants’ Swiss army knife when determining SPECint rates is the Exchange Processor Query Tool, an Excel sheet designed by Scott Alexander from Microsoft, which allows you to easily look up and determine the SPECint_rate2006 value by inputting a processor model. While still useful, the tool has been out there since 2011. Also, it would be nice sometimes to see which systems are eligible for a certain sizing specification, rather than validating if the planned processor configuration meets the sizing requirements.

So, I wrote a PowerShell script which can query the SPECint rates for you. Because the rating scores are returned as objects, you can perform additional tasks using PowerShell functionality, such as:

  • Use additional criteria, such as vendor, min/max number of cores, etc.
  • Calculate the average SPECint2006 Rate Value for a certain CPU/cores configuration.
  • You can use the SPECint value calculated by the Server Role Requirements Calculator  to find hardware configurations which meet the required total megacycles requirements, optionally including a required overhead percentage.
  • You can select if you are sizing for Exchange Server 2010 or Exchange Server 2013.

Requirements
The script requires PowerShell and internet access to query the SPECint database.

Usage
The script is called Exchange-PQT.ps1, in honor of the Processor Query Tool (PQT).  The syntax is as follows:

Exchange-PQT.ps1 [-CPU <String>] [-Vendor <String>] [-System <String>] [-Overhead <Int32>] [-MinMegaCycles <Int32>] [-Type <String>] [-MinCores <Int32>] [-MaxCores <Int32>] [-MinChips <Int32>] [-MaxChips <Int32>] [<CommonParameters>]

The information returned and which you can use for post-processing is: Vendor, System, CPU (processor description), Cores, Chips (number of CPU’s), CoresPerChip (number of Cores per CPU), Speed, Result, Baseline, MCyclesPerCore (megacycles per core), MCyclesTotal (total megacycles), OS and Published. Note that megacycles calculations are based on the selected Exchange version, by default this is Exchange Server 2013.

A quick walk-through on the parameters:

  • CPU, Vendor or System can be used for partial matching on the respective attribute.
  • Type specifies what calculation to perform. Possible values are 2010 for Exchange Server 2010 and 2013 for Exchange Server 2013. Default value is 2013.
  • MinCores/MaxCores/Cores can be used to only return information for systems with less, more or a specific number of cores.
  • MinChips/MaxChips/Chips can be used to only return information for systems with this more, less or a specific number of CPU’s.
  • MinMegaCycles can be used to specify a threshold for the total megacycles value for returned items, using the specified Type for calculations.
  • Overhead can optionally be used to take into account a certain percentage for megacycles overhead. Default is 0 (0%).
  • Ratio/vCPU can be used to specify the vCPU:pCPU ratio. For example, specify a Ratio of 2 to use a 2:1 vCPU to pCPU ratio. Default is 1 (1:1). Use the vCPU paramete to specify the the number of vCPU allocated.

Few notes:

  • MinCores/MaxCores and MinChips/MaxChips are mutually exclusive, because we can not specify both in the query against the SPECint database. However, you can use additional filtering on objects returned in the pipeline to distill information, e.g.
    Exchange-PQT.ps1 –MaxCores 32 –MaxChips 8 | Where { $_.Cores –ge 4 –and $_.Chips –ge 2}.

    Do note that usage of these parameters is recommended when possibe, as it will minimize the result set from SPECint.

  • Make sure you set Type to 2010 when sizing for Exchange 2010.

Examples

Lookup the specifications of the server used by Jeff in his sizing example (Hewlett-Packard DL380p Gen8 server with Intel Xeon E5-2630 processors @2.30GHz):

.\Exchange-PQT.ps1 -System 'DL380p Gen8'  -CPU 2630 | select System,MCycle*

Search all specs for systems from Dell containing x5470 processors and return megacycle information for Exchange 2010 calculations:

.\Exchange-PQT.ps1 -CPU x5470 -Vendor 'Dell Inc.' -Type 2010 | Select System,*cycle*

image

Calculate average SPECint 2006 rate values for  hex-core x5450 systems:

.\Exchange-PQT.ps1 -CPU x5470 | Where { $_.Cores -eq 8 } | Measure -Average Result

Search all specs for Dell systems using x5670 CPUs, with a minimum total of 16,000 megacycles and 20% megacycle overhead:

.\Exchange-PQT.ps1 –Vendor Dell -CPU x5670  -MinMegaCycles 16000 -Overhead 20 

image

To calculate when using a non-1:1 vCPU:pCPU ratio, use Ratio in combination with vCPU. For example, to calculate the average SpecInt rate for 20 core systems with an E5-2670 CPU, using a 2:1 vCPU:pCPU ratio, allocating 12 vCPU cores:

.\Exchange-PQT.ps1 -CPU 'e5-2670' -Cores 20 -Ratio 2 -vCPU 12 | Measure-Object -Average -Property Result

Download
You can download the script from the TechNet Gallery page or  GitHub.

Feedback
Feedback is welcomed through the comments. If you got scripting suggestions or questions, do not hesitate using the contact form.

Revision History
See TechNet Gallery page.