<?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>PowerShell.nu &#187; Client Management</title>
	<atom:link href="http://www.powershell.nu/tag/client-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.powershell.nu</link>
	<description>Windows PowerShell</description>
	<lastBuildDate>Thu, 08 Dec 2011 14:46:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>PowerShell &amp; SCCM &#8211; Client</title>
		<link>http://www.powershell.nu/2010/10/07/powershell-sccm-client/</link>
		<comments>http://www.powershell.nu/2010/10/07/powershell-sccm-client/#comments</comments>
		<pubDate>Thu, 07 Oct 2010 20:27:09 +0000</pubDate>
		<dc:creator>Niklas Goude</dc:creator>
				<category><![CDATA[Client Management]]></category>
		<category><![CDATA[SCCM 2007]]></category>
		<category><![CDATA[WMI]]></category>

		<guid isPermaLink="false">http://www.powershell.nu/?p=1051</guid>
		<description><![CDATA[In the previous posts we created a new Package containing Windows PowerShell and distributed it to all all XP clients in the &#8220;All Windows XP Systems&#8221; Collection. Assuming that everything went OK the package should have been distributed and installed on the Client. With Windows PowerShell installed on the Client we can manage the SMS [...]]]></description>
		<wfw:commentRss>http://www.powershell.nu/2010/10/07/powershell-sccm-client/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Managing Local Groups through PowerShell</title>
		<link>http://www.powershell.nu/2009/07/06/managing-local-groups-through-powershell/</link>
		<comments>http://www.powershell.nu/2009/07/06/managing-local-groups-through-powershell/#comments</comments>
		<pubDate>Mon, 06 Jul 2009 14:46:26 +0000</pubDate>
		<dc:creator>Niklas Goude</dc:creator>
				<category><![CDATA[Client Management]]></category>

		<guid isPermaLink="false">http://www.powershell.nu/?p=781</guid>
		<description><![CDATA[When managing Local Groups through PowerShell, we can use the [ADSI] type adapter. Starting off, We have to connect to the Local Group that we want to modify. PS > $ComputerName = $env:COMPUTERNAME PS > $Group = "Administrators" PS > $LocalGroup = [adsi]"WinNT://$computerName/$Group,group" PS > $LocalGroup distinguishedName : Path : WinNT://Computer01/Administrators,group Now that we&#8217;re connected [...]]]></description>
		<wfw:commentRss>http://www.powershell.nu/2009/07/06/managing-local-groups-through-powershell/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing Local Accounts through PowerShell</title>
		<link>http://www.powershell.nu/2009/07/06/managing-local-accounts-through-powershell/</link>
		<comments>http://www.powershell.nu/2009/07/06/managing-local-accounts-through-powershell/#comments</comments>
		<pubDate>Mon, 06 Jul 2009 13:27:07 +0000</pubDate>
		<dc:creator>Niklas Goude</dc:creator>
				<category><![CDATA[Client Management]]></category>

		<guid isPermaLink="false">http://www.powershell.nu/?p=775</guid>
		<description><![CDATA[When managing Local Accounts through PowerShell, it&#8217;s possible to use the [ADSI] type adapter. Starting off, let&#8217;s look at how to connect to the Local Computer. PS > $ComputerName = $env:COMPUTERNAME PS > $Computer = [adsi]"WinNT://$ComputerName" PS > $Computer distinguishedName : Path : WinNT://Computer01 Now that we have a variable holding the reference to our [...]]]></description>
		<wfw:commentRss>http://www.powershell.nu/2009/07/06/managing-local-accounts-through-powershell/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Get-PrinterInformation</title>
		<link>http://www.powershell.nu/2009/06/18/get-printerinformation/</link>
		<comments>http://www.powershell.nu/2009/06/18/get-printerinformation/#comments</comments>
		<pubDate>Thu, 18 Jun 2009 18:41:04 +0000</pubDate>
		<dc:creator>Niklas Goude</dc:creator>
				<category><![CDATA[Client Management]]></category>
		<category><![CDATA[WMI]]></category>

		<guid isPermaLink="false">http://www.powershell.nu/?p=762</guid>
		<description><![CDATA[Gathering Printerinformation can be done through WMI. Win32_Printer contains information about printers that are used by a computer and Win32_PrinterDriver contains information about the printer drivers. We can combine these 2 WMI classes and retrieve information about both the printer and it&#8217;s drivers. This script checks for the following properties: Computer : Client1 Name : [...]]]></description>
		<wfw:commentRss>http://www.powershell.nu/2009/06/18/get-printerinformation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Set Folder Permissions using a PowerShell script</title>
		<link>http://www.powershell.nu/2009/02/13/set-folder-permissions-using-a-powershell-script/</link>
		<comments>http://www.powershell.nu/2009/02/13/set-folder-permissions-using-a-powershell-script/#comments</comments>
		<pubDate>Fri, 13 Feb 2009 13:15:45 +0000</pubDate>
		<dc:creator>Niklas Goude</dc:creator>
				<category><![CDATA[Client Management]]></category>
		<category><![CDATA[ACL]]></category>

		<guid isPermaLink="false">http://www.powershell.nu/?p=430</guid>
		<description><![CDATA[A common Admin task is Setting permissions on folders for new Users or Groups. doing this manually can be pretty boring and timeconsuming. This script automates these steps through PowerShell. The parameters that I&#8217;ve added to the script are: -Path Folder to Create (Required) -User User who should have access (Required) -Permission Specify Permission for [...]]]></description>
		<wfw:commentRss>http://www.powershell.nu/2009/02/13/set-folder-permissions-using-a-powershell-script/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
		<item>
		<title>Client Inventory through PowerShell</title>
		<link>http://www.powershell.nu/2009/02/05/client-inventory-through-powershell/</link>
		<comments>http://www.powershell.nu/2009/02/05/client-inventory-through-powershell/#comments</comments>
		<pubDate>Thu, 05 Feb 2009 20:23:24 +0000</pubDate>
		<dc:creator>Niklas Goude</dc:creator>
				<category><![CDATA[Client Management]]></category>

		<guid isPermaLink="false">http://www.powershell.nu/?p=409</guid>
		<description><![CDATA[There are numerous ways of doing a Client Inventory in the Windows environment. You can use various Microsoft technologies to accomplish this, you can collect information stored in the registry or you can retrieve information through WMI. In this post, I&#8217;m going to show how to do this through WMI and PowerShell. WMI is a [...]]]></description>
		<wfw:commentRss>http://www.powershell.nu/2009/02/05/client-inventory-through-powershell/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

