AppCmd

AppCmd introduction and examples

AppCmd.exe is a command-line utility to manage Windows Server IIS 7+ web servers. The AppCmd command is your one-stop-shop for administering Windows Server IIS web servers. In combination with WinRM it’s your Swiss Army knife for your daily routine. This post introduces appcmd and provides you with a lot of helpful appcmd examples.

Microsoft Internet Information Services logo

Conditionally start Application Pools on remote IIS web servers

Here is how to start stopped application pools on IIS with AppCmd or PowerShell in a loop.

In my routine, I occasionally have to start multiple website application pools when they are in a stopped state. On more than one web server. Being a lazy system administrator, I find it too much work to log on every server. Therefore I start those application pools in a loop. A condition for me to start application pools is that the IIS ApplicationPool.AutoStart Property is set to true. This is because I set autostart to false when I disable hacked websites, and those application pools may not be started until all problems are resolved of course.

Target multiple ASP.NET versions with AppCmd.exe

You can address both x86 and x64 versions of .NET with AppCmd. When administering an IIS web server you frequently have to use AppCmd.exe to make configuration changes. Whether it is for a specific web site or server wide. Some think AppCmd is very limited. Target multiple ASP.NET versions with AppCmd!

Microsoft Internet Information Services logo

Add websites and application pools to IIS with PowerShell, in a for loop

How to use PowerShell to create websites and application pools in IIS. How to use PowerShell to create websites and application pools in IIS… A client of the company I work for wanted to quickly add 60 sub-domains to his website. But, the sub-domains had to be created as self contained IIS websites, and running in their own application pools. Luckily, the client wanted 60 consecutive sub-domain names. This made our task a bit easier, because we could easily script this in PowerShell