I have one thind to say and it is a great software that fixed my problem. Keroon.

Anonymous User 3/16/2005 7:19:51 AM

I downloaded the scripts and used listing 4 to list systems. It ran once on my domain and then failed. It says "user could not be found". And references this line: "Set oComputerAccount=GetObject(oComputer.AdsPath & "$,user")"

Any ideas what I am doing wrong?

kukri8/13/2004 2:09:11 PM

I changed my password but now cannot remember it or the administrator password either. How can I get my password reset without losing any information on my machine. I am running Windows XP Professional.

Tommy E Burton 2/14/2004 1:47:14 AM

This is exactly what I am looking for. I have tried to download the Excel file from the Windows Scripting Solutions Web site, but it is no longer available. Where can I get it?

Note from the Editors: To obtain the Excel file, click the 16292.zip link that appears under the Download the Code heading at the beginning of the article.

Francois Greyling 12/19/2003 2:34:47 AM

Is the time frame for the "Inactive Accounts" Listing 4 wrong? If seconds are used to determine machine accounts older than 180 days, this condition should be 15552000 not 7776000. My calculations say that if seconds are used 7776000 comes out to 90 days not 180.

Jeff Fink 12/16/2003 6:49:38 PM

Will this work in Windows NT 4.0 domain?

P Shah 10/9/2002 8:44:21 AM

This article really sparked an interest in me. I just found one thing missing and one thing wrong.

The one thing missing: Research on "secure channel password" needs more detail. Standard TechNet documentation is only partially clear. What happens after 10 days? It's not clear!

I've been looking at the refresh rate (number of days since last password change) and found that several are still pingable at 22 days. If the default is 7 days and the response to an 'Immediate reply" is required, why isn't the machine updating it's secure channel password within the logon sequence or while it's logged in?
My biggest concern is with the remote users. Imagine having to get a remote user "out of" and "back in" a domain over the phone. Not what I want as a part of my daily routine.

Overall, I like this tool, but clarification is needed from Microsoft before I'll go deleting accounts... particularly, remote accounts. And of course those aren't readily known as remote accounts. I'm going to do some remote access testing, if I find anything meaningful, I'll pass it along to you if you'd like.

The one thing wrong: 7776000 is only 90 days. The article indicates 180 days.

James Turner 1/17/2001 8:19:49 PM