# Scripting Examples - Simple inline script. PowerShell scripts in DeployR Task Sequences can be as simple or as complex as you like. A simple PowerShell Step can look like this: ``` Get-ChildItem tsenv: ``` That simple script, you can paste right into a step, and it will return a list of all of the Task Sequence Variables, which will then show up in the DeployR log. I typically add this for debugging to see what the variables are at a specific point in the Task Sequence.

Now that's an extreme example of how simple this can be. One more quick example would be to have your step install a module and run another command. An example of updating HP BIOS while in WinPE: ``` install-module -name HPCMSL -AcceptLicense -SkipPublisherCheck -Force if ((Get-HPBIOSUpdates -Check) -eq $false){Get-HPBIOSUpdates -Flash -Yes -Bitlocker Ignore} ```

This step also supports longer scripts, which you can more easily view by clicking the enlarge icon on the upper right corner of the script dialog box.

It will then open into the full screen of the browser. you can click the blue minimize button in the upper right to return to normal view.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://documentation.2pintsoftware.com/deployr/powershell-modules/scripting-examples-simple-inline-script..md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.