Use the Get-Command cmdlet to test for the existence of a cmdlet: if (Get-Command $cmdName -errorAction SilentlyContinue) { “$cmdName exists” } And if you want to ensure it is a cmdlet (and not an exe or function or script) use the -CommandType parameter e.g -CommandType Cmdlet
Exported commands are not available if the module is not loaded. You need to load the module first and then execute Get-Command: Import-Module -Name <ModuleName> Get-Command -Module <ModuleName>
This is what the code would look like in a batch file(tested, works): powershell -Command “& {set-location ‘HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings’; set-location ZoneMap\Domains; new-item SERVERNAME; set-location SERVERNAME; new-itemproperty . -Name http -Value 2 -Type DWORD;}” Based on the information from: PowerShell script in a .bat file
In PowerShell 2.0, it is still not possible to get the Copy-Item cmdlet to create the destination folder, you’ll need code like this: $destinationFolder = “C:\My Stuff\Subdir” if (!(Test-Path -path $destinationFolder)) {New-Item $destinationFolder -Type Directory} Copy-Item “\\server1\Upgrade.exe” -Destination $destinationFolder If you use -Recurse in the Copy-Item it will create all the subfolders of the source … Read more
You put a certain style of comment at the top of the file that can be decoded by the PowerShell help system. Here’s an example: <# .SYNOPSIS . .DESCRIPTION . .PARAMETER Path The path to the . .PARAMETER LiteralPath Specifies a path to one or more locations. Unlike Path, the value of LiteralPath is used … Read more
The -match operator tests a regex, combine it with the magic variable $matches to get your result PS C:\> $x = “—-start—-Hello World—-end—-” PS C:\> $x -match “—-start—-(?<content>.*)—-end—-” True PS C:\> $matches[‘content’] Hello World Whenever in doubt about regex-y things, check out this site: http://www.regular-expressions.info
There’s really nothing at the namespace level like that. I often assign commonly used types to variables and then instantiate them: $thingtype = [FooCompany.Bar.Qux.Assembly.With.Ridiculous.Long.Namespace.I.Really.Mean.It.Thingamabob]; $blurb = New-Object $thingtype.FullName Probably not worth it if the type won’t be used repeatedly, but I believe it’s the best you can do.
You basically have 3 options to prevent the PowerShell Console window from closing, that I describe in more detail on my blog post. One-time Fix: Run your script from the PowerShell Console, or launch the PowerShell process using the -NoExit switch. e.g. PowerShell -NoExit “C:\SomeFolder\SomeScript.ps1” Per-script Fix: Add a prompt for input to the end … Read more
-Filter only accepts a single string. -Include accepts multiple values, but qualifies the -Path argument. The trick is to append \* to the end of the path, and then use -Include to select multiple extensions. BTW, quoting strings is unnecessary in cmdlet arguments unless they contain spaces or shell special characters. Get-ChildItem $originalPath\* -Include *.gif, … Read more
This will open a new window. Either: start-process powershell Or: start powershell