GRANIKOS

Troubleshooting von Kalender-Stellvertretungen und kalenderbasiertem Präsenzstatus Im ersten Teil der Serie haben ich einen Überblick über das Zusammenspiel der Teams Backend Services mit lokalen Exchange Organisationen vorstellt. Der zweite Teil der Serie beschreibt, wie die Teams Backend Services die lokale Exchange Organisation per AutoDiscover finden und welche Möglichkeiten Sie haben, um Fehlerquellen zu isolieren, sollte es bei diesem Prozess und dem Zugriff der Kalender-App zu Problemen kommen. Dieser dritte Teil befasst sich mit Kalender-Stellvertretungen für Teams-Meetings und dem kalenderbasierten Präsenzstatus. Zum Themenkomplex möglicher Verbindungsprobleme zwischen den Microsoft Backend Services und Exchange Server finden Sie zusätzliche Information in der Microsoft Online Dokumentation.   Troubleshooting Microsoft Teams und Kalender-Stellvertretungen Der Microsoft Teams Client stellt Ihnen nur den persönlichen Kalender zur Verfügung, um Besprechungen oder Live-Meetings zu planen. Wenn ein Stellvertreter eine Team-Besprechung in meinem Namen in meinem Kalender erstellen soll, muss diese Besprechung über Outlook für Desktop geplant werden. Die Planung einer neuen Teams-Besprechung ist nur möglich, wenn das Microsoft Teams AddIn im Outlook Client des Stellvertreters geladen ist. Eine weitere wichtige Voraussetzung ist, dass die Stellvertreterberechtigung über den Outlook-Einrichtungsassistenten für Stellvertretungen erfolgt ist. Eine direkte Berechtigung auf dem ...

Troubleshooting der Kalender-App Teams Backend AutoDiscover Die Teams Backend Services nutzen AutoDiscover Version 2, um das Exchange Anwender-Postfach im Auftrag eines Teams-Clients zu finden. Dieser AutoDiscover V2 Aufruf ist aus Performancegründen ein anonymer Aufruf, um möglichst schnell die Exchange Ziel-URL für das gesuchte Postfach zu ermitteln. Wie bereits im ersten Teil erwähnt, wird erfolgt zuerst immer eine Abfrage gegen den AutoDiscover-Endpunkt von Exchange Online durchgeführt. Sollte sich das Postfach nicht in Exchange Online befinden, erhalten die Backend Services in einer Redirect-Antwort die Zieladresse der lokalen Exchange Organisation, um eine erneute AutoDiscover-Abfrage durchzuführen. Hierbei werden folgende Schritte durchlaufen: Die Teams Backend Services fragen den Exchange Online AutoDiscover-Endpunkt per AutoDiscover V2 JSON-Abfrage nach der URL für das EWS-Protokoll https://outlook.office365.com/autodiscover/autodiscover.json?Email=John.Doe@varunagroup.de&Protocol=EWS   Exchange Online prüft den Empfängertyp (RecipientType) der angefragten E-Mail-Adresse und gibt für den gefundenen Empfängertyp folgende Antworten: RecipientType: Mailbox https://outlook.office365.com/EWS/Exchange.asmx Das Postfach ist ein Exchange Online Postfach, somit sind keine weiteren Schritte notwendig. Die Teams Backend Services haben die notwendige Information, um auf das Postfach und den Kalender zuzugreifen.   RecipientType: MailUser Exchange Online ermittelt den AutoDiscover-Endpunkt ...

Being in a situation where you need to recover IT components or even a whole IT infrastructure after a disastrous event can be stressful. It would help if you stayed concentrated while dealing with the constant status requests by the management. In such a situation, it can help to isolate your mind by listening to music. Music that helps you focus your thoughts, anger, and feelings in such a moment. Maybe you find my Spotify playlist helpful. The playlist contains about 12 hours of music. IT Recovery Playlist Listening to music using a headphone is good, but playing music loud and feeling the rhythm and every single bass is much better. Enjoy.    

This post was published first on April 1st 2021   Wouldn't it be nice if you could stay in Microsoft Teams even when working with your emails? Microsoft Teams is getting even more mature by providing an App for integrating Outlook into the Microsoft Teams client. At least it seems that this is the case. or was it?   The Outlook App (Preview) Last week a new App, still in preview, showed up in the Teams Admin Center (TAC) of some demo tenants. I filtered the list of available apps using Outlook as a search term.   When selecting the app, the details showed that the app was still in preview (v0.41).   As long as the app is enabled within Teams, you can add the app to a Teams Setup Policy and make it available for users. Your users can then access the Outlook App using the Teams app bar.   You can simply click on Outlook in the app bar and, voilá, you have your Outlook inbox in Microsoft Teams. Due to the architecture of Microsoft Teams, you have access to your Outlook on the Web version of your inbox.   Links Learn more ...

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.        Links MCT Summit Middle East My PowerPoint slide deck on SlideShare   

Services of third-party software solutions often interfere with installing a new Exchange Server cumulative update, because these services have a file lock active.  To avoid any issues when installing a CU, or having the prerequisites check fail due to open files, you simply stop the Windows services and ensure that those services do not restart automatically. Especially monitoring solutions that use some kind of watchdog service are a candidate that you must disable for installing an Exchange Server CU. The following two PowerShell examples help you to prepare the Windows services for installing an Exchange Server CU.   Prepare for CU installation In preparation for the installation of an Exchange Server cumulative update, you can use the following PowerShell commands. # Disable and stop services or just stop services # Add other services as needed # Set SMEX service to manual and stop services Get-Service -Name 'ScanMail*' | Set-Service -StartupType Manual Get-Service -Name 'ScanMail*' | ?{$_.Status -eq 'Running'} | Stop-Service -Force # Stop SMEX SQL Express instance Get-Service -Name 'MSSQL*' | ?{$_.Status -eq 'Running'} | Stop-Service -Force # Disable and stop ENow monitoring services Get-Service 'ENow*' | Set-Service -StartupType Disabled Get-Service 'ENow*' | ?{$_.Status -eq 'Running'} ...

You sometimes need some (or even many) test user objects in Active Directory. This script helps you create any number of test users in your Active Directory domain, which you can easily enable for on-premises or remote mailboxes afterward.   The Script # Number of user accounts to create $UserCount = 5 $RandomPassword = $true $DefaultPassword = 'Pa55w.rd' # User name prefix # New user object will be named TestUser1, TestUser2, ... $TestUserPrefix = 'TestUser' # User object properties $GivenName = 'Test' $Surname = 'User' $Company = 'Varunagroup' $JobTitle = @('Junior Consultant','Senior Consultant','Technical Consultant','Business Consultant') $PreferredLanguage = 'de-DE' # Name of the new organizational unit for test user object $TestOU = 'Test User' # Target OU path where the script creates the new OU $TargetOU = 'OU=IT,dc=varunagroup,dc=de' # Import Active Directory PowerShell Module Import-Module -Name ActiveDirectory # Build OU Path $UserOUPath = ("OU={0},{1}" -f $TestOU, $TargetOU) # Check if OU exists $OUExists = $false try { $OUExists = [adsi]::Exists("LDAP://$UserOUPath") } catch { $OUExists =$true } if(-not $OUExists) { # Create new organizational unit for test users New-ADOrganizationalUnit -Name $TestOU -Path $TargetOU -ProtectedFromAccidentalDeletion:$false -Confirm:$false } else { Write-Warning ('OU {0} exists please delete the OU and user ...

  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: Englisch Spanish German French Italian Portuguese Polish   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: Exchange Hybrid - What, Why, and How Session schedule details 13:00h (UK)    Links Scottish Summit 2021 Website Register for Scottish Summit Scottish Summit Sessions Scottish Summit 2020 YouTube Channel   See you online for the Virtual Scottish Summit.

Use this script with modern public folders only. See this post for legacy public folders.   Description When you want to migrate your modern public folders from Exchange 2013 or newer to modern public folders in Exchange Online, you must prepare the public folder names for migration. Public folder names are not allowed to contain the following: A backslash "\" A forward slash "/" A semicolon ";" A comma "," A colon ":" Leading or trailing spaces The script Fix-ModernPublicFolderNames.ps1 fixes the public folder names to prepare migration to modern public folders in Exchange Online.   Examples # EXAMPLE 1 # Rename and trim public folders .\Fix-ModernPublicFolderNames.ps1 # EXAMPLE 2 # Rename and trim public folders, export list of renamed # folders and folders with renaming errors as text files .\Fix-ModernPublicFolderNames.ps1 -ExportFolderNames   Version History 1.0, Initial community release   Links The script for updating modern public folder names and legacy public folder names share the same repository.   Download and follow at Github: https://github.com/Apoc70/Fix-PublicFolderNames   Follow Twitter @stensitzki LinkedIn   Community Are you located in Germany, Austria, or Switzerland? Join the Exchange User Group DACH to collaborate with other Exchange enthusiasts. Follow us on Twitter @exusg.        

I was involved in a troubleshooting request for a hybrid mail flow issue. Before I take a closer look at the issue, let's talk about the hybrid setup. Hybrid Setup A managed service provider runs separated on-premises Exchange Organizations for various clients. Also, the service provider runs it's own Exchange Organization in a hybrid setup with Exchange Online (EXO) utilizing centralized mail flow. Let's name the managed service provider Varunagroup, using the primary domain varunagroup.de. The on-premises IT-Infrastructure consists of the following email components: Centralized Third-Party Email Gateway Solution with two nodes TLS certificates in use mx01.varunagroup.de mx02.varunagroup.de   Varunagroup on-premises Exchange Organisation Hybrid setup with Exchange Online Hybrid mail flow using Edge Transport Servers TLS certificate in use smtpo365.varunagroup.de Centralized mail flow with EXO inbound connector configured by HCW  Tenant name: varunagroup.onmicrosoft.com Internet Send Connector with address space '*' uses the centralized Third-Party gateways as smart hosts    Multiple separated on-premises Exchange Organization hosted for SPLA-clients ...

I am honored to speak at TeamsFest 2020.  TeamsFest 2020 is a TeamsFest is a 100% free, 100% community-driven conference dedicated to Microsoft Teams. It aims to bring together exceptional technical talent and thought leaders to democratize knowledge about Microsoft Teams, encourage participation in the Microsoft Teams community, and give those who are struggling financially an opportunity to attend a first-class Teams conference. My session will cover the requirements for implementing an Exchange Hybrid configuration with Exchange Online when utilizing on-premises mailboxes with Microsoft Teams.   Date 7th October 08:00h - 18:30h (CEST)   Links TeamsFest 2020 Registration TeamsFest Overview and agenda   See you at TeamsFest 2020!    

Last updated: 2020-09-17   Problem The use of Exchange Edge Transport Servers requires the synchronization of user and configuration data from internal Exchange Servers to the Edge Transport Servers. The synchronization utilizes secure LDAP (EdgeSync) to transmit the data securely and is based on an Edge Subscription. When you create a new Edge Subscription on your internal Exchange Servers by importing the Edge Subscription XML-file, establishing the EdgeSync-connection might fail. You will find the following error in the application event log of the internal Exchange Server: Log Name: Application Source: MSExchange EdgeSync Event ID: 1035 Task Category: Synchronization Level: Error Keywords: Classic Description: EdgeSync failed to synchronize because it only supports Cryptographic API certificates. The local Hub Transport server's default certificate with thumbprint XYZ isn't a CAPI certificate. To set a CAPI certificate as the default certificate, use the Enable-ExchangeCertificate cmdlet with the Services parameter using the value of SMTP. When you encounter this error I recommend removing the Edge Subscription from the internal ...