Tag: Exchange

This Connect-ExchangeServer function runs the PowerShell code to log into an Exchange server on premises using remote PowerShell. Using the -Computer parameter (required), tells the function which Exchange server to connect to. Using the -Prefix parameter (optional), allows a modification to the noun of the imported cmdlets, so that you can have multiple connections in

Here are some handy short links that help Exchange Server engineers keep up with what's happening within the Exchange world. As always, it's best to have some kind of RSS feed notification, using tools such as: Microsoft Flow or IFTTT.com. The Exchange Team blog, you Had Me at EHLO: aka.ms/ehlo Exchange Server build numbers and

The Get-DotNETVersion function presents the current .NET version on a machine. This is part of the MO_Module PowerShell code that helps administrators in their daily tasks. From an Exchange Server perspective, .NET support is very sensitive to which version of Exchange and which .NET is allowed to be used. This value also changes based on

I’d like to introduce you to my MO_Module. It’s a PowerShell module, combining several daily administrative tasks into simple Verb-Noun Functions for engineers to perform their jobs easier. I was developing/maintaining several different PS modules, which became more work, so I thought I’d just combine everything into one single place. Since my primary technologies are

https://docs.microsoft.com/en-us/windows-server/failover-clustering/deploy-cloud-witness No, neither version supports the cloud witness option. However, Exchange Server does fully support an Exchange File Share Witness server in Azure. If you choose this option, you’ll need a writable Domain Controller and a Windows Server to host up the File Share Witness directory. The reason for a Windows Server for the FSW,

I was recently called into help on a ‘Crit Sit’ (Critical Situation) that a customer had with their Exchange 2010 environment. During the previous night, a few of the Databases that have a total of 3 copies spread across a DAG flipped to different servers. This ultimately was caused by Exchange asking AD a question

The Exchange online engineering team would like your feedback on the user interface within O365: https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR49eFzv9DqVGqZMZy6mK_45UQVUzS1JGSU9YSU9OMTQxT1VNT0U2Wk5JSy4u

Yes. You can leverage Azure for a test period. See this page on how to setup the environment, including a DC and a single Exchange Server. https://technet.microsoft.com/en-us/library/mt733070(v=exchg.160).aspx

With the recent security updates released for all versions of Exchange: Exchange Server 2019 Cumulative Update 1 (KB4471391), VLSC Download Exchange Server 2016 Cumulative Update 12 (KB4471392), Download, UM Lang Packs Exchange Server 2013 Cumulative Update 22 (KB4345836), Download, UM Lang Packs Exchange Server 2010 Service Pack 3 Update Rollup 26 (KB4487052), Download, also available on Microsoft Update The question comes

If you haven’t looked lately, and I know most of us don’t, but of possible interest to many is the Exchange Sever 2019 version only has a 7-year lifecycle. The stated end date of extended support is the same as the 2016 version. Product released Lifecycle start date Mainstream support end date Extended support end