24PinTech Wiki - User contributions [en]

Resetting Cisco 3800 Series Routers

2019-02-05T20:15:02Z

Bwatson:

==Introduction==
Cisco's 3800 series include 4 different type of routers: Cisco 3825, Cisco 3825-NOVPN, the Cisco 3845, and the Cisco 3845-NOVPN. Depending on the series of the router, there will be different methods of resetting. All Cisco routers will use the ROMMON mode to reset if a password was configured. ROMMON mode is to be used for troubleshooting purposes, or if a password from a previous configuration has been forgotten. The following is the method to reset a Cisco 3800 Series router.

==Clearing Configurations on a Cisco 3800==
If a router has a previous configuration, a network administrator may have to clear the configurations in order to configure the necessary components needed on a network. As such, ensure that the router is accessible; ''SSH or Telnet can be used to remote access, but otherwise access through console''. Before proceeding to clear the configurations, connect the console rollover cable. The pin-end should be connected to the corresponding port on the host device, and the RJ45 end should be connected to the console port found behind the router. A terminal to get access the router is needed. Some popular terminals include TeraTerm, PuTTY, and SecureCRT ''(make sure to have any of these installed on the host device)'' .

==Key Items Needed==

*Host Computer
*Rollover Console Cable
*Terminal Emulator (I.e. TeraTerm, SecureCRT, PuTTY)

==Clearing Configurations==
Be sure to always clear all configurations of the 3800 if it is not being used.
===Step One: Hardware===
Plug in the power cable of the router to an open outlet. Connect to the router using a console cable (usually light blue).

*NOTE: The RJ45 end of the console cable connects to the corresponding console port on the router, and the pin end connects to the corresponding port on the host device.

Turn on the host computer and the Cisco 3800 router by flipping the switch. Make sure that all lights on the router are on and identified as a light green.

===Step Two: Terminal Programs===
From the host computer, open any of the terminal emulators installed. A window will open with a menu of settings prior to accessing the router. By default, the menu should already be set, assuming console connection.

*NOTE: If the router is being consoled, then ensure that the terminal is set to '''Serial Com 1'''.

Once the menu is set, click '''OK'''. The router will boot and open its configuration files.

===Step Three: Booting===
Upon booting, the router may input the following message:

*'''Would you like to enter the initial dialog? [yes/no]'''

Respond to the message by typing '''no''', and then hit enter. Depending on the age of the router and the amount of configurations, the router may take awhile to process the '''no''' message. After it loads, the following message will show:

*'''Press RETURN to get started'''

From here, you would press '''enter'''. '''Then you will enter [http://24pin.tech/ww2w.html the hidden page].'''

===Step Four: Clearing Process===
After hitting enter, you will be in '''User Exec Mode''' once the following output shows:

*'''[''Hostname'']>'''

All the '''show commands''' are available in '''Privileged Exec Mode'''. To enter this mode, type '''enable''':

*'''[''Hostname'']>enable'''

A signaler that indicates that you have entered '''Privileged Exec''' is by the '''pound symbol''' at the end of the command line:

*'''[''Hostname'']#'''

The first thing you should do is ensure that there is a saved configuration file. You would have to use a series of '''show commands''' to verify. Some of the show commands you can use are as follows:

*'''[''Hostname'']#show ip int brief''' - This command specifically shows which interfaces on the router have been assigned IP addresses. It can be used as an indicator that there is indeed a saved configuration file.
*'''[''Hostname'']#show running-config''' - This command will show '''ALL''' the configurations including any configured protocols, encapsulation methods, and etc.

Once you have verified that there is a saved file, enter the following command to delete the configuration file:

*'''[''Hostname'']#erase startup-config'''
**NOTE: The router will ask you if you are sure about deleting the file. Simply press '''enter'''.

===Step Five: Reload/Verification===
NOTE: It is crucial that you reload the router once you delete the file. The following command will essentially reboot the router to a "factory" state:

*'''[''Hostname'']#reload'''
**NOTE: The computer will begin to reboot. It might look like it is frozen, but it really isn't. The router is is processing the blank file and is trying to assume its factory state. '''DO NOT EXIT THE TERMINAL, AND DO NOT SPAM ANY KEYS. BY DOING SO, THE ROUTER WILL ASSUME THAT IT IS TO ABORT THE REBOOT, AND YOU WOULD HAVE TO DO THE PROCESS ALL OVER AGAIN'''

A signaler that the reboot is working is if you see the router spamming symbols such as '''#####''', or '''&&&&&'''. The router will then show the prompts under '''Step Three'''. You would follow the same steps. To verify that the 3800 is blank, use the show commands under '''Step 4'''.

==Common Issues & Troubleshooting==
Often, with a pre-configured router, there will be a password that a network technician or administrator might not be able to identify. These passwords are crucial for accessing the router itself and deleting the configuration file. If the password is not known, a mode called '''ROMMON''' would have to be used in order to delete that password from the configuration file, and allow access into the router.

==ROMMON Method==
Booting into ROMMON is a bit different than booting into the router's default mode:

===Step 1===
Follow the same '''Hardware''' and '''Software''' steps on the '''Clearing Configurations''' section.

===Step 2===
Perform a break by holding down '''ALT + B''' upon boot.

*NOTE: Do NOT let go of these keys. Hold them down until you see the following prompt: '''''Rommon 1>'''''
*SECOND NOTE: the number after the ROMMON prompt does not affect commands.

===Step 3===

*Type the command: '''confreg 0x2142''' and hit enter. What this command does, is that it will command the router to boot from '''Flash'''. It will essentially bypass the startup configuration where the passwords are stored.
**'''''Rommon 1>confreg 0x2142'''''

===Step 4===
Now type the '''reset''' command on the next prompt. This will allow the router to reboot and ignores any of the saved configurations:

*'''''Rommon 1>reset'''''

===Step 5===
The router will now reboot and may take a few minutes. Make sure NOT to press any keys that can possibly abort the reboot.

*For any setup questions, type '''No'''.

===Step 6===
Once the router finishes booting, hit enter when the following prompt shows:

*'''Press RETURN to get started'''

===Step 7===
Hit enter to go into '''User EXEC Mode'''.

===Step 8===
Enter '''Privileged EXEC''' Mode by typing '''enable'''.

===Step 9===
Now all you have to do is verify that the saved file is deleted using show commands:

*'''''[Router Name]#show running-config'''''
**NOTE: If necessary, or just to be sure, you may use the '''erase startup-config''' command:
***'''''[Router Name]#erase startup-config'''''

==Quick Notes==
All the documentation above is specifically for Cisco 3800 Series routers. As far as the hardware and software aspect, everything will be pretty much the same regardless of the Cisco device. The only method that differs between Cisco devices, are booting into ROMMON and the '''confreg''' command to boot into '''Flash'''.

Resetting Cisco 3800 Series Routers

2019-02-04T20:33:11Z

Bwatson:

==Introduction==
Cisco's 3800 series include 4 different type of routers: Cisco 3825, Cisco 3825-NOVPN, the Cisco 3845, and the Cisco 3845-NOVPN. Depending on the series of the router, there will be different methods of resetting. All Cisco routers will use the ROMMON mode to reset if a password was configured. ROMMON mode is to be used for troubleshooting purposes, or if a password from a previous configuration has been forgotten. The following is the method to reset a Cisco 3800 Series router.

==Clearing Configurations on a Cisco 3800==
If a router has a previous configuration, a network administrator may have to clear the configurations in order to configure the necessary components needed on a network. As such, ensure that the router is accessible; ''SSH or Telnet can be used to remote access, but otherwise access through console''. Before proceeding to clear the configurations, connect the console rollover cable. The pin-end should be connected to the corresponding port on the host device, and the RJ45 end should be connected to the console port found behind the router. A terminal to get access the router is needed. Some popular terminals include TeraTerm, PuTTY, and SecureCRT ''(make sure to have any of these installed on the host device)'' .

==Key Items Needed==

*Host Computer
*Rollover Console Cable
*Terminal Emulator (I.e. TeraTerm, SecureCRT, PuTTY)

==Clearing Configurations==
Be sure to always clear all configurations of the 3800 if it is not being used.
===Step One: Hardware===
Plug in the power cable of the router to an open outlet. Connect to the router using a console cable (usually light blue).

*NOTE: The RJ45 end of the console cable connects to the corresponding console port on the router, and the pin end connects to the corresponding port on the host device.

Turn on the host computer and the Cisco 3800 router by flipping the switch. Make sure that all lights on the router are on and identified as a light green.

===Step Two: Terminal Programs===
From the host computer, open any of the terminal emulators installed. A window will open with a menu of settings prior to accessing the router. By default, the menu should already be set, assuming console connection.

*NOTE: If the router is being consoled, then ensure that the terminal is set to '''Serial Com 1'''.

Once the menu is set, click '''OK'''. The router will boot and open its configuration files.

===Step Three: Booting===
Upon booting, the router may input the following message:

*'''Would you like to enter the initial dialog? [yes/no]'''

Respond to the message by typing '''no''', and then hit enter. Depending on the age of the router and the amount of configurations, the router may take awhile to process the '''no''' message. After it loads, the following message will show:

*'''Press RETURN to get started'''

From here, you would press '''enter'''. '''Then you will enter [http://wiki.24pin.tech/index.php?title=Hidden_page the hidden page].'''

===Step Four: Clearing Process===
After hitting enter, you will be in '''User Exec Mode''' once the following output shows:

*'''[''Hostname'']>'''

All the '''show commands''' are available in '''Privileged Exec Mode'''. To enter this mode, type '''enable''':

*'''[''Hostname'']>enable'''

A signaler that indicates that you have entered '''Privileged Exec''' is by the '''pound symbol''' at the end of the command line:

*'''[''Hostname'']#'''

The first thing you should do is ensure that there is a saved configuration file. You would have to use a series of '''show commands''' to verify. Some of the show commands you can use are as follows:

*'''[''Hostname'']#show ip int brief''' - This command specifically shows which interfaces on the router have been assigned IP addresses. It can be used as an indicator that there is indeed a saved configuration file.
*'''[''Hostname'']#show running-config''' - This command will show '''ALL''' the configurations including any configured protocols, encapsulation methods, and etc.

Once you have verified that there is a saved file, enter the following command to delete the configuration file:

*'''[''Hostname'']#erase startup-config'''
**NOTE: The router will ask you if you are sure about deleting the file. Simply press '''enter'''.

===Step Five: Reload/Verification===
NOTE: It is crucial that you reload the router once you delete the file. The following command will essentially reboot the router to a "factory" state:

*'''[''Hostname'']#reload'''
**NOTE: The computer will begin to reboot. It might look like it is frozen, but it really isn't. The router is is processing the blank file and is trying to assume its factory state. '''DO NOT EXIT THE TERMINAL, AND DO NOT SPAM ANY KEYS. BY DOING SO, THE ROUTER WILL ASSUME THAT IT IS TO ABORT THE REBOOT, AND YOU WOULD HAVE TO DO THE PROCESS ALL OVER AGAIN'''

A signaler that the reboot is working is if you see the router spamming symbols such as '''#####''', or '''&&&&&'''. The router will then show the prompts under '''Step Three'''. You would follow the same steps. To verify that the 3800 is blank, use the show commands under '''Step 4'''.

==Common Issues & Troubleshooting==
Often, with a pre-configured router, there will be a password that a network technician or administrator might not be able to identify. These passwords are crucial for accessing the router itself and deleting the configuration file. If the password is not known, a mode called '''ROMMON''' would have to be used in order to delete that password from the configuration file, and allow access into the router.

==ROMMON Method==
Booting into ROMMON is a bit different than booting into the router's default mode:

===Step 1===
Follow the same '''Hardware''' and '''Software''' steps on the '''Clearing Configurations''' section.

===Step 2===
Perform a break by holding down '''ALT + B''' upon boot.

*NOTE: Do NOT let go of these keys. Hold them down until you see the following prompt: '''''Rommon 1>'''''
*SECOND NOTE: the number after the ROMMON prompt does not affect commands.

===Step 3===

*Type the command: '''confreg 0x2142''' and hit enter. What this command does, is that it will command the router to boot from '''Flash'''. It will essentially bypass the startup configuration where the passwords are stored.
**'''''Rommon 1>confreg 0x2142'''''

===Step 4===
Now type the '''reset''' command on the next prompt. This will allow the router to reboot and ignores any of the saved configurations:

*'''''Rommon 1>reset'''''

===Step 5===
The router will now reboot and may take a few minutes. Make sure NOT to press any keys that can possibly abort the reboot.

*For any setup questions, type '''No'''.

===Step 6===
Once the router finishes booting, hit enter when the following prompt shows:

*'''Press RETURN to get started'''

===Step 7===
Hit enter to go into '''User EXEC Mode'''.

===Step 8===
Enter '''Privileged EXEC''' Mode by typing '''enable'''.

===Step 9===
Now all you have to do is verify that the saved file is deleted using show commands:

*'''''[Router Name]#show running-config'''''
**NOTE: If necessary, or just to be sure, you may use the '''erase startup-config''' command:
***'''''[Router Name]#erase startup-config'''''

==Quick Notes==
All the documentation above is specifically for Cisco 3800 Series routers. As far as the hardware and software aspect, everything will be pretty much the same regardless of the Cisco device. The only method that differs between Cisco devices, are booting into ROMMON and the '''confreg''' command to boot into '''Flash'''.

FOG

2019-02-04T20:27:33Z

Bwatson:

==Initial Setup==
Format and install Ubuntu 17.04 on the computer that will be hosting the FOG Server (or whatever version of Linux you prefer). You can download it [https://www.ubuntu.com/download here].

==Getting Things Ready==
Download FOG (it is recommended that you get the latest version from [https://fogproject.org/download here]).

==Installing FOG==
Run these commands in the download directory ''(this requires an internet connection)'': <code>tar -xzvf FOG_FILENAME_HERE.tar.gz && cd FOG_FILENAME_HERE/bin && sudo ./install.sh</code>

''TIP: After starting the install command <code>(sudo ./install.sh)</code>, don’t cancel while the installation is in progress as some files will remain and may cause issues when trying to install later.''

==Configuring Your FOG Installation==
The last command will initialize the install process, which is fairly straightforward. If you need help with the install process, or are using a different OS, visit the FOG wiki: [https://wiki.fogproject.org/wiki/index.php?title=Main_Page]. Some of the settings require you know the basics of your network setup, so it will vary depending on the network.

More info on installation specifically can be found here: [https://wiki.fogproject.org/wiki/index.php?title=Installation FOG Official Install Guide]

==Access the FOG GUI==
This can be done by opening a browser tab on any computer on the same network by typing the IP of the FOG server and ending it with /fog.
There you can access the settings and manage images and accounts.

For example: 10.21.25.4/fog

==PXE Booting Your Computer==
You will need to access the BIOS and turn on network boot if not already enabled, and enable legacy network boot if available for better compatibility. You may need to turn off the secure boot setting depending on the device.

==Registering==
To register computers, you must PXE boot them into FOG, and it recommended that you use full host registration. Then follow the on screen steps to register your device. The registration process itself remains the same across all devices, but PXE booting will be different across devices.

==Updating a FOG Imaging Server==
This will be a quick rundown of how to update a FOG imaging server, and how to fix some common issues you may run into while doing so.
This was written for the Linux version of FOG (specifically Ubuntu) it may be different on other Linux distros and is very different. If you are running a Windows version of FOG, at the time of writing that is not officially supported by FOG Project, so you are pretty much on your own for now.

===The Initial Steps===
If you are updating to a newer FOG version, you need to download the appropriate fog_x.x.x.tar.gz file (if you are new to Linux tar.gz files are basically a .zip, .rar, or .7zip in Windows). You will the need to run this set of commands to unzip it and run the install script inside of it. If you have installed FOG before, this is the same process and doing an installation, just the install file uses your existing FOG server settings and only changes the files that it needs to (so don't worry it's not a total reinstall everything will still be there).

[https://fogproject.org/download FOG Download]

''(this requires an internet connection and must be run in the Downloads directory)'':

<code>tar -xzvf fog_x.x.x.tar.gz

cd fog_x.x.x/bin

sudo ./install.sh</code>

The install.sh file as you can see must be run as sudo or root to be able to properly install, so you will need the password for that level of access if necessary.

The script will run, and may ask you to confirm your current settings, and will update FOG and it's dependencies to the latest version accordingly. A restart of the host afterwards is recommended.

More info on an initial install can be found here: [[FOG Server Surface Compatability]] and here: [https://wiki.fogproject.org/wiki/index.php?title=Installation FOG Official Install Guide]

===Kernel Updates===
After you update FOG you will need to update the kernel that fog uses for the bzimage and bzimage32. These files are what the computers and devices PXE booting from the server will use to boot, and the newer versions add compatibility for newer devices (such as ones with finicky UEFI BIOS'). To update the kernel you will need to open the FOG management console (either by localhost/fog on the host machine or by the IP address you set to it on another machine with /fog). You will then click on the wrench in the top right to get to the FOG Configuration page. On the right there is a kernel update link you need to click on. Then there will be a list of kernels available if your kernel is not up to date. You will need to install two kernels, both the latest version. The ones at the top will be the latest, so click download button (big green downward arrow) below the first kernel labeled x86_64. You can rename the kernel, but for most instances that is unnecessary so click next and it will update. Repeat this for a x64 kernel.

More info on kernel updates can be found here: [https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update Official FOG Kernel Update Guide]

==Imaging Microsoft Surfaces (Surface Pro 2) with FOG==
Here are the details for making a FOG server work with Surface Pros and other devices that might be particular in the same way:

===PXE Booting Your Surface Pro 2===
To PXE boot a microsoft surface you must first disable secure boot. This can be done by holding the volume up button and holding power, and releasing the power button when the Surface screen is displayed. Then click on the secure boot option and click disable then save and exit.

To PXE boot the microsoft surface, you then hold down the volume down button and power at the same time. Once the Surface screen is displayed, release the power button. Then the PXE boot screen will come up. (make sure it is connected to a network via ethernet adapter before PXE booting)

When the FOG menu pops up, you can capture an image to use for the rest of the surfaces.

===More Information on Surfaces and Other Special Device Booting===
The IPXE protocol version used by microsoft surfaces is only supported by the latest versions of FOG. Version 1.4.4 (september 2017) is what was used for this, along with the surface pro 2 tablets, and this used a windows 8 Pro installation (as windows 10 is not natively supported by the original surfaces). FOG was installed on a small computer inside of the Ubuntu 17.04 OS. If you are going to use computers such as these (ones with UEFI or very custom BIOS') then you must use the latest version possible of FOG.

If you have any errors with DHCP and UEFI, I recommend looking [https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence here]. '''Then look for the topic that talks about starting anew.'''

==Troubleshooting==
Here are different solutions we have found to various FOG problems that you may encounter:

==="What if FOG is blocked?"===
If the download fails during the install process, check your proxy settings on your network or ask your network administrator if it is blocked. If so, have the admin allow access, use a VPN (with proper permission), or take it to another network.

(If installed on another network, once it is moved to another network all IP settings for the server will need to be reconfigured. If it is installed on the same network it is being used on, then skip the next step)

(only do this if installed on a different network than it will be used on, or if there are IP configuration errors.)
Look through all of the settings in the FOG server gui, and make sure all things that reference IP addresses are properly configured for your network. This varies by FOG version and type of install, so it is a tedious but necessary process. Then, you will need to edit the fog configuration file, which you can find by checking the wiki as it’s location varies by OS and FOG version. You will also need to edit the dhcpd.conf file and the network config settings of the Ubuntu operating system to have the correct IP config settings. (This may vary by Ubuntu version, or linux version, so check the wiki and the proper documentation for that OS).

===TFTP Errors===
The error looks like this or something similar depending on configuration:

[[File:ftp_put_error.jpg|550px]]

If you get a tftp or ftp_put() error when trying to update the kernel, these are the solutions we've found:

====Solution 1: Credentials====
There are a few different places where FOG uses credentials to manage different files using the fog user account. If the credentials mismatch in any of the places, some functionality will not work. In total there are four different places where those credentials should match (on a standard installation at least, if you need it different you know what you are doing and probably don't need this).
The places where credentials need to match can be found in these places:

*Web Interface -> Storage Management -> [Your storage node] -> Management Username & Management Password
*Web Interface -> FOG Configuration -> FOG Settings -> TFTP Server -> FOG_TFTP_FTP_USERNAME & FOG_TFTP_FTP_PASSWORD
*The local 'fog' user's password on the Linux FOG server
*Server file: /opt/fog/.fogsettings -> username and password settings (For recent FOG Trunk versions only. 1.2.0 does not have this setting. 1.3.0 and newer versions at the time of writing will contain this.)

The first two are easy to check, just use the FOG web interface using a web browser on the host or a machine on the same network.

The fog user password can be changed by using the command:

<code>sudo passwd fog</code>

The server file can be edited using vim in the Linux terminal:

<code>vi /opt/fog/.fogsettings</code>

(More info on vim or vi can be found [https://wiki.fogproject.org/wiki/index.php?title=Vi here].

Official FOG documentation on this issue can be found [https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Credentials_.2F_Passwords here].

====Solution 2: Use a Kernel Install Script====
If the first solution doesn't fix the problem, then this probably will. This solution is to manually install the kernel update through a script in the terminal, and as long as you have the correct permissions and a somewhat new version of Linux (CentOS 7+, Fedora 19+, RHEL 7+, Debian8+, and Ubuntu14+) this should work fine.

This script will backup the old kernel versions you already have installed in case of emergency, and will update to the newest ones. It has comments within it to make it easy to understand exactly what each step does.
<code>#Delete previous backed up kernels & inits.

rm -rf /var/www/html/fog/service/ipxe/old

#Make a directory to put old kernels & inits into.

mkdir /var/www/html/fog/service/ipxe/old

#Move old inits, get new ones.

mv /var/www/html/fog/service/ipxe/init.xz /var/www/html/fog/service/ipxe/old

wget https://fogproject.org/inits/init.xz -O /var/www/html/fog/service/ipxe/init.xz

mv /var/www/html/fog/service/ipxe/init_32.xz /var/www/html/fog/service/ipxe/old

wget https://fogproject.org/inits/init_32.xz -O /var/www/html/fog/service/ipxe/init_32.xz

#Move old kernels, get new ones.

mv /var/www/html/fog/service/ipxe/bzImage /var/www/html/fog/service/ipxe/old

wget https://fogproject.org/kernels/bzImage -O /var/www/html/fog/service/ipxe/bzImage

mv /var/www/html/fog/service/ipxe/bzImage32 /var/www/html/fog/service/ipxe/old

wget https://fogproject.org/kernels/bzImage32 -O /var/www/html/fog/service/ipxe/bzImage32</code>

<code>#Reset Ownership:</code>

<code>#Fedora, CentOS, RHEL:</code>

<code>chown -R fog:apache /var/www/html/fog/service/ipxe</code>

<code>#Ubuntu, Debian:</code>

<code>chown -R fog:www-data /var/www/html/fog/service/ipxe</code>

<code>#Set permissions:</code>

<code>chmod -R 775 /var/www/html/fog/service/ipxe</code>

<code>#Script complete.</code>

<code>echo DONE!</code>

The official FOG documentation can be found [https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update here] at the bottom of the page.

===Multicast Not Working===
If after an update Multicast stops functioning, or you find it stops working at some point, this is what has worked in the past.

''Please note this will not fix any and all Multicast problems, but it did fix our issue where it would open partclone and not start the cast itself, and it showed the error <code> This is not the master node</code> in the logs for multicast''

====Multicast Repair Step One====
This first step may seem scary, but it will not damage any of the FOG images or files.

We are going to delete the directory /opt/fog
<code>sudo rm -r /opt/fog</code>

''(The -r is necessary to delete directories)''

Then rerun the installer by downloading the version of FOG you were using (or the latest one available if you're not using it). Then try running a multicast and see if it works. If not, move on to step two.

====Multicast Repair Step Two====
This step will require us to modify the MySQL tables by running some commands in the terminal. You should run <code>sudo su</code> before running the script to make things easier.

Below are the commands you will need to run:

<code>mysql</code>

<code>use fog</code>

<code>DELETE FROM `multicastSessions` WHERE 1;</code>

<code>DELETE FROM `multicastSessionsAssoc` WHERE 1;</code>

<code>DELETE FROM `tasks` WHERE `taskTypeID` = 8;</code>

<code>quit</code>

This will clear the MySQL tables. After this you will need to rerun the installer and everything should work fine from there.

The official Multicast FOG Documentation can be found [https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_Downloading_-_Multicast Here].

===For Issues You Can't Solve with This Page===
Check the [https://wiki.fogproject.org/wiki/index.php?title=Main_Page FOG Project Wiki] and the [https://forums.fogproject.org/ FOG Project Forums]. These pages should solve any other issues you have, and any issues you solve that aren't on here should be properly documented here to help future 24PinTechs.

==xRDP==

This is a very useful tool that is currently installed on our FOG server. This allows for any Windows user to use remote desktop to remotely control the host Linux system with full GUI support. To connect just use the FOG IP, and when prompted type in the login.

To learn more about xRDP, go to the wiki page: [[xRDP]]

D-Link Camera Setup

2019-02-04T20:24:35Z

Bwatson:

Discover what the serial number is and search this up to find the specific software for the camera. Open up the start up wizard and follow the instructions. '''Continue to the topic of ominous weather.'''

Setting Up A MAME Machine

2018-12-10T16:34:48Z

Bwatson: Added Front End list

==Downloading the correct version of MAME==

===What we use===
The version of MAME we are using that we recommend using is the latest version available found [https://www.mamedev.org/release.html here]. The latest supported version is '''MAME v0.204''' and '''''is the only version''''' that will be used on the MAME kiosk at all times.

'''[https://github.com/mamedev/mame/releases/download/mame0204/mame0204b_64bit.exe Download MAME v0.204]'''

===What can be used for a personal build===
Any version below above '''MAME v0.197''' can be used for our games library.

==Installing MAME==

===Step 1: Download MAME===
Download your preferred version of MAME.

===Step 2: Run the EXE===
Run the installation .exe and run through the steps. MAME can be perfectly set up for USB portability, just make sure you have all the files and leave none behind. If you are installing on a USB, make sure to have at least 16gb of storage to leave space for any games you may want to play.

===Step 3: Insert your ROMS.===
You're all good to go! Start up MAME and you should be ready to insert your ROMs. Your ROMs should be the folder titled "roms" in whatever location you have chosen to install MAME to, just drag and drop your files into there.

==Adding a Front End==

===Selecting your Front End===
Selecting a front end for your MAME machine is all decided on what functionality you want and whatever aesthetic you wish, so I'll provide a link to all available front-ends, free and premium. Front Ends are the fancy GUI you see while selecting which game you wish to play on whatever system you have ready to emulate and is fairly easy to set up, so long you follow their instructions provided.

==== Windows supported front ends ====

* [http://www.advancemame.it AdvanceMenu] - Free
* [http://www.mameworld.info/pc2jamma/frontend.html ArcadeOS] - Free
* [https://www.dribin.org/dave/game_launcher/ Game Launcher] - Free
* '''[https://hyperspin-fe.com HyperSpin] - Freemium'''
* [http://kymaera.sourceforge.net Kymaera] - Free
* '''[http://www.mgalaxy.com mGalaxy] - Freemium (Our selection)'''
* '''[https://www.launchbox-app.com LaunchBox]''' '''- Freemium'''

==== Mac, DOS, and Linux supported front ends ====

* '''[https://www.launchbox-app.com LaunchBox]''' '''- Freemium'''
* [http://www.cabrio-fe.org Cabrio] - Free
* [http://www.anti-particle.com/wahcade.shtml Wah!Cade] - Free

Setting Up A MAME Machine

2018-12-06T16:12:14Z

Bwatson: Started MAME documentation

== Downloading the correct version of MAME ==

=== What we use: ===
The version of MAME we are using that we recommend using is the latest version available found [https://www.mamedev.org/release.html here]. The latest supported version is '''MAME v0.204''' and '''''is the only version''''' that will be used on the MAME kiosk at all times.

'''[https://github.com/mamedev/mame/releases/download/mame0204/mame0204b_64bit.exe Download MAME v0.204]'''

=== What can be used for a personal build: ===
Any version below above '''MAME v0.197''' can be used for our games library.

== Installing MAME ==

=== Step 1: ===
Download your preferred version of MAME.

=== Step 2: ===
Run the installation .exe and run through the steps.

=== Step 3: ===
You're all good to go! Start up MAME and you should be ready to insert your ROMs.

== Adding your set of ROMs ==

=== Using our own preset games list: ===

POS Retail System Device

2018-09-14T15:42:58Z

Bwatson: Added the entire POS System Maintenance.

==Fixing the SQL Server==

===WMI Errors===
You'll experience an error with "WMI" if you attempt to use any of the prebuilt SQL Server management options, but don't worry about this. We won't be using the prebuilt SQL Server management options, so this WMI error is basically useless to us to fix.

===Use SQL Server Management Studio===
SQL Server Management Studio (SSMS) will be our playground for managing the databases for SQL Server 2005 and SQL Server 2008 R2. Both versions are installed onto the Windows XP box, and for good reason, as SQL Server 2008 R2 is a lot easier to manage than 2005, but 2005 is required for POSitive Retail Manager to function, so '''DO NOT REMOVE SQL SERVER 2005'''.

Once inside of SSMS, you will need to log in to a master database manager, and to do so you will need to click on '''New Query''' then log in as '''MHS-RETAIL''' using Windows Authentication, no password. Here you'll be able to restore databases from backup, create a new database, or manage existing ones. It is recommended to restore from a database backup off of the USB stick that Mr. Rodriguez has, seeing as it's already formatted for POSitive Retail Manager and Copa Corner. There's not much more to do with the SQL Server after this, so don't mess with anything else.

==Installing and maintaining the Receipt Printer==

===Knowing our printer===
The printer currently attached to the Windows XP POS box is an '''SNBC BTP-R180II (U)''', and it will stay that way. To manage the setting of the SNBC BTP-R180II (U), do ''not'' go through Windows GUI or Control Panel, instead, hold down the FEED button while powering up the device to print self-test mode. After the initial self-test, it will ask if you want to finish self-test or configure the settings, and you will hold down the FEED button until it prints out a menu.

===Configuring our printer===
As explained above, you will enter configuration mode through the printer itself. Once in configuration mode, the only option you need to check in order to ensure it can even connect to the POS Windows XP box is what mode it is in. To check the current mode of the printer, press the FEED button 7 times, then hold down the FEED button until it prints out the new page. Make sure the printer is in '''WinDriver''' mode, as it will not work on Windows XP in '''API''' mode. After checking this, you don't need to worry about any other configuration setting on the device. Don't forget to save, then exit configuration mode.

===Installing the printer===
Once you've checked to make sure the printer is in WinDriver mode, install the drivers (found here: https://www.crs-usa.com/products/printers/thermal-printers/snbc-btp-r180ii-thermal-receipt-printer-series-) while the receipt printer is plugged into the POS system AND powered on. Once it is installed, enter Printers and Devices through the Windows menu and ensure it is the default printer of the computer.

==Installing the Cash Drawer==

===Installing the cash drawer===
Take the ''one and only'' cable sticking out from the back of the cash drawer and plug it straight into receipt printer. That's it, don't do anything else. I'm serious.

==Installing the Barcode Scanner==

===Installing the barcode scanner===
Take the USB cable that's connected to the scanner and plug it in. Make sure the drivers are installed (there aren't any special ones online) correctly through Windows XP automatic installer, then you're done.

==Managing POSitive Retail Manager==

===Enter POSitive Retail Manager===
Open up POSitive Retail Manager through the desktop icon and log in to '''Copa Corner'''. The ID and password for '''Copa Corner''' is '''POS'''. Enter POS into both fields and choose '''Touchscreen Mode'''.

===Managing the settings of POSitive Retail Manager===
Once inside of Copa Corner, if you need to change the settings, enter through '''Manager Mode''', found in the black button in the bottom right, then tap on the other black button found on the bottom. You should find yourself in a menu screen with multiple different options, but we're not going to mess with any of those. In the top right corner you should find a tab called "Management", tap on it, then tap on '''Station Setting''' or something like that. '''We will only modify POS 1, POS 2 is unused and could possibly mess up if messed with.''' Edit POS 1 and you'll be in the settings.

=== Set up any peripherals ===
Chances are that POSitive Retail Manager could be reading the wrong printer for tending to the purchase, so in order to fix this, tap on the Devices tab and then Cash Drawer. Under this windows, you'll find which default printer the settings are using for sales, and it should read '''BTP-R180II (U) (Copy)'''. If it doesn't say this, tap on the three dots and change the default printer to BTP-R180II (U) (Copy). In the off chance that you ''need'' to print receipts, go under Printers & Options and tap on Invoice, and here you can change the default printer for printing Invoices. Once again, it should read BTP-R180II (U) (Copy), and if it doesn't, change it.

POS Retail System Device

2018-09-14T15:38:15Z

Bwatson:

==Fixing the SQL Server==

===WMI Errors===
You'll experience an error with "WMI" if you attempt to use any of the prebuilt SQL Server management options, but don't worry about this. We won't be using the prebuilt SQL Server management options, so this WMI error is basically useless to us to fix.

===Use SQL Server Management Studio===
SQL Server Management Studio (SSMS) will be our playground for managing the databases for SQL Server 2005 and SQL Server 2008 R2. Both versions are installed onto the Windows XP box, and for good reason, as SQL Server 2008 R2 is a lot easier to manage than 2005, but 2005 is required for POSitive Retail Manager to function, so '''DO NOT REMOVE SQL SERVER 2005'''.

Once inside of SSMS, you will need to log in to a master database manager, and to do so you will need to click on '''New Query''' then log in as '''MHS-RETAIL''' using Windows Authentication, no password. Here you'll be able to restore databases from backup, create a new database, or manage existing ones. It is recommended to restore from a database backup off of the USB stick that Mr. Rodriguez has, seeing as it's already formatted for POSitive Retail Manager and Copa Corner. There's not much more to do with the SQL Server after this, so don't mess with anything else.

==Installing and maintaining the Receipt Printer==

===Knowing our printer===
The printer currently attached to the Windows XP POS box is an '''SNBC BTP-R180II (U)''', and it will stay that way. To manage the setting of the SNBC BTP-R180II (U), do ''not'' go through Windows GUI or Control Panel, instead, hold down the FEED button while powering up the device to print self-test mode. After the initial self-test, it will ask if you want to finish self-test or configure the settings, and you will hold down the FEED button until it prints out a menu.

===Configuring our printer===
As explained above, you will enter configuration mode through the printer itself. Once in configuration mode, the only option you need to check in order to ensure it can even connect to the POS Windows XP box is what mode it is in. To check the current mode of the printer, press the FEED button 7 times, then hold down the FEED button until it prints out the new page. Make sure the printer is in '''WinDriver''' mode, as it will not work on Windows XP in '''API''' mode. After checking this, you don't need to worry about any other configuration setting on the device. Don't forget to save, then exit configuration mode.

===Installing the printer===
Once you've checked to make sure the printer is in WinDriver mode, install the drivers (found here: https://www.crs-usa.com/products/printers/thermal-printers/snbc-btp-r180ii-thermal-receipt-printer-series-) while the receipt printer is plugged into the POS system AND powered on. Once it is installed, enter Printers and Devices through the Windows menu and ensure it is the default printer of the computer.

==Installing the Cash Drawer==

===Installing the cash drawer===
Take the ''one and only'' cable sticking out from the back of the cash drawer and plug it straight into receipt printer. That's it, don't do anything else. I'm serious.

==Installing the Barcode Scanner==

===Installing the barcode scanner===
Take the USB cable that's connected to the scanner and plug it in. Make sure the drivers are installed (there aren't any special ones online) correctly through Windows XP automatic installer, then you're done.

==Managing POSitive Retail Manager==

===Enter POSitive Retail Manager===
Open up POSitive Retail Manager through the desktop icon and log in to '''Copa Corner'''. The ID and password for '''Copa Corner''' is '''POS'''. Enter POS into both fields and choose '''Touchscreen Mode'''.

=== Managing the settings of POSitive Retail Manager ===
Once inside of Copa Corner, if you need to change the settings, enter through '''Manager Mode''', found in the black button in the bottom right, then tap on the other black button found on the bottom. You should find yourself in a menu screen with multiple different options, but we're not going to mess with any of those. In the top right corner you should find a tab called "Management", tap on it, then tap on '''Station Setting''' or something like that. '''We will only modify POS 1, POS 2 is unused and could possibly mess up if messed with.''' Edit POS 1 and you'll be in the settings.

POS Retail System Device

2018-09-13T20:30:23Z

Bwatson:

POS Retail System Device

2018-09-13T20:23:30Z

Bwatson:

POS Retail System Device

2018-09-13T20:20:18Z

Bwatson:

POS Retail System Device

2018-09-13T20:15:51Z

Bwatson: Created page with "== Fixing the SQL Server == === WMI Errors === You'll experience an error with "WMI" if you attempt to use any of the prebuilt SQL Server management options, but don't worry..."

User:Bwatson

2018-07-30T20:23:41Z

Bwatson: I made the page, yo.

It's me, the boy, the OS-meister.

[[File:This is God.png|thumb|The OS-meister himself.]]

= Why am I here? =
In order to become big boy tech supreme and dominate my submissive co-workers.

= What do I want to learn? =
Tech stuff like you'd never know.

= What do I want to leave behind? =
A piece of me in everyone's hearts and some terrible memes that everyone hates, like everyone hates me.

File:This is God.png

2018-07-30T20:20:29Z

Bwatson:

True image of god.