GRANIKOS

Der browserbasierte Zugriff auf ein Exchange Postfach mit Hilfe von Outlook on the Web (OWA) ermöglicht Ihren Anwendern die Anzeige und Bearbeitung von Office-Dateianhängen ganz ohne Medienbruch in eine andere Applikation.  Für Kunden von Microsoft 365 und Exchange Online sind hierzu keine weiteren Konfigurationen notwendig. Die Integration von Office Online mit Outlook on the Web ist standardmäßig aktiviert. Jedem Anwender wird automatisch eine Standard-Richtlinie zu gewiesen. Zu den Betriebsrisiken später mehr. Wenn Sie diese Funktion auch für Ihre lokale Exchange Organisation bereitstellen möchten, müssen Sie zuerst eine Office Online Server Umgebung aufbauen und, falls erforderlich, aus dem Internet erreichbar machen. Die Anforderungen und Implementierungsoptionen einer Office Online Umgebung schauen wir uns in einem der nächsten Artikel an. In Outlook on the Web wird die Möglichkeit einer Anzeige im Browser im Auswahlmenü eines Dateianhanges anzeigt: Ebenso ist das Öffnen des Anhanges das Standardverhalten bei einem Klick auf den Dateinamen.   Problem Im Rahmen einer betrieblichen Anforderung kann es notwendig sein, dass bestimmten Anwendergruppen der Zugriff auf Office Online aus OWA heraus zu unterbinden und stattdessen das Herunterladen von Office-Dateianhängen zu erzwingen. Die Gründe hierfür können sehr unterschiedlich sein.   Lösungen Je nachdem, ob Sie ...

Das Blog Cumulative Update für März 2019 (CU0319) fasst interessante Themen rund um Cloud Sicherheit, Exchange Server, Office 365, Azure und Microsoft Teams des Monats März 2019 zusammen. Exchange Server Outlook License Requirements for Exchange Features How to log EWS Traces to a file in PowerShell Exchange 2019 on Windows Server Core disk management Announcing the updated Exchange Deployment Assistant site Exchange Move Requests | Large Items | And Setting TCP KeepAliveTime To A Large Value bin/ExSMIME.dll Copy Error During Exchange Patching The REAL Exchange Experience | Die Exchange Server Konferenz Exchange 2019 on Windows Server Core - Installation Guide Microsoft 365 | OneDrive | Exchange Online | and more [STICKY] Office 365 Network Performance Tool [STICKY] Office 365 Support and Recovery Assistant (aka SaRA) [STICKY] Office 365 URLs and IP address ranges [STICKY] Office 365-Trust Center OneDrive | GPO: Configure team site libraries to sync automatically Announcing new integrations with Autodesk AutoCAD for Microsoft OneDrive and SharePoint Severe Outlook for Mac issue Mail flow insights (Wave 2) will soon be available in O365 Security & Compliance Center Office 365: Challenges with Distribution Groups ...

This post was originally published on April, 1st, 2019 on http://JustCantGetEnough.Granikos.eu Exchange Server 2019 is the most recent release of the successful email messaging solution, introduced by Microsoft in 1996. Since the early days of the product supported a single primary email address only. The primary email address is used as the sender address when a user composes a new email message and sends the message. A mailbox can have multiple email addresses to receive messages for, but only one so-called reply-address.  But the limitation is not valid anymore. A recent build of the Exchange Server 2019 Cumulative Update 1 released to VLSC contains a new feature called Multi-Reply Addresses.  This new feature is very helpful in scenarios where a single user sends email messages for multiple companies. Think of a business owner who is responsible for two or more companies. In the past, it was required to configure a mailbox account per primary email address used as a reply address. Such a configuration resulted not only on multiple inboxes but in multiple calendars and contact folders as well.  The new Multi-Reply Addresses feature of ...

Sometimes you might be interested in gathering a list of all computer from an Active Directory domain in preparation for migration. You can gather a list of all computer objects using the following command. # Fetch a sorted list of all computer objects Get-ADComputer -Filter * -Property * | Sort-Object Name   The wildcard used with the Property parameter fetches all available attributes for a computer object. Check the available attributes in the result set to identify the attributes you are interested in. # Example output for the first computer object gathered from Active Directory (Get-ADComputer -Filter * -Property * | Sort-Object Name)[0] AccountExpirationDate : accountExpires : 9223372036854775807 AccountLockoutTime : AccountNotDelegated : False AllowReversiblePasswordEncryption ...

A new Exchange Server Conference is coming to Europe.  The REAL Exchange Experience In recent years, the main topics of the major Microsoft conferences have changed more and more towards cloud topics. The simplicity of migrating from on-premises Exchange Server mailboxes to Exchange Online is emphasized at each event. Also, new options have been made available to establish a full hybrid setup with Exchange Online more easily. Topics covering the stable and secure operation of on-premises Exchange Server organizations have no room at these events. The REAL Exchange Experience wants to address the demand for topics related to the operation of Exchange Server in an on-premises IT infrastructure. The conference will be held as a 1-day conference in different cities in Europe. Read more about the conference and register for the conference newsletter here: https://www.granikos.eu/en/Events/TheREALExchangeExperience Enjoy Exchange Server 2019!  

Office 365 supports the upload of PST files to Azure storage for a direct import to mailboxes hosted in Exchange Online. The steps are described in detail in the online documentation at Microsoft Docs. Import CSV using an email address Workload,FilePath,Name,Mailbox,IsArchive,TargetRootFolder,SPFileContainer,SPManifestContainer,SPSiteUrl Exchange,,SALES.pst,TeamMailbox-Sales@varunagroup.de,FALSE,IMPORT,,,   But you might encounter the following error after starting the import job using the Security & Compliance dashboard. X-Psws-ErrorCode: 840001 X-Psws-Exception: Microsoft.Exchange.Configuration.Tasks.ManagementObjectAmbiguousException,The operation couldn't be performed because 'TeamMailbox-Sales@varunagroup.de' matches multiple entries. X-Psws-Warning: When an item can't be read from the source database or it can't be written to the destination database, it will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting Exchange not copy such items to the destination mailbox. At move completion, these corrupted items will not be available at the destination mailbox. X-Content-Type-Options: nosniff Before you were able to start the import job the job configuration, the CSV file, and the content of the PST file were analyzed successfully. There was no hint of multiple entries for the target mailbox. The detailed error message can be retrieved using the View log link. A clear text message is stated in the Status detail column, ...

In Legacy Public Folder World with Exchange Server 2010 it was pretty easy to find the parent path of email enabled public folder: (Get-MailPublicFolder MAILADRESS | Get-PublicFolder).ParentPath   Problem When you try the same approach with modern public folders using Exchange Server 2013+ EMS, you receive an error. Get-MailPublicFolder MSTeamsPF@varunagroup.de | Get-PublicFolder Cannot process argument transformation on parameter 'Identity'. Cannot convert the "varunagroup.de/Microsoft Exchange System Objects/MSTeamsPF" value of type "Microsoft.Exchange.Data.Directory.ADObjectId" to type "Microsoft.Exchange.Configuration.Tasks.PublicFolderIdParameter". + CategoryInfo : InvalidData: (MSTEamsPF:PSObject) [Get-PublicFolder], ParameterBindinmationException + FullyQualifiedErrorId : ParameterArgumentTransformationError,Get-PublicFolder + PSComputerName : P01.varunagroup.de   Solution You need to use the EntryId paramater of the Get-MailPublicFolder result. $pf = Get-MailPublicFolder MSTeamsPF@varunagroup.de Get-PublicFolder -Identity $pf.EntryId Name Parent Path ---- --------- MSTeamsPF \Modern Collaboration Get-PublicFolder does not take pipeline inputs.   Links Find parent path for email activated Public Folder   Enjoy modern public folders :-) 

When you install a Cumulative Update for Exchange Server 2016 you might receive the following informational message: MAPI over HTTP, the preferred Outlook desktop client connectivity with Exchange server, is currently not enabled. Consider enabling it using: Set-OrganizationConfig -MapiHttpEnabled $true For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarnMapiHttpNotEnabl ed.aspx This modern protocol for Outlook has been introduced to Exchange Server with Exchange Server 2013 SP1. The protocol removes the dependency to the Windows Server RPC over HTTP component. The reduced complexity enhances the reliability of the client access protocoll. It's available for quite some time now.  You can enable MAPI over HTTP on the organization level using the following Exchange cmdlet: Set-OrganizationConfig -MapiHttpEnabled $true You can still controll the protocol setting at the user level by deactiviting MAPI of HTTP for certain users, if required: Set-CASMailbox -Identity [USER] -MapiHttpEnabled:$false If your IT infrastructue is still not ready for MAPI of HTTP, your IT components pretty outdated. It's time to move forward and to modernize the infrastructure.  NOTE Did you know that MAPI over HTTP connects to Exchange Server using TLS to encrypt the connection? Even though that the protocol name is "overHTTP" it literally uses HTTPS ...

Description The script can be used to assign an application account (e.g. CRM, ERP) send-as permission to user mailboxes to send emails AS the user and not as the application. This script loops through a membership list of an Active Directory security group. A single mailbox (CRM/ERP service account mailbox) is added to each mailbox (CRM/ERP user mailbox) of the security group members to provide send-as permission.  The script has been developed as a solution to enable proper functionality with Dynamics NAV 2016.   Examples   # Assign Send-As permission to crmapplication@varunagroup.de for all members # of 'CRM-FrontLine' security group. The mailboxes as hosted On-Premises! .\Set-SendAsPermission.ps1 -SendAsGroup 'CRM-FrontLine' -SendAsUserUpn 'crmapplication@varunagroup.de' # Assign Send-As permission to ax@granikoslabs.eu for all members of 'AX-Sales' # security group. All mailboxes are hosted in Exchange Online! .\Set-SendAsPermission.ps1 -SendAsGroup 'AX-Sales' -SendAsUserUpn 'ax@granikoslabs.eu' -ExchangeOnline Requirements Exchange Server 2016 or newer Exchange Online PowerShell connection Exchange Online PowerShell Module to connect w/ MFA   Utilizes GlobalFunctions PowerShell Module Version History 1.0, Initial community release Links Download and follow at Github: https://github.com/Apoc70/Set-SendAsPermission Follow Twitter @stensitzki LinkedIn Xing

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