Articles in the Powershell Category
• Execution policy:
– Restricted : Interactive shell only, no scripts, only signed config files
– Allsigned: requires digital signatures (verisign or selfsigned(makecert))
– Remotesigned local created scripts run. foreign scripts not
– Unrestricted local created scripts run. foreign …
The process of importing multiple users’ PST files into Exchange 2010 is not as simple as perhaps you might expect, and certainly not as simple is probably should be, given how common this particular task …
Profiles
A PowerShell profile is a saved collection of settings for customizing the PowerShell environment. There are four types of profiles, loaded in a specific order each time PowerShell starts. The following sections explain these profile …
PowerShell ISE
Another new feature that was introduced in PowerShell 2.0 is called the Integrated Scripting Environment (ISE). The ISE, as shown in Figure 21.1, is a Windows Presentation Foundation (WPF)–based host application for Windows PowerShell. …
Remoting
With PowerShell 1.0, one of its major disadvantages was the lack of an interface to execute commands on a remote machine. Granted, you could use Windows Management Instrumentation (WMI) to accomplish this and some cmdlets …
Shells are a necessity in using operating systems. They give the ability to execute arbitrary commands as a user and the ability to traverse the file system. Anybody who has used a computer has dealt …
Windows Management Instrumentation (WMI) is one of those tools that can change your proverbial life. But while it’s been around since the early 90s, the adoption of WMI has been slowed due to …
The set of cmdlets which come with PowerShell is restricted to generic cmdlets and those intended for managing aspects of the Windows Server OS. If you are unfamiliar with using PowerShell cmdlets please check out PowerShell …
If PowerShell’s learning curve has kept you from embracing it for daily use, “cool” might not be a word you’d associate with it. But PowerShell is here to stay. It’s a core part of Exchange …
#Parameter- Name of the VMware cluster to work in
param($cluster)
Write-Output “`n$(Get-Date)- Script started`n”
# Validate parameter input
$IsClusterNameInvalid = $true
Get-Cluster | % { If ($_.Name -eq $Cluster) {$IsClusterNameInvalid = $false} }
If ($IsClusterNameInvalid) {
Write-Host “Error- Invalid Cluster Name” …
