<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><title type="html">Active Directory Powershell Blog</title><subtitle type="html">&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;</subtitle><id>http://blogs.msdn.com/adpowershell/atom.xml</id><link rel="alternate" type="text/html" href="http://blogs.msdn.com/adpowershell/default.aspx" /><link rel="self" type="application/atom+xml" href="http://blogs.msdn.com/adpowershell/atom.xml" /><generator uri="http://communityserver.org" version="2.1.61025.2">Community Server</generator><updated>2009-05-05T19:29:00Z</updated><entry><title>Redirecting Well Known Containers (CN=Users; CN=Computers etc.)</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/adpowershell/archive/2009/11/25/redirecting-well-known-containers-cn-users-cn-computers-etc.aspx" /><link rel="enclosure" type="application/octet-stream" length="3348" href="http://blogs.msdn.com/adpowershell/attachment/9928827.ashx" /><id>http://blogs.msdn.com/adpowershell/archive/2009/11/25/redirecting-well-known-containers-cn-users-cn-computers-etc.aspx</id><published>2009-11-25T22:03:00Z</published><updated>2009-11-25T22:03:00Z</updated><content type="html">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 of a domain, For example: PS C:\Users\Administrator.DSWAMIPAT-W7-V1&amp;gt; Get-ADDomain | select *Container ComputersContainer : CN=Computers,DC=dswamipat-w7-vm1,DC=nttest,DC=microsoft,DC=com DeletedObjectsContainer : CN=Deleted Objects,DC=dswamipat-w7-vm1,DC=nttest,DC=microsoft,DC=com...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author><category term="Script" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Script/default.aspx" /><category term="ScriptSnippet" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ScriptSnippet/default.aspx" /><category term="WKGUID" scheme="http://blogs.msdn.com/adpowershell/archive/tags/WKGUID/default.aspx" /></entry><entry><title>Accessing Replication Metadata using ADPowerShell</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/adpowershell/archive/2009/11/01/accessing-replication-metadata-using-adpowershell.aspx" /><link rel="enclosure" type="application/octet-stream" length="3510" href="http://blogs.msdn.com/adpowershell/attachment/9915814.ashx" /><id>http://blogs.msdn.com/adpowershell/archive/2009/11/01/accessing-replication-metadata-using-adpowershell.aspx</id><published>2009-11-01T09:50:00Z</published><updated>2009-11-01T09:50:00Z</updated><content type="html">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 Attribute Available on Objects Corresponding Binary Attribute msDS-ReplQueueStatistics Root DSE - msDS-ReplAllInboundNeighbors Root DSE - msDS-ReplAllOutboundNeighbors Root DSE - msDS-NCReplCursors NC Head replUpToDateVector msDS-NCReplInboundNeighbors...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author></entry><entry><title>View/Configure Protected ACL and Fixing Broken Inheritance</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/adpowershell/archive/2009/10/22/view-configure-protected-acl-and-fixing-broken-inheritance.aspx" /><id>http://blogs.msdn.com/adpowershell/archive/2009/10/22/view-configure-protected-acl-and-fixing-broken-inheritance.aspx</id><published>2009-10-22T19:33:19Z</published><updated>2009-10-22T19:33:19Z</updated><content type="html">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 container level rather than on individual leaf objects. However, sometimes we may want to block such inheritance on some special objects. With a protected ACL set on the object, any inheritable ACEs set on its parent will not be able to propagate down...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author><category term="ACL" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ACL/default.aspx" /><category term="AccessControl" scheme="http://blogs.msdn.com/adpowershell/archive/tags/AccessControl/default.aspx" /></entry><entry><title>Add Object Specific ACEs using Active Directory Powershell</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/adpowershell/archive/2009/10/13/add-object-specific-aces-using-active-directory-powershell.aspx" /><id>http://blogs.msdn.com/adpowershell/archive/2009/10/13/add-object-specific-aces-using-active-directory-powershell.aspx</id><published>2009-10-13T22:37:12Z</published><updated>2009-10-13T22:37:12Z</updated><content type="html">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 a detailed explanation of access control and delegation in Active Directory and with an assumption that the readers have had basic knowledge. Additional information on Active Directory access control and delegation can be found in the Best Practices...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author><category term="ACL" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ACL/default.aspx" /><category term="AccessControl" scheme="http://blogs.msdn.com/adpowershell/archive/tags/AccessControl/default.aspx" /></entry><entry><title>How to view SOAP XML messages to and from AD Webservices and Powershell</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/adpowershell/archive/2009/10/05/how-to-view-soap-xml-messages-to-and-from-ad-webservices-and-powershell.aspx" /><id>http://blogs.msdn.com/adpowershell/archive/2009/10/05/how-to-view-soap-xml-messages-to-and-from-ad-webservices-and-powershell.aspx</id><published>2009-10-06T01:12:48Z</published><updated>2009-10-06T01:12:48Z</updated><content type="html">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 those messages by enabling Windows Communication Foundation (WCF) logging through ADWS configuration. For more in general on WCF configuring message logging, please see: http://msdn.microsoft.com/en-us/library/ms730064.aspx 1) Stop Active Directory...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author><category term="Error" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Error/default.aspx" /><category term="Exception" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Exception/default.aspx" /><category term="ADWebservice" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ADWebservice/default.aspx" /><category term="ADWS" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ADWS/default.aspx" /></entry><entry><title>How to find extended rights that apply to a schema class object</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/adpowershell/archive/2009/09/22/how-to-find-extended-rights-that-apply-to-a-schema-class-object.aspx" /><id>http://blogs.msdn.com/adpowershell/archive/2009/09/22/how-to-find-extended-rights-that-apply-to-a-schema-class-object.aspx</id><published>2009-09-23T01:44:31Z</published><updated>2009-09-23T01:44:31Z</updated><content type="html">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 and can be found stamped in the security descriptor of an object. There are KB articles that describe how to find extended rights that apply to a given objectClass using VBScript or C++. http://support.microsoft.com/kb/302514 I was curious to find...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author><category term="ScriptSnippet" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ScriptSnippet/default.aspx" /><category term="Schema" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Schema/default.aspx" /></entry><entry><title>Active Directory Management Gateway Service released to web - manage YOUR Windows 2003/2008 DCs USING AD POWERSHELL !</title><link rel="alternate" type="text/html" 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" /><id>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</id><published>2009-09-18T03:15:19Z</published><updated>2009-09-18T03:15:19Z</updated><content type="html">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 release of in-box version of Windows Server 2008 R2&amp;#160; ADWS and provides the same functionality. One can download and install ADMGS on servers and domain controllers running the following operating systems: Windows Server® 2003 R2 with Service...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author><category term="Installation" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Installation/default.aspx" /><category term="ADAC" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ADAC/default.aspx" /><category term="ADWebservice" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ADWebservice/default.aspx" /><category term="ADWS" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ADWS/default.aspx" /></entry><entry><title>Token Bloat Troubleshooting by Analyzing Group Nesting in AD</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/adpowershell/archive/2009/09/05/token-bloat-troubleshooting-by-analyzing-group-nesting-in-ad.aspx" /><id>http://blogs.msdn.com/adpowershell/archive/2009/09/05/token-bloat-troubleshooting-by-analyzing-group-nesting-in-ad.aspx</id><published>2009-09-05T05:52:51Z</published><updated>2009-09-05T05:52:51Z</updated><content type="html">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 of groups and the recursive group membership count. For e.g. in the diagram below, the maximum nesting level of ‘group a’ is 3 and its recursive group membership count is 6. Analyzing the recursive group membership of a group is helpful in troubleshooting...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author></entry><entry><title>Active Directory Powershell to manage Sites and Subnets – Part 3 (Getting Site and Subnets)</title><link rel="alternate" type="text/html" 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" /><id>http://blogs.msdn.com/adpowershell/archive/2009/08/18/active-directory-powershell-to-manage-sites-and-subnets-part-3-getting-site-and-subnets.aspx</id><published>2009-08-18T14:30:00Z</published><updated>2009-08-18T14:30:00Z</updated><content type="html">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 in your existing script. ## Get a specified Active Directory Site. $siteName = "Default-First-Site-Name" $configNCDN = (Get-ADRootDSE).ConfigurationNamingContext $siteContainerDN = ( "CN=Sites," + $configNCDN) $siteDN = "CN=" + $siteName + "," + $siteContainerDN...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author><category term="Sites" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Sites/default.aspx" /><category term="ScriptSnippet" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ScriptSnippet/default.aspx" /></entry><entry><title>Active Directory Powershell to manage Sites and Subnets – Part 2 (New-XADSubnet)</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/adpowershell/archive/2009/08/11/active-directory-powershell-to-manage-sites-and-subnets-part-2-new-xadsubnet.aspx" /><id>http://blogs.msdn.com/adpowershell/archive/2009/08/11/active-directory-powershell-to-manage-sites-and-subnets-part-2-new-xadsubnet.aspx</id><published>2009-08-11T19:00:00Z</published><updated>2009-08-11T19:00:00Z</updated><content type="html">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 AD Powershell. Before going into details of creating a subnet object, first let us understand what is a Site and Subnet. The following definition is from: http://technet.microsoft.com/en-us/library/cc782048(WS.10).aspx In Active Directory, a site...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author><category term="Script" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Script/default.aspx" /><category term="ActiveDirectoryExtension" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ActiveDirectoryExtension/default.aspx" /><category term="Sites" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Sites/default.aspx" /></entry><entry><title>Three Module Extensions (DC Health, Trust Management and Demo Script)</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/adpowershell/archive/2009/08/04/three-module-extensions-dc-health-trust-management-and-demo-script.aspx" /><link rel="enclosure" type="application/x-zip-compressed" length="10978" href="http://blogs.msdn.com/adpowershell/attachment/9857543.ashx" /><id>http://blogs.msdn.com/adpowershell/archive/2009/08/04/three-module-extensions-dc-health-trust-management-and-demo-script.aspx</id><published>2009-08-04T19:12:00Z</published><updated>2009-08-04T19:12:00Z</updated><content type="html">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: DemoScript – This is module wrapping Jeffrey Snover’s start-demo script. It has several updates from various sources inside and outside of Microsoft. This would make a pretty good start to a set of cmdlets to create and run demo scripts, test...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author><category term="Script" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Script/default.aspx" /></entry><entry><title>Use Active Directory Powershell to manage Windows 2003/2008 DCs</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/adpowershell/archive/2009/06/23/use-active-directory-powershell-to-manage-windows-2003-2008-dcs.aspx" /><id>http://blogs.msdn.com/adpowershell/archive/2009/06/23/use-active-directory-powershell-to-manage-windows-2003-2008-dcs.aspx</id><published>2009-06-23T23:58:00Z</published><updated>2009-06-23T23:58:00Z</updated><content type="html">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 beta for down level DCs is here. Using this beta download, you can manage your existing Active Directory forests using ADPowershell. Below are the steps to participate in this beta program: Visit http://connect.microsoft.com and enter the invitation...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author><category term="ADWebservice" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ADWebservice/default.aspx" /><category term="ADWS" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ADWS/default.aspx" /></entry><entry><title>Inspecting Deleted Objects before Restore</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/adpowershell/archive/2009/06/01/inspecting-deleted-objects-before-restore.aspx" /><link rel="enclosure" type="text/plain" length="8787" href="http://blogs.msdn.com/adpowershell/attachment/9680070.ashx" /><id>http://blogs.msdn.com/adpowershell/archive/2009/06/01/inspecting-deleted-objects-before-restore.aspx</id><published>2009-06-01T21:36:00Z</published><updated>2009-06-01T21:36:00Z</updated><content type="html">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 in the AD hierarchy. In Active Directory, when deleted objects are moved to the deleted objects container, they lose their hierarchy (because the DN is mangled to ensure uniqueness). Once accidental deletions happen it's important to analyze the impact...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author><category term="Tree" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Tree/default.aspx" /><category term="Undelete" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Undelete/default.aspx" /></entry><entry><title>Tab completing LDAP attribute names inside Advanced Filters</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/adpowershell/archive/2009/05/19/tab-completing-ldap-attribute-names-inside-advanced-filters.aspx" /><link rel="enclosure" type="text/plain" length="23250" href="http://blogs.msdn.com/adpowershell/attachment/9630101.ashx" /><id>http://blogs.msdn.com/adpowershell/archive/2009/05/19/tab-completing-ldap-attribute-names-inside-advanced-filters.aspx</id><published>2009-05-19T20:00:00Z</published><updated>2009-05-19T20:00:00Z</updated><content type="html">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 } ## Gets all the user accounts whose manager is JohnSmith .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin:...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author><category term="Script" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Script/default.aspx" /><category term="ActiveDirectoryExtension" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ActiveDirectoryExtension/default.aspx" /><category term="Filter" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Filter/default.aspx" /></entry><entry><title>ACTIVE DIRECTORY POWERSHELL TO MANAGE SITES – Part 1 (New-XADSite)</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/adpowershell/archive/2009/05/05/active-directory-powershell-to-manage-sites-part-1-new-xadsite.aspx" /><id>http://blogs.msdn.com/adpowershell/archive/2009/05/05/active-directory-powershell-to-manage-sites-part-1-new-xadsite.aspx</id><published>2009-05-05T21:29:00Z</published><updated>2009-05-05T21:29:00Z</updated><content type="html">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 of sites. First of all we need to understand what an AD site is made of. We can say that an AD site is represented by three directory objects and a reference in an attribute in a different object (i.e. the Site Link object). In detail an AD site...(&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;</content><author><name>ActiveDirectoryPowershellTeam</name><uri>http://blogs.msdn.com/members/ActiveDirectoryPowershellTeam.aspx</uri></author><category term="Script" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Script/default.aspx" /><category term="ActiveDirectoryExtension" scheme="http://blogs.msdn.com/adpowershell/archive/tags/ActiveDirectoryExtension/default.aspx" /><category term="Sites" scheme="http://blogs.msdn.com/adpowershell/archive/tags/Sites/default.aspx" /></entry></feed>