Episode 289 - PowerScripting Podcast - Mike Hendrickson and Jason Walker from Microsoft on Configuring Exchange With DSC

Listen:

In This Episode

Tonight on the PowerScripting Podcast, we talk to Mike Hendrickson and Jason Walker from Microsoft about their DSC resources for Exchange

News

 

Interview

 

Chatroom Highlights

<halr9000> http://blogs.technet.com/b/mhendric/archive/2014/10/17/managing-exchange-2013-with-dsc-part-1-introducing-xexchange.aspx

<halr9000> https://msconfiggallery.cloudapp.net/packages/xExchange/

<halr9000> http://blogs.technet.com/b/mhendric/archive/2014/10/17/managing-exchange-2013-with-dsc-part-1-introducing-xexchange.aspx

<Stuwee> DSC Resource Kit Wave 8 : https://gallery.technet.microsoft.com/DSC-Resource-Kit-All-c449312d

<halr9000> https://gist.github.com/halr9000/20ab184a91277f3a2438

<MikeFRobbins> https://github.com/pester/Pester

<MikeFRobbins> Using Pester for Test Driven Development in PowerShell http://mikefrobbins.com/2014/10/09/using-pester-for-test-driven-development-in-powershell/

<halr9000> https://gallery.technet.microsoft.com/DSC-Resource-Kit-All-c449312d

<halr9000> https://msconfiggallery.cloudapp.net/packages/xExchange/

<halr9000> https://gallery.technet.microsoft.com/xExchange-PowerShell-1dd18388/view/Discussions#content

<halr9000> http://blogs.technet.com/b/mhendric/archive/2014/10/17/managing-exchange-2013-with-dsc-part-1-introducing-xexchange.aspx

<MikeFRobbins> My New Book: Windows PowerShell TFM 4th Edition is now Available! http://mikefrobbins.com/2014/11/13/my-new-book-windows-powershell-tfm-4th-edition-is-now-available/

<MikeFRobbins> ## Do you use your resources for only the initial config or to also correct configuration problem with issues occur?

<sepeck> ## but this is an example of how powershell allows for outside 'unforseen' contributions to occur within or outside microsoft

 

Question

  • Mike: Omniscience
  • Jason: Jedi Knight
About the Author

Jonathan Walz

Profile photo of Jonathan Walz

Since March 2007, Jonathan Walz has been the co-host and technical brains for the PowerScripting Podcast. Conceived as a radio show for the PowerShell community, the podcast is the longest-lived PowerShell show in existence, and has featured dozens of weekly guests.

14 Comments

  1. PowerShell on Linux exists to help Windows admins to help them transition away from Windows Server. But In a decade, when > 75% of workloads running on Azure are Linux, the tools used to manage those workloads will be designed for and meet the needs of the Linux administrator mindset. Linux administrators have a great set of mature tools and it isn't entirely clear why they'd want to transition to using PowerShell. Linux has won. The growth of Linux on Azure shows that. It's time for Azure to be a Linux First environment - and PowerShell on Linux doesn't really fit because it's primarily trying to graft a new and unproven Microsoft way of doing things onto successful practices and culture. Sure they can do it - but they'd be better off retraining everyone to "Think Linux".

    If Microsoft has (apparently) given up on Windows Server and understand that only a few legacy holdouts will want to run it in Azure in 10 years time (with the majority of workloads being Linux), they are wasting resources trying to reinvent how Linux administrators do things as a way of placating legacy Windows administrators. Legacy Windows administrators should bite the bullet and go "all-in" and adopt existing successful open source administration paradigms. The clock is ticking on their relevance and if they spend precious time investing in a nascent administration technology instead of fully transitioning to an open source mindset, they'll be less employable in future.

    PowerShell on Linux would be a neat idea if Windows Server had a future. It'll remain around in the same way that mainframes are still with us - but Microsoft has no interest in making a compelling case for organizations to choose their product over the free alternative. The future of Windows Server is the current reality of Windows Phone.

    • Thank you SO much for contributing your perspective! I do think - and I'm not a Microsoft fanboy per se - that you're misinformed, or at least under-informed. Time will tell, of course, but I suspect you've brought some personal bias to your viewpoint.

    • Interesting perspective. But I think you missed the point why Microsoft is actually open sourcing PowerShell. If you followed the talks that Jeffrey Snover did the last few years, it became clear that they want to be able to support heterogeneous environments. And for what I've seen now from Microsoft, and especially the PowerShell team, is that they don't have a hidden agenda. Microsoft is not the Microsoft anymore from let's say, 5-10 years ago.

      I agree with you, that there's a lot of Linux on Azure. But many, many companies I come are mainly Windows based infrastructures. Also guys that I know that work for other companies almost only see Windows based infra's.

      Yes, Linux has it's place in this world, but according for Microsoft there's no battle between Windows or Linux. They're citizens in IT which Microsoft wants to support best. And PowerShell is not a tool per se, it's meant to be a management framework. A framework that operates with built-in tools or in the case of Windows, the .NET framework.

      Windows Server has a big future, just look at the developments Microsoft is doing on Nano server.

  2. If I have to copy files from installation folder to destination and I have to do exception handling because everything is automated, then how to do that? What all errors may arise and how to recognize and handle them? Please help.

  3. powershell ought to get the credit it deserves for enabling a developer to rapidly create rich output handling complex decisions based upon datasets gathered from various means and implementing a nearly infinite number of actions based on these. Simply put, it can be, and it is, much more than an admin tool, in the right hands.

  4. To start this is a thing of beauty in it's simplicity.
    Does anyone have experience with how much memory the results occupy and doing Get-job | Receive-Job at the end? If I run say a 1000 or 10,000 will this cause memory problems? I am thinking doing Get-Job -State Complete | Receive-Job & then |remove-job inside the loop (and logging it) would reduce the chance of running the host out of memory, or am I just over complicating it?

Leave a Reply

Your email address will not be published. Required fields are marked *