free computer help


view:  full / summary

Linux/Puppet Master Commands

Posted by RICHARD BEI on February 22, 2017 at 2:35 PM Comments comments (0)

Here is a list of helpfull Puppet commnds: run at root (sudo -i) or do sudo before each command (there is one space between commands and switches but its hard to see)

Killall puppet (Kills all puppet services)

pupet cert generate hosts cr -all    (generates ssl certificates for specific hosts in the node)

puppet master --verbose --no-daeomonize  (--verbose switch will give on screen display of the process and --no-daemonize will run the command but not as a background process. Great for troubleshooting Puppet)

puppet cert generate hosts cr -all  (generate all ssl certificates for all hosts in the node)

puppet cert sign -all  (sign all ssl certificates for any hosts in the node. Note, blindly approving all certs is not suggested if you are concerned with security)

puppet agent --server masterport 8140 -verbose (sets the puppet agent to use masterport 8140 to connect to the puppet master. This is default)

puppet ca list  (Lists all pending Certificate Authority requests within the node)

sudo /etc/init.d/puppet restart  (restart the puppet agent even if your not in that pwd)

puppet agent --test --debug --verbose  (test the puppet agent in --debug  --verbose mode. Great for troubleshooting)

netstat -an  (show all ports and the status)

puppet agent --no daemonize --onetime --verbose (self explanatory)



Posted by RICHARD BEI on November 9, 2015 at 2:15 PM Comments comments (0)

Ok. So what to do when you uninstalled GUI AND DESKTOP EXPERIENCE? No GUI. Not to worry. Control+Alt+Delete-Task manager-File run once type "Powershell"

Enter command Get-WindowsFeature to see what is installed via server manager.

Enter command Install-WindowsFeature to under TFTP client check User Interfaces and Infrastructure/Graphical Management Tools and Infrastructure/Desktop Exeperience and server graphical shell.

Reboot! Done!






Posted by RICHARD BEI on August 6, 2015 at 8:50 AM Comments comments (0)

I am in cyber security amongst other things and had a very difficult time getting Nessus to enumerate the Windows 7 registry. Here is the fix:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLE and then make sure DCOM is set to yes.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System add reg DWORD name is LocalAccountTokenFilterPolicy and set to "1"

Services: set the following to Automatic and started/Remote registry/DCOM/Computer browser/RPC/RPC locator/RPC endpoint mapper/WMI/WMI performance adapter/RPC endpoint mapper.

In the Group Policy window please navigate to Computer Configuration -> Administrative Templates ->

Network -> Network Connections -> Windows Firewall -> Domain Profile and open Windows Firewall:

Allow inbound file and printer sharing exception. Windows Firewall opens UDP ports 137 and 138, and TCP ports 139 and 445.

GPO: Windows firewall: inbound and outbound allow for Public domain and private then turn off public/domain and private firewall.

Why turn off the firewall after setting the file and printer sharing? Windows firewall is very tenacious. I have always found it is 100 percent effective to make exceptions and then turn off the firewall.

Next, go to services and stop/disable Windows Defender/Windows Firewall.

Finally, Turn off User Account Control. When the Nessus scan is launched watch for the Admin$ share. If you see Nessus, then it is working. Also at command prompt run netstat -t 1. Look for port 139 and 445 to be established.

When the scan is complete and the report is generated look for these plug in id's:

10428-Microsoft Windows SMB registry Not Fully Accesible Detection

19506-Nesus Scan Information

21745-Authentication Failure-Local Checks Not Run

24786-Nessus Windows Scan Not Performed wWth Admin Privilages

26917-Microsoft Windows SMB Registry-Nessus Cannot Access The Windows Registry


Posted by Richard on March 12, 2012 at 4:20 PM Comments comments (0)

Ok. Blue screen of death? It seems that all the posts I see on the internet are way too complicated regarding this issue or over simplified. This post is meant to be a catch all. While the blue screen of death may have been caused by such a number of things, such as drivers, etc, there are a few simple tools to help you troubleshoot this. First, you can start your computer in safe mode.

This is the same for Windows Vista and Windows 7, 32 or 64 bit.

Remove all floppy disks, CDs, and DVDs from your computer, and then restart your computer. Click the Start button, click the arrow next to the Lock button, and then click Restart.

Do one of the following: If your computer has a single operating system installed, press and hold the F8 key as your computer restarts. You need to press F8 before the Windows logo appears. If the Windows logo appears, you will need to try again by waiting until the Windows logon prompt appears, and then shutting down and restarting your computer. If your computer has more than one operating system, use the arrow keys to highlight the operating system you want to start in safe mode, and then press F8.On the Advanced Boot Options screen, use the arrow keys to highlight the safe mode option you want, and then press ENTER. Log on to your computer with a user account that has administrator rights. When your computer is in safe mode, you’ll see the words Safe Mode in the corners of the display. To exit safe mode, restart your computer and let Windows start normally. From safe mode you can run some diagnostics.

Another way, which is actually easier, is to hit ctrl+alt+delete at your blue screen or blank screen. Here, you want to select “Task Manager".

Here we see a number of tabs: Applications/Processes/Services/Performance/Networking/Users. On Applications tab, you can close anything that may have caused your computer to improperly boot. Processes: You can click on the button on the bottom left to show all processes from all users. If you click the memory tab within Processes, you can sort the processes by the ones that utilize the most memory. If there is a process that you do not recognize, you can Google it. For example: Firefox.exe. I do not recommend closing anything related to Microsoft. Services are the same. The service is tied to the Processes or program but it is more difficult to identify which one may be causing an issue. We will skip Performance/Networking and Users for now. In Windows Task Manager click File-New Task Run. Type msconfig at the prompt. Here you will see the System Configuration. You are probably running in Normal Startup. You can just click on “Diagnostic Startup" This will only start the basic programs necessary for your computer to boot properly. Ok, so, want to know what startup programs are causing the issue? Go back to Task Manger Click on “Hide all Microsoft Services". More than likely Microsoft is not causing the problem. Here you can select the Services tab and close any unknown services. One that I found that will cause my computer problems sometimes is Anti Virus software, especially Panda. Click on the Startup tab, deselect any programs not needed except only those that are essential for your computer to start properly. Do not disable Microsoft programs. Eventually, by the process of elimination, you will find the process and or startup program that is causing the issue.


Posted by Richard on March 12, 2012 at 4:05 PM Comments comments (0)

What is GOD MODE anyway? Well, quite simply it's a one stop utility for your computer that has all kinds of neat administrative tools. To enable GOD MODE, right click anywhere on your desktop and create a new blank folder. Then rename the folder with the following code: God Mode.{ED7BA470-8E54-465E-825C-99712043E01C}. To do this simply copy and paste what I have here in its entirety as your new folder name.

WARNING! This is only for 32 bit systems. This works on 32 bit Windows VISTA and Windows 7. If you are running 64 bit and enable GOD MODE your computer may crash. If you have already crashed your computer, see my blog titled "Blue Screen"


Posted by Richard on March 8, 2010 at 2:25 PM Comments comments (0)

Ok, so my daughter accidently spilled soda on my computer and then dropped it! What to do? Well, the hard drive sounded like an old motor. I persevered though and used a number of tools to recover as much as I could and installed a new hard drive. One tool I used was the vista reinstallation CD. I didn’t have this so I had to download it (check my Links area for this). That didn’t work. I tried EBCD. No luck. Tried UBCD. Still no luck! Sometimes you have to shell out some money. I did find a program that I have never used before called HDD Regenerator. This program utilizes advanced algorithms to recover bad/damaged sectors. It did the trick!