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.

The UC Architects Podcast Ep41


iTunes-Podcast-logo[1]I’m happy to announce the availability of episode 41 of The UC Architects podcast.

This episode is hosted by Steve Goodman, who is joined by Pat Richard, Stale Hansen and Tom Arbuthnot. Editing was done by Andrew Price.

Some of the topics discussed in this episode are:

 

  • Microsoft ordered to hand over overseas email, throwing EU privacy rights in the fire
  • Microsoft’s unified technology event for enterprises
  • Exchange Log Level GUI Powershell Script
  • Lingering entries for long-departed servers retained by Exchange 2013
  • Outlook 2013 cannot connect to Exchange 2013 using MAPI over HTTP when proxy is enabled
    Exchange 2013′s Hybrid Configuration Wizard in SP1 and CU5 is BROKEN!
  • Walking through Exchange 2013′s Hybrid Configuration Wizard steps
  • Microsoft Exec Discusses Plan To Offer Customers Free Office 365 Migration Services
  • Signatures in Office 365
  • BitTitan Data Encryption Released
  • Complete Home Lync Lab
  • Isn’t It Time For Lync To Make Way For Skype?
  • Assign Lync Policies to Lync users based on Active Directory Group membership
  • Change Lync Conferencing Dial-In Number Display Order (GUI)
  • Installing and Configuring Lync 2013 Watcher Node
  • Plantronics-as-a-Service
  • Lync Snom Configuration Manager
  • Lync Phone Edition July 2014 CU
  • Microsoft selects 911Enable for Lync Online Dedicated
  • New Lync PowerShell tool: Lync 2013 Contact Backup and Restore Tool (GUI)
  • Polycom UCS 5.1 for VVX phones
  • Using Lync Like a LyncPro
  • Logitech cc3000e review
  • Lync Users Group
  • UC Birmingham User Group – August 13th @ The Priory Rooms Meeting & Conference Centre
  • Norwegian Lync Day October 14th, 2014

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.

 

HCW 2013 Subtask CheckPrereqs execution failed


Ex2013 LogoA quick heads-up on the Hybrid Configuration Wizard (HCW) in Exchange 2013, which is broken. The HCW in Exchange 2010 does not have this issue.

The HCW is needed when you want to configure or maintain your Exchange 2013 Hybrid configuration. When checking the prerequisites, the Exchange 2013 HCW may throw the following error message:

Subtask CheckPrereqs execution failed: Check Tenant Prerequisites
Deserialization fails due to one SerializationException: 
Microsoft.Exchange.Compliance.Serialization.Formatters.BlockedTypeException: 
The type to be (de)serialized is not allowed: 
Microsoft.Exchange.Data.Directory.DirectoryBackendType

The issue has been documented in KB2988229. An Interim Update is available, as reported here. The IU is available for Exhange 2013 Service Pack 1 (CU4) and Cumulative Update 5. Unfortunately, the IU is not available publicly, but must be requested through support.

The fix will be incorporated in Exchange 2013 Cumulative Update 6.

If you must, you can use Exchange fellow Steve Goodman’s instructions documented here, which describes the process to manually configure Exchange 2013 Hybrid deployments. Be advised that, as Steve also points out, the Exchange Hybrid deployment support status depends on the ability to run HCW successfully.

Microsoft announces Unified Technology Event for Enterprises


imageOne Event to rule them all, One Event to find them,
One Event to bring them all and in the darkness bind them

Today, through Microsoft’s General Manager for Office, Julia White, Microsoft announced that there will be a Microsoft Unified Technology Event for Enterprises in Chicago next year, to be held in the week of May 4th. This new event is aiming at the current attendees of TechEd, Sharepoint Conference, Lync Conference, Project Conference (uh, what), the Microsoft Management Summit and our beloved Exchange Conference. It is also replacing those events starting next year, meaning RIP for events like MEC, SPC and TechEd. There is nothing mentioned regarding the faith of the related events held in non-NA regions, like TechEd Europe or TechEd Australia.

I consider myself lucky being able to attend the – what looks to be the last (again) – Microsoft Exchange Conference this year. Looking back at that event, thinking about setting, identity and depth, one can only hope for the best with this new monstrous event. After all, looking at recent attendance numbers and assuming there are some attendees visiting multiple of these events, adding recent numbers of TechEd North America (10k+), SPC (12k+), MMS (5k+), MEC (2,5k), LyncConf (0,5k) show the estimated attendance could easily go in the direction of 20,000+ attendees. That estimate is without representation from the related product groups and exhibitors. That is one big event.

With the next release of Exchange being announced for 2015, one could assume there are more products lined up for a common launch next year, similar to the Wave15 launch end of 2012 when Exchange 2013 was released together with Lync 2013, Office 2013 and SharePoint 2013. Though, I do not know the exact timelines of the non-Exchange products, so I could be wrong here.

An event of this scale event poses some serious challenges. That could be as elementary as transport or where to put that many people in the near surroundings of the convention center. Also, what sessions will be scheduled and at what level, given the mixed crowds of the generalistic TechEd and the more product-oriented deep-dive events like MEC. Companies sending delegations of their IT staff to these events may need to have drawings on who needs to stay back at home to keep IT running.

For people worried about the new unified event, Julia White tries to reassure people that the new format will be as ‘magical’ and ‘enjoyable’ as the individual events and it will even exceed them regarding ‘awesomeness’ and value. Meanwhile, Exchange fellows Tony Redmond and Paul Robichaux written up their own views on this change, I suggest you check them out as well.

Note that this site mentions McCormick Place as the event venue (thanks Mike Rigsby). It also mentions the event takes place from Monday until Friday:

Event Name Venue Start Date End Date Attendees
Microsoft Commercial Event 2015
Lakeside Center at McCormick Place

Map It

05/04/2015 05/09/2015 20000

The official announcements can be found here and here. More details will be made available around September.

Clearing AutoComplete and other Recipient Caches


Exchange 2010 Logo

Last version: 1.21, April 28th, 2021: Updated formatting and link to GitHub

Anyone who has participated in migrations or transitions to Exchange has most likely encountered or has had to work around potential issues caused by the nickname cache. A “cache,” also known by its file extension, NK2 in older Outlook clients, is a convenience feature in Outlook and Outlook WebApp (OWA) which lets users pick recipients from a list of frequently-used recipients. This list is displayed when the end user types in the first few letters.

The potential issue revolves around end users using those lists to send messages, as the list contains cached recipient information. Because this information is static, it may become invalid at some point. Thus, when users pick recipients when sending messages, they may be sending messages to non-existent recipients or invalid e-mail addresses, which create issues like non-delivery of e-mail.

Read the full article over on ENow Solutions Engine blog.

Clean-AutoComplete

Using the script mentioned in the article, which can be used to clear cached recipient information, is straightforward. It requires Exchange 2010 or later and Exchange Web Services Managed API 1.2 (or later) which you can download here. Alternatively, you can copy the Microsoft.Exchange.WebServices.DLL with the script as it will also look for it in the current folder.

The script Clean-AutoComplete.ps1 has the following syntax:

Clear-AutoComplete.ps1 [-Mailbox] <String> [-Server <String>] [-Impersonation] [-Credentials <PSCredential>] [-Type <Array>] [-Pattern <String[]>]

Where:

  • Mailbox is the name or e-mail address of the mailbox.
  • Server is the name of the Client Access Server to access for Exchange Web Services. When omitted, the script will use AutoDiscover.
  • Switch Impersonation specifies if impersonation will be used for mailbox access, otherwise the current user context will be used.
  • Credentials specifies the user credentials to use.
  • Type specifies what cached recipient information to clear. Options are Outlook  (Outlook AutoComplete stream), OWA (OWA Autocomplete stream), SuggestedContacts, RecipientCache or All. Default is Outlook,OWA.
  • Pattern is the pattern of e-mail entries to remove from cache. Only works with OWA, SuggestedContacts and RecipientCache type clearances.

So for example, suppose you want to clear the Autocomplete stream used by Outlook on a mailbox, you can use:

Clear-AutoComplete.ps1 -Identity Olrik -Type Outlook -Verbose
ScreenCap

To remove the Autocomplete stream used by OWA on your Office 365 account, you can use:

Clear-AutoComplete.ps1 -Identity olrik@office365tenant.com –Credentials (Get-Credential) –Type OWA

Be advised that clearing the Outlook AutoComplete stream will only have effect for Outlook running in Online mode. Outlook caches this information as well in the OST file, leaving the options of running Outlook with the /CleanAutocompleteCache switch, or remove and let Outlook recreate the OST file. The temporary Stream_AutoComplete *.dat files created under %USERPROFILE%\AppData\Local\Microsoft\Outlook\RoamCache are used by Outlook to speed things up.

Disabling Auto-Complete and Suggested Contacts
Alternatively, you can disable Auto-Complete, the equivalent of unchecking the Outlook option ‘Use Auto-Complete List to suggest names when typing in the To, Cc and Bcc line‘, by setting the following registry key:

Note: In the examples below, you need to modify the version number in the examples corresponding to the Outlook version you wish to apply these settings against. Use 16.0 as indicated for Outlook 2016, but change it to 15.0 for Outlook 2013, or 14.0 for Outlook 2010.

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Preferences\
ShowAutoSug=0 (REG_DWORD)

To configure this setting using a Group Policy, use the following registry setting:

HKEY_CURRENT_USER\Software\Policies\Microsoft\office\16.0\Outlook\Preferences\ShowAutoSug=0 (REG_DWORD)

You can also disable Suggested Contacts folder, the equivalent of unchecking the Outlook option ‘Automatically create Outlook contacts for recipients that do not belong to an Outlook Address Book’, with the following registry key:

HKEY_CURRENT_USER\Software\Microsoft\office\16.0\Outlook\Contact\CreateContactsForOneOffs= 0 (REG_DWORD)

The related Group Policy setting is:

HKEY_CURRENT_USER\Software\Policies\Microsoft\office\16.0\Outlook\Contact\CreateContactsForOneOffs= 0 (REG_DWORD)

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

Download
You can download the script from GitHub here.

Multi-Factor Authentication in Office 365 (Part 2)


wp_ss_20140521_0001Multifactor Authentication is a must-have for services based in the cloud, especially for accounts with administrative purposes. We have already covered what Office 365 Multifactor Authentication is and how to configure it in Office 365 tenants with the Office 365 admin center, and we briefly showed the end user experience. Now we will look at how we can use the Azure Active Directory Module for Windows PowerShell to configure Office 365 authentication with MFA.

Azure Active Directory Module for Windows PowerShell (AADMPS) enables organizations to not only configure MFA for existing end users who use PowerShell, but also enhance their current provisioning process with MFA options. By pre-configuring MFA, administrators can prevent end users from having to go through the initial MFA setup process and use their currently configured mobile phone or office number for verification.

Read the full article over on SearchExchange