You can use WMI from within PowerShell to accomplish this. Assuming there is a network adapter who’s device name has Wireless in it, the series of commands might look something like the following: $adaptor = Get-WmiObject -Class Win32_NetworkAdapter | Where-Object {$_.Name -like “*Wireless*”} $adaptor.Disable() $adaptor.Enable() Remember, if you’re running this with Window’s Vista, you may … Read more
TryParse should work as long as you use ref and declare the variable first: $out = $null if ([bool]::TryParse($a, [ref]$out)) { # parsed to a boolean Write-Host “Value: $out” } else { Write-Host “Input is not boolean: $a” }
In fact, if you call a .ps1 file, by default any functions and variables declared within it are scoped privately within the script (this is referred to as “script scope”). Since you’re seeing both functions defined globally, I infer that you’re dot-sourcing SvcTest.ps1, i.e. invoking it like this PS> . <path>\SvcTest.ps1 rather than calling it … Read more
Have you tried: .\MyScript.ps1 2>&1 | tee -filePath c:\results.txt 2>&1 is what you’re looking for Note: This answer works great in PowerShell 1.0 and 2.0, but will capture ONLY standard output and errors in PowerShell 3.0 and later.
It is a security feature so that you do run scripts that you think you are running. That is why unlike cmd, you do not have . ( current directory) in PATH and you have to do .\my.exe etc. If you don’t want to do this and subvert this precaution, add . to your PATH: … Read more
This is probably because the PowerShell script is being launched from a 32 bit instance of PowerShell. The ServerManager commands are only available from 64 bit version of PowerShell. See: Can’t access ServerManager module via PowerShell –Edit – To add to jbsmith’s comments— Extra things to try: When you ran the Get-Command cmdlt: gcm | … Read more
You have made an error in the property; as wOxxOm suggests, you should be using TargetPath rather than Target: $sh = New-Object -ComObject WScript.Shell $target = $sh.CreateShortcut(‘<full-path-to-shortcut>’).TargetPath Google and MSDN were indeed helpful here; additionally, piping objects to Get-Member can often be useful and educational. This question also shows how to manipulate shortcuts using PowerShell, … Read more
Get-Item Gets the item at the specified location. Get-Item .\foo # returns the item foo Get-ChildItem Gets the items and child items in one or more specified locations. Get-ChildItem .\foo # returns all of the children within foo note: Get-ChildItem can also recurse into the child directories Get-ChildItem .\foo -Recurse # returns all of the … Read more
If you use Start-Process, you create a new child process that has your powershell session as its parent process. If you kill the powershell parent process that starts this, the new process will be orphaned and keep running. It will, however, not survive if you kill the parent’s process tree Start-Process -FilePath notepad.exe Powershell cannot … Read more