GRANIKOS

Die Migration von Öffentlichen Ordnern alter Bauart (bis einschließlich Exchange Server 2010) zu modernen Öffentlichen Ordnern (ab Exchange Server 2013 und in Exchange Online) ist eine komplexe und fehleranfällige Prozedur. Die Vorbereitung und die Durchführung erfordern Arbeiten in der alten und neuen Exchange Server Welt.  Um die Aufgaben unter den Beteiligten in einem Migrationsprojekt für Öffentliche Ordner zuzuweisen und den jeweiligen Status der Aufgaben nachzuverfolgen, kann ein Aktionsplan helfen. Dieser Aktionsplan hat den Schwerpunkt einer Migration von Öffentlichen Ordnern alter Bauart (Legacy Public Folder) zu modernen Öffentlichen Ordner in Exchange Online. Die Arbeitsmappe besteht aus drei Arbeitsblättern: Übersicht Auf dem Arbeitsblatt "Übersicht" können Sie die gewünschten Namen für die Quell- und Zielplattform un die Verantwortlichen für die Migration in der On-Premises und der Cloud-Infrastruktur definieren. Diese Namen werden im zweiten Arbeitsbaltt verwendet. Weiterhin geben Sie ein Startdatum für die Migration an. Dieses Datum wird ins zweite Arbeitsblatt übernommen. Hier ist Ihre Kreativität erforderlich. Zuletzt dargestellt, wieviele Aufgaben sich im Status Nicht begonnen, In Ausführung und Abgeschlossen befinden.   Public Folder Migration Das Arbeitsblatt "Public Folder Migration" stellt den eigentlichen Aktionsplan dar, der ...

Das Blog Cumulative Update für Juli 2018 (CU0718) fasst interessante Themen rund um Cloud Sicherheit, Exchange Server, Office 365, Azure und Skype for Business des Monats Juli 2018 zusammen. Exchange Server Outlook License Requirements for Exchange Features Expanded Folder Age and Attachment reporting for Exchange / Office 365 Mailboxes with EWS and Powershell Hybrid Configuration Wizard and licensing of your on-premises server used for hybrid How to install Exchange Server 2019 on Windows Server 2019 Core Step-by-Step Office 365 | OneDrive | Exchange Online | and more [STICKY] Office 365-Trust Center [STICKY] Office 365 URLs and IP address ranges Office 365 Support and Recovery Assistant (aka SaRA) Office 365: The mystery of mobile phone Exchange Migrations and the data migrated information Upcoming changes to Exchange Web Services (EWS) API for Office 365 Microsoft OneDrive named as a leader in Gartner Magic Quadrant for Content Collaboration Platforms What's new for IT Admins in Microsoft Teams The Downside to Turning Off OneDrive Sharing Microsoft Intune announces support for Android enterprise purpose-built devices Correcting users who have had a mailbox in the cloud and on-premises SSL ...

The Excel workbook Public-Folder-Migration-Actionplan-EN.xlsx spreadsheet is supposed to support you during a migration of Legacy Public Folders (Exchange Server 2010) to Modern Public Folders in Exchange Online. The workbook consists of three spreadsheets: Overview The spreadsheet "Overview" is used to define the names of the source and target platform. Additionally, you can define the names of the persons or groups responsible for the on-premises and cloud infrastructure. Those names are used in the second spreadsheet. You can define a start date for the migration project. There is no additonal calculation taking place. The date is just referenced in the second spreadsheet. It's up to your creativity to add automatic calculations. Finally, a summary for each available task status (Open, In Progress, Finished) is provided.   Public Folder Migration The spreadsheet "Public Folder Migration" contains the top down action plan for migration Legacy Public Folders to Modern Public Folders in Exchange Online. The required tasks are grouped and each task can be assigned and the status can be tracked.    Lookup This spreadsheet is used to provided the task status ...

Problem You have an Exchange Server 2016 organization and plan to upgrade to Cumulative Update 10. You log on to an  Exchange Server, activate DAG maintenance and prepare the Server Component States for installing the new Cumulative Update.  You open an elevated PowerShell Session and start the Setup using ./Setup.exe /Mode:Upgrade /IAcceptExchangeServerLicenseTerms Out of a sudden the Exchange Server CU Setup fails while executing setup step Stopping Services with an error: Microsoft Exchange Server 2016 Cumulative Update 10 Unattended Setup Copying Files... File copy complete. Setup will now collect additional information needed for installation. Languages Management tools Mailbox role: Transport service Mailbox role: Client Access service Mailbox role: Unified Messaging service Mailbox role: Mailbox service Mailbox role: Front End Transport service Mailbox role: Client Access Front End service Performing Microsoft Exchange Server Prerequisite Check Configuring Prerequisites ...

It happend again. A new .Net Framework version has been released via the Windows Update distribution channel and the Exchange Server Team has decided to skip support for the new release. You're only option is to block the automatic installation by the local Windows Update Agent using a registry. The follow BlockNetFramework472.reg file simplifies setting the registry key.   Links Do Not Install .NET Framework 4.7.2 on Exchange Servers How to temporarily block the installation of .NET Framework 4.7.2 As always... Enjoy Exchange Server

The PowerShell script New-RoomMailbox has been updated and release v1.2 has been published to GitHub and TechNet Gallery. The script now creates a third mail-enabled security group to limit the set of users which are allowed to book the resource. The group itself is created (prepared) only, but not assigned to the room resource. Additionally, the default language (locale) is configured. This prohibits the "Set locale" - dialogue when accessing the room mailbox using Outlook on the Web.  Read more here: https://www.granikos.eu/en/justcantgetenough/PostId/337/create-a-new-room-mailbox-with-security-groups Enjoy Exchange.

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