﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>System Center Scripting with Powershell</title>
    <description>System Center Scripting with Powershell</description>
    <link>http://powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/BlogId/9/Default.aspx</link>
    <language>en-US</language>
    <managingEditor>kcolby@securevantage.com</managingEditor>
    <webMaster>do-not-reply@powershellcommunity.org</webMaster>
    <pubDate>Tue, 06 Jan 2009 10:59:13 GMT</pubDate>
    <lastBuildDate>Tue, 06 Jan 2009 10:59:13 GMT</lastBuildDate>
    <docs>http://backend.userland.com/rss</docs>
    <generator>Blog RSS Generator Version 3.4.0.39853</generator>
    <item>
      <title>Initial steps with Scripting System Center Configuration Manager</title>
      <description>I've begun delving into the ConfigMgr SDK to start writing some scripts for it.  My primary interest is in working on a set of Resource Kit tools for Desired Configuration Manager.  I've found that everything I've looked so far has been in WMI.  Which is both a blessing and a curse. It certainly makes it easier to access from Powershell's native Get-WMIObject Cmdlet.</description>
      <link>http://powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/31/Default.aspx</link>
      <author>kcolby@securevantage.com</author>
      <guid isPermaLink="true">http://powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=31</guid>
      <pubDate>Mon, 12 Nov 2007 15:14:12 GMT</pubDate>
      <trackback:ping>http://powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=31</trackback:ping>
    </item>
  </channel>
</rss>