http://blogs.technet.com/bahramr/archive/2008/01/25/powershell-script-to-disable-inactive-accounts-in-active-directory.aspxIn order to improve network security and at the same conform with regulatory requirements, companies have to make sure that they disable stalled accounts in their domains in a timely manner. The two scripts described in this post show you how you canen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.technet.com/bahramr/archive/2008/01/25/powershell-script-to-disable-inactive-accounts-in-active-directory.aspx#3019983Tue, 25 Mar 2008 08:28:20 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3019983Find Disabled and Inactive User and Computer Accounts using Powershell - Part I « Just Another Sysadmin<p>PingBack from <a rel="nofollow" target="_new" href="http://justanothersysadmin.wordpress.com/2008/03/24/find-disabled-and-inactive-user-and-computer-accounts-using-powershell-part1/">http://justanothersysadmin.wordpress.com/2008/03/24/find-disabled-and-inactive-user-and-computer-accounts-using-powershell-part1/</a></p> http://blogs.technet.com/bahramr/archive/2008/01/25/powershell-script-to-disable-inactive-accounts-in-active-directory.aspx#3066005Wed, 04 Jun 2008 17:46:15 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3066005Doc Dish<p>I have found that when retrieving the User account properties (e.g. &quot;string]$lastLogonInterval = $user.Properties.lastlogontimestamp&quot;) the property value is only correctly retrieved if the property name is all lowercase (e.g. &quot;lastlogontimestamp&quot;). Any other case causes a null value to be returned.</p> <p>If you look at the property names in ADSI Edit, for example, they are all Camel cased (e.g. &quot;lastLogonTimestamp&quot;)</p>