GRANIKOS

De-Mail Mit dem De-Mail Gesetz vom 28. April 2011 sollte ein neues Zeitalter der sicheren und verschlüsselten E-Mail Kommunikation zwischen Behörden, Unternehmen und Bürgern eingeläutet werden. Das Gesetz regelt die De-Mail-Dienste, die Akkreditierung von De-Mail-Anbietern, die Durchführung der Aufsicht und den Zugang zu De-Mail. De-Mail wurde mit der Intention ins Leben gerufen, die Verbreitung der Ende-zu-Ende Verschlüsselung zwischen E-Mail-Absendern und -Empfängern zu fördern.  Aktuell werden De-Mail-Dienstleistungen von vier Anbieter bereitgestellt: 1&1 De-Mail GmbH Mentana-Claimsoft GmbH T-Systems International GmbH Telekom Deutschland GmbH Der Erwerb einer eigenen De-Mail-Domäne, wie z.B. varunagroup.de-mail.de, ist für Unternehmenskunden nur über einen der akkreditierten Anbieter möglich. Nach Erwerb der De-Mail-Domäne ist auch eine Gateway-basierende Anbindung für den Versand und Empfang von De-Mail-Nachrichten über diesen Anbieter möglich. Der Anbieter selber stellt hierbei die E-Mail-Verschlüsselung nach De-Mail-Standard sicher.  Die Informationen zum Erwerb einer De-Mail-Adresse bzw. De-Mail-Domäne ist bei den vier akkreditierten Anbietern unterschiedlich gut auffindbar.   1&1 De-Mail GmbH Bei 1&1 ist das Produkt De-Mail relativ gut in der zweiten Menüebene zu finden. 1&1 versucht De-Mail Kunden mit einem finanziellen Einsparpotential gegenüber normaler Post zu locken. Hier ist allerdings bisher niemandem aufgefallen, dass mit leicht veralteten ...

Am 31. Mai 2018 fand in den Räumlichkeiten der JAEMACOM das Q2 2018 Treffen der Exchange User Group Berlin statt. Torsten Schlopsnies und ich haben das Open Source Projekt Master Category List Manager vorgestellt. Das Tool dient zum exportieren oder importieren der Hauptkategorieliste eines Exchange Postfaches. Die Kategorieliste eines Quellpostfaches kann direkt in ein anderes Benutzerpostfach oder geteiltes Postfach kopiert werden. Ebenso wird das Kopieren in einen Microsoft Teams Kalender unterstützt. Der Quellcode wird in ca. 14 Tagen veröffentlicht. Links Exchange User Group Berlin Exchange User Group Berlin Meetup Follow Twitter @stensitzki LinkedIn Xing

Description The Category List Manager is a C# Visual Studio Solution that allows you to connect to a source mailbox which is either hosted on an on-premises Exchange Server or in Exchange Online using Exchange Web Services (EWS). You can use AutoDiscover or a static Url to connect to the Exchange Server or Office 365. By default the solution uses the credentials of the user executing the program. These credentials are referred to as default credentials. You can use the Settings form to set dedicated credentials of an user with appropriate access rights to the mailbox(es). The program helps you to Export the master category list from a mailbox to a Xml file Import a master category list Xml file to into a mailbox Copy a master category list from a source mailbox to a target mailbox The supported target mailbox types are: User Mailbox Shared Mailbox Microsoft Teams Mailbox The GUI comes with an easy-to-use UI. The execuable works a command line tool as well and can be used for automation purposes. Use CategoryManager.exe -help to get the most recent command line help information.   Example Screenshot   Presentation Watch the presentation ...

Exchange Server extends the Active Directory schema during the PrepareSchema step during setup. The steps PrepareAD, PrepareDomain, or PrepareAlLDomains create Active Directory containers and objects that are crucially important for a stable operation of Exchange Server. There are different Active Directory objects that are used to determine, if Active Directory has a proper Exchange Server configuration up and running. Forest level At Active Directory forest level the following attributes are used to determine the Exchange Server release: rangeUpper attribute of the ms-Exch-Schema-Version-Pt schema object  msExchProductId attribute of the Exchange organization object in the configuration partition objectVersion attribute of the Exchange organization object in the configuration partition objectVersion of the Microsoft Exchange System Objects (MESO) container  Domain level At Active Directory domain level the following attribute is used to determine the Exchange Server release: objectVersion of the Microsoft Exchange System Objects (MESO) container    I have written a PowerShell script to fetch all required information for all domains in an Active Directory forest. The script simplifies the process of gathering the data. Read more about the script here.   Schema versions Exchange Forest (rangeUpper) ...

Description This script reads the Exchange schema version from the Active Directory schema partition. The Exchange organization name is fetched from Active Directory automatically.    The script fetches at forest level: objectVersion of MESO Container rangeUpper of ms-Exch-Schema-Version-Pt  msExchProductId of Exchange Organization container objectVersion of Exchange Organization container The script fetches at domain level: objectVersion of MESO Container   Examples Code Samples # Fetch all version information in the Active Directory forest .\Get-ExchangeServerVersionInfo.ps1 Sample Output: PS D:\Scripts> .\Get-ExchangeServerVersionInfo.ps1 Exchange Server Schema and Object Information for forest [VARUNA.ROOT] Exchange Organization Name : VARUNA-GROUP Active Directory Schema rangeUpper: 15332 Working on VARUNA.ROOT MESO Container objectVersion : 13236 Exchange Configuration msExchProductId : 15.01.1466.003 Exchange Configuration objectVersion : 16213 Working on VARUNAGROUP.DE MESO Container objectVersion : 13236 Version History 1.0, Initial community release Links Download and follow at Github: https://github.com/Apoc70/Get-ExchangeServerVersionInfo Download and like at TechNet Gallery: https://gallery.technet.microsoft.com/Get-Exchange-Schema-73d3e629 Follow Twitter @stensitzki LinkedIn Xing   Enjoy Exchange Server!

You might have the requirement to authenticate mobile devices and authorize user access to on-premises Exchange Server mailboxes using a multi-vendor strategy. This blog post focuses on the configuration of a Kemp LoadMaster located in an internal network segment. The Kemp LoadMaster ESP functionality is used to allow ActiveSync connections for members of a dedicated security group only. This results in the following authentication and authorization endpoints: MobileIron access policies Kemp LoadMaster ESP security group membership validation Exchange Server ActiveSync client access allowance  Exchange Server mobile device policy   Overview The following diagram shows a simplified overview for mobile devices connecting to an on-premises Exchange Server. The perimeter and internal network segments are omitted for simplification reasons. A MobileIron managed device connects to MobileIron Sentry which validates access with MobileIron policies If a MobileIron policy allows access the device connects to Kemp LoadMaster ESP Kemp LoadMaster ESP configuration validates the security group membership of the authenticating user If the user is a member of the security group, the device connects to Exchange Server Exchange Server authenticates the user and checks, if the ActiveSync protocol ...

SharePoint Conference North America is just 4 weeks away! Now is a great time to register and make your plans to BE THERE in Las Vegas. See the schedule, available now, with over 160 sessions to immerse yourself each day on what you need to know about SharePoint, OneDrive, Yammer, Microsoft Teams, and Office 365. Check out The Road to @SPConf, which reveals the inside scoop about SharePoint Conference North America and what you can expect with the return of the SharePoint community. Register today | Don't miss the conference   Links SharePoint Conference North America - Schedule Register for SharePoint Conference North America    

Description When migrating to new version of Exchange Servers you must move your internal SMTP relay endpoints. This can be a challeging tasks as application owners mostly ignore your requests for such changes.  You can use the information provided in the receive connector log files to identify remote clients (MTAs / MTUs) connecting to the legacy infrastructure. The assumption is that protocol logging is enabled. You can easily active protocol logging across all receive connector fo a single server using the following EMS PowerShell one-liner: Get-ReceiveConnector -Server EX01 | Set-ReceiveConnector -ProtocolLoggingLevel Verbose The scripts searches the log files for the connection's EHLO response which containes the remote name or remote IP-address of the system connecting to the receive connector. You can either search Legacy Exchange Servers (aka Exchange Server 2010) Modern Exchane Servers  Frontend Transport or Backend Transport (aka Hub Transport) For more information read the readme.md file at Github. Note You need to adjust the log file path to suit your IT infrastructure. A next releas will contain a more automatic solution. Examples # Search legacy Exchange servers SMTP receive log files for ...

Today is a wonderful day. I just received the notification email that I am awarded as a MVP for Office Servers and Services. Looking forward to interesting times with the other fellow MVPs, MCM and MCSM colleagues. Thanks.

This article was originally posted on April 1st 2018 The latest downloadable build of Exchange Server 2016 Cumulative Update 9 disclosed an information that was previously shown accidently to the public by Greg T. during his breakout session BRK3249 - Modern Authentication for Exchange Server On-Premises at Microsoft Ignite 2017.   As part of the global harmonization of the product name space of the well established Outlook brand the next release of Exchange Server will be named Outlook Server 2019. This name change was mentioned originally on this slide:   Give it a thought and you'll realize that this change makes absolute sense as different product names for the same software function distract customers and users.  Outlook Outlook for iOS Outlook for Android Outlook on the web Outlook Server Another reason for renaming Exchange Server is a new functionality for integrating personal mailbox files (PST). It was and still is a tedious task for administrators to get hold of all those PST files in use by end users. Instead of implementing a complex and data protection safe process to import PST files to the primary users mailbox the new Outlook Server 2019 ...

Description When you want to migrate your legacy public folders from Exchange 2010 to modern public folders in Exchange Online you must prepare the public folder names for migration. Public folder names are not allowd to contain the following: Backslash "\" Forward slash "/" Leading or trailing spaces The script Fix-PublicFolderNames.ps1 fixes the public folder names in preparation for migration to modern public folders. Examples # EXAMPLE # Rename and trim public folders found on Server MYPFSERVER .\Fix-PublicFolderNames -PublicFolderServer MYPFSERVER Version History 1.0, Initial community release Links Download and follow at Github: https://github.com/Apoc70/Fix-PublicFolderNames Download and like at TechNet Gallery: https://gallery.technet.microsoft.com/Rename-and-Trim-Legacy-85e483b1 Follow Twitter @stensitzki LinkedIn Xing

Just a quick PowerShell one-liner on how to find all configured room lists in your Exchange organization: Set-ADServerSettings -ViewEntireForest $true Get-DistributionGroup -ResultSize Unlimited | Where {$_.RecipientTypeDetails -eq "RoomList"} | Format-Table DisplayName,Identity,PrimarySmtpAddress –AutoSize Enjoy Exchange.