Hello everyone! I have had a big hiatus from posting to my blog, but the impending release of Lync Server 2013 and Exchange Server 2013 has brought me back to the table! Over the last year or so, I’ve begun delving into the world of PowerShell. This fall, with the release of PowerShell v3, the Windows scripting world gets more exciting. Integrated Scripting Environment improvements, more easily readable command syntax, and the Show-Command cmdlet are just a few of the many things this update brings to the PowerShell platform. Bulk automation is the name these days, and so I’ve decided to focus my series of blog posts this time ‘round on leveraging PowerShell to smooth the deployment and operations of a Microsoft Unified Communications infrastructure.
We’re going to take it from the top, with a PowerShell one-liner to install the operating system prerequisites on a Lync Server 2013 front end server. This can be executed interactively at a PowerShell console or via a script. In order to execute via a script, simply copy and paste the text into the PowerShell ISE and then save the resulting file with a .ps1 extension.
Import-Module ServerManager; Add-WindowsFeature Web-Server, Web-Static-Content, Web-Default-Doc, Web-Scripting-Tools, Web-Windows-Auth, Web-Asp-Net, Web-Log-Libraries, Web-Http-Tracing, Web-Stat-Compression, Web-Default-Doc, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Errors, Web-Http-Logging, Web-Net-Ext, Web-Client-Auth, Web-Filtering, Web-Mgmt-Console, Web-Asp-Net, Web-Dyn-Compression, Web-Mgmt-Console