The local administrator password on our workstations and servers should be changed regularly, and when an administrator leaves the staff. There are many ways to do this: with scripts, Hyena, and others, but none of those let you evaluate what needs to be changed and what has been changed. I wrote the Local Administrator Password Manager v 1.1 (LAPMan) to address that need. First, you import the computer accounts from AD. Second, you connect to the systems and get the current administrator data. You can see what the local admin account name is, and the account age (how long since password last set). In the information screen you can check a box which exempts systems from being changed. Each time you run the “Get Info” button, it only tries to get the information from systems where this has not yet been collected.
The change password screen lets you choose between workstations and servers. It asks for the local administrator name — but even if the name is not correct, the password will be updated. On a successful name change the database is updated. You can run the change password routine multiple times to pickup laptops and other systems that were off-line. Each time this routine is launched, only the unchanged systems will be done.
On the PCInfo page is a tools tab. Some interesting things there that may help you, such as ping, manage the PC, and others.
The program is multi-threaded, launching multiple copies of the password changing script at time. The impact to the network from this traffic is minimal. The program lets you select your OU, and I suggest you begin with a test OU. I appreciate your feedback and comments.
LAPMan requires Microsoft Access.