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
Learn PowerShell Core 6.0

You're reading from  Learn PowerShell Core 6.0

Product type Book
Published in Jul 2018
Publisher Packt
ISBN-13 9781788838986
Pages 552 pages
Edition 1st Edition
Languages
Authors (2):
David das Neves David das Neves
Profile icon David das Neves
Jan-Hendrik Peters Jan-Hendrik Peters
Profile icon Jan-Hendrik Peters
View More author details
Toc

Table of Contents (26) Chapters close

Title Page
Dedication
Packt Upsell
Contributors
Preface
1. Current PowerShell Versions 2. PowerShell ISE Versus VSCode 3. Basic Coding Techniques 4. Advanced Coding Techniques 5. Writing Reusable Code 6. Working with Data 7. Understanding PowerShell Security 8. Just Enough Administration 9. DevOps with PowerShell 10. Creating Your Own PowerShell Repository 11. VSCode and PowerShell Release Pipelines 12. PowerShell Desired State Configuration 13. Working with Windows 14. Working with Azure 15. Connecting to Microsoft Online Services 16. Working with SCCM and SQL Server 17. PowerShell Deep Dives 1. PowerShell ISE Hotkeys 2. Assessments 3. Other Books You May Enjoy Index

EventLog


EventLog stores log information for the whole system via Event Tracing for Windows (ETW). For troubleshooting purposes, it is always important to take a dedicated look at the logs to find further information. PowerShell makes this very easy for us with two cmdlets: Get-EventLog and Get-WinEvent. Get-WinEvent is the newer cmdlet, which also allows you to retrieve events from the applications and services logs and uses server-side filtering. Get-EventLog returns objects of the type System.Diagnostics.EventLogEntry, and Get-WinEvent returns objects of the type System.Diagnostics.Eventing.Reader.EventLogRecord. There are significant differences in the properties, as the Source becomes ProviderName, the EntryType becomes LevelDisplayName, and the Category becomes TaskDisplayName. In addition, the replacement strings are only visible if the events are saved as XML. The main purpose of having the new Get-WinEvent cmdlet, though, is for performance reasons, which has been proven by many...

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}