BlackBelt – Troubleshooting the Windows OS with Sami Laiho
Kursavgift: kr 25 000 | Varighet: 4 dager
This training is meant for all administrators who want to deepen their knowledge and troubleshooting skills in Windows. It is also suitable for people who think they know everything about the Windows OS… It’s a deep dive course and surely in no way suitable for only the beginners but for seasoned administrators as well (I guarantee you won’t be disappointed!). If someone want’s to become a true BlackBelt troubleshooter you should first take this course which is more Tools-oriented and then continue to take the BlackBelt – Advanced Troubleshooting the Windows OS -course which is more Content-oriented.
About Sami Laiho - author and instructor of this training
Sami Laiho is one of the world’s leading experts in the Windows OS and an exceptional teacher/entertainer. Sami’s sessions have been evaluated as best session in multiple TechEd’s over the last years. Sami has been awarded Microsoft MVP (Most Valueable Professional) in Windows OS since 2011.
Sami has been a Windows admin for more than 15 years and a certified trainer for more than ten. Sami is a well known public speaker on Conferences in Europe, Australia etc.
Currently Sami works for his own company as a Senior Technical Fellow and specializes in Troubleshooting and security training and consulting. Sami’s company also consults and produces products to help companies to get rid of end user admin rights. Sami is also known globally as the developer of Wioski – a free replacement for Microsoft Steady State.
Read more about Sami Laiho on these pages:
- Basic experience with Windows Administration
- Basic understanding of Active Directory
- Basic understanding of networking infrastructure
This four day course trains you how to become a better troubleshooter of any environment that runs on Windows. The best way to become a great troubleshooter is to learn from the ground up. The biggest flaws people do while troubleshooting are that they believe that Administrator account should be used for troubleshooting or that in Windows processes can execute code – Both are incorrect. So usually people troubleshoot the wrong objects with too few permissions.. How could that work? It can’t and there’s a good reason for you to join this training.
Labmanual and slides.
Detailed content description (Agenda):
Tools and procedures for troubleshooting Windows
- What are we against?
- How to isolate the error
- How to document the error
- Most important tools for troubleshooting
- Appropriate permissions
- Windows modes
- Processes and threads
- Services and programs
Troubleshooting of the SLOW
- Registry structure
- How to manage the registry
Troubleshooting security related issues
- Slow startup/logon
- Slow operations
- Memory/Disk/CPU bottlenecks
Troubleshooting network issues
- Security internals of Windows
- How to troubleshoot issues related to permissions
- How to troubleshoot issues related to domains
Troubleshooting device drivers
- Best practises to troubleshooting network issues
- Monitoring network activity
Unbootable machine troubleshooting
- How Windows uses its Driver Store
- How to troubleshoot device drivers
Basics of debugging and debuggers
- Safe modes and other advanced startup modes
- Windows PE/RE internals
- Tools for fixing an unbootable OS
- How to debug a machine
- When to debug a machine with an actual debugger
- How BSOD works and how to make one
- How to analyze memory dumps