discover the luxury rolex imitacion online watch store.
replica watches are the best qulity online.
richard mille fakes are the perfect mix between italian design and swiss technology at the service of the passion for the sea.
I am honored to speak at CloudEight Virtual Summit 2021.
CloudEight is a conference about Microsoft 365 related topics and takes place for the third time.
My session covers the topic "Microsoft Teams and On-Premises Mailbox - Why?"
What are the reasons for using Microsoft Teams with on-premises mailboxes, what are the technical requirements, and why is this approach not necessarily a good idea?
Looking forward to seeing you at the virtual conference.
I am honored to be a speaker at the Virtual Scottish Summit 2021 conference, taking place on Saturday, 27. February.
The Scottish Summit is a truly European event. You can choose from 365 sessions covering mostly any about Microsoft 365 workloads in seven languages:
Attend my session when you are interested in the challenges of implementing Exchange Server Hybrid, and the requirements to make it work with Microsoft Teams and on-premises mailboxes.
My session at Scottish Summit 2021:
See you online for the Virtual Scottish Summit.
This year's MCT Summit Middle East took place on 19-20 March, with two full days of content about Microsoft technologies. Four session tracks plus a workshop track offered possibilities to learn and share knowledge, not only with the MCT community.
The session recording will be made available on the event website.
I enjoyed talking about Exchange Hybrid, what it is, why you need it and how you implement it using the Hybrid Configuration Wizard.
My PowerPoint presentation is available on Slideshare.
I look forward to next years' event.
The Microsoft 365 Virtual Marathon is happening on May 27-28 2020.
This is a free online event, providing you with 36 hours of non-stop sessions from speakers around the globe. You can join every time.
The virtual conference is a joint effort with SPC.
I speak at Microsoft 365 Virtual Marathon about:
The marathon session plan is available here.
The Microsoft 365 Virtual Marathon took place on May 27-28 2020.
The recording of my session "Exchange Hybrid - What, Why, and How" is available on YouTube.
Browse all recordings of the Microsoft 365 Virtual Marathon here: https://www.youtube.com/channel/UCrtmT6Ir1MIs0ZES7sKMmqA
I am honored to speak at Teams Nation 2021 on 12th May about Microsoft Teams Admin Roles and Teams Admin Center.
Register today and visit my session in room Teams Nation Germany (TCD). As suspected, the session will be in German.
Teams Nation is a community conference and offers 115 sessions in 11 tracks.
Visit the conference site and register today.
Lastly I've encountered an interesting PowerShell error after upgrading several servers running Exchange Server 2013 CU9 to Exchange Server 2013 CU11.
After a successful upgrade, the Exchange PowerShell script to redistribute the DAG databases failed with an error.
.\RedistributeActiveDatabases.ps1 -DagName DAG01 -BalanceDbsByActivationPreference -Confirm:$false
Cannot process argument transformation on parameter 'Identity'. Cannot convert value "MAILBOXDB01" to type
"Microsoft.Exchange.Configuration.Tasks.DatabaseCopyIdParameter". Error: "Cannot convert hashtable to an object of the
following type: Microsoft.Exchange.Configuration.Tasks.DatabaseCopyIdParameter. Hashtable-to-Object conversion is not
supported in restricted language mode or a Data section."
+ CategoryInfo : InvalidData: (:) [Get-MailboxDatabaseCopyStatus], ParameterBindin...mationException
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,Get-MailboxDatabaseCopyStatus
+ PSComputerName : SERVER01.mcsmemail.de
The interesting part to note is conversion is not supported in restricted language mode
The supported language mode is configured in the application settings of the PowerShell virtual directory of the Exchange Back End website.
The application settings after Exchange Server 2013 CU11 update:
Running PSLanguageMode with value RestrictedLanguage is the default setting. You should change this setting only, if you encounter PowerShell issues.
Double-click PSLanguageMode and change the value to FullLanguage.
Currently I have not validation why a clean Exchange 2013 CU11 setup does not show this behaviour. A plain Exchange 2013 CU11 setup executes the script without any issues.