Packt+ | Advance your knowledge in tech

You're reading from Windows Server 2012 Automation with PowerShell Cookbook If you work on a daily basis with Windows Server 2012, this book will make life easier by teaching you the skills to automate server tasks with PowerShell scripts, all delivered in recipe form for rapid implementation.

Product type Paperback

Published in Mar 2013

Publisher Packt

ISBN-13 9781849689465

Length 372 pages

Edition 1st Edition

Tools

Windows Server

Concepts

System Administration

Author (1):

EDRICK GOAD

View More author details

Table of Contents (19) Chapters

Windows Server 2012 Automation with PowerShell Cookbook

Credits

About the Author

About the Reviewers

www.PacktPub.com

Preface

1. Understanding PowerShell Scripting

2. Managing Windows Network Services with PowerShell FREE CHAPTER

3. Managing IIS with PowerShell

4. Managing Hyper-V with PowerShell

5. Managing Storage with PowerShell

6. Managing Network Shares with PowerShell

7. Managing Windows Updates with PowerShell

8. Managing Printers with PowerShell

9. Troubleshooting Servers with PowerShell

10. Managing Performance with PowerShell

11. Inventorying Servers with PowerShell

12. Server Backup

Index

Forwarding event logs to a central log server

In Windows Server, it is possible to configure the forwarding of event logs to remote servers. By forwarding events to another system, the centralized server can be configured with different retention options, reporting, and potentially performing actions based on the forwarded events.

This event forwarding uses a standard-based communication method using SOAP over HTTP.

There are two types of event log subscriptions: client-initiated and collector-initiated. For client-initiated subscriptions, we use a Group Policy and configure clients to push events to the collector. For collector-initiated, we configure the collector to pull events from each of the clients.

In this recipe, we will be creating a client-initiated subscription. We will use a Group Policy to distribute the configuration to our event sources. We will only be configuring one client, but the process can be extended to include dozens or even hundreds of clients.