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.
If you are in the Indianapolis area, we will have Session from 9am – 12pm and a Session from 1pm – 4pm. Sign up today! (317) 575-7600
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.
Microsoft just announced the release of Server 2016 and System Center 2016 in September during their Ignite Event (Sep 26-30). However, you can get Tech Preview v5 now… System Center 2016 TP5 and Server 2016 TP5 and start playing around. To find out more about the Release Date, check out Windows IT Pro.
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.
People frequently ask, “Where can I learn more about PowerShell?” Today’s post will highlight popular video training options available directly from Microsoft. Click here for more information.
If you have DevOps FoMO (fear of missing out), the DevOps Fundamentals series is for you. It explains key concepts and practices, and maps them to technical demos with Microsoft technologies. Regardless of your role at work, you can learn some practices to help your team!
Here is a great blog post by Thomas Maurer on replacing your basic networking commands with PowerShell. He mentions that after working with Microsoft Azure, Nano Server and Containers, Powershell together with networking becomes more and more important. He created this little cheat sheet so it becomes easier for people to get started.
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,