Forum Widgets
Latest Discussions
Exchange Server 2016 / 2019 coexistence CU update
Hi, We are running Exchange Server 2016 CU19 and Exchange Server 2019 CU14. We want to install the latest CU for Exchange Server 2016. Can we do this with Exchange Server 2019 CU14 already installed? Any pitfalls? I am thinking about the AD Schema perhaps. Any insights welcome! Greetings Nfs!
Usage data for Personal Bookings/Bookings with me
Is there a way (powershell cmdlet or graph call) to get a count of how many users in a tenant have created/enabled Personal Bookings? I'm not talking about shared Bookings calendars, but people who have turned on the "Bookings with me" feature. The reason I'm looking for this data is that right now we have some departments who are using other similar services, in some cases they are costing the org quite a bit of money. If we can demonstrate that a significant percentage of users are making use of this feature that we're already paying for, we have leverage to recoup some operating costs.
Enable IPv6
Hello, Recently the Exchange Team has enabled IPv6 for the accepted domains. When I check the status with 'Get-IPv6StatusForAcceptedDomain' for our domains, I see that IPv6 is enabled. But I see a difference between the domains where IPv6 is enabled by Micorosft Support (before IPv6 was global available). In the 'AdditionalInfo'-field there is no info (as expected). For domains where IPv6 is enabled through global availability, the Additional Info says: Enabled status does not guarantee that IPv6 is enabled for your domain. For more information, please use Get-Help Get-IPv6StatusForAcceptedDomain. What does this means? And how can I check if IPv6 is really enabled? Disable and enable IPv6 again makes no difference. The Get-Help command doesn't show any extra information.
Exchange Online Mailbox Retention
To utilize EXO for SEC Regulation and Purview eDiscovery. I think we need to have some kind of 7 years retention. What is the best way to accomplish this? MRM, Compliance Policy, Preservation lock, some kind hold policy, litigation hold ? So deleted items are not deleted and Primary mailbox will expand to Archive up to 1.5 TB. EX: under Data lifecycle management, create a 7 years retention policy for EXO, and other services. Would this be sufficient? For mailbox reaching 1.5TB with retention in place, how would I move mailbox data to secondary mailbox and allow users to access both. If a leaver mailbox is delete after 30 days, will the retention keep the data for purview searches?Exchange Server 2019 HA & DR - Design
Hello Team, I'm asked to setup a HA & DR of Exchange Server 2019 (In-House) with only Internal Clients connecting to it. There will be no Internet or external access. There are 2 Sites, A & B connected by Dark Fibre of 10G and though users are around 3000 but their usage is very minimum as it is only for internal purposes. They are keen to have HA & DR and in current setup I had setup HA with 3 servers. I was reading about cross-site DAG and need little assistance in setting up the same. I need to design HA & DR so that if there is a site failure then automatically the DR should continue the work. I thought Active-Active would be best because if anyone of the site fails, say Site A fails, the 40-50% of the users who would have their mailboxes on them would move to Site B. 1. Is it best to setup Active-Active or Active-Passive, benefits, safety, Administrator's Tasks in failover scenario? 2. Is it better to keep even nodes on each side with Witness Server (for Site A - Witness Server will be on B) & Alternate Witness Server ? If anyone has a sample design document with key configuration to keep in mind, if you can share it, please let me know,
Public Folder Migration Failed
We have a problem migrating public folders from an Exchange 2019 OnPremise to an Exchange Online. We followed the Microsoft guide: Batch migrate Exchange Server public folders to Microsoft 365 or Office 365 | Microsoft Learn We get to step 7. When completing the PublicFolderMigration job, the status changes to “Completing” and then to “Failed”. The error message in the EXO Shell is: Status: Failed Message: Error calling “net.tcp://be1p281mb2001.deup281.prod.outlook.com:9821/Microsoft.Exchange.MailboxReplicationService BE1P281MB2001.DEUP281.PROD.OUTLOOK.COM (15.20.8207.17 ServerCaps:FFFFFFFF, ProxyCaps:1FFFFFFFFFFFFFFFC7DD2DFDBF5FFFFFCB07EFFF, MailboxCaps:, legacyCaps:FFFFFFFF)”. Error details: The communication object System.ServiceModel.Channels.ServiceChannel cannot be used for communication because it is in a Faulted state. --> The communication object System.ServiceModel.Channels.ServiceChannel cannot be used for communication because it is in a Faulted state. Does anyone have an idea what this error means? We have already removed and restarted the entire migration, but the same error occurs again.
PopDeepTestProbe Issue
I've recently built two Exchange 2019 servers in a DAG to replace our 2016 servers which are in their own unique DAG. They are not yet active but are ready with the exception of an Exchange HealthSet failing on one of the servers. Running Get-ServerHealth -Identity 'Server' -HealthSet 'POP.Protocol' shows the PopDeepTestMonitor is Unhealthy. Running Invoke-MonitoringProbe -Identity:"POP.Protocol\PopDeepTestProbe" -Server:Server | fl returns "WARNING: No mailboxes were found to use in the DeepTest probe." I've tried rebooting the server multiple times along with recreating the Exchange monitoring mailboxes multiple times. Nothing has solved this issue. Does anyone have ideas?
'$skiptoken' limit error for Microsoft Exchange online Reporting web service API
I was working on integratingMessageTrace report APIas a part of my SIEM integration: https://reports.office365.com/ecp/reportingwebservice/reporting.svc/MessageTrace[?ODATA options] I have noticed that, whenever my $skiptoken reaches the limit 999999 , it throws the following error with 500 status code: { "odata.error": { "code": "UnknownError", "message": { "lang": "", "value": "An error has occurred on the server." } } } It was working fine for the 999998 value, but wasn't for the $skiptoken value 999999. Is there any limitations on $skiptoken value from the API itself? Also, need information, if $skiptoken value 999999 exists, for example, "odata.nextLink": "../../reportingwebservice/reporting.svc/MessageTrace?$filter=StartDate%20eq%20DateTime'2024-12-02T00%3A00%3A00Z'%20and%20EndDate%20eq%20DateTime'2024-12-02T23%3A59%3A59Z'&$skiptoken=999999" then how can we request the data from next set of events? Can someone let me know, is there any max limit from Microsoft API side or for the $skiptoken?
