<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>itsolutionsdirect.com &#187; Powershell</title>
	<atom:link href="http://itsolutionsdirect.com/category/scripting/powershell/feed/" rel="self" type="application/rss+xml" />
	<link>http://itsolutionsdirect.com</link>
	<description>Exploring the technology of tommorow</description>
	<lastBuildDate>Mon, 06 Feb 2012 22:40:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Get-Hotfix&#8211;Retrieve hotfix information using Powershell</title>
		<link>http://itsolutionsdirect.com/get-hotfixretrieve-hotfix-information-using-powershell/435/</link>
		<comments>http://itsolutionsdirect.com/get-hotfixretrieve-hotfix-information-using-powershell/435/#comments</comments>
		<pubDate>Sun, 27 Mar 2011 06:20:12 +0000</pubDate>
		<dc:creator>neil</dc:creator>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Scripting]]></category>

		<guid isPermaLink="false">http://itsolutionsdirect.com/get-hotfixretrieve-hotfix-information-using-powershell/435/</guid>
		<description><![CDATA[Recently I wanted to verify that I had a certain hotfix installed on my server. I thought i could see if there was a nice and easy way in Powershell to do this and there was. The cmdlet get-hotfix will retrieve the information you need. PS C:\Users\Administrator&#62; Get-HotFix Source&#160;&#160;&#160;&#160;&#160;&#160;&#160; Description&#160;&#160;&#160;&#160;&#160; HotFixID&#160;&#160;&#160;&#160;&#160; InstalledBy&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; InstalledOn &#8212;&#8212;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &#8212;&#8212;&#8212;&#8211;&#160;&#160;&#160;&#160;&#160; [...]]]></description>
		<wfw:commentRss>http://itsolutionsdirect.com/get-hotfixretrieve-hotfix-information-using-powershell/435/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Test user &#8216;extest_b648a1a700f64&#8242; isn&#8217;t accessible when running test-owaconnectivity</title>
		<link>http://itsolutionsdirect.com/test-user-extest_b648a1a700f64-isnt-accessible-when-running-test-owaconnectivity/363/</link>
		<comments>http://itsolutionsdirect.com/test-user-extest_b648a1a700f64-isnt-accessible-when-running-test-owaconnectivity/363/#comments</comments>
		<pubDate>Sun, 31 Oct 2010 11:31:04 +0000</pubDate>
		<dc:creator>neil</dc:creator>
				<category><![CDATA[Exchange 2010]]></category>
		<category><![CDATA[Powershell]]></category>

		<guid isPermaLink="false">http://itsolutionsdirect.com/?p=363</guid>
		<description><![CDATA[I was recently playing about in Exchange 2010 in preparation for my exam in a few days time and I noticed i was getting an error when i ran the test-owaconnectivity commandlet. I error message i was recieving was: WARNING: Test user &#8216;extest_b648a1a700f64&#8242; isn&#8217;t accessible, so this cmdlet won&#8217;t be able to test Client Access [...]]]></description>
		<wfw:commentRss>http://itsolutionsdirect.com/test-user-extest_b648a1a700f64-isnt-accessible-when-running-test-owaconnectivity/363/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Powershell Survival Guide</title>
		<link>http://itsolutionsdirect.com/powershell-survival-guide/357/</link>
		<comments>http://itsolutionsdirect.com/powershell-survival-guide/357/#comments</comments>
		<pubDate>Sun, 18 Jul 2010 19:21:38 +0000</pubDate>
		<dc:creator>neil</dc:creator>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Scripting]]></category>

		<guid isPermaLink="false">http://itsolutionsdirect.com/powershell-survival-guide/357/</guid>
		<description><![CDATA[There is a really nice article on the TechNet Wiki which has a nice list of Powershell URL’s to help you learn and master powershell You can view it here: http://social.technet.microsoft.com/wiki/contents/articles/windows-powershell-survival-guide.aspx]]></description>
		<wfw:commentRss>http://itsolutionsdirect.com/powershell-survival-guide/357/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Enter Exchange 2007 Product Key using powershell</title>
		<link>http://itsolutionsdirect.com/enter-exchange-2007-product-key-using-powershell/334/</link>
		<comments>http://itsolutionsdirect.com/enter-exchange-2007-product-key-using-powershell/334/#comments</comments>
		<pubDate>Sun, 07 Mar 2010 10:13:12 +0000</pubDate>
		<dc:creator>neil</dc:creator>
				<category><![CDATA[Exchange Server 2007]]></category>
		<category><![CDATA[Powershell]]></category>

		<guid isPermaLink="false">http://itsolutionsdirect.com/enter-exchange-2007-product-key-using-powershell/334/</guid>
		<description><![CDATA[Just a quick post on how to enter the product key using the exchange management shell: set-exchangeserver -Identity servername -ProductKey XXXX-XXXXX-XXXXX-XXXX-XXXXX]]></description>
		<wfw:commentRss>http://itsolutionsdirect.com/enter-exchange-2007-product-key-using-powershell/334/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>End a process in powershell</title>
		<link>http://itsolutionsdirect.com/end-a-process-in-powershell/311/</link>
		<comments>http://itsolutionsdirect.com/end-a-process-in-powershell/311/#comments</comments>
		<pubDate>Sat, 23 Jan 2010 08:40:38 +0000</pubDate>
		<dc:creator>neil</dc:creator>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Scripting]]></category>

		<guid isPermaLink="false">http://itsolutionsdirect.com/end-a-process-in-powershell/311/</guid>
		<description><![CDATA[I recently encountered a problem where i wanted to end multiple processes that were running. In my quest to learn powershell I had a look to see if could do it via this method. It was a simple one line cmdlet: stop-process -name iexplore Simples! NAME &#160;&#160;&#160; Stop-Process SYNOPSIS &#160;&#160;&#160; Stops one or more running [...]]]></description>
		<wfw:commentRss>http://itsolutionsdirect.com/end-a-process-in-powershell/311/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Retrieve a list of all powershell cmdlets</title>
		<link>http://itsolutionsdirect.com/retrieve-a-list-of-all-powershell-cmdlets/307/</link>
		<comments>http://itsolutionsdirect.com/retrieve-a-list-of-all-powershell-cmdlets/307/#comments</comments>
		<pubDate>Sat, 09 Jan 2010 19:58:53 +0000</pubDate>
		<dc:creator>neil</dc:creator>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Scripting]]></category>

		<guid isPermaLink="false">http://itsolutionsdirect.com/retrieve-a-list-of-all-powershell-cmdlets/307/</guid>
		<description><![CDATA[If you want a list of all powershell cmdlets run this command. I have exported it to a text file &#160; Get-Command &#124; Format-List]]></description>
		<wfw:commentRss>http://itsolutionsdirect.com/retrieve-a-list-of-all-powershell-cmdlets/307/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing Exchange Administrators with Powershell</title>
		<link>http://itsolutionsdirect.com/managing-exchange-administrators-with-powershell/305/</link>
		<comments>http://itsolutionsdirect.com/managing-exchange-administrators-with-powershell/305/#comments</comments>
		<pubDate>Tue, 05 Jan 2010 21:18:56 +0000</pubDate>
		<dc:creator>neil</dc:creator>
				<category><![CDATA[Exchange Server 2007]]></category>
		<category><![CDATA[Powershell]]></category>

		<guid isPermaLink="false">http://itsolutionsdirect.com/managing-exchange-administrators-with-powershell/305/</guid>
		<description><![CDATA[To view Exchange Administrators with powershell we can use the get-exchangeadministrator commandlet. This will tell me the current exchange administrator groups in the domain. Example below is: [PS] C:\Windows\system32&#62;get-exchangeadministrator &#124; format-list Identity : EXCHANGELAB.LOCAL/Users/Administrator Scope&#160;&#160;&#160; : Organization wide Role&#160;&#160;&#160;&#160; : OrgAdmin Identity : EXCHANGELAB.LOCAL/Microsoft Exchange Security Groups/Exchange Organi &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; zation Administrators Scope&#160;&#160;&#160; : Organization wide [...]]]></description>
		<wfw:commentRss>http://itsolutionsdirect.com/managing-exchange-administrators-with-powershell/305/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Retrieve information about an Exchange 2007 Server</title>
		<link>http://itsolutionsdirect.com/retrieve-information-about-an-exchange-2007-server/304/</link>
		<comments>http://itsolutionsdirect.com/retrieve-information-about-an-exchange-2007-server/304/#comments</comments>
		<pubDate>Tue, 05 Jan 2010 20:18:27 +0000</pubDate>
		<dc:creator>neil</dc:creator>
				<category><![CDATA[Exchange Server 2007]]></category>
		<category><![CDATA[Powershell]]></category>

		<guid isPermaLink="false">http://itsolutionsdirect.com/retrieve-information-about-an-exchange-2007-server/304/</guid>
		<description><![CDATA[If you want to retrieve information about an exchange server you can use the GET-EXCHANGESERVER commandlet. This will retrieve information like the computer name, OU location, site name etc etc. The syntax of the command is: SYNTAX &#160;&#160;&#160; Get-ExchangeServer [-Identity &#60;ServerIdParameter&#62;] [-DomainController &#60;Fqdn &#160;&#160;&#160; &#62;] [-Status &#60;SwitchParameter&#62;] [&#60;CommonParameters&#62;] &#160;&#160;&#160; Get-ExchangeServer -Domain &#60;Fqdn&#62; [-DomainController &#60;Fqdn&#62;] [-Status [...]]]></description>
		<wfw:commentRss>http://itsolutionsdirect.com/retrieve-information-about-an-exchange-2007-server/304/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Retrieve time zone information through Powershell</title>
		<link>http://itsolutionsdirect.com/retrieve-time-zone-information-through-powershell/295/</link>
		<comments>http://itsolutionsdirect.com/retrieve-time-zone-information-through-powershell/295/#comments</comments>
		<pubDate>Fri, 27 Nov 2009 15:38:22 +0000</pubDate>
		<dc:creator>neil</dc:creator>
				<category><![CDATA[Powershell]]></category>

		<guid isPermaLink="false">http://itsolutionsdirect.com/retrieve-time-zone-information-through-powershell/295/</guid>
		<description><![CDATA[For this we can use get-wmiobject to query WMI: get-wmiobject -class win32_timezone &#124; format-list Bias&#160;&#160;&#160;&#160;&#160; : 0 SettingID : Caption&#160;&#160; : (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London]]></description>
		<wfw:commentRss>http://itsolutionsdirect.com/retrieve-time-zone-information-through-powershell/295/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing AD with Powershell</title>
		<link>http://itsolutionsdirect.com/managing-ad-with-powershell-2/283/</link>
		<comments>http://itsolutionsdirect.com/managing-ad-with-powershell-2/283/#comments</comments>
		<pubDate>Fri, 13 Nov 2009 14:55:55 +0000</pubDate>
		<dc:creator>neil</dc:creator>
				<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Windows Server 2008 R2]]></category>

		<guid isPermaLink="false">http://itsolutionsdirect.com/managing-ad-with-powershell-2/283/</guid>
		<description><![CDATA[Windows Server 2008 R2 gives us the ability to manage Active Directory with Powershell. Here is a really nice poster for all the powershell commandlets for AD downloaded from here: http://blogs.msdn.com/adpowershell/archive/2009/03/05/active-directory-powershell-overview.aspx]]></description>
		<wfw:commentRss>http://itsolutionsdirect.com/managing-ad-with-powershell-2/283/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.660 seconds -->

