<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Active Directory Powershell Blog</title><link>http://blogs.msdn.com/adpowershell/default.aspx</link><description>&lt;strong&gt;Pipelining AD – one object at a time&lt;/strong&gt;&lt;br/&gt;
&lt;img src="http://61fi7g.bay.livefilestore.com/y1p6cx3yrvnylzPXILBdIFsfLHdUfXHSamX_FUAny1auenFFluWBtvbZ2G8WEbMX46qyMnDnpn6DJUjg7ZD2WIvyQ/ADPSBlogLogo.PNG" alt="The Active Directory Powershell Blog"/&gt;</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Redirecting Well Known Containers (CN=Users; CN=Computers etc.)</title><link>http://blogs.msdn.com/adpowershell/archive/2009/11/25/redirecting-well-known-containers-cn-users-cn-computers-etc.aspx</link><pubDate>Wed, 25 Nov 2009 22:03:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9928827</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9928827.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9928827</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9928827</wfw:comment><description>In this post we will see the Powershell way of redirecting Users and Computers containers (i.e. Powershell equivalent of tools: redirusr.exe and redircmp.exe ). By now you might know that you can use Get-ADDomain cmdlet for viewing the well-known containers...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/11/25/redirecting-well-known-containers-cn-users-cn-computers-etc.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9928827" width="1" height="1"&gt;</description><enclosure url="http://blogs.msdn.com/adpowershell/attachment/9928827.ashx" length="3348" type="application/octet-stream" /><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Script/default.aspx">Script</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ScriptSnippet/default.aspx">ScriptSnippet</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/WKGUID/default.aspx">WKGUID</category></item><item><title>Accessing Replication Metadata using ADPowerShell</title><link>http://blogs.msdn.com/adpowershell/archive/2009/11/01/accessing-replication-metadata-using-adpowershell.aspx</link><pubDate>Sun, 01 Nov 2009 09:50:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9915814</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9915814.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9915814</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9915814</wfw:comment><description>Metadata associated with Active Directory Replication is exposed in AD via many constructed attributes. Some of these metadata attributes come in pairs of binary blob &amp;amp; xml representation of the metadata element. Constructed Replication XML Metadata...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/11/01/accessing-replication-metadata-using-adpowershell.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9915814" width="1" height="1"&gt;</description><enclosure url="http://blogs.msdn.com/adpowershell/attachment/9915814.ashx" length="3510" type="application/octet-stream" /></item><item><title>View/Configure Protected ACL and Fixing Broken Inheritance</title><link>http://blogs.msdn.com/adpowershell/archive/2009/10/22/view-configure-protected-acl-and-fixing-broken-inheritance.aspx</link><pubDate>Thu, 22 Oct 2009 19:33:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9911629</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9911629.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9911629</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9911629</wfw:comment><description>ACL inheritance is one of key concept in Active Directory delegation of control. It allows ACEs set on a parent container gets inherited by its child objects. It simplifies access management significantly as it allows the management to be done on the...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/10/22/view-configure-protected-acl-and-fixing-broken-inheritance.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9911629" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ACL/default.aspx">ACL</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/AccessControl/default.aspx">AccessControl</category></item><item><title>Add Object Specific ACEs using Active Directory Powershell</title><link>http://blogs.msdn.com/adpowershell/archive/2009/10/13/add-object-specific-aces-using-active-directory-powershell.aspx</link><pubDate>Tue, 13 Oct 2009 22:37:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9906868</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9906868.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9906868</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9906868</wfw:comment><description>Active Directory Powershell implements two Powershell Provider cmdlets specifically for access control management in Active Directory: Get-ACL and Set-ACL. This blog series is to give a few examples on how to use them. Note that it is not intended for...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/10/13/add-object-specific-aces-using-active-directory-powershell.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9906868" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ACL/default.aspx">ACL</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/AccessControl/default.aspx">AccessControl</category></item><item><title>How to view SOAP XML messages to and from AD Webservices and Powershell</title><link>http://blogs.msdn.com/adpowershell/archive/2009/10/05/how-to-view-soap-xml-messages-to-and-from-ad-webservices-and-powershell.aspx</link><pubDate>Tue, 06 Oct 2009 01:12:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9903447</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9903447.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9903447</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9903447</wfw:comment><description>I am sure many of us are curious to see the XML messages communicated between the AD Powershell webservices client and a Windows server hosting AD Webservices whenever a powershell cmdlet gets executed. In this blog, I am providing information to view...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/10/05/how-to-view-soap-xml-messages-to-and-from-ad-webservices-and-powershell.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9903447" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Error/default.aspx">Error</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Exception/default.aspx">Exception</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ADWebservice/default.aspx">ADWebservice</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ADWS/default.aspx">ADWS</category></item><item><title>How to find extended rights that apply to a schema class object</title><link>http://blogs.msdn.com/adpowershell/archive/2009/09/22/how-to-find-extended-rights-that-apply-to-a-schema-class-object.aspx</link><pubDate>Wed, 23 Sep 2009 01:44:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9898212</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9898212.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9898212</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9898212</wfw:comment><description>Recently, I came across this question (how to find extended rights that apply to a schema class) in our internal mailing lists. Extended rights are special permissions that denote a special task or function. These rights apply to one or more object classes...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/09/22/how-to-find-extended-rights-that-apply-to-a-schema-class-object.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9898212" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ScriptSnippet/default.aspx">ScriptSnippet</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Schema/default.aspx">Schema</category></item><item><title>Active Directory Management Gateway Service released to web - manage YOUR Windows 2003/2008 DCs USING AD POWERSHELL !</title><link>http://blogs.msdn.com/adpowershell/archive/2009/09/18/active-directory-management-gateway-service-released-to-web-manage-your-windows-2003-2008-dcs-using-ad-powershell.aspx</link><pubDate>Fri, 18 Sep 2009 03:15:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9896591</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9896591.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9896591</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9896591</wfw:comment><description>RTW version of Active Directory Management Gateway Service (ADMGS), an Active Directory Web Services (ADWS overview here ) out of band release for down level servers is now available to download from Microsoft Download Center Page . ADMGS is a down level...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/09/18/active-directory-management-gateway-service-released-to-web-manage-your-windows-2003-2008-dcs-using-ad-powershell.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9896591" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Installation/default.aspx">Installation</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ADAC/default.aspx">ADAC</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ADWebservice/default.aspx">ADWebservice</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ADWS/default.aspx">ADWS</category></item><item><title>Token Bloat Troubleshooting by Analyzing Group Nesting in AD</title><link>http://blogs.msdn.com/adpowershell/archive/2009/09/05/token-bloat-troubleshooting-by-analyzing-group-nesting-in-ad.aspx</link><pubDate>Sat, 05 Sep 2009 05:52:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9891682</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9891682.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9891682</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9891682</wfw:comment><description>This tool started when I was finding ways to analyze the complexity of group memberships in AD. Other than the usual average/median/min/max of number of members, number of memberships etc, I was also interested in finding out the maximum nesting levels...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/09/05/token-bloat-troubleshooting-by-analyzing-group-nesting-in-ad.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9891682" width="1" height="1"&gt;</description></item><item><title>Active Directory Powershell to manage Sites and Subnets – Part 3 (Getting Site and Subnets)</title><link>http://blogs.msdn.com/adpowershell/archive/2009/08/18/active-directory-powershell-to-manage-sites-and-subnets-part-3-getting-site-and-subnets.aspx</link><pubDate>Tue, 18 Aug 2009 14:30:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9874409</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9874409.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9874409</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9874409</wfw:comment><description>Hello folks! Here are few Active Directory Powershell script snippets that you will find useful while writing scripts. They deal with fetching sites, subnets and servers. Most of the snippets are simple and self-explanatory and can be simply copy-pasted...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/08/18/active-directory-powershell-to-manage-sites-and-subnets-part-3-getting-site-and-subnets.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9874409" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Sites/default.aspx">Sites</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ScriptSnippet/default.aspx">ScriptSnippet</category></item><item><title>Active Directory Powershell to manage Sites and Subnets – Part 2 (New-XADSubnet)</title><link>http://blogs.msdn.com/adpowershell/archive/2009/08/11/active-directory-powershell-to-manage-sites-and-subnets-part-2-new-xadsubnet.aspx</link><pubDate>Tue, 11 Aug 2009 19:00:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9865142</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9865142.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9865142</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9865142</wfw:comment><description>In an earlier post “Active Directory Powershell to manage sites – Part 1 (New-XADSite)” Jairo explained in detail about how to create a Site in Active Directory using AD Powershell. In today’s post I am going to discuss about how to create Subnets using...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/08/11/active-directory-powershell-to-manage-sites-and-subnets-part-2-new-xadsubnet.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9865142" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Script/default.aspx">Script</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ActiveDirectoryExtension/default.aspx">ActiveDirectoryExtension</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Sites/default.aspx">Sites</category></item><item><title>Three Module Extensions (DC Health, Trust Management and Demo Script)</title><link>http://blogs.msdn.com/adpowershell/archive/2009/08/04/three-module-extensions-dc-health-trust-management-and-demo-script.aspx</link><pubDate>Tue, 04 Aug 2009 19:12:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9857543</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9857543.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9857543</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9857543</wfw:comment><description>This is a short blog post to highlight a few module extensions that we have been demoing at conferences this year. They show some of the new features in our PowerShell module as well as a few examples extending them. In this update, there are three modules:...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/08/04/three-module-extensions-dc-health-trust-management-and-demo-script.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9857543" width="1" height="1"&gt;</description><enclosure url="http://blogs.msdn.com/adpowershell/attachment/9857543.ashx" length="10978" type="application/x-zip-compressed" /><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Script/default.aspx">Script</category></item><item><title>Use Active Directory Powershell to manage Windows 2003/2008 DCs</title><link>http://blogs.msdn.com/adpowershell/archive/2009/06/23/use-active-directory-powershell-to-manage-windows-2003-2008-dcs.aspx</link><pubDate>Tue, 23 Jun 2009 23:58:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9800207</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>3</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9800207.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9800207</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9800207</wfw:comment><description>Many of the readers have expressed interest in having the ability to manage their down level (running Win 2003/2008) DCs using ADPowershell. The only missing piece was the availability of the Active Directory Web Service (ADWS overview here ). Well, ADWS...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/06/23/use-active-directory-powershell-to-manage-windows-2003-2008-dcs.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9800207" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ADWebservice/default.aspx">ADWebservice</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ADWS/default.aspx">ADWS</category></item><item><title>Inspecting Deleted Objects before Restore</title><link>http://blogs.msdn.com/adpowershell/archive/2009/06/01/inspecting-deleted-objects-before-restore.aspx</link><pubDate>Mon, 01 Jun 2009 21:36:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9680070</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9680070.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9680070</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9680070</wfw:comment><description>Accidental deletions can happen in Active Directory in many ways. An administrator can end up deleting a single user object unintentionally or fat finger an entire tree of OUs. A rogue script could end up deleting multiple objects at multiple locations...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/06/01/inspecting-deleted-objects-before-restore.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9680070" width="1" height="1"&gt;</description><enclosure url="http://blogs.msdn.com/adpowershell/attachment/9680070.ashx" length="8787" type="text/plain" /><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Tree/default.aspx">Tree</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Undelete/default.aspx">Undelete</category></item><item><title>Tab completing LDAP attribute names inside Advanced Filters</title><link>http://blogs.msdn.com/adpowershell/archive/2009/05/19/tab-completing-ldap-attribute-names-inside-advanced-filters.aspx</link><pubDate>Tue, 19 May 2009 20:00:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9630101</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9630101.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9630101</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9630101</wfw:comment><description>In my previous post about Advanced filter s I showed how to use Powershell variables to represent values inside filters. Example: PS D:\&amp;gt; $JohnSmith = Get-ADUser JohnSmith PS D:\&amp;gt; Get-ADUser -Filter { manager -eq $JohnSmith.DistinguishedName } ##...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/05/19/tab-completing-ldap-attribute-names-inside-advanced-filters.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9630101" width="1" height="1"&gt;</description><enclosure url="http://blogs.msdn.com/adpowershell/attachment/9630101.ashx" length="23250" type="text/plain" /><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Script/default.aspx">Script</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ActiveDirectoryExtension/default.aspx">ActiveDirectoryExtension</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Filter/default.aspx">Filter</category></item><item><title>ACTIVE DIRECTORY POWERSHELL TO MANAGE SITES – Part 1 (New-XADSite)</title><link>http://blogs.msdn.com/adpowershell/archive/2009/05/05/active-directory-powershell-to-manage-sites-part-1-new-xadsite.aspx</link><pubDate>Tue, 05 May 2009 21:29:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9589424</guid><dc:creator>ActiveDirectoryPowershellTeam</dc:creator><slash:comments>6</slash:comments><comments>http://blogs.msdn.com/adpowershell/comments/9589424.aspx</comments><wfw:commentRss>http://blogs.msdn.com/adpowershell/commentrss.aspx?PostID=9589424</wfw:commentRss><wfw:comment>http://blogs.msdn.com/adpowershell/rsscomments.aspx?PostID=9589424</wfw:comment><description>In this opportunity I am going to provide a solution to manage sites in your Active Directory (AD) forest by extending Active Directory PowerShell by implementing functions that allow creation, retrieval, update (moving to a site link, renaming) and deletion...(&lt;a href="http://blogs.msdn.com/adpowershell/archive/2009/05/05/active-directory-powershell-to-manage-sites-part-1-new-xadsite.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9589424" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Script/default.aspx">Script</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/ActiveDirectoryExtension/default.aspx">ActiveDirectoryExtension</category><category domain="http://blogs.msdn.com/adpowershell/archive/tags/Sites/default.aspx">Sites</category></item></channel></rss>