Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Windows Server 2019 Automation with PowerShell Cookbook - Third Edition

You're reading from  Windows Server 2019 Automation with PowerShell Cookbook - Third Edition

Product type Book
Published in Feb 2019
Publisher Packt
ISBN-13 9781789808537
Pages 542 pages
Edition 3rd Edition
Languages
Author (1):
Thomas Lee Thomas Lee
Profile icon Thomas Lee
Toc

Table of Contents (19) Chapters close

Windows Server 2019 Automation with PowerShell Cookbook Third Edition
Foreword
Contributors
Preface
1. Establishing a PowerShell Administrative Environment 2. Managing Windows Networking 3. Managing Windows Active Directory 4. Managing Windows Storage 5. Managing Shared Data 6. Managing Windows Update 7. Managing Printing 8. Introducing Containers 9. Managing Windows Internet Information Server 10. Managing Desired State Configuration 11. Managing Hyper-V 12. Managing Azure 13. Managing Performance and Usage 14. Troubleshooting Windows Server Index

Managing IIS applications and application pools


In the earliest versions of IIS, all of the web pages and sites on a given system ran in a single Windows process. This meant that one application, if not written well, could cause issues with other applications. An application with a memory or handle leak would eventually require a restart of the single process (or even a reboot of the server).

In later versions of IIS, Microsoft added the concept of web applications and application pools to IIS. With IIS, a web application is a set of one or more URLs (web pages). For example, the pages for the WWW2.Reskit.Org example that you created in the Configuring IIS bindings recipe are stored in C:\inetpub\www2 on SRV1. You can configure IIS to run different web applications inside of independent worker processes. This means that your default website and the WWW2 site could run inside of totally different worker processes, and issues with one are not going to affect the other.

An application pool is...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}