18756 Stone Oak Park Way, Suite200, San Antonio TX 78258 USA
100 Queen St W, Brampton, ON L6X 1A4, Canada
country flagUnited States
share button

55039: Windows PowerShell Scripting And Toolmaking Training


What 55039: Windows PowerShell Scripting And Toolmaking training is all about?

The five-day course is designed for IT professionals interested in updating their industry-relevant skills in PowerShell as well as administrative automation. This course considers the individual taking the course possesses fundamental knowledge of PowerShell as an interactive shell and teaches students how to create appropriate patterns and practices to build reusable, tightly scoped automation units.

5 SATVs applicable


Schedule
  • Delivery Format:
Date: Nov 16, 2020 | 9:00 am - 5:00 pm EST
Location: Online
$2875 USD
What are the course objectives for 55039: Windows PowerShell Scripting And Toolmaking training?
  • Describing correct patterns to build modularized tools in PowerShell
  • Building highly modular functions complying with native patterns in PowerShell.
  • Building user interfaces exposing controller scripts and automate business processes
  • Managing data in different formats
  • Writing tools automating tests
  • Debugging tools
Who should attend 55039: Windows PowerShell Scripting And Toolmaking training?

The course is suitable for admins working in Microsoft environments and now wants to learn the skills of building reusable automation units, business process automation and enabling colleagues to complete administration related tasks.

What are the prerequisites for 55039: Windows PowerShell Scripting And Toolmaking training?

Before going to 55039: Windows PowerShell Scripting And Toolmaking course, understudies must have:

  • Involvement in overseeing Windows server and customer PCs
  • Involvement in running intuitive Windows PowerShell summons from the charge provoke
  • Course 10961 is unequivocally prescribed as a pre-imperative to this course
What is the course outline for 55039: Windows PowerShell Scripting And Toolmaking training?
  • 1. Tool Design
  • a). Tools do one thing
  • b). Tools are flexible
  • c). Tools look native
  • d). Lab: Designing a Tool
  • 2. Start with a Command
  • a). Why start with a command?
  • b). Discovery and experimentation
  • c). Lab: Start with a command
  • 3. Build a Basic Function and Module
  • a). Start with a basic function
  • b). Create a script module
  • c). Check prerequisites
  • d). Run the new command
  • e). Lab: Build a basic function and module
  • 4. Adding CmdletBinding and Parameterizing
  • a). About CmdletBinding and common parameters
  • b). Accepting pipeline input
  • c). Mandatory-ness
  • d). Parameter validation
  • e). Parmeter aliases
  • f). Lab: Adding CmdletBinding and Parameterizing
  • 5. Emitting Objects as Output
  • a). Assembling information
  • b). Constructing and emitting output
  • c). Quick tests
  • d). Lab: Emitting objects as output
  • 6. An Interlude: Changing Your Approach
  • a). Examining a script
  • b). Critiquing a script
  • c). Revising the script
  • d). Lab: No lab
  • 7. Using Verbose, Warning, and Informational Output
  • a). Knowing the six channels
  • b). Adding verbose and warning output
  • c). Doing more with verbose output
  • d). Informational output
  • e). Lab: Using Verbose, Warning, and Informational Output
  • 8. Comment-Based Help
  • a). Where to put your help
  • b). Getting started
  • c). Going further with comment-based help
  • d). Broken help
  • e). Lab: Comment-based help
  • 9. Handling Errors
  • a). Understanding errors and exceptions
  • b). Bad handling
  • c). Two reasons for exception handling
  • d). Handling exceptions in our tool
  • e). Capturing the actual exception
  • f). Handling exceptions for non-commands
  • g). Going further with exception handling
  • h). Deprecated exception handling
  • i). Lab: Handling errors
  • 10. Basic Debugging
  • a). Two kinds of bugs
  • b). The ultimate goal of debugging
  • c). Developing assumptions
  • d). Write-Debug
  • e). Set-PSBreakpoint
  • f). The PowerShell ISE
  • g). Lab: Basic debugging
  • 11. Going Deeper with Parameters
  • a). Parameter positions
  • b). Validation
  • c). Multiple parameter sets
  • d). Value from remaining arguments
  • e). Help messages
  • f). Aliases
  • g). More CmdletBinding
  • h). Lab: No Lab
  • 12. Writing Full Help
  • a). External help
  • b). Using PlatyPs
  • c). Supporting online help
  • d). “About” topics
  • e). Making your help updatable
  • f). Lab: Writing full help
  • 13. Unit Testing Your Code
  • a). Sketching out the test
  • b). Making something to test
  • c). Expanding the test
  • d). Going further with Pester
  • e). Lab: Unit testing your code
  • 14. Extending Output Types
  • a). Understanding types
  • b). The Extensible Type System
  • c). Extending an object
  • d). Using Update-TypeData
  • e). Lab: No Lab
  • 15. Analyzing Your Script
  • a). Performing a basic analysis
  • b). Analyzing the analysis
  • c). Lab: Analyzing your script
  • 16. Publishing Your Tools
  • a). Begin with a manifest
  • b). Publishing to PowerShell Gallery
  • c). Publishing to private repositories
  • d). Lab: Publishing your tools
  • 17. Basic Controllers: Automation Scripts and Menus
  • a). Building a menu
  • b). Using UIChoice
  • c). Writing a process controller
  • d). Lab: Basic controllers
  • 18. Proxy Functions
  • a). A proxy example
  • b). Creating the proxy base
  • c). Modifying the proxy
  • d). Adding or removing parameters
  • e). Lab: Proxy functions
  • 19. Working with XML Data
  • a). Simple: CliXML
  • b). Importing native XML
  • c). ConvertTo-XML
  • d). Creating native XML from scratch
  • e). Lab: Working with XML
  • 20. Working with JSON Data
  • a). Converting to JSON
  • b). Converting from JSON
  • c). Lab: Working with JSON data
  • 21. Working with SQL Server Data
  • a). SQL Server terminology and facts
  • b). Connecting to the server and database
  • c). Writing a query
  • d). Running a query
  • e). Invoke-SqlCmd
  • f). Thinking about tool design patterns
  • g). Lab: No Lab
  • 22. Final Exam
  • a). Lab problem
  • b). Break down the problem
  • c). Do the design
  • d). Test the commands
  • e). Code the tool
  • f). Lab 1: Final Exam
  • g). Lab 2: Final Exam
5 Days | $ 2875
Enroll Now
4
  236 Ratings

1254 Learners

Get In Touch

Are you being sponsored by your employer to take this class?
* I authorize Microtek Learning to contact me via Phone/Email