Batch Password Change

batchpasswordsmLocal Account Batch Password Change

This utility will change the password of local accounts on any Windows NT, 2000, 2003 server or workstation. Why is this important? Because this utility does batch changes.

Say you manage a medium sized network with 100 hundred or so servers, or maybe just 20 servers. One of the IT people leaves the company and you have to change the password to a local account on every server. Well fire up this utility and place a text file with the names of all the servers on the root of your "c" drive and in a few minutes, your done!




{phocadownload view=file|id=8|text=Download Batch Password Change|target=s}



1. Create a text file on the root of "C" (there's an example file if you click the "example" button).
2. Enter the names of the servers or workstations you want to change the local account password on.
3. Start the program and type the account name (the account on the server) in the "User ID" field.
4. Enter the new password
5. Enter it again (just to make sure)
6. Make absolutely sure you want to do this. Click "Change Password".
A log file of the changes will be placed at "C:\localpasswordchange.txt".

NOTE: This program will ping every computer on the list first to make sure its there. If it finds a system that's not online it will write that to the log. The you can go back to those systems to find out the issue.

Remember if your running a local firewall (windows XP built in firewall or such) then you may have a problem.

Please remember you must be a local admin or a member of the "local admins" group on the system you are running the tools



Print Email

RDPEnable Instructions


rdp1The RDPEnable program icon is shown to the left. Best practice would be to place the program in a folder somewhere on the system drive and then drag a shortcut to wherever its easiest for you to access.


Please don't forget there is a training video availible.

Once the program is open it looks as shown in figure 1. The most current version is 3.0.0.







Basic Use

You will see several areas that you can check or enter information.rdp3 For it's most basic use you can just enter the NetBios, FQDN or IP address of the system you need to enable RDP on in the "Name or IP" box. I prefer to use the IP if known. Then click the "CHANGE" button at the bottom. If you are connected to the same domain as the system you are enabling and logged in with administrative permissions you should not need to do anything else.

NOTE: If the NetBios name is used please do NOT place any backslashes in front of the name, i.e., "\\system name".

If you need to disable RDP on the system in question then check the "Disable RDP" check-box as shown later in figure 2.

As you may not be logged into the same domain as the system your enabling you may need to pass permissions to the system to have the privileges needed to enable or disable it.



To do so check the "Pass Credentials" check-box as shown in figure 2. Then enter the user name; please use the "domain\user" format.

Next enter the password and click on the "CHANGE" button. This opens the IPC$ share on the system which passes credentials to do so. So you basically have a persistent connection to the system you are enabling. This allows the program to access the system and make changes with the permissions you passed it.



Adding users to the Remote Desktop Users group

You may need to, from time to time, add users accounts to the Remote Desktop Users group on the system you are enabling. You may get a call and be asked to grant permission to an engineer or end user to RDP a server or workstation. Normally you would have to connect to the system and add the permission through system manager or system properties. With RDPEnable you can enter the IP of the server/workstation an pass credentials if needed. Enter the name of the user account using the format "user@domain" as shown in figure 5.



Once you have enter the user name in the correct format click the "Add" button. In the results screen at the bottom you should see "User added to Remote Users group" or "User NOT added to Remote Users group. Could not obtain access to system or User Account already in group" if it fails. Possible reasons it could fail are:

  • No access to the system.
  • Bad user account.
  • The account already exists in the group.
  • The firewall is on.


Changing the RDP port

For an added layer of security you can change the port the RDP listens on and accepts connections. To do do this first find and unused port. You can find lists that contain the default ports used by windows systems at Microsoft's website. Once you have a port number to use open the RDPEnable tool and enter the name or IP of the server/workstation and if needed fill out the "Pass Credentials" section. Now check the "Yes Change Port" box and enter the port number as shown in figure 4.



Now click on "CHANGE" and the port will be changed to whatever you entered. Remember that to access that system you will now enter the name and port number when access the system with RDP. so the entry will look like "system-name:port". You can always change it back if needed. The default port is listed on the program so you won't need to search for it.


NOTE: I have had some problems getting the port change to work with Vista. I have tested it with XP, 2000, 2003, 2008 and Windows 7 successfully.


Well that's it. It's a very simple but powerful program to make your work a little easier. Please watch the training video if you have more questions or post a comment.


Print Email

Log Parser Instructions


  1. Open the utility (Log Parser).

Log Parser Main Screen


  1. Locate the files you want to search by clicking on the "Locate Fle(s)" button. You can select as many as you want I have tested up to 35 at a time.

Locate Files

selected files


  1. Enter the string you want to search for. NOTE: Searches are CASE SENSITIVE!
  2. Set the line(s) to include in report (if you want more than the first one).
    • Example: You have a log file and it contains blocks of data you want to capture. The line your interested in has "Texas" in it, but you know that the following 3 lines will contain the extra information you want to capture. Increment the number in the "lines to capture" box to 3.lines to capture

Now when the LogParser runs through your files any lines that contain "Texas" will be written to the log file as well as the next 3 lines. So you have captured the "block" of text in your log file/report. If you don't want to capture any extra lines leave the setting at "0".

  1. Choose if you want to exclude any data or strings from your final output.
    • Example: Lets say you have a file with locations of government offices in the U.S. And you want to capture any line that has "California" in it. But you want to exclude any that have "San Francisco". Enter "San Francisco" in the "Data to exclude" box. Now any line that has California in it will be captured but if it also contains "San Francisco" it will be ignored.
  2. Choose the name and path of the output file (or leave at default). If you run the LogParser multiple times you may want to increment the name so you can distinguish them easily. As well if you do not change the name it will just keep appending data to the original log file/report.
  3. Click on start.

  1. A log file/text file containing any lines that have the data you searched on is created. You can see in the image below that all the lines with "Boost" were captured in every file searched. (I only show 2 files here). As well you may notice that the name of each file searched is listed before the captured data. This way you can keep track of what data came from what file.
    • If you want you can now search on your outputted file to even further narrow your results.

Print Email

Network Monitor

Download Now!

This is not a typical program out here. This is a "system" a conglomeration of several programs to make up a network monitoring system.

This is an ever evolving monitoring system(as most of the tools out here are). Changed by input from you.

I used this system, or should I say, one of my previous employers used it to monitor 230 servers and several switches for about 4 years. It was finally replaced by NetIQ (a system that was more than a $100,000) and yet this was still left running for several months until they were sure the new system would provide the same reliability.

NOTE: This versions setup routine is a little buggy. If you have issues please address them in the support forum. I'll do my best to get you set up.





Immediate Uses___________________________________________________________________________


  • This is a full fledged Monitoring system. It will check, system availability, disk space, running services and more. It will alert you based of the settings you define; when it finds a problem. It will automatically restart services that you list as critical. It will automatically try to clean up a hard drive if space is running low.
  • You could definitely buy a system that has more bells and whistles but this one is free.
  • Monitor every server in your network (best for Windows servers).
  • Monitor perimeter devices (ping only)




This program is a "work in progress". I am continually changing it, updating it and adding features. I rely on other engineers to let me know what they need (that's within the limits of Winbatch) so I can improve it. I have added the source files out here, they are:

Please feel free to copy these and improve them and send them back. if the improvements are valuable I will definitely compile them to the downloads. Also I will make the code available on this site with your name attached to it so any one can download it.

  1. Download and unzip the files.
  2. Open the "Monitor5" folder and double click on the file "Monitor_Setup.exe".
  3. The Setup program will open. As shown below (click on it for a larger veiw)

Monitor Setup Program

  1. Now enter the data as asked on the setup screen. Remember any setting your not sure of you can change later.
  2. Click OK and the setup process will begin. It only takes a few seconds to complete. A log file will be created on the C:\ drive of the system you run it on. This will list file locations.
  3. NOTE: I have tried to make this as foolproof as possible; but there is always the chance your environment will have something different that I couldn't account for. If you have any problems look over the help file and if that doesn't work send me an email from the contact page with your question. Also you can post to the forum as well.
  4. Ok that's the basic setup now you will need to confirm a few things:
    1. That the service installed correctly.
    2. That the "srvrmntr.ini" file was created and it's settings are correct.
    3. All the directories exist (look in the instructions)
    4. Make sure you share the "Network_monitor" folder. This has to be done manually for the time being. You can set permissions up how you like as long as the monitor program and anyone managing it has read-write access.
  5. You can also read the Help/instructions file located here.

**Please remember you must be a "local admin" or a member of the "local admins" group on the system you are running the tools from.



Please remember you must be a "local admin" or a member of the "local admins" group on the system you are running the tools from.



Print Email

RDP Enable Utility ( remote desktop enable )



RDP Enable version 3.0.1 - Updated 02.22.2012

Remote Desktop Enable Utility will enable Remote Desktop connections on remote servers. It will also change the port number that RDP listens on. This is good to add a layer of security in.

Enable Remote Desktop (RDP) if you forgot to do it when you built the system or if your working remotley and cant access the server. Also change the port number Remote Desktop listens on.



RDP has been updated to version 3.0.0. Powerful new features include-

  • Ability to enable remote desktop on systems that are on different domains. That means you can be at home or wherever on a computer that is not part of the domain you are accessing and still turn on RDP as long as you have a username and password with permission.
  • Add users to the "Remote Desktop Users Group" on any server/workstation you have access too.
  • Turn off RDP on any system you have access too.
  • Results window that gives you blow by blow stats on what is happening when you run the utility.


This is one of those "Must Have Utilities!"

I get emails from engineers all the time thanking me for this one, here are a couple...

"I like to support those who do little programs that can save me and my techs a lot of time in the field. Sometimes we have clients where we need 10-12 desktops RDP accessible from the internet - and this just makes it a breeze!" -Oly G .

"Got home last night and couldnt access the system I set up just before I left work! Your tool got me access easily, Thanks again!" -Scott L.

So if you need to access a system using RDP and it's not turned on here's the tool that will get the job done quick and easy.

Included with your purchase updates will be sent to you automatically for one full year!

Hurry and Purchase RDP Enable only for $19.99 


New RDP Training video!


Remote Desktop Enable overview and use.


Print Email

Sign Up Now