Tag: Exchange

Some of you may ask, what is OMA? Back in the day, Exchange 2003, mobile devices were starting to make their way into the corporate world. Outlook Mobile Access (OMA) was introduced to help provide a small, thin foot print to mobile devices. You have to also remember that back in 2003, cellular networks were not what they are

Yes, it would be supported. Any supported virtualization product on this list is supported: https://www.windowsservercatalog.com/svvp.aspx From an Exchange perspective, it wouldn’t care what it rides on. You can mix and match all day long, as long as the Exchange versions are consistent. In fact, the Exchange role requirements calculator doesn’t even care about virtualization, the

Just a reminder, Exchange Server versions have some important dates coming up: Exchange Server 2010 support will end on January 14, 2020 October 14, 2020 is the new date: https://docs.microsoft.com/en-us/office365/enterprise/exchange-2010-end-of-support Exchange Server 2013 has now entered extended support and that will end April 11, 2023 Exchange Server 2016 extended support ends October 14, 2025 Exchange

Yes.  However, the PG chose not to extend Jetstress functionality to cover MCDB (on Flash/SSD storage), therefore, Jetstress will only validate HDD performance for Exchange Server 2019. What is JetStress? The JetStress tool (download) is a Microsoft supported tool that validates database hard drive performance before you install the Exchange Server application on a Windows

In the part 1 of this function, we covered an option to set all Exchange servers to use every AD site in an organization, minus any 'deployment' ones. But what if you have a very large organization, with multiple data centers hosting Exchange servers, various regions to support, and you want to target specific locations

In this blog post a few years ago: https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Exchange-Active-Directory-Deployment-Site/ba-p/604329 was a discussion around Exchange AutoDiscoverSiteScope information. The good news is, it worked perfectly in a lab, however, rarely is any production environment like a lab. Thus, there was some missing information. We're updating the article to include solutions to fix the problem. This post is

Well, the one constant in IT is change. The MO_Module was too confusing for people to know what it was for, so I went back and updated the Exchange_AddIn PowerShell Module. All of the updated functions over the past several months are being cut over, I've updated all of the helpURI values, and added in

Had this question the other day, what are current Exchange on premises limits for messages? And can end users send 10GB file attachments? This site talks about limits, but it also depends on what is available vs. what you can support. By running some PowerShell code, the answers can be provided: Get-ReceiveConnector  | Set-ReceiveConnector -MaxMessageSize

Many times in an Exchange server, the IIS (Internet Information Services) is not the issue, but only the sub-set Autodiscover Application Pool. Therefore, once again, instead of just a one-off cmdlet against a single server, we have this function, to blast out to all Exchange servers, to restart their Autodiscover (sometimes referred to as AutoD),

Added this to the MO_Module to remote in and restart just the IIS service on a single computer or a list of computers. Easy enough to do without a function, but I added some logic and Write-Verbose information to help the person running the command to see the content easier and quick. This will restart