GRANIKOS

Die Module zur Vorbereitung eines Upgrades von Skype for Business zu Microsoft Teams, vorgestellt im Blog-Artikel vom 19. November, wurden aktualisiert und von drei auf vier Teile erweitert.   Upgrade von Skype for Business zu Microsoft Teams Videos Introduction to Upgrade from Skype for Business to Microsoft Teams (1 of 4) Plan your upgrade from Skype for Business to Microsoft Teams (2 of 4) Manage Coexistence and Interoperability between Skype for Business and Microsoft Teams (3 of 4) Administrator experience for the upgrade from Skype for Business to Microsoft Teams (4 of 4)     Viel Spaß mit Microsoft Teams!   Sie interessieren sich für Microsoft Teams? Dann werden Sie Mitglied des Microsoft Teams Meetup Berlin.       

Microsoft Teams ist der zentrale Ort für die sichere und produktive Zusammenarbeit in Office 365. Hier sind die interessantesten Informationen aus KW 48.   Blogs Teams Adoption Hub - Enhanced guidance for user adoption projects   Microsoft Teams PowerShell Modul Microsoft Teams PowerShell Module 0.9.6   Neue Office Icons Redesigning the Office App Icons to Embrace a New World of Work Video: Meet the new icons for Office 365   Dokumentation Overview of dynamic membership for teams Skype for Business 2016 MSI client doesn’t display emoticons or emojis    Viel Spaß mit Microsoft Teams!   Sie interessieren sich für Microsoft Teams? Dann werden Sie Mitglied des Microsoft Teams Meetup Berlin.       

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

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