Exchange administrators can really take advantage of the Exchange Management Shell for the administration of their messaging infrastructure on-premises or in the cloud. Here is a reference to the Exchange 2016 Powershell Cmdlets. In addition, here is a blog by Paul Cunningham on creating a Powershell function to speed up remoting into an Exchange Server.
In Exchange Server 2016, mail flow occurs through the transport pipeline. The transport pipeline is a collection of services, connections, components, and queues that work together to route all messages to the categorizer in the Transport service on an Exchange 2016 Mailbox server inside the organization.
Managed Availabilty integrates active monitoring and automated recovery for Exchange Server 2013/2016 workloads. Instead of just attempting to identify and alert on the root cause of an issues, Managed Availability tries to perform recovery aspects that adresses three key areas of the users experience, Availability, Latency, and Errors.
I am surprised I have not posted this before, but here it is… The Exchange Server 2016 Quick Start Guide from Paul Cunningham. And if you are planning on taking the 70-345 exam, I highly recommend both his book and videos for preparation resources.
Some older links on working with PowerShell and Exchange. I really liked this quick reference sheet from Exchangepedia.com that describes the most commonly used Exchange 2007 shell cmdlets and is still relevant today. And then over at MSExchange.org I always liked this 5 part series on PowerShell 101 for the Messaging Administrator. As always, the free sample PowerShell scripts for Exchange over at ExchangeServerPro.com is a must have link in any Messaging Administrators toolbox. Finally, we cannot forget TechNet which has a list of all the Exchange 2016 PowerShell cmdlets.
Passed the Exchange 2016 exam today with a very high score.What is humorous is that I thought it was tomorrow and had not really studied that much. I would say I took it cold, but I did just teach the Exchange 2013 class two weeks ago. One thing I was surprised about was that I thought I would only earn the Specialist certification for passing the 70-345 exam. However, since I already have the qualifying MCSA certifications, this exam re-earned my MCSE: Productivity for 2017. Not sure what I am going to do for next year. I might have to learn Sharepoint.
I find it slightly amusing this appeared on my Twitter feed today as I finish up studying for my Office 365 exam. It is a great introduction into the Identity Models for Office 365, but even more important you can get access to Office 365 for IT Pros. This online guide is continually updated to match developments within Office 365. Authored by a team of MVPs, this book gives you the real world, independent view of Office 365 that Microsoft’s marketing materials don’t provide.
There were so many great session at Microsoft Ignite that I could not attend them all. Fortunately, we can catch all the videos online. One session I did attend that I want to see again is the Exchange Online vs Exchange On-Premises debate.
Just finished renewing my Exchange 2013 certification and should be good for another three years. It was a pretty good idea to double check the requirements as they went from 15 down to 13 courses. I will probably take the Exchange 2016 exam in the next few weeks. But with all the SQL Saturday events coming up, I am not sure how much study time I am going to get.
If you plan to implement Exchange Server 2016 or Exchange Online, or if you want to make sure that your implementation was done right, these online training courses are for you! The Exchange Team is excited to announce the release of four new edX online training courses for Microsoft Exchange Server 2016:
When trouble strikes, the most valuable person in the room is the one who can confidently tackle the unknown. Being an effective troubleshooter is more important than being a walking encyclopedia of solutions to known issues. Rather than try to cover every possible problem and solution the Exchange Server Troubleshooting Companion takes a different approach. This eBook will provide you with the information you need to confidently solve any problem that you encounter.
Desired State Configuration is a PowerShell extension that ships with Windows Server 2012 R2 and Windows 8.1. Why is PowerShell Desired State Configuration (DSC) so cool. Well to borrow from this Technet Blog here are a few reasons.
- First of all declaring a DSC configuration is PowerShell based. So you can leverage all your PowerShell skills to not only define a configuration, but also for troubleshooting.
- DSC is designed to support “continuous deployments” which means that you can deploy your configuration over and over without breaking anything
- When a DSC configuration is being applied only those settings which do not match will be set, the rest will be skipped which can result in a faster deployment time
- You can separate the configuration data from the logic of your configuration so that you can reuse your configuration data for different resources, nodes, and configurations.
- DSC can be used on-premise, in a public or in a private Cloud environment. You just need either Windows Server 2012 R2 or Windows 8.1 and local administrator permissions to execute the DSC PowerShell scripts
- You can integrate DSC with any Microsoft or non-Microsoft solutions as long as you can execute a PowerShell script on the target system.
To learn more about DSC, you can visit the MVA Jumpstart with the Jeffrey Snover, Microsoft Distinguished Engineer and inventor of PowerShell, along with Windows PowerShell MVP Jason Helmick, You can also view this session that I attended at TechED 2014 on DSC presented by Don Jones.
Use the Microsoft Exchange Server User Monitor to gather real-time data to better understand current client usage patterns, and to plan for future work. Administrators can view details on server resource utilization as reported through server-side tracing. This tool works with Microsoft Exchange Server 2013 and 2016. The tool is provided as-is. At this time, there are no updates or patches planned for future release. No formal support is provided for the tool. Some minimal support may be provided by Microsoft but not all reported issues will be able to be addressed or resolved.
With the release of Exchange 2016, Microsoft is becoming more proactive about the way that they want to see customers deploy Exchange and have described their views in the Exchange 2016 Preferred Architecture or their “best practice recommendation for what we believe is the optimum deployment architecture for Exchange 2016”. Click here to get a better understanding of what the Exchange 2016 Preferred Architecture really means.
- Best Practice Series: Exchange Server 2013
- Core Solutions of Exchange Server 2013 Jump Start
- Data Loss Prevention in Office 365
- Encryption in Office 365
- Exchange Online Integration with Office 365
- Implementing Exchange Server 2013
- Managing Exchange Online Using Microsoft Online Console
- Managing Exchange Online Using PowerShell
- Managing Exchange Server 2013 Using EAC, PowerShell, & RBAC
- Migrating to Exchange Online
- Office 365 Security & Compliance: Exchange Online Protection
- Top Support Issues for Exchange Online
- Virtualizing & Managing Exchange with Microsoft Cloud Platform
- Exchange Server 2013: Public Folders & Mailbox Servers
- Manage Exchange Online Services
Exchange 2016 released and is available to download starting today! There is quite a bit of content out there already. I recommend checking these out.
- Exchange 2016 debuts to delight on-premises customers — Tony Redmond
- Exchange Server 2016: Forged in the cloud — Exchange Team Blog
- What’s New and Cool in Exchange 2016 – It’s out now! — Jason Sherry
- Exchange Server 2016 is available! Now what? — Dave Stork
- Exchange Server 2016 Architecture — Exchange Team Blog
- Exchange Server 2016 – Planning, Deployment & Migration — Paul Cunningham
- Exchange Server 2016 – Performance and Architecture – Greg Taylor
The Exchange Server 2016 Architecture builds upon the architecture introduced in Exchange Server 2013, with the continued focus goal of improving the architecture to serve the needs of deployments at all scales.The key change you will notice is the Exchange team removed the Client Access server (CAS) role and added the client access services to the Mailbox role. Even without the CAS role, the system maintains loose coupling in terms of functionality, versioning, user partitioning and geographical affinity. To find out more check out the Exchange Server Team blog.
Made it to my first Ignite Session of the week – Meet Exchange Server 2016 which builds upon the architecture introduced in Exchange Server 2013, with the continued focus goal of improving the architecture to serve the needs of deployments at all scales.Click here to find out more.
This topic provides information about the network ports that are used by Microsoft Exchange Server 2013 for communication with email clients, Internet mail servers, and other services that are external to your local Exchange organization. Before we get into that, understand the following ground rules: To read more click here.