The 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.
You will see several areas that you can check or enter information. 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.
- Open the utility (Log Parser).
- 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.
- Enter the string you want to search for. NOTE: Searches are CASE SENSITIVE!
- 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.
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".
- 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.
- 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.
- Click on start.
- 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.