Windows Powershell has a built in web request module that you can use to test/check the availability of website URL(s).
The full script to do this is below;
[string] $url = "http://www.google.com"
[net.httpWebRequest] $req = [net.webRequest]::create($url)
$req.method = "HEAD"
[net.httpWebResponse] $res = $req.getresponse()
The first line is self explanatory - simply put in the full URL for the website you wish to check. In this example we will be checking http://www.google.com
[string] $url = "http://www.google.com"
The second line is where we create the actual web request instance in Powershell - under the $req variable
[net.httpWebRequest] $req = [net.webRequest]::create($url)
On the third line, we change the request method to be "HEAD" which means that only header information for the requested URL is retrieved. This speeds up the web request process as it does not pull all the data from the web URL - only the header information. If you leave this line out, the default method is "GET".
$req.method = "HEAD"
On the last line we actually submit the web request, and store the response in the $res variable
[net.httpWebResponse] $res = $req.getresponse()
For a successful web request, the response should look something like this:
IsMutuallyAuthenticated : False
Cookies : {}
Headers : {Cache-Control, Content-Type, Date, Expires...}
ContentLength : -1
ContentEncoding :
ContentType : text/html; charset=ISO-8859-1
CharacterSet : ISO-8859-1
Server : gws
LastModified : 28/03/2014 10:24:19 AM
StatusCode : OK
StatusDescription : OK
ProtocolVersion : 1.1
ResponseUri : http://www.google.com.au/?gfe_rd=cr&ei=I7M0U5P_BenC8gfRvIHADg
Method : HEAD
IsFromCache : False
Based on this, you could check the statuscode or statusdescription properties of $res to make sure the value matches "OK".
Alternatively, if you enter an invalid URL for a website that doesn't exist, you will get an error, and the value of $res will be $null. The error you get will be something along the lines of;
Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (502) Bad Gateway."
At line:4 char:46
+ [net.httpWebResponse] $res = $req.getresponse <<<< ()
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException
Friday 28 March 2014
Wednesday 26 March 2014
Get Folder Size (including subfolders) with Powershell
The method for obtaining the size of all items within a folder using Windows Powershell is unfortunately not as straight forward as it probably should be. The method outlined below is very useful for querying multiple folders to determine the size of all items inside, including all subfolders and files.
$dir = "C:\temp"
$totaldirsize = (get-childitem $dir -recurse -force | measure-object -property length -sum)
The first variable sets the directory that we wish to query - in this example it is C:\temp.
Next, we use a get-childitem to query the directory. The -recurse and -force switches mean that all sub directories and files are also included. We then pipe the results to measure-object and calculate the length of each child item (which is actually the size in bytes) and use the -sum switch to add them all up.
If you run the above command, and then look at the $totaldirsize variable, you will see something like below;
PS C:\> $totaldirsize
Count : 38
Average :
Sum : 51652089
Maximum :
Minimum :
Property : length
So from this we can see there are 38 items in total in the C:\temp directory, and the sum of all files is 51652089 bytes. To make this more useful, we can easily convert this value to KB, MB or GB
$mbsize = $totaldirsize.sum / 1MB
If we now look at $mbsize, we'll usually have an integer with a large number of decimal places. In this example, the result I got was 49.2592706680298. So as a final step, I'd like to round this number to 2 decimal places
$mbsize2 = "{0:N2}" -f $mbsize
Now if we look at the value of $mbsize2, the result is 49.26.
You can change the 2 in {0:N2} to any other digit to round the number to that many places after the decimal point.
$dir = "C:\temp"
$totaldirsize = (get-childitem $dir -recurse -force | measure-object -property length -sum)
The first variable sets the directory that we wish to query - in this example it is C:\temp.
Next, we use a get-childitem to query the directory. The -recurse and -force switches mean that all sub directories and files are also included. We then pipe the results to measure-object and calculate the length of each child item (which is actually the size in bytes) and use the -sum switch to add them all up.
If you run the above command, and then look at the $totaldirsize variable, you will see something like below;
PS C:\> $totaldirsize
Count : 38
Average :
Sum : 51652089
Maximum :
Minimum :
Property : length
So from this we can see there are 38 items in total in the C:\temp directory, and the sum of all files is 51652089 bytes. To make this more useful, we can easily convert this value to KB, MB or GB
$mbsize = $totaldirsize.sum / 1MB
If we now look at $mbsize, we'll usually have an integer with a large number of decimal places. In this example, the result I got was 49.2592706680298. So as a final step, I'd like to round this number to 2 decimal places
$mbsize2 = "{0:N2}" -f $mbsize
Now if we look at the value of $mbsize2, the result is 49.26.
You can change the 2 in {0:N2} to any other digit to round the number to that many places after the decimal point.
Working with Windows Services in Powershell
We can use the get-wmiobject method in order to retrieve properties of windows services on local or remote servers.
The query below is an example on how to get the properties of the Print Spooler service on a local machine (ie. the same machine that the script is being executed on)
To get the "Service Name" of a windows service, go to services.msc, select a service, open it's properties (right click > Properties) and look at the "Service Name" at the top.
$serviceprops = get-wmiobject -class win32_service -filter "name='Spooler'"
If we then run $serviceprops we get the following information;
ExitCode : 0
Name : Spooler
ProcessId : 1628
StartMode : Auto
State : Running
Status : OK
This information could therefore be used to check the respective windows process ID, start mode, state and status of a service
The query below is an example on how to get the properties of the Print Spooler service on a remote machine (server1)
$serviceprops = get-wmiobject -computername "server1" -class win32_service -filter "name='Spooler'"
As you can see, the command is mostly the same, we have simply added the argument "-computername "server1"" to make the get-wmiobject query run on the remote server.
We can then take this one step further and perform an action (aka method) on a service, such as starting or stopping it. To view the available methods for the service, run a get-member on the $serviceprops variable;
$serviceprops | get-member
You will then see a list of available methods (and properties) for the variable.
Two of the most common methods for a service would be to start or stop the service. We simply append the respective methods onto the end of the $serviceprops variable (after it has run the get-wmiobject query above to get the service properties).
To start a service;
$serviceprops.startservice()
To stop a service;
$serviceprops.stopservice()
The query below is an example on how to get the properties of the Print Spooler service on a local machine (ie. the same machine that the script is being executed on)
To get the "Service Name" of a windows service, go to services.msc, select a service, open it's properties (right click > Properties) and look at the "Service Name" at the top.
$serviceprops = get-wmiobject -class win32_service -filter "name='Spooler'"
If we then run $serviceprops we get the following information;
ExitCode : 0
Name : Spooler
ProcessId : 1628
StartMode : Auto
State : Running
Status : OK
This information could therefore be used to check the respective windows process ID, start mode, state and status of a service
The query below is an example on how to get the properties of the Print Spooler service on a remote machine (server1)
$serviceprops = get-wmiobject -computername "server1" -class win32_service -filter "name='Spooler'"
As you can see, the command is mostly the same, we have simply added the argument "-computername "server1"" to make the get-wmiobject query run on the remote server.
We can then take this one step further and perform an action (aka method) on a service, such as starting or stopping it. To view the available methods for the service, run a get-member on the $serviceprops variable;
$serviceprops | get-member
You will then see a list of available methods (and properties) for the variable.
Two of the most common methods for a service would be to start or stop the service. We simply append the respective methods onto the end of the $serviceprops variable (after it has run the get-wmiobject query above to get the service properties).
To start a service;
$serviceprops.startservice()
To stop a service;
$serviceprops.stopservice()
Subscribe to:
Posts (Atom)