Everyday Nerd » PowerShell

PowerShell: Move Windows Server 2008 Cluster Group

Nerd — Mon, 21 Nov 2011 17:55:13 +0000

Where I work, we were a little behind finally getting to Windows Server 2008 R2. Our Exchange Servers were running on Server 2003 R2 until recently. Windows clustering is quite different on 2k8 vs. 2k3. I wrote this function to move the Windows cluster group “Cluster Group” (quorum) to the other node of the cluster. I know it’s not that difficult to do this, but it saves a few extra keystrokes.

Function Invoke-WindowsClusterFailover
{
	#Requires -version 2
	[CmdletBinding(SupportsShouldProcess=$true,ConfirmImpact="High")]
	param()
	Write-Verbose "Checking to see if $($env:computername) is a Clustered Exchange Server"
	Get-ClusteredMailboxServerStatus -ErrorAction SilentlyContinue | Out-Null
	If ($? -eq $False)
	{
		Write-Verbose "$($env:computername) is not a clustered Exchange Server - Exiting"
		Throw "$($env:computername) is not a clustered Exchange Server"
	}
	Else
	{
		Write-Verbose "$($env:computername) is a Clustered Exchange Server"
		If (((Get-WmiObject Win32_OperatingSystem).Caption).ToString() -like "*2008*")
		{
			Write-Verbose "$($env:computername) is a Windows Server 2008 or later"
			Write-Verbose "Loading Windows Failover Cluster PowerShell Module"
			Import-Module FailoverClusters
		}
		Else
		{
			Write-Verbose "$($env:computername) is not Windows Server 2008 or later"
			Write-Verbose "$((Get-WmiObject Win32_OperatingSystem).Caption) does not support the Powershell FailoverCluster Module - Exiting"
			Throw "$((Get-WmiObject Win32_OperatingSystem).Caption) does not support the Powershell FailoverCluster Module"
		}
		Write-Verbose "Getting Windows Cluster Name"
		$ClusterName = (Get-Cluster).Name
		Write-Verbose "Checking ShouldContinue if OK to proceed"
		if($PSCmdlet.ShouldProcess("$($ClusterName)", "Failover Windows Cluster"))
		{
			Write-Verbose "Moving Windows Cluster Group"
			Get-ClusterGroup "Cluster Group" | Move-ClusterGroup
		}
		Write-Verbose "End"
	}
				.SYNOPSIS
		Moves the Windows cluster "Cluster Group" to the other node of the cluster

		.DESCRIPTION
		Moves the Windows cluster "Cluster Group" to the other node of the cluster.  This requires
		Windows Server 2008 or later.  This function supports "Should Continue" so it prompts the
		user to continue at the "dangerous" portion of the function (Move-ClusterGroup).  If you
		don't want the should continue prompt, you can use the  param.

		.NOTES
		Function Name: Invoke-WindowsClusterFailover
		Author: Dan Burgess
		Email: nerd@everydaynerd.com
		Script Requires:  Powershell 2.0 or higher; Windows Server 2008 or later
	#>
}

I really enjoyed using the “SupportsShouldProcess” feature of CmdletBinding! Expand the code above, and double click to select all.

PowerShell: Get-Uptime for Computer(s)

Nerd — Fri, 18 Nov 2011 20:53:04 +0000

I needed to check the server uptime for multiple servers, and well, I wanted to do it in PowerShell. I found a sample from MSDN, and modified it, and threw it into a function.

Function Get-Uptime
{
	#Requires -version 2
	[CmdletBinding(SupportsShouldProcess=$true,ConfirmImpact="High")]
	Param(
	[parameter(Mandatory=$false,HelpMessage="Computer Name(s)",ValueFromPipeline=$true)]
	[object[]]$ComputerName = "."
	)
	PROCESS
	{
		$WmiOS = Get-WMIObject -class Win32_OperatingSystem -computer $ComputerName
		Function ConvertWMIDateToDateTime($BootTime)
		{
			[System.Management.ManagementDateTimeconverter]::ToDateTime($BootTime)
		}
		Function GetUptime($ComputerName)
		{
			$BootTime = $WmiOS.LastBootUpTime
			$LastBootUpTime = ConvertWMIDateToDateTime($BootTime)
			$Uptime = (Get-Date) - $lastBootUpTime
			$days = $Uptime.Days
			$hours = $Uptime.Hours
			$min = $uptime.Minutes
			$sec = $uptime.Seconds
			[console]::ForegroundColor = "Green"
			"$($ComputerName) has been up for: {0} days, {1} hours, {2} minutes and {3} seconds" -f $days,$hours,$min,$sec
			[console]::ResetColor()
		}
		GetUptime $ComputerName
	}
	<#
		.SYNOPSIS
		Gets uptime of a system via WMI

		.DESCRIPTION
		Get-Uptime uses WMI (specificaly Win32_ComputerSystem) to get the uptime of a system.
		The core component of the script was found at http://msdn.microsoft.com/en-us/library/aa394591(VS.85).aspx
		and addapted with additional functionality.

		.EXAMPLE
		PS c:\> Get-UpTime SERVER01
		SERVER01 has been up for: 355 days, 23 hours, 59 minutes and 59 seconds

		.EXAMPLE
		PS c:\> Get-ExchangeServer | Get-Uptime
		SERVER01 has been up for: 355 days, 23 hours, 59 minutes and 59 seconds
		SERVER02 has been up for: 355 days, 23 hours, 59 minutes and 59 seconds
		SERVER03 has been up for: 355 days, 23 hours, 59 minutes and 59 seconds
		SERVER04 has been up for: 355 days, 23 hours, 59 minutes and 59 seconds

		.LINK
		Script Posted to:

http://everydaynerd.com

		Adapted from sample posted at:

http://msdn.microsoft.com/en-us/library/aa394591(VS.85).aspx

		.NOTES
		Function Name : Get-UpTime
		Author: Dan Burgess
		Email: nerd@everydaynerd.com
		Script Requires:  Powershell 2.x or higher
	#>
}

Here’s an alternative to this function that outputs to a powershell object – rather than just writing to the screen. (Thanks for the encouragement Jeffery)

Function Get-Uptime
{
	#Requires -version 2
	[CmdletBinding(SupportsShouldProcess=$true,ConfirmImpact="High")]
	Param(
	[parameter(Mandatory=$true,HelpMessage="Computer Name(s)",ValueFromPipeline=$true)]
	[object[]]$ComputerName
	)
	PROCESS
	{
		$System = Get-WMIObject -class Win32_OperatingSystem -computer $ComputerName
		Function GetUptime($ComputerName)
		{
			$Bootup = $System.LastBootUpTime
			$LastBootUpTime = $System.ConvertToDateTime($System.LastBootUpTime)
			$now = Get-Date
			$Uptime = $now - $lastBootUpTime
			$NewObjectProperties = @{
				ComputerName=$ComputerName
				Days=$Uptime.Days;`
				Hours=$Uptime.Hours;`
				Minutes=$Uptime.Minutes;`
				Seconds=$Uptime.Seconds;`
				}
			New-Object psobject -Property $NewObjectProperties
		}
		$Results = GetUptime $ComputerName
		$Results | Select ComputerName, Days, Hours, Minutes, Seconds
	}
	<#
		.SYNOPSIS
		Gets uptime of a system via WMI

		.DESCRIPTION
		Get-Uptime uses WMI (specificaly Win32_ComputerSystem) to get the uptime of a system.
		The core component of the script was found at http://msdn.microsoft.com/en-us/library/aa394591(VS.85).aspx
		and addapted with additional functionality.

		.EXAMPLE
		PS c:\> Get-UpTime server01
		ComputerName : {server01}
		Days         : 27
		Hours        : 2
		Minutes      : 21
		Seconds      : 26

		.EXAMPLE
		PS c:\> Get-ExchangeServer | Get-Uptime | ft -AutoSize
		ComputerName Days Hours Minutes Seconds
		------------ ---- ----- ------- -------
		{server01}    27     2      15      49
		{server02}   130     6      40      23

		.LINK
		Script Posted to:

http://everydaynerd.com

		Adapted from sample posted at:

http://msdn.microsoft.com/en-us/library/aa394591(VS.85).aspx

		.NOTES
		Function Name : Get-UpTime
		Author: Dan Burgess
		Email: nerd@everydaynerd.com
		Script Requires:  Powershell 2.x or higher
	#>
}

Happy PowerShelling!

PowerShell: Drive Space Info from multiple systems

Nerd — Wed, 28 Sep 2011 18:24:13 +0000

With PowerShell 2 came Powershell remoting and jobs, both of which are REALLY cool! I’m going to show you two ways to get drive space info from multiple systems, first with a normal foreach loop, and then with remoting (which is basically a remote job). Both methods use WMI class Win32_LogicalDisk to query the drives for information.

First, the old fashion foreach loop. Notice the “Process” section – this in essence does a foreach of the $Identity – notice that in the parameter that the $Identity has [object[]] in front of it. Two things about this: One, [] denotes an array, versus a single object. Two, it’s object, instead of string, int or other data type. Object allows the parameter to be just a string – a computer name (“SERVER01″), a string array (“SERVER01″, “SERVER02″), or even the identity from other objects (Get-ExchangeServer | GetDriveSpace). I’ll be posting more in the future about parameters, and advanced functions (cmdletbinding).

Function GetDriveSpace
{
	[CmdletBinding(SupportsShouldProcess=$true, ConfirmImpact="Low")]
	param (
	[parameter(Mandatory=$true,HelpMessage="ComputerName(s)",ValueFromPipeline=$true)]
	[Object[]]$Identity
	)
	Process
	{
		$Name = (Get-WmiObject -ComputerName $Identity win32_computersystem  | Select Name).Name.ToString()
		$drives = Get-WmiObject -ComputerName $Identity Win32_LogicalDisk | Where-Object {$_.DriveType -eq 3}

		foreach($drive in $drives)
		{
			$NewObjectProperties = @{
				ComputerName=$Name;`
				DriveLetter=$drive.DeviceID;`
				Label=($drive.VolumeName);`
				DriveSize=($drive.Size/1gb).ToString("0.00");`
				FreeSpaceMB=($drive.freespace/1GB).tostring("0.00");`
				PercentFree=((($drive.freespace/1GB)/($drive.size/1GB))*100).tostring("0.00")`
			}
			New-Object psobject -Property $NewObjectProperties
		}
	}

	GetDriveSpace -Identity SERVER01

		Returns Drive Space Info for SERVER01

		.EXAMPLE
		PS] C:\>Get-MailboxServer | GetDriveSpace | FT

		Returns Drive Space Info for Exchange Mailbox Servers

		.EXAMPLE
		PS] C:\>GetDriveSpace -Identity SERVER01, SERVER02 | FT -AutoSize

		Returns Drive Space Info for SERVER01 & SERVER02

		.NOTES
		Function Name : GetDriveSpace
		Author : Dan Burgess
		Email: nerd@everydaynerd.com
		Script Requires:  Powershell 2.0 or higher
	#>
}

Now, lets do the same thing, but this time with PowerShell remoting. As before, the function is utilizing CmdletBinding, Parameter, with a single param [object[]]$Identity, and the Process block, but an End block as well. In the Process block, each server passed in the parameter has a remote job started with the Invoke-Command cmdlet, passing the script block with the code to query WMI to return the disk space information. Note the -AsJob switch – this allows the invoke-command to work in the background, instead of waiting on the job to finish. The End block then checks all the jobs, and waits till none of the jobs have a status of “Running” before issuing a “Receive-Job”. This gathers all the returned values from each job that ran. The -Keep leaves a copy of the results in the job queue – if receive-job is run with out this, the results are removed from the job status.

Function GetDriveSpace-Remoting
{
	[CmdletBinding(SupportsShouldProcess=$true, ConfirmImpact="Low")]
	param (
	[parameter(Mandatory=$true,HelpMessage="ComputerName(s)",ValueFromPipeline=$true)]
	[Object[]]$Identity
	)
	Process
	{
		Invoke-Command -ComputerName $Identity -ScriptBlock {$drives = Get-WmiObject Win32_LogicalDisk | Where-Object {$_.DriveType -eq 3}
			foreach($drive in $drives)
			{
				$NewObjectProperties = @{
					DriveLetter=$drive.DeviceID;`
					Label=($drive.VolumeName);`
					DriveSizeMB=($drive.Size/1gb).ToString("0.00");`
					FreeSpaceMB=($drive.freespace/1GB).tostring("0.00");`
					PercentFree=((($drive.freespace/1GB)/($drive.size/1GB))*100).tostring("0.00")`
				}
				New-Object psobject -Property $NewObjectProperties
			}
		} -SessionOption (New-PSSessionOption -NoMachineProfile) -AsJob

	}
	End
	{
		While (Get-Job -State "Running")
		{
			$i = ((Get-Job).Count) - ((Get-Job -State "Running").count)
			$Progress = [int][Math]::Ceiling(($i / ((Get-Job).Count) * 100))
			Write-Progress -Activity "Waiting on $(((Get-Job -State "Running").count)) Jobs to finish" -PercentComplete $progress -Status "$($progress)% Complete" -Id 1;
		}
		$Results = Get-Job | % {Receive-Job $_ }
		$Results
	}

	GetDriveSpace-Remoting -Identity SERVER01

		Returns Drive Space Info for SERVER01

		.EXAMPLE
		PS] C:\>Get-MailboxServer | GetDriveSpace-Remoting | FT

		Returns Drive Space Info for Exchange Mailbox Servers

		.EXAMPLE
		PS] C:\>GetDriveSpace-Remoting -Identity SERVER01, SERVER02 | FT -AutoSize

		Returns Drive Space Info for SERVER01 & SERVER02

		.NOTES
		Function Name : GetDriveSpace-Remoting
		Author : Dan Burgess
		Email: nerd@everydaynerd.com
		Script Requires:  Powershell 2.0 or higher and WinRM enabled on remote hosts
	#>
}

Both methods work, but in my tests, the remote function was MUCH faster when pulling from multiple systems. For a list of 48 systems, the normal foreach loop took 30 seconds, while the remote function only took 5 seconds!!!

PowerShell: Change PS Window Size on the fly

Nerd — Wed, 28 Sep 2011 10:00:34 +0000

First, my apologies for not posting ANYTHING to EverydayNerd since April 25, but hey, this is just for fun, and I DO have a day job

I am going to be posting a LOT of PowerShell stuff here, as it has, over the last 6 months, become my best friend at the office! Thanks to Gary Siepser, I have gone from writing super simple scripts, to now, well trust me, it’s a day/night difference.

So I work on a laptop, but also dock, and when I un-dock my resolution changes – enough that I have scroll bars in my PowerShell window. This was really annoying, so I wrote a quick function that will change the window size on the fly.

I put these functions into my PowerShell profile, so I can call them whenever I need to change my PS window size. Works like a charm! If you don’t know how to edit our PowerShell profile, just enter this in your shell: notepad $Profile

Hope this helps, and stay tuned for more PowerShell goodies!

Source Code:

Function Set-Wide
{
	$aff = (Get-Host).UI.RawUI
	$bff = $aff.BufferSize
	$bff.Width = 170
	$bff.Height = 9000
	$aff.BufferSize = $bff
	$wff = $aff.WindowSize
	$wff.Width = 170
	$wff.Height = 60
	$aff.WindowSize = $wff
}

Function Set-Small
{
	$aff = (Get-Host).UI.RawUI
	$wff = $aff.WindowSize
	$wff.Width = 90
	$wff.Height = 45
	$aff.WindowSize = $wff
	$bff = $aff.BufferSize
	$bff.Width = 90
	$bff.Height = 9000
	$aff.BufferSize = $bff
}

Related posts:

Free E-Book: PowerShell
PowerShell: Move Windows Server 2008 Cluster Group
PowerShell: Get-Uptime for Computer(s)

Exchange PowerShell Script: Get Mailbox Count by Database

Nerd — Sat, 26 Mar 2011 17:20:55 +0000

Here’s a PowerShell script that does a quick count of mailboxes on each database of a server, or all servers – depending if you specify the server name as a script parameter.

** Updated: I made some improvements to the script, and have posted the updated code. One notable items is that I separated the count of mailboxes and disconnected mailboxes. Previously, the count included both mailboxes and disconnected mailboxes. This may skew the numbers a bit, depending on what you are looking for.

#=================================================================================================
# NAME: Get-MailboxCountPerDatabase.ps1
#
# AUTHOR:  Dan B.
# EMAIL:   Nerd@EverydayNerd.com 
# DATE:    03/27/2011
# Version: 1.0
#
# COMMENT: Script to return the count of mailboxes on each server by database
#
#=================================== Change Log ==================================================
# Version 1.0
# -Initial script
# -Changed output to an array instead of just write-host
# -Added total count to single server
#
#=================================================================================================
# Script Paramaters to allow server name to be typed after the script name.   If no Param, all servers are returned
 
param([string] $Param )     
 
$Results = @()
$CountMB = 0
 
if(!$param)
    {
        $Servers = Get-ExchangeServer | Where {$_.ServerRole -eq "Mailbox"} | Sort Name
 
        Foreach($Server in $Servers)
            {
                $dbs = Get-MailboxDatabase -server $Server | Sort Name
                
                foreach($db in $dbs)
                    {
                        $mb = Get-MailboxStatistics -Database $db | Where {$_.DisconnectDate -eq $null -and $_.ObjectClass -eq 'Mailbox'} | Measure-Object
                        $mbdis = Get-MailboxStatistics -Database $db | Where {$_.DisconnectDate -ne $null -and $_.ObjectClass -eq 'Mailbox'} | Measure-Object
                        
                        Write-Host "$($Server) `t $($db.name)`t $($a.count)"
                        
                        $Obj = New-Object PSObject
                        $Obj | Add-Member NoteProperty -Name "Server" -Value $Server
                        $Obj | Add-Member NoteProperty -Name "Database" -Value $db.Name
                        $Obj | Add-Member NoteProperty -Name "Mailboxes" -Value $mb.count
                        $Obj | Add-Member NoteProperty -Name "Disconnected Mailboxes" -Value $mbdis.count
                        $Results += $Obj
                    }
            }
    }
else
    {
    $server = $param
        $dbs = Get-MailboxDatabase -server $Server | Sort Name
 
        foreach($db in $dbs)
            {
                $mb = Get-MailboxStatistics -Database $db | Where {$_.DisconnectDate -eq $null -and $_.ObjectClass -eq 'Mailbox'} | Measure-Object
                $mbdis = Get-MailboxStatistics -Database $db | Where {$_.DisconnectDate -ne $null -and $_.ObjectClass -eq 'Mailbox'} | Measure-Object
 
                $Obj = New-Object PSObject
                $Obj | Add-Member NoteProperty -Name "Server" -Value $Server
                $Obj | Add-Member NoteProperty -Name "Database" -Value $db.Name
                $Obj | Add-Member NoteProperty -Name "Mailboxes" -Value $mb.count
                $Obj | Add-Member NoteProperty -Name "Disconnected Mailboxes" -Value $mbdis.count
                $Results += $Obj
                $countmb += $mb.count
                
            }
        Write-Host
        Write-Host "$($Server) has a total of $($CountMB) mailboxes" -ForegroundColor Green
    }
 
$Results | FT -AutoSize
 
#===================================== End of Script ==============================================

Script can be downloaded here: Get-MailboxCountPerDatabase.ps1

Script: Get time of Exchange last online defrag

Nerd — Thu, 19 Mar 2009 20:18:00 +0000

digging through the Application log can be a real pain sometimes. Last night, I was asked by a Microsoft Engineer to give me the last online defrag of a server that we had a case opened on. So, instead of opening up the Event Viewer, I went to Powershell:

# Script to return the date and time of the last online defrag of each Exchange 2007 Database# Highly recommended to run this locally on the Exchange server, not remotely.# Written by Dan Burgess# nerd@EverydayNerd.com

$servername = read-host "Enter Exchange Mailbox Server Name"$db = Get-StorageGroup -Server $servername | Get-MailboxDatabase

foreach ($objItem in $db)    {        $EventLogs = get-EventLog -Logname Application| Where-Object {$_.EventID -eq 703 -or $_.EventID -eq 701 -and $_.source -eq 'ESE' } | Where-Object {$_.ReplacementStrings -like $objItem.EdbFilePath} | select-object -first 1        write-host ' Mailbox store: ' $objItem.Identity        write-host ' Last Defrag completed: ' $EventLogs.TimeGenerated        write-host ' '    }

Works like a charm! Next time you need to extract info from a computers log files, edit this script to match the EventID that you need, and slap it in Powershell! Happy scripting!

Powershell Script: Display Exchange 2007 Queue by Site

Nerd — Wed, 18 Mar 2009 17:23:00 +0000

Working in a multi site Exchange 2007 environment can be cumbersome when trying to view queue information on the Hub servers. I wrote this script to simplify this process.
The script queries the Exchange 2007 organization, finds the servers with the Hub Transport Roles, and grouping them into sites (you will have to define the sites yourself, based on your organizational configuration). You can find the sites for your organization by entering this command:

Get-ExchangeServer | Where { $_.isHubTransportServer -eq $true } | sort name

This will output a table of all the Hub Transport servers and list the Site for each. Take these site names, and change the script with your values. You can also modify the variable names to match each site’s name.

Script:

# Exchange 2007 Powershell Script# Script to display queue information of Hub Transport Servers# Dynamicly selects Exchange Hub Transport Servers from Exchange 2007 Organization# Selects server's location by Site# Output queue information# Writen by Dan Burgess# nerd@EverydayNerd.com

cls

# Set variables$last = "begin"$choice = 'start'

# Dynamicly set variables for each site's hub transport servers, and sort by server name$usa = Get-ExchangeServer | where { $_.isHubTransportServer -eq $true -and $_.Site -like '*USA*' } | sort name $eur = Get-ExchangeServer | Where { $_.isHubTransportServer -eq $true -and $_.Site -like '*EUR*' } | sort name $chi = Get-ExchangeServer | Where { $_.isHubTransportServer -eq $true -and $_.Site -like '*CHI*' } | sort name $aus = Get-ExchangeServer | Where { $_.isHubTransportServer -eq $true -and $_.Site -like '*AUS*' } | sort name $afr = Get-ExchangeServer | Where { $_.isHubTransportServer -eq $true -and $_.Site -like '*AFR*' } | sort name $allhub = Get-ExchangeServer | Where { $_.isHubTransportServer -eq $true } | sort name

# Start WHILE loop, that allows the user to repeat or select the choice selection instead of exiting the script after completionwhile ($choice -ne 'x'){write-host ""write-host "0 - All Sites" -foregroundcolor Yellowwrite-host "1 - America (USA)" -foregroundcolor Yellowwrite-host "2 - Europe (EUR)" -foregroundcolor Yellowwrite-host "3 - China (CHI)" -foregroundcolor Yellowwrite-host "4 - Austrialia (AUS)" -foregroundcolor Yellowwrite-host "5 - Africa (AFR)" -foregroundcolor Yellowwrite-host "6 - All Queue with messages higher than 10" -foregroundcolor Greenwrite-host "X - Exit" -foregroundcolor Redwrite-host ""

# If statement to see check if first selection, or sequencialif($last -eq "begin")    {        [console]::ForegroundColor = "Green"        $choice = read-host "Select site to check Hub Queue's"        [console]::ResetColor()    }else    {        [console]::ForegroundColor = "Green"        $choice = read-host "Select site to check Hub Queue's (Press Enter to repeat your last selection)"        [console]::ResetColor()        }

    switch ($choice)        {            0 { $hub = $allhub }            1 { $hub = $usa }            2 { $hub = $eur }            3 { $hub = $chi }            4 { $hub = $aus }            5 { $hub = $afr }            6 { $hub = $allhub }            x {  }            default { $choice = $last }        }

# For each server in the site selected, get the queue information, and list as a table    if($choice -eq "6")        {        "Begin Hub List" > HubQueueOutput.txt        "--------------------------------------" >> HubQueueOutput.txt        foreach ( $server in $hub )            {                get-exchangeserver $server -erroraction silentlycontinue | get-queue -erroraction silentlycontinue | where {$_.MessageCount -gt 10 } >> HubQueueOutput.txt            }        "--------------------------------------" >> HubQueueOutput.txt        "End Hub List" >> HubQueueOutput.txt        more HubQueueOutput.txt        }        elseif($choice -ne "x")        {        "Begin Hub List" > HubQueueOutput.txt        "--------------------------------------" >> HubQueueOutput.txt        foreach ( $server in $hub )            {                get-exchangeserver $server -erroraction silentlycontinue | get-queue -erroraction silentlycontinue >> HubQueueOutput.txt            }        "--------------------------------------" >> HubQueueOutput.txt        "End Hub List" >> HubQueueOutput.txt        more HubQueueOutput.txt        }    else        {            write-host ""            write-host "Script exiting" -foregroundcolor DarkCyan            write-host ""            write-host "Have a nice day..."            write-host ""            write-host ""        }$last = $choice    # Go back to begining of WHILE loop, and do it again!    }

Of course this has to be ran on a machine that hat the Exchange 2007 Powershell installed. Hope this helps, and saves time!

Script to Find Whitespace on all Exchange 2007 Servers

Nerd — Fri, 23 Jan 2009 17:53:00 +0000

As an Exchange Admin, I’m sure you have had the need to find out how much whitespace is in each of your Exchange databases. This can be a real pain to do, crawling through the Event Log, looking for Event ID 1221. This script will query all Exchange 2007 Mailbox servers, crawl through the Event logs, and return the Whitespace for every Database you have. This information can also be exported to a SQL database, if you un-comment the appropriate lines.

Hope this makes your job easier!

*** Special thanks to my co-worker Stephen M for writing this script, and suggesting that I post it to ExchangeStyle.EverydayNerd.com – Thanks!

# Script: Get-WhiteSpace.ps1 will return the Whitespace on every Mailbox Server in an Exchange 2007 Environment# Author: EverydayNerd.com# Contact: Nerd [at] everydaynerd.com

# Uncomment to write to a database                              

#$db = “Enter Server Name Here”#$catalog = “Enter Database Catalog Here”#$conn = New-Object System.Data.SqlClient.SqlConnection("Data Source=$db; Initial Catalog=$catalog; Integrated Security=SSPI")#$conn.Open()

$WmidtQueryDT = [System.Management.ManagementDateTimeConverter]::ToDmtfDateTime([DateTime]::UtcNow.AddDays(-1))$servers = Get-ExchangeServer | Where{$_.ServerRole -eq 'None' -or $_.ServerRole -like '*Mailbox*'} | sort nameforeach ($server in $servers){Write-Host $serverGet-WmiObject -computer $server -query ("Select * from Win32_NTLogEvent Where Logfile='Application' and Eventcode = '1221' and TimeWritten >='" + $WmidtQueryDT + "'") |ForEach-Object{                $time = [System.Management.ManagementDateTimeConverter]::ToDateTime($_.TimeGenerated).ToString()                $date = $time.split("' '")                $writedate = $date[0]                $mbnamearray = $_.message.split("' '")                $store = $mbnamearray[2]                $store = $store -replace '"', ''                $size = [math]::round(($mbnamearray[4]/1024),4)                $search = $server.ToString() + "\" + $store.ToString()

                                $test = Get-ExchangeServer $server                                If ($server.ServerRole -eq 'None'){                                                $root =[ADSI]'LDAP://RootDSE'                                                $cfConfigRootpath = "LDAP://" + $root.ConfigurationNamingContext.tostring()                                                $configRoot = [ADSI]$cfConfigRootpath                                                $searcher = New-Object DirectoryServices.DirectorySearcher($configRoot)                                                $searcher.Filter = '(&(objectCategory=msExchExchangeServer)(cn=' + $Server + '))'                                                $searchres = $searcher.FindOne()                                                $snServerEntry = New-Object System.DirectoryServices.directoryentry                                                $snServerEntry = $searchres.GetDirectoryEntry()

                                                $adsiServer = [ADSI]('LDAP://' + $snServerEntry.DistinguishedName)                                                $dfsearcher = new-object System.DirectoryServices.DirectorySearcher($adsiServer)                                                $dfsearcher.Filter = "(objectCategory=msExchPrivateMDB)"                                                $srSearchResults = $dfsearcher.FindAll()                                                foreach ($srSearchResult in $srSearchResults){                                                                $msMailStore = $srSearchResult.GetDirectoryEntry()                                                                $srnamearray = $_.message.split("'\'")                                                                $srstore = $mbnamearray[2]                                                                $srstore = $srstore -replace '"',''                                                                If ($srstore.ToString() -like $store.ToString()){                                                                $EDBFile = $msMailStore.msExchEDBFile                                                                $EDBFilePath = "\\" + $server.ToString() + "\" + $EDBFile.ToString()                                                                $EDBFilePath = $EDBFilePath -replace ':', '$'                                                                $EDBFileSize = Get-Item $EDBFilePath.ToString() | select Length                                                                }                                                }                                }                                Else{                                                $EDBFile = Get-MailboxDatabase -Identity $search | select EDBFilePath                                                $EDBFile = $EDBFile -replace '@{EdbFilePath=', ''                                                $EDBFile = $EDBFile -replace '}', ''                                                $EDBFile = $EDBFile -replace ':', '$'                                                $EDBFilePath = "\\" + $server.ToString() + "\" + $EDBFile.ToString()                                                $EDBFileSize = Get-Item $EDBFilePath.ToString() | select Length                                                }

                                $EDBFileSize = $EDBFileSize -replace '@{Length=', ''                                $EDBFileSize = $EDBFileSize -replace '}', ''                                $EDBFileSize = [math]::round(((($EDBFileSize/1024)/1024)/1024),2)

# Uncomment to write to a database                                              #$cmd = $conn.CreateCommand()                #$cmd.CommandText ="INSERT EventLog1221 VALUES ('$writedate', '$server', '$store', '$size', '$EDBFileSize')"                #$cmd.ExecuteNonQuery()

                Write-Host $writedate $server $store $size $EDBFileSize                }}# Uncomment to write to a database                              #$conn.Close()

Related posts:

Script: Get time of Exchange last online defrag

Powershell Script: Display Exchange 2007 Queue by Site

Exchange PowerShell Script: Get Mailbox Count by Database

Save Password in .RDP File

Nerd — Fri, 23 Jan 2009 17:51:06 +0000

I shared with you how to create multiple .rdp files with Powershell, and now, I want to show you how to make your job even easier! I ran across this blog, and downloaded his RDP password Hash program. It got me thinking, I could make my job easier by saving the password in a hashed format in each RDP file that my Powershell script creates!

** Note: Please see my original post about this if you have questions of the files needed, and folder structure.

First, I modified the .CSV file, adding a new column “PASS” – in that column, add the hashed password created from remkoweijnen.nl’s password hash program [DOWNLOAD]

Then I modified my Powershell script, adding in the password to script, so it’s added to the .RDP file.

No more typing in passwords to connect to servers. Also, the nice thing is, if you have to change the password, just modify the hash file in the .CSV file, and re-run the Powershell script!

Here is the modified Powershell Script:

$List = Import-CSV RDPLIST.CSV $resolutions = ("Console","Cullscreen","Widescreen","Docked") ForEach($Entry in $List) { ForEach($resolution in $resolutions) { # Prepend the destination directory info for RDP files $Dir = "..\" + $resolution + "\" + $Entry.Directory # Create new folder New-Item -Path $Dir -ItemType Directory -Force # Build the file name $FileName = $Dir + "\" + $Entry.ServerName + ".RDP" # Remove the old file Remove-Item $FileName -Force # Begin building RDP file $temp = "`nfull address:s:" + $Entry.IP switch ($resolution) { "Console" { $temp += "`nscreen mode id:i:1" $temp += "`ndesktopwidth:i:1024" $temp += "`ndesktopheight:i:768" $temp += "`nusername:s:" + $Entry.USER $temp += "`npassword 51:b:" + $Entry.PASS $temp += "`nadministrative session:i:1" } "Fullscreen" { $temp += "`nscreen mode id:i:2" $temp += "`nusername:s:" + $Entry.USER $temp += "`npassword 51:b:" + $Entry.PASS } "Widescreen" { $temp += "`nscreen mode id:i:1" $temp += "`ndesktopwidth:i:1152" $temp += "`ndesktopheight:i:720" $temp += "`nusername:s:" + $Entry.USER $temp += "`npassword 51:b:" + $Entry.PASS } "Docked" { $temp += "`nscreen mode id:i:1" $temp += "`ndesktopwidth:i:1152" $temp += "`ndesktopheight:i:864" $temp += "`nusername:s:" + $Entry.USER $temp += "`npassword 51:b:" + $Entry.PASS } } $temp | out-file $FileName write-host $temp get-content template_bottom.txt >> $FileName } }

Related posts:

Save Hashed Password in RDP file

Create multiple RDP files with Powershell

Change Windows forgotten password with KonBoot

Auto Grow DPM Protection Groups by Percentage Thresholds

Nerd — Tue, 20 Jan 2009 19:04:00 +0000

Managing many DPM servers can turn into quite a time consuming activity, especially when it comes to allocating more disk space to Data Sources. The Ctrl-P DPM blog has a real simple auto-grow script on their site, but I personally have had issues with it, as have many others on the Net. It is also rather lacking in “bells and whistles” but for an everyday DPM admin, it sure would make life easier. In my quest for ways to make my job easier, I found this absolutely AWESOME script that Owen Clashing wrote on his blog.

#This DPM powershell script helps automate the growing of replica and shadow copy volumes which need to be grown.param([string] $DPMServerName, [string] $Mode, [int] $ReplicaThreshold, [int] $ReplicaGrowBy, [int] $RecoveryPointThreshold, [int] $RecoveryPointGrowBy) ###### Define variables for default values$DefaultDPMServerName = $env:COMPUTERNAME # Assumes that the current computer is the DPM server$DefaultMode = "A"$DefaultReplicaThreshold = 90$DefaultReplicaGrowBy = 5$DefaultShadowCopyThreshold = 90$DefaultShadowCopyGrowBy = 5###### function Usage(){ write-host write-host "Usage::" write-host "AutoGrowByPercentWithDefaults.ps1" write-host "AutoGrowByPercentWithDefaults.ps1 -DPMServerName [DPMServername] -Mode [A|C]" write-host write-host "Run 'AutoGrowByPercentWithDefaults.ps1 -detailed' for detailed help" write-host write-host} if(("-?","-help") -contains $args[0]){ Usage exit 0} if(("-detailed") -contains $args[0]){ write-host write-host "Detailed Help : Use this script to automatically grow the replica and recovery point volume sizes" write-host "Parameters:" write-host "-DPMServerName [DPMServername] :: The name of the DPM server that is being targetted" write-host "-Mode [A|C] :: A - Audit only (make no disk allocation changes); C - Change disk allocations" write-host "-ReplicaThreshold [Replica Threshold %] :: Percentage usage above which disk space allocation for the replica volume will be triggered" write-host "-ReplicaGrowBy [Replica Grow By %] :: Percentage by which to grow the replica volume" write-host "-RecoveryPointThreshold [Recovery Point Threshold %] :: Percentage usage above which disk space allocation for the recovery point volume will be triggered" write-host "-RecoveryPointGrowBy [Recovery Point Grow By %] :: Percentage by which to grow the recovery point volume" write-host "Current default values:" write-host "-DPMServerName $DefaultDPMServerName" write-host "-Mode $DefaultMode" write-host "-ReplicaThreshold $DefaultReplicaThreshold" write-host "-ReplicaGrowBy $DefaultReplicaGrowBy" write-host "-RecoveryPointThreshold $DefaultShadowCopyThreshold" write-host "-RecoveryPointGrowBy $DefaultShadowCopyGrowBy" write-host exit 0} if(!$DPMServerName){ $DPMServerName = $DefaultDPMServerName} if(!$Mode){ $Mode = $DefaultMode}else{ if (($Mode -ne "A") -or ($Mode -ne "C")) { Usage exit 0 }} if(!$ReplicaThreshold){ $ReplicaThreshold = $DefaultReplicaThreshold} if(!$ReplicaGrowBy){ $ReplicaGrowBy = $DefaultReplicaGrowBy} # Note the inconsistency in the naming - Object model name Shadow Copy, GUI name Recovery Point# We use the GUI names in naming the parameters to keep it familiar for the casual user.if(!$RecoveryPointThreshold){ $ShadowCopyThreshold = $DefaultShadowCopyThreshold}else{ $ShadowCopyThreshold = $RecoveryPointThreshold} if(!$RecoveryPointGrowBy){ $ShadowCopyGrowBy = $DefaultShadowCopyGrowBy}else{ $ShadowCopyThreshold = $RecoveryPointGrowBy} switch ($Mode){ "A" { $ChangeHighlightColor = "Green" write-host "In audit mode - No changes will be made to the disk allocations" -foregroundcolor $ChangeHighlightColor } "C" { $ChangeHighlightColor = "Red" write-host "In change mode - Changes will be made to the disk allocations" -foregroundcolor $ChangeHighlightColor }} $dpmserver = Connect-DPMServer $DPMServerName if(!$dpmserver){ write-error "Unable to connect to $dpmservername" exit 1} $PGList = @(Get-ProtectionGroup $DPMServerName) foreach($PG in $PGList){ # Use a modifiable protection group only if we are in change mode # A non-modifiable protection group object is significantly faster if ($Mode -eq "C") { $MPG = Get-ModifiableProtectionGroup $PG } else {
$MPG = $PG } $dslist=@(get-datasource $MPG) foreach ($ds in $dslist) { $ReplicaUsedPercent = ($ds.ReplicaUsedSpace/$ds.ReplicaSize) $ShadowCopyUsedPercent = ($ds.ShadowCopyUsedSpace/$ds.ShadowCopyAreaSize) "------------------------------------------------------------------------" #"Protection Group: $PG.Name" "$ds" # $ds.ReplicaSize = -1 when there is no replica component to the backup # Only process if there is replica disk space allocated if ($ds.ReplicaSize -ne -1) { "Replica Used % : {0:P2}" -f $ReplicaUsedPercent if($ReplicaUsedPercent -gt $ReplicaThreshold/100) { $ReplicaGrowByActual = ($ReplicaGrowBy/100)*$ds.ReplicaSize $NewReplicaSize = $ds.ReplicaSize + $ReplicaGrowByActual "Replica Grow % : {0:P2}" -f $($ReplicaGrowBy/100) write-host $("Replica Grow Actual (GB) : {0:N2}" -f $($ReplicaGrowByActual/1GB)) -foregroundcolor $ChangeHighlightColor "Replica New Total (GB) : {0:N2}" -f $($NewReplicaSize/1GB) if ($Mode -eq "C") { Set-DatasourceDiskAllocation -Manual -Datasource $ds -ProtectionGroup $MPG -ReplicaArea $NewReplicaSize } } else { "Replica Grow % : 0.00 %" "Replica Grow Actual (GB) : 0.00" "Replica New Total (GB) : {0:N2}" -f $(($ds.ReplicaSize)/1GB) } } else { "No disk space allocated for replica" } # $ds.ShadowCopyAreaSize = -1 when there is no shadow copy component to the backup # Only process if there is shadow copy disk space allocated if ($ds.ShadowCopyAreaSize -ne -1) { "Recovery Point Used % : {0:P2}" -f $ShadowCopyUsedPercent if($ShadowCopyUsedPercent -gt $ShadowCopyThreshold/100) { $ShadowCopyGrowByActual = ($ShadowCopyGrowBy/100)*$ds.ShadowCopyAreaSize $NewShadowCopySize = $ds.ShadowCopyAreaSize + $ShadowCopyGrowByActual "Recovery Point Grow % : {0:P2}" -f $($ShadowCopyGrowBy/100) write-host $("Recovery Point Grow Actual (GB): {0:N2}" -f $($ShadowCopyGrowByActual/1GB)) -foregroundcolor $ChangeHighlightColor "Recovery Point New Total (GB) : {0:N2}" -f $($NewShadowCopySize/1GB) if ($Mode -eq "C") { Set-DatasourceDiskAllocation -Manual -Datasource $ds -ProtectionGroup $MPG -ShadowCopyArea $NewShadowCopySize } } else { "Recovery Point Grow % : 0.00 %" "Recovery Point Grow Actual (GB): 0.00" "Recovery Point New Total (GB) : {0:N2}" -f $($ds.ShadowCopyAreaSize/1GB) } } else { "No disk space allocated for recovery point" } } # Update the protection group if we are in change mode if ($Mode -eq "C") { Set-ProtectionGroup $MPG }} Disconnect-DPMServer $DPMServerName "------------------------------------------------------------------------"

I LOVE the –MODE switch, allowing me to run the script, and see the results, without actually changing any disk allocations. I’ve added this script to the DPM servers that I manage, and have the task scheduler run it twice a day. No more failed jobs due to lack of disk space! Yeah!

Related posts:

Script to remove all datasources in Inactive Protection

Script – Create Recovery Points

Fix Error 3114 & Error 30216

Script – Create Recovery Points

Nerd — Fri, 16 Jan 2009 19:04:00 +0000

In the environment that I work, DPM protects the Exchange 2007 servers. I have only one Exchange server in each protection group. Each Exchange server has between 10-20 Storage Groups (or Data Sources). If I want to initiate a backup on the entire server, it is a pain to select each storage group, click Create Recovery Point, and select either Full or Incremental, then click Close.

The script below does all that for me. It connects to the DPM server, lists the Protection Groups, asks if you want to run an Express Full, or Incremental backup, then initiates the jobs for each Data Source in the Protection Group (each Storage Group on the Exchange Server).

# DPM 2007 Powershell Script# Script to initiate a Recovery Point for each Data Source in a Protection Group# Initial Script from Technet, but Modified to give more choices# Edited by Dan Burgess# nerd@EverydayNerd.com param([string] $dpmname, [string] $pgname, [string] $backupoption) # Clear the screencls#Get name of Localhost$CompStat = Get-WmiObject win32_computersystem$Localhst = $CompStat.Name # Notify that connected to Localhostwrite-host ""write-host "Script: Create-RecoveryPoint" -foregroundcolor Blue -backgroundcolor whitewrite-host ""write-host ""Write-host "Connected to Localhost: $Localhst" -foregroundcolor Blue -backgroundcolor whitewrite-host ""write-host "" # Set DPM Servername$dpmname = read-host "DPM Server Name (Enter for $Localhst):" if ($dpmname -eq "") { $dpmname = $Localhst write-host "Using Localhost $dpmname " -foregroundcolor green write-host "" write-host "" } # List Protection Groups on DPM server$pglist = get-protectiongroup -DPMServerName $dpmnamewrite-host "Protection Groups on $dpmname :" -foregroundcolor greenwrite-output $pglistwrite-host ""write-host "" #Enter name of Protection Group you wish to create Recovery Point$pgname = read-host "Enter Protection Group Name:"write-host ""write-host "" #List choices for JobChoice1 Variablewrite-host "1: Express Full"write-host "2: Incremental"write-host "" $JobChoice1 = read-host "Enter Backup type - 1 or 2 [Default is 1: Express Full]:" switch ($JobChoice1) { 1 { $backupoption = 'ExpressFull' } 2 { $backupoption = 'Incremental' }default { $backupoption = 'ExpressFull' } }write-host ""Write-host "You selected $backupoption" -foregroundcolor Blue -backgroundcolor whitewrite-host "" trap{"Error in execution... $_";break} if($clipg -eq $abc) { write-host "" Throw "No ProtectionGroup found" write-host "" } else { write-host "" write-host "Getting DataSource from Protection Group $pgname..." -foregroundcolor green write-host "" # Create variable of each Datasource from Protection Group $backupds = @(Get-Datasource $clipg) # Run the Job for each DataSource in Protection Group foreach ($ds in $backupds) { write-host "" write-host "Creating Recovery point for $ds..." -foregroundcolor Blue -backgroundcolor white write-host "" $job = New-RecoveryPoint -Datasource $ds -Disk -BackupType $backupoption $jobtype = $job.jobtype Write-host "$jobtype Job has been triggerred..." -foregroundcolor green } }}

I’ve been playing around with this script for a while, and there is more that I want to do to it, but I figured I’d share it, and hope it helps someone out. I’d love some input on how to make the script better!

One thing I’d really like to do, but have not been able to figure it out yet, is have a status update at the end, updating every 10 seconds showing the Server name, PGname, Status, and HasCompleted – until True. Just a thought… would save me from having to RDP into all the DPM servers…

Related posts:

Auto Grow DPM Protection Groups by Percentage Thresholds

Script to remove all datasources in Inactive Protection

Powershell Script: Display Exchange 2007 Queue by Site

Powershell Script to list all Cluster Active Nodes

Nerd — Fri, 09 Jan 2009 19:54:00 +0000

If you have a medium to large infrastructure, it is helpful to know what node of your Exchange Clusters is the active node. This can be done manually, but it is much easier if done with the following script:

$Clusters = Get-MailboxServer | Where-Object { $_.RedundantMachines } | Select Name

foreach ($cluster in $clusters) {

Get-ClusteredMailboxServerStatus -identity $Cluster.name | Select OperationalMachines,State

}

Related posts:

PowerShell: Move Windows Server 2008 Cluster Group

PowerShell: Drive Space Info from multiple systems

Exchange PowerShell Script: Get Mailbox Count by Database

Script to remove all datasources in Inactive Protection

Nerd — Thu, 25 Sep 2008 14:28:00 +0000

After I moved several protected servers from one DPM server to another, I had a LOT of exchange storage groups left in the Inactive Protection that I wanted to get rid of. Doing this manually was very time consuming, and lots of clicks. So, after a quick search, I found a script on the Ctrl P blog that does exactly what I needed to do!

Usage:

Remove-InactiveDatasource.ps1 -DPMServerName [DPMServername] -RemoveOption [Remove Options]

Run ‘Remove-InactiveDatasource.ps1 -detailed’ for detailed help

Attachment: Remove-InactiveDatasource.ps1

Related posts:

Auto Grow DPM Protection Groups by Percentage Thresholds

Script – Create Recovery Points

Script to Find Whitespace on all Exchange 2007 Servers

Create multiple RDP files with Powershell

Nerd — Sun, 14 Sep 2008 01:43:51 +0000

RDP – Remote Desktop Connection, or what we called back in the day, Terminal Services. Every system administrator uses it daily. At work, the team I work on has 145 servers that we are responsible for, and only a handful of them are in the same building as us (although we still remote into them as well).

This being said, I was getting tired of typing in the server’s name or IP address every time I needed to connect to it. I know Microsoft has an mmc for Remote Desktops, but I just don’t like the clunky way it has to be setup, plus, did I mention I had 145 to put in? Well, call me lazy, but I knew there had to be a way to script it – after all, a RDP file is nothing but some text (open a .rdp file with notepad – you’ll see!).

So, enough background, lets do some scripting! There are 3 files here: Powershell script, a CSV file, and a Text file.

First, the CSV File: It has 4 columns with the first row being the headers. Do not change row. Name this file RDPLIST.csv

ServerName,IP,Directory,USER FRIENDLYNAME,FQDNorIP,FOLDERNAME\SUBFOLDER,DOMAIN\USERNAME

Next, is the Text File. This contains other parameters that are going to be the same between every connection – such as enabling shared clipboard, 16bit colors, disable themes, etc. You can customize this to your liking (to get it just the way you want it, create an .rdp file, and edit it with notepad, and you will see a list similar to below). Name this file template_bottom.txt

audiomode:i:2 authentication level:i:0 autoreconnection enabled:i:1 bitmapcachepersistenable:i:1 compression:i:1 disable cursor setting:i:0 disable full window drag:i:1 disable menu anims:i:1 disable themes:i:1 disable wallpaper:i:1 displayconnectionbar:i:1 keyboardhook:i:2 redirectclipboard:i:1 redirectcomports:i:0 redirectdrives:i:0 redirectprinters:i:0 redirectsmartcards:i:0 session bpp:i:16 prompt for credentials:i:0 promptcredentialonce:i:1

Lastly, the Powershell script: Name this file CreateRDP.ps1

$List = Import-CSV RDPLIST.CSV $resolutions = ("Console","fullscreen","1024x768","1152x864") ForEach($Entry in $List) { ForEach($resolution in $resolutions) { # Prepend the destination directory info for RDP files $Dir = "..\" + $resolution + "\" + $Entry.Directory # Create new folder New-Item -Path $Dir -ItemType Directory -Force # Build the file name $FileName = $Dir + "\" + $Entry.ServerName + ".RDP" # Remove the old file Remove-Item $FileName -Force # Begin building RDP file $temp = "`nfull address:s:" + $Entry.IP switch ($resolution) { "Console" { $temp = $temp + "`nscreen mode id:i:1" $temp = $temp + "`ndesktopwidth:i:1024" $temp = $temp + "`ndesktopheight:i:768" $temp = $temp + "`nusername:s:" + $Entry.USER $temp = $temp + "`nadministrative session:i:1" } "Fullscreen" { $temp = $temp + "`nscreen mode id:i:2" $temp = $temp + "`nusername:s:" + $Entry.USER } "1024x768" { $temp = $temp + "`nscreen mode id:i:1" $temp = $temp + "`ndesktopwidth:i:1024" $temp = $temp + "`ndesktopheight:i:768" $temp = $temp + "`nusername:s:" + $Entry.USER } "1152x864" { $temp = $temp + "`nscreen mode id:i:1" $temp = $temp + "`ndesktopwidth:i:1152" $temp = $temp + "`ndesktopheight:i:864" $temp = $temp + "`nusername:s:" + $Entry.USER } } $temp | out-file $FileName write-host $temp get-content template_bottom.txt >> $FileName } }

Now, you need a folder structure:

Powershell_RDP

rdp

_script

Put all three files in the _script folder.

And just because I’m a nice guy, here’s a zip of the files and the correct folder structure. Just unzip, make your edits to the csv file, save and close it, and open PowerShell (as Administrator if using Vista) and navigate to the _Script folder. Once there, run the CreateRDP.ps1 (put a ./ in front of the filename)

Download Powershell_RDP.zip

Feel free to customize this script to your own liking! It’s a simple script, so it shouldn’t be too hard to mess with. It works like a CHARM!!! I created 290 RDP files in less than 30 seconds! Great thing is, it creates a separate folder structure for the different resolutions (I used 1024×768 & 1152×864 because my laptop is a widescreen, but when I’m docked, it’s a standard monitor).

One more tip, I made two new toolbars, and pushed them all the way over to the right of the taskbar, making a nifty little launcher!

Hope you enjoy this – I know I did! It took me longer to write this post than it did to get all my .RDP files!

[ UPDATE: Original Script was written by Aaron Dodd, just tweaked by me]

Related posts:

Save Password in .RDP File

Save Hashed Password in RDP file

Windows 7 Slow Remote Desktop (RDP) fix

Free E-Book: PowerShell

Nerd — Fri, 15 Jun 2007 14:56:00 +0000

Source: https://blogs.technet.com/chitpro-de

English version of Windows PowerShell course book available for download

Due to its great popularity, we have decided to translate the Windows PowerShell course book to English. The book gives you a short introduction with many exercises about the interactive part of Windows PowerShell as well as some hints how to use other objects like WMI, .NET or COM objects like Excel or Internet Explorer.
The book is available for free and you can share it with all your colleagues or friends if you leave it as it is. The books can be used with or without the demo files available at this blog as well.

Related posts:

Free e-Book: Introducing SQL Server 2008

PowerShell: Move Windows Server 2008 Cluster Group

PowerShell: Change PS Window Size on the fly