Re-locate ost-files
Hi everybody, we have a customer with a default ost-file location to the Homedrive of the user because they used Citrix in the past and now using AVD. They now want to migrate to OneDrive and disable the homedrive. In that case we want to move the ost-files back to the default location within the profile because now the profile is re-located by fslogix. As far as I know a re-location of existing ost-files is not possible and the only way to change this is to create a new Outlook profile. Cannot change the location of .ost file - Outlook | Microsoft Learn Does anyone have a better idea to solve that issue without less effort? Thanks in advance Guido
Backing up Microsoft Exchange 2016 DAG with Veeam to ensure exchange log truncation.
Hello Everyone, Our currently DAG setup is consist of two 2016 exchange member servers along with a witness server. Node 1 - DB1 (Active), DB2 (Passive), DB3 (Active), DB4 (Passive) Node 2 - DB1 (Passive) DB2 (Active), DB3 (Passive), DB4 (Active) Now according to our backup vendor (Veeam) when they are almost finished with backing up the server, Veeam send a signal to Microsoft VSS to basically truncated the exchange logs which then will truncate both the active and passive database. In this case for our example, when node 1 is completely backup Veeam will then send a signal to Microsoft VSS provider to then truncate logs of both passive and active database. (Please correct me if I miss understood how exchange logs are truncated.) It will then replicated the changes among the other DAG members. Therefore, my question and concern is from what Veeam indicated it is by Microsoft design that VSS provider can truncate passive database and then replicated to the primary source, is that truly the case?Query for PR_HIERARCHY_SERVER property returns MAPI_E_INVALID_PARAMETER.
Hi, Our application(IBM Content Collector - ICC) is trying to query PR_HIERARCHY_SERVER property. We use the MSMAPI32.dll, acting as client to Exchange servers. However MAPI call HrGetProp for the property PR_HIERARCHY_SERVER = 0x6633001F fails with MAPI Error 'MAPI_E_INVALID_PARAMETER'. We noticed the issue is not seen when we use Outlook 2010 as client. Below are all the scenariosand results: 1) ICC with Exchange 2019 : Outlook 2019 : Public folder archiving fails 2) ICC with Exchange Online : Outlook 2019 : Public folder archiving fails 3) ICC with Exchange 2016 : Outlook 2016 : Public folder archiving fails 4) ICC with Exchange 2016 : Outlook 2010 : Public folder archiving works! Do we have to make any changes to code when using newer Outlook client versions? Kindly provide suggestions as this is a blocker for one of our Customers(env: ICC with Exchange Online : Outlook 365). Regards, Salil Verlekar(saverlek@in.ibm.com) Mob: 9823961730exchange 2019 outlook 2016 search problem
The problem is native from the beginning and is still present. We are in trouble with the search from outlook 2016 in online mode. We can find some results with a specific search query: (R: I: 2020 360-R: 20117- 1548GSC -A******** - Demande de pièce de rechange) * i censored some privacy info but searching for '2020-360' match all elements except for 2 specific items. Refining our search query, including other texts that is part of the object of the mail, can find also the target mails. with the query : 'Demande' we find all the items requested. We have verified the update level of the clients 2016, Office Professional Plus 2016 16.0.5095.1000 MSO 16.0.5095.1000 a 32bit we have a new fresh deployed Server Windows 2019 with exchange server 2019 CU 7 onboard. We tried all possibilities offered in this article: https://support.microsoft.com/it-it/office/risoluzione-dei-problemi-di-ricerca-in-outlook-2556b11f-f4d8-46be-b0a7-de33a3f4f066#bkmk_incompleteresults In OWA we can find all items without problems, than we assume that Server side was fine. but We notice also that on Exchange console, with the command: Get-MailboxStatistics m********@a********.it | fl *funn*,*MCDB* we obtain some strange behavoirs: BigFunnelIsEnabled : True BigFunnelMaintainRefiners : True BigFunnelMessageCount : 16668 BigFunnelIndexedCount : 16002 BigFunnelPartiallyIndexedCount : 666 BigFunnelNotIndexedCount : 0 BigFunnelCorruptedCount : 0 BigFunnelStaleCount : 0 BigFunnelShouldNotBeIndexedCount : 1030
