GRANIKOS

Als freiberuflicher Trainer in der IT-Branche erhält man regelmäßig Anfragen von Schulungsunternehmen zur Durchführung von vorgefertigten Kursen oder individuell zusammengestellten Schulungen. Solche Anfragen erreichen einen oftmals mit einem festen Preisangebot. Um einordnen zu können, ob es sich dabei um ein Preisangebot handelt, von du auch leben kannst, muss du als Trainer deine Kosten genau kennen und wissen, wie viel du mit einer Schulung verdienen möchtest. In diesem Artikel liegt der Fokus auf MCTs, also Microsoft Certified Trainer, die offizielle Microsoft Trainingskurse unterrichten dürfen. Schulungsunternehmen fragen in der Regel mehrere Trainer gleichzeitig an und entscheiden sich für den Trainer der den günstigsten All-In Preis anbietet. Dies führt leider immer wieder zu einem Preis-Dumping, das auf Dauer die Existenz aller Trainer gefährdet.  Der All-In Preis ist hierbei das besondere Risiko, da du einen festen Tagespreis angibst, der alle Kosten, wie Anreise, Übernachtung usw. enthält. Gerade als Neuling ist es nicht einfach, alle Kosten zu kennen und im Blick zu haben. Um hier ein wenig Abhilfe zu schaffen, habe ich eine Kalkulationsvorlage auf Excel-Basis erstellt. Den Download-Link findest du am Ende des Artikels. Die Vorlage kann ...

Das Blog Cumulative Update für Dezember 2020 (CU1220) fasst interessante Themen rund um Cloud Sicherheit, Exchange Server, Office 365, Microsoft Teams und Azure des Monats Dezember 2020 zusammen. Allgemein [STICKY] Modern Collaboration Architecture (MOCA) [STICKY] Microsoft Products Reaching End of Support for 2020 A breakthrough year for passwordless technology Reader question: Do you recommend Defender in place of third-party antivirus or security tools? Neue allgemeine Datenschutzerklärung Microsoft 1. November 2020 Creating PowerShell Property Names What we've learned working remote in 2020   Exchange Server [STICKY] Outlook License Requirements for Exchange Features Fehler mit E-Mail-aktivierter Sicherheitsgruppe DKIM record in WordPress DNS A reboot from a previous installation is pending. Please restart the system and then rerun Setup Tech Talk - 10 - Exchange und hybride Identitäten WBSC WEBDAY - Exchange Server - Aufzeichnungen Security Updates Exchange Server December 2020 Released: December 2020 Quarterly Exchange Updates   Microsoft 365 | OneDrive | Exchange Online | and more [STICKY] Microsoft Compliance Configuration Analyzer (MCCA) [STICKY] Office 365 Network Performance Tool [STICKY] Office 365 Support and Recovery Assistant (aka SaRA) [STICKY] Office 365 URLs and IP address ranges [STICKY] ...

  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 ...

Exchange Server uses Receive Connectors for providing SMTP endpoints for incoming connections. A modern Exchange Server provides a default connector on TCP port 25.  Sometimes you might have a requirement to create a new receive connector for selected incoming SMTP connections. A standard requirement is a receive connector for relaying messages to external recipients. This cannot (should not) be achieved using the default connector. Each connector uses the RemoteIPRanges attribute to store the list of IP addresses of remote systems that can connect to that connector. The default connector utilizes the full IPv4 and IPv6 addresses ranges. Your new receive connector requires at least a single IP address for a selected remote system that is supposed to connect to that receive connector. You can add a single IP address, address ranges, or IP addresses using CIDR notation. The attribute RemoteIPRanges is a multi-value attribute and has a limit of IP address entries that can be added.  The maximum number of address entries that you can add to that attribute varies. You can store approximately 1,300 entries. When you exceed the number of values you receive the ...

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 Enjoy!    

This is a post summarizing the configuration values for important Exchange-related Active Directory object attributes. Whenever you need to look up these values for troubleshooting, or editing the values manually. Note: You should not edit any of the values manually, just because you can. Edit any Exchange-related attributes, if you are familiar with the result of your changes.   RemoteRecipientType Attribute msExchRemoteRecipientType    1 ProvisionMailbox 2 ProvisionArchive (On-Premises Mailbox) 3 ProvisionMailbox, ProvisionArchive 4 Migrated (UserMailbox) 6 ProvisionArchive, Migrated ...

Microsoft 365 Groups are the backbone of various Microsoft 365 workloads. As you might know, each group utilizes a SharePoint site collection, and an Exchange shared mailbox. When you create a new Microsoft 365 group, SharePoint Online must store the associated site collection somewhere. SharePoint Online uses predefined paths to determine the storage location. These paths are called: Managed Paths. SharePoint Online uses two different pre-configured managed paths: /sites /teams With /sites as the default setting for the Microsoft 365 tenant. Whenever you create, e.g., a new team in Microsoft Teams, the associated site collection is stored in https://TENANTNAME.sharepoint.com/sites/TEAMNAME. As a SharePoint administrator, you see the site collection paths in the list of active sites in the SharePoint Admin Center.   But what can you do, if you want to store the associated site collections in the /teams managed path?   Changing the Managed Path The SharePoint Admin Center provides you with an option to change the managed path for sites, created by users.  Open the SharePoint Admin Center, navigate to Settings -> Site Creation.   Change the setting for Create team sites under to /teams/.   The description of this setting is misleading. ...

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.  300+ Speakers 400+ Sessions Keynotes by Jeff Teper, Naomi Moneypenny, Bill Baer, Jon Levesque, Laurie Pottmeyer, and Michael Holste Sessions are primarily in Englisch, but there are session in six additional languages French, German, Japanese, Korean, Portuguese, and Spanish  Hashtag: #M365VM The virtual conference is a joint effort with SPC.   I speak at Microsoft 365 Virtual Marathon about: Exchange Hybrid - What, Why, and How Wednesday, May 27th 23:00h (CEST)   The marathon session plan is available here. Register now.   Link Register for Microsoft 365 Virtual Marathon   Enjoy!