https://wiki.24pin.tech/api.php?action=feedcontributions&feedformat=atom&user=Ebrownthunder24PinTech Wiki - User contributions [en]2026-05-08T14:08:12ZUser contributionsMediaWiki 1.37.1https://wiki.24pin.tech/index.php?title=FOG&diff=1089FOG2020-03-11T18:33:20Z<p>Ebrownthunder: </p>
<hr />
<div>==Initial Setup==<br />
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].<br />
<br />
==Getting Things Ready==<br />
Download FOG (it is recommended that you get the latest version from [https://fogproject.org/download here]).<br />
<br />
==Installing FOG==<br />
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><br />
<br />
''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.''<br />
<br />
==Configuring Your FOG Installation==<br />
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.<br />
<br />
More info on installation specifically can be found here: [https://wiki.fogproject.org/wiki/index.php?title=Installation FOG Official Install Guide]<br />
<br />
===Setting up FOG to be Used on Another Network===<br />
<br />
FOG when installing will automatically pull the network information from the network adapter you tell it that you would like to use. To configure FOG to be used on another network, during the start of the install your network adapter will need to be configured with the settings of the other network. It will seem wrong, as you will have no internet (or limited access) but it is the only way to trick FOG.<br />
<br />
Then once you reach the point to where you have configured all of your settings, it will show all of the settings and ask if you'd like to continue the installation with those settings. '''Before typing y to continue''' you must have internet access. So you must set your network adapter to work with your current network, as the rest of the install will be pulling necessary files and programs from the internet. '''Even if the dependencies are already installed''' you must have internet and follow all the way through the install, as it does internet connectivity tests and does not create all of the necessary FOG, MySQL, and database files until the very end.<br />
<br />
'''If you have installed before, and now want to move to a new network''' you need to remove the /opt/fog folder. Do so by running the command: <code>sudo rm -r /opt/fog</code> this will remove the old installation configuration information, but will keep all important things like your images, just follow the directions for setting up FOG for another network if you want to set it up for a different network you are not on, or do the normal installation on the new network.<br />
<br />
==Access the FOG GUI==<br />
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.<br />
There you can access the settings and manage images and accounts.<br />
<br />
For example: 10.21.25.4/fog<br />
<br />
==DHCP Setup==<br />
In order for Fog to work correctly you will need to make some adjustments to the Scope Options in DHCP. You will need to do two settings for both BIOS and UEFI machines using scope options 66 and 67. I have included a picture of the scope settings on our server.<br />
[[File:DHCP Scope Options Fog.png|left|thumb|520x520px]]<br />
<br />
Here are some helpful links from the Fog Wiki to assist you.<br />
<br />
[https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence BIOS and UEFI Co-Existence]<br />
<br />
[https://wiki.fogproject.org/wiki/index.php?title=Windows_DHCP_Server Windows DHCP Server]<br />
<br />
==PXE Booting Your Computer==<br />
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.<br />
<br />
==Registering==<br />
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.<br />
<br />
==Updating a FOG Imaging Server==<br />
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.<br />
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.<br />
<br />
===The Initial Steps===<br />
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).<br />
<br />
[https://fogproject.org/download FOG Download]<br />
<br />
''(this requires an internet connection and must be run in the Downloads directory)'':<br />
<br />
<code>tar -xzvf fog_x.x.x.tar.gz<br />
<br />
cd fog_x.x.x/bin<br />
<br />
sudo ./install.sh</code><br />
<br />
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.<br />
<br />
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.<br />
<br />
More info on an initial install can be found here: [https://wiki.fogproject.org/wiki/index.php?title=Installation FOG Official Install Guide]<br />
<br />
===Kernel Updates===<br />
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.<br />
<br />
More info on kernel updates can be found here: [https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update Official FOG Kernel Update Guide]<br />
<br />
==Imaging Microsoft Surfaces (Surface Pro 2) with FOG==<br />
Here are the details for making a FOG server work with Surface Pros and other devices that might be particular in the same way:<br />
<br />
===PXE Booting Your Surface Pro 2===<br />
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.<br />
<br />
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)<br />
<br />
When the FOG menu pops up, you can capture an image to use for the rest of the surfaces.<br />
<br />
===More Information on Surfaces and Other Special Device Booting===<br />
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.<br />
<br />
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].<br />
<br />
==Troubleshooting==<br />
Here are different solutions we have found to various FOG problems that you may encounter:<br />
<br />
==="What if FOG is blocked?" (During Installation)===<br />
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.<br />
<br />
(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)<br />
<br />
(only do this if installed on a different network than it will be used on, or if there are IP configuration errors.)<br />
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).<br />
<br />
===TFTP Errors===<br />
The error looks like this or something similar depending on configuration:<br />
<br />
[[File:ftp_put_error.jpg|550px]]<br />
<br />
If you get a tftp or ftp_put() error when trying to update the kernel, these are the solutions we've found:<br />
<br />
====Solution 1: Credentials====<br />
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).<br />
The places where credentials need to match can be found in these places:<br />
<br />
*Web Interface -> Storage Management -> [Your storage node] -> Management Username & Management Password<br />
*Web Interface -> FOG Configuration -> FOG Settings -> TFTP Server -> FOG_TFTP_FTP_USERNAME & FOG_TFTP_FTP_PASSWORD<br />
*The local 'fog' user's password on the Linux FOG server<br />
*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.)<br />
<br />
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.<br />
<br />
The fog user password can be changed by using the command:<br />
<br />
<code>sudo passwd fog</code><br />
<br />
The server file can be edited using vim in the Linux terminal:<br />
<br />
<code>vi /opt/fog/.fogsettings</code><br />
<br />
(More info on vim or vi can be found [https://wiki.fogproject.org/wiki/index.php?title=Vi here].<br />
<br />
Official FOG documentation on this issue can be found [https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Credentials_.2F_Passwords here].<br />
<br />
====Solution 2: Use a Kernel Install Script====<br />
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.<br />
<br />
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.<br />
<code>#Delete previous backed up kernels & inits.<br />
<br />
rm -rf /var/www/html/fog/service/ipxe/old<br />
<br />
<br />
#Make a directory to put old kernels & inits into.<br />
<br />
mkdir /var/www/html/fog/service/ipxe/old<br />
<br />
<br />
#Move old inits, get new ones.<br />
<br />
mv /var/www/html/fog/service/ipxe/init.xz /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/inits/init.xz -O /var/www/html/fog/service/ipxe/init.xz<br />
<br />
mv /var/www/html/fog/service/ipxe/init_32.xz /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/inits/init_32.xz -O /var/www/html/fog/service/ipxe/init_32.xz<br />
<br />
<br />
#Move old kernels, get new ones.<br />
<br />
mv /var/www/html/fog/service/ipxe/bzImage /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/kernels/bzImage -O /var/www/html/fog/service/ipxe/bzImage<br />
<br />
mv /var/www/html/fog/service/ipxe/bzImage32 /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/kernels/bzImage32 -O /var/www/html/fog/service/ipxe/bzImage32</code><br />
<br />
<br />
<code>#Reset Ownership:</code><br />
<br />
<code>#Fedora, CentOS, RHEL:</code><br />
<br />
<code>chown -R fog:apache /var/www/html/fog/service/ipxe</code><br />
<br />
<code>#Ubuntu, Debian:</code><br />
<br />
<code>chown -R fog:www-data /var/www/html/fog/service/ipxe</code><br />
<br />
<br />
<code>#Set permissions:</code><br />
<br />
<code>chmod -R 775 /var/www/html/fog/service/ipxe</code><br />
<br />
<code>#Script complete.</code><br />
<br />
<code>echo DONE!</code><br />
<br />
The official FOG documentation can be found [https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update here] at the bottom of the page.<br />
<br />
===Multicast Not Working===<br />
If after an update Multicast stops functioning, or you find it stops working at some point, this is what has worked in the past.<br />
<br />
''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''<br />
<br />
====Multicast Repair Step One====<br />
This first step may seem scary, but it will not damage any of the FOG images or files.<br />
<br />
<br />
We are going to delete the directory /opt/fog<br />
<code>sudo rm -r /opt/fog</code><br />
<br />
''(The -r is necessary to delete directories)''<br />
<br />
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.<br />
<br />
====Multicast Repair Step Two====<br />
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.<br />
<br />
Below are the commands you will need to run:<br />
<br />
<code>mysql</code><br />
<br />
<code>use fog</code><br />
<br />
<code>DELETE FROM `multicastSessions` WHERE 1;</code><br />
<br />
<code>DELETE FROM `multicastSessionsAssoc` WHERE 1;</code><br />
<br />
<code>DELETE FROM `tasks` WHERE `taskTypeID` = 8;</code><br />
<br />
<code>quit</code><br />
<br />
This will clear the MySQL tables. After this you will need to rerun the installer and everything should work fine from there.<br />
<br />
The official Multicast FOG Documentation can be found [https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_Downloading_-_Multicast Here].<br />
<br />
===For Issues You Can't Solve with This Page===<br />
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.<br />
<br />
===The Sanders-Cure-All===<br />
<br />
If there is an issue with FOG that is not easily solvable, you can follow these steps and 9/10 times it will fix it. All of these steps are found in different solutions for other problems, but done in this order can solve many common problems that seemingly can't be explained. Trust me. I've tried.<br />
<br />
''When we run commands, they are run in the Linux terminal, and run them as sudo (that means do the command <code>sudo su</code> before running them to make it easier, if it throws an error saying not to run as sudo, then open a new terminal and don't run the sudo command first.''<br />
<br />
====Step One====<br />
<br />
First we run the manual kernel update script, to ensure that all our kernels aren't broke and are the latest version:<br />
<br />
<code>#Delete previous backed up kernels & inits.<br />
<br />
rm -rf /var/www/html/fog/service/ipxe/old<br />
<br />
<br />
#Make a directory to put old kernels & inits into.<br />
<br />
mkdir /var/www/html/fog/service/ipxe/old<br />
<br />
<br />
#Move old inits, get new ones.<br />
<br />
mv /var/www/html/fog/service/ipxe/init.xz /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/inits/init.xz -O /var/www/html/fog/service/ipxe/init.xz<br />
<br />
mv /var/www/html/fog/service/ipxe/init_32.xz /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/inits/init_32.xz -O /var/www/html/fog/service/ipxe/init_32.xz<br />
<br />
<br />
#Move old kernels, get new ones.<br />
<br />
mv /var/www/html/fog/service/ipxe/bzImage /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/kernels/bzImage -O /var/www/html/fog/service/ipxe/bzImage<br />
<br />
mv /var/www/html/fog/service/ipxe/bzImage32 /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/kernels/bzImage32 -O /var/www/html/fog/service/ipxe/bzImage32</code><br />
<br />
<br />
<code>#Reset Ownership:</code><br />
<br />
<code>#Fedora, CentOS, RHEL:</code><br />
<br />
<code>chown -R fog:apache /var/www/html/fog/service/ipxe</code><br />
<br />
<code>#Ubuntu, Debian:</code><br />
<br />
<code>chown -R fog:www-data /var/www/html/fog/service/ipxe</code><br />
<br />
<br />
<code>#Set permissions:</code><br />
<br />
<code>chmod -R 775 /var/www/html/fog/service/ipxe</code><br />
<br />
<code>#Script complete.</code><br />
<br />
<code>echo DONE!</code><br />
<br />
====Step Two====<br />
<br />
Now we delete everything that has to do with FOG from the MySQL server. Cause MySQL hates us so we fight fire with fire.<br />
<br />
<code>mysql</code><br />
<br />
<code>use fog</code><br />
<br />
<code>DELETE FROM `multicastSessions` WHERE 1;</code><br />
<br />
<code>DELETE FROM `multicastSessionsAssoc` WHERE 1;</code><br />
<br />
<code>DELETE FROM `tasks` WHERE `taskTypeID` = 8;</code><br />
<br />
<code>quit</code><br />
<br />
====Step Three====<br />
<br />
Now we need to delete most of the FOG files that are on the server, cause FOG itself hates us to. Don't worry, it's not you, it's them.<br />
<br />
<code>sudo rm -r /opt/fog</code><br />
<br />
''(This doesn't delete any settings or images don't worry''<br />
<br />
====Step Four====<br />
<br />
Now we start to reinstall FOG, because a lot of it is no longer there. '''IF THERE IS A NEWER VERSION, THIS IS A GOOD TIME TO UPGRADE. IT'S ALREADY BROKEN, AND NEWER VERSIONS HAVE GOTTEN A LOT MORE STABLE PLEASE'''<br />
<br />
Download FOG (it is recommended that you get the latest version from [https://fogproject.org/download here]).<br />
<br />
If there isn't a new version and the FOG files are still in the downloads folder, then you can skip this step.<br />
<br />
====Step Five====<br />
<br />
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><br />
<br />
''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.''<br />
<br />
''PPS: It should find the old settings and try and pull some of the config. It might not. Verify all settings while running the installer.''<br />
<br />
====Step Six====<br />
<br />
Now FOG may have changed some passwords. Yeah, it can do that.<br />
<br />
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).<br />
The places where credentials need to match can be found in these places:<br />
<br />
*Web Interface -> Storage Management -> [Your storage node] -> Management Username & Management Password<br />
*Web Interface -> FOG Configuration -> FOG Settings -> TFTP Server -> FOG_TFTP_FTP_USERNAME & FOG_TFTP_FTP_PASSWORD<br />
*The local 'fog' user's password on the Linux FOG server<br />
*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.)<br />
<br />
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.<br />
<br />
The fog user password can be changed by using the command:<br />
<br />
<code>sudo passwd fog</code><br />
<br />
The server file can be edited using vim in the Linux terminal:<br />
<br />
<code>vi /opt/fog/.fogsettings</code><br />
<br />
(More info on vim or vi can be found [https://wiki.fogproject.org/wiki/index.php?title=Vi here].<br />
<br />
Official FOG documentation on this issue can be found [https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Credentials_.2F_Passwords here].<br />
<br />
'''''If you need to run as sudo and it says the password has already changed (like you can't run sudo) look at the .fogsettings file and it will contain the *new* password in plaintext. It is gonna be long and is gonna suck. If you are logged out and need to get back in, log in as guest or as another user, or boot off of a bootable linux live usb, and go to the file and take a picture of the password.'''''<br />
<br />
====Step Seven====<br />
<br />
The FOG Server may be fixed at this point, and if so yay! You're done. If it is still acting up there is more to do.<br />
<br />
Run steps two through six again and it should work, it usually is always good after a second try. If that doesn't work you'll have to do more than the cure-all, cause every time it's gone more than two it was a more in depth issue.<br />
<br />
==xRDP==<br />
<br />
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.<br />
<br />
To learn more about xRDP, go to the wiki page: [[xRDP]]<br />
<br />
==FOGBANK SERVER==<br />
the fogbank server is the server that runs our fog server for our classroom, this computer cannot be accessed via remote desktop, you need to go into the back in order to access the computer.<br />
<br />
*Processor: Intel Xeon CPU @2.80 CPU<br />
*Memory: <br />
*Storage: Samsung SSD 850 GB<br />
*System:</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=FOG&diff=1088FOG2020-03-11T18:23:58Z<p>Ebrownthunder: </p>
<hr />
<div>==Initial Setup==<br />
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].<br />
<br />
==Getting Things Ready==<br />
Download FOG (it is recommended that you get the latest version from [https://fogproject.org/download here]).<br />
<br />
==Installing FOG==<br />
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><br />
<br />
''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.''<br />
<br />
==Configuring Your FOG Installation==<br />
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.<br />
<br />
More info on installation specifically can be found here: [https://wiki.fogproject.org/wiki/index.php?title=Installation FOG Official Install Guide]<br />
<br />
===Setting up FOG to be Used on Another Network===<br />
<br />
FOG when installing will automatically pull the network information from the network adapter you tell it that you would like to use. To configure FOG to be used on another network, during the start of the install your network adapter will need to be configured with the settings of the other network. It will seem wrong, as you will have no internet (or limited access) but it is the only way to trick FOG.<br />
<br />
Then once you reach the point to where you have configured all of your settings, it will show all of the settings and ask if you'd like to continue the installation with those settings. '''Before typing y to continue''' you must have internet access. So you must set your network adapter to work with your current network, as the rest of the install will be pulling necessary files and programs from the internet. '''Even if the dependencies are already installed''' you must have internet and follow all the way through the install, as it does internet connectivity tests and does not create all of the necessary FOG, MySQL, and database files until the very end.<br />
<br />
'''If you have installed before, and now want to move to a new network''' you need to remove the /opt/fog folder. Do so by running the command: <code>sudo rm -r /opt/fog</code> this will remove the old installation configuration information, but will keep all important things like your images, just follow the directions for setting up FOG for another network if you want to set it up for a different network you are not on, or do the normal installation on the new network.<br />
<br />
==Access the FOG GUI==<br />
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.<br />
There you can access the settings and manage images and accounts.<br />
<br />
For example: 10.21.25.4/fog<br />
<br />
==DHCP Setup==<br />
In order for Fog to work correctly you will need to make some adjustments to the Scope Options in DHCP. You will need to do two settings for both BIOS and UEFI machines using scope options 66 and 67. I have included a picture of the scope settings on our server.<br />
[[File:DHCP Scope Options Fog.png|left|thumb|520x520px]]<br />
<br />
Here are some helpful links from the Fog Wiki to assist you.<br />
<br />
[https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence BIOS and UEFI Co-Existence]<br />
<br />
[https://wiki.fogproject.org/wiki/index.php?title=Windows_DHCP_Server Windows DHCP Server]<br />
<br />
==PXE Booting Your Computer==<br />
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.<br />
<br />
==Registering==<br />
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.<br />
<br />
==Updating a FOG Imaging Server==<br />
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.<br />
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.<br />
<br />
===The Initial Steps===<br />
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).<br />
<br />
[https://fogproject.org/download FOG Download]<br />
<br />
''(this requires an internet connection and must be run in the Downloads directory)'':<br />
<br />
<code>tar -xzvf fog_x.x.x.tar.gz<br />
<br />
cd fog_x.x.x/bin<br />
<br />
sudo ./install.sh</code><br />
<br />
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.<br />
<br />
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.<br />
<br />
More info on an initial install can be found here: [https://wiki.fogproject.org/wiki/index.php?title=Installation FOG Official Install Guide]<br />
<br />
===Kernel Updates===<br />
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.<br />
<br />
More info on kernel updates can be found here: [https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update Official FOG Kernel Update Guide]<br />
<br />
==Imaging Microsoft Surfaces (Surface Pro 2) with FOG==<br />
Here are the details for making a FOG server work with Surface Pros and other devices that might be particular in the same way:<br />
<br />
===PXE Booting Your Surface Pro 2===<br />
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.<br />
<br />
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)<br />
<br />
When the FOG menu pops up, you can capture an image to use for the rest of the surfaces.<br />
<br />
===More Information on Surfaces and Other Special Device Booting===<br />
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.<br />
<br />
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].<br />
<br />
==Troubleshooting==<br />
Here are different solutions we have found to various FOG problems that you may encounter:<br />
<br />
==="What if FOG is blocked?" (During Installation)===<br />
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.<br />
<br />
(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)<br />
<br />
(only do this if installed on a different network than it will be used on, or if there are IP configuration errors.)<br />
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).<br />
<br />
===TFTP Errors===<br />
The error looks like this or something similar depending on configuration:<br />
<br />
[[File:ftp_put_error.jpg|550px]]<br />
<br />
If you get a tftp or ftp_put() error when trying to update the kernel, these are the solutions we've found:<br />
<br />
====Solution 1: Credentials====<br />
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).<br />
The places where credentials need to match can be found in these places:<br />
<br />
*Web Interface -> Storage Management -> [Your storage node] -> Management Username & Management Password<br />
*Web Interface -> FOG Configuration -> FOG Settings -> TFTP Server -> FOG_TFTP_FTP_USERNAME & FOG_TFTP_FTP_PASSWORD<br />
*The local 'fog' user's password on the Linux FOG server<br />
*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.)<br />
<br />
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.<br />
<br />
The fog user password can be changed by using the command:<br />
<br />
<code>sudo passwd fog</code><br />
<br />
The server file can be edited using vim in the Linux terminal:<br />
<br />
<code>vi /opt/fog/.fogsettings</code><br />
<br />
(More info on vim or vi can be found [https://wiki.fogproject.org/wiki/index.php?title=Vi here].<br />
<br />
Official FOG documentation on this issue can be found [https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Credentials_.2F_Passwords here].<br />
<br />
====Solution 2: Use a Kernel Install Script====<br />
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.<br />
<br />
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.<br />
<code>#Delete previous backed up kernels & inits.<br />
<br />
rm -rf /var/www/html/fog/service/ipxe/old<br />
<br />
<br />
#Make a directory to put old kernels & inits into.<br />
<br />
mkdir /var/www/html/fog/service/ipxe/old<br />
<br />
<br />
#Move old inits, get new ones.<br />
<br />
mv /var/www/html/fog/service/ipxe/init.xz /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/inits/init.xz -O /var/www/html/fog/service/ipxe/init.xz<br />
<br />
mv /var/www/html/fog/service/ipxe/init_32.xz /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/inits/init_32.xz -O /var/www/html/fog/service/ipxe/init_32.xz<br />
<br />
<br />
#Move old kernels, get new ones.<br />
<br />
mv /var/www/html/fog/service/ipxe/bzImage /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/kernels/bzImage -O /var/www/html/fog/service/ipxe/bzImage<br />
<br />
mv /var/www/html/fog/service/ipxe/bzImage32 /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/kernels/bzImage32 -O /var/www/html/fog/service/ipxe/bzImage32</code><br />
<br />
<br />
<code>#Reset Ownership:</code><br />
<br />
<code>#Fedora, CentOS, RHEL:</code><br />
<br />
<code>chown -R fog:apache /var/www/html/fog/service/ipxe</code><br />
<br />
<code>#Ubuntu, Debian:</code><br />
<br />
<code>chown -R fog:www-data /var/www/html/fog/service/ipxe</code><br />
<br />
<br />
<code>#Set permissions:</code><br />
<br />
<code>chmod -R 775 /var/www/html/fog/service/ipxe</code><br />
<br />
<code>#Script complete.</code><br />
<br />
<code>echo DONE!</code><br />
<br />
The official FOG documentation can be found [https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update here] at the bottom of the page.<br />
<br />
===Multicast Not Working===<br />
If after an update Multicast stops functioning, or you find it stops working at some point, this is what has worked in the past.<br />
<br />
''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''<br />
<br />
====Multicast Repair Step One====<br />
This first step may seem scary, but it will not damage any of the FOG images or files.<br />
<br />
<br />
We are going to delete the directory /opt/fog<br />
<code>sudo rm -r /opt/fog</code><br />
<br />
''(The -r is necessary to delete directories)''<br />
<br />
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.<br />
<br />
====Multicast Repair Step Two====<br />
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.<br />
<br />
Below are the commands you will need to run:<br />
<br />
<code>mysql</code><br />
<br />
<code>use fog</code><br />
<br />
<code>DELETE FROM `multicastSessions` WHERE 1;</code><br />
<br />
<code>DELETE FROM `multicastSessionsAssoc` WHERE 1;</code><br />
<br />
<code>DELETE FROM `tasks` WHERE `taskTypeID` = 8;</code><br />
<br />
<code>quit</code><br />
<br />
This will clear the MySQL tables. After this you will need to rerun the installer and everything should work fine from there.<br />
<br />
The official Multicast FOG Documentation can be found [https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_Downloading_-_Multicast Here].<br />
<br />
===For Issues You Can't Solve with This Page===<br />
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.<br />
<br />
===The Sanders-Cure-All===<br />
<br />
If there is an issue with FOG that is not easily solvable, you can follow these steps and 9/10 times it will fix it. All of these steps are found in different solutions for other problems, but done in this order can solve many common problems that seemingly can't be explained. Trust me. I've tried.<br />
<br />
''When we run commands, they are run in the Linux terminal, and run them as sudo (that means do the command <code>sudo su</code> before running them to make it easier, if it throws an error saying not to run as sudo, then open a new terminal and don't run the sudo command first.''<br />
<br />
====Step One====<br />
<br />
First we run the manual kernel update script, to ensure that all our kernels aren't broke and are the latest version:<br />
<br />
<code>#Delete previous backed up kernels & inits.<br />
<br />
rm -rf /var/www/html/fog/service/ipxe/old<br />
<br />
<br />
#Make a directory to put old kernels & inits into.<br />
<br />
mkdir /var/www/html/fog/service/ipxe/old<br />
<br />
<br />
#Move old inits, get new ones.<br />
<br />
mv /var/www/html/fog/service/ipxe/init.xz /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/inits/init.xz -O /var/www/html/fog/service/ipxe/init.xz<br />
<br />
mv /var/www/html/fog/service/ipxe/init_32.xz /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/inits/init_32.xz -O /var/www/html/fog/service/ipxe/init_32.xz<br />
<br />
<br />
#Move old kernels, get new ones.<br />
<br />
mv /var/www/html/fog/service/ipxe/bzImage /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/kernels/bzImage -O /var/www/html/fog/service/ipxe/bzImage<br />
<br />
mv /var/www/html/fog/service/ipxe/bzImage32 /var/www/html/fog/service/ipxe/old<br />
<br />
wget https://fogproject.org/kernels/bzImage32 -O /var/www/html/fog/service/ipxe/bzImage32</code><br />
<br />
<br />
<code>#Reset Ownership:</code><br />
<br />
<code>#Fedora, CentOS, RHEL:</code><br />
<br />
<code>chown -R fog:apache /var/www/html/fog/service/ipxe</code><br />
<br />
<code>#Ubuntu, Debian:</code><br />
<br />
<code>chown -R fog:www-data /var/www/html/fog/service/ipxe</code><br />
<br />
<br />
<code>#Set permissions:</code><br />
<br />
<code>chmod -R 775 /var/www/html/fog/service/ipxe</code><br />
<br />
<code>#Script complete.</code><br />
<br />
<code>echo DONE!</code><br />
<br />
====Step Two====<br />
<br />
Now we delete everything that has to do with FOG from the MySQL server. Cause MySQL hates us so we fight fire with fire.<br />
<br />
<code>mysql</code><br />
<br />
<code>use fog</code><br />
<br />
<code>DELETE FROM `multicastSessions` WHERE 1;</code><br />
<br />
<code>DELETE FROM `multicastSessionsAssoc` WHERE 1;</code><br />
<br />
<code>DELETE FROM `tasks` WHERE `taskTypeID` = 8;</code><br />
<br />
<code>quit</code><br />
<br />
====Step Three====<br />
<br />
Now we need to delete most of the FOG files that are on the server, cause FOG itself hates us to. Don't worry, it's not you, it's them.<br />
<br />
<code>sudo rm -r /opt/fog</code><br />
<br />
''(This doesn't delete any settings or images don't worry''<br />
<br />
====Step Four====<br />
<br />
Now we start to reinstall FOG, because a lot of it is no longer there. '''IF THERE IS A NEWER VERSION, THIS IS A GOOD TIME TO UPGRADE. IT'S ALREADY BROKEN, AND NEWER VERSIONS HAVE GOTTEN A LOT MORE STABLE PLEASE'''<br />
<br />
Download FOG (it is recommended that you get the latest version from [https://fogproject.org/download here]).<br />
<br />
If there isn't a new version and the FOG files are still in the downloads folder, then you can skip this step.<br />
<br />
====Step Five====<br />
<br />
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><br />
<br />
''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.''<br />
<br />
''PPS: It should find the old settings and try and pull some of the config. It might not. Verify all settings while running the installer.''<br />
<br />
====Step Six====<br />
<br />
Now FOG may have changed some passwords. Yeah, it can do that.<br />
<br />
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).<br />
The places where credentials need to match can be found in these places:<br />
<br />
*Web Interface -> Storage Management -> [Your storage node] -> Management Username & Management Password<br />
*Web Interface -> FOG Configuration -> FOG Settings -> TFTP Server -> FOG_TFTP_FTP_USERNAME & FOG_TFTP_FTP_PASSWORD<br />
*The local 'fog' user's password on the Linux FOG server<br />
*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.)<br />
<br />
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.<br />
<br />
The fog user password can be changed by using the command:<br />
<br />
<code>sudo passwd fog</code><br />
<br />
The server file can be edited using vim in the Linux terminal:<br />
<br />
<code>vi /opt/fog/.fogsettings</code><br />
<br />
(More info on vim or vi can be found [https://wiki.fogproject.org/wiki/index.php?title=Vi here].<br />
<br />
Official FOG documentation on this issue can be found [https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Credentials_.2F_Passwords here].<br />
<br />
'''''If you need to run as sudo and it says the password has already changed (like you can't run sudo) look at the .fogsettings file and it will contain the *new* password in plaintext. It is gonna be long and is gonna suck. If you are logged out and need to get back in, log in as guest or as another user, or boot off of a bootable linux live usb, and go to the file and take a picture of the password.'''''<br />
<br />
====Step Seven====<br />
<br />
The FOG Server may be fixed at this point, and if so yay! You're done. If it is still acting up there is more to do.<br />
<br />
Run steps two through six again and it should work, it usually is always good after a second try. If that doesn't work you'll have to do more than the cure-all, cause every time it's gone more than two it was a more in depth issue.<br />
<br />
==xRDP==<br />
<br />
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.<br />
<br />
To learn more about xRDP, go to the wiki page: [[xRDP]]<br />
<br />
== FOGBANK SERVER ==<br />
the fogbank server is the server that runs our fog server for our classroom, this computer cannot be accessed via remote desktop, you need to go into the back in order to access the computer.<br />
<br />
* Processor:<br />
* Memory:<br />
* Storage:<br />
* System:</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=Freyr&diff=1087Freyr2020-03-10T19:53:04Z<p>Ebrownthunder: </p>
<hr />
<div>==General Overview==<br />
Freyr (10.21.25.5) is a backup server for Logan. It primarily functions as a backup for [[Logan]] which is our print server, BDC (backup domain controller), host our DHCP/DNS backups and is our LEMP (NGINX) server.<br />
<br />
==System Information==<br />
<br />
*Processor: Intel Xeon E5620 @2.40 GHz (16CPUs)<br />
*Memory: 48.0 GB DDR3<br />
*Storage: HP LOGICAL VOLUME SCSI Disk<br />
*System Model: ProLiant DL 360G7<br />
<br />
==Services==<br />
<br />
* Hyper-V Manager<br />
* NGINX<br />
* DHCP (Backup)<br />
* DNS(Backup)<br />
<br />
== Programs ==</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=Freyr&diff=1084Freyr2020-02-27T05:03:25Z<p>Ebrownthunder: </p>
<hr />
<div>==General Overview==<br />
Freyr (10.21.25.5) is a backup server for Logan. It primarily functions as a backup for [[Logan]] which is our print server, BDC (backup domain controller), host our DHCP/DNS backups and is our LEMP (NGINX) server.<br />
<br />
= System Information =<br />
<br />
* Processor: Intel Xeon E5620 @2.40 GHz (16CPUs)<br />
* Memory: 48.0 GB DDR3<br />
* Storage: HP LOGICAL VOLUME SCSI Disk<br />
* System Model: ProLiant DL 360G7</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=SURTR&diff=1083SURTR2020-02-27T05:01:58Z<p>Ebrownthunder: </p>
<hr />
<div>= System Information =<br />
<br />
* Processor: Intel Core i7 - 3960X @ 3.30GHz (12CPUs)<br />
* Memory: 32.0 GB DDR3<br />
* Storage ST1000DMC03-1ER162<br />
* System Model: N/A</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=MACmini_Servers&diff=1081MACmini Servers2020-02-27T03:46:03Z<p>Ebrownthunder: </p>
<hr />
<div>= Overview =<br />
The MACmini Server is used to manage all of the macs that around the 100 building in other classrooms, you are able to monitor each of the macs from the MACmini server and access them if needed. There is another MACmini server known as MACmini Backup, which as its name suggests is the backup to the MACmini. Backups and will save continuously just in case the MACmini does malfunction. <br />
<br />
= System Information =<br />
MACmini<br />
<br />
* Processor: Intel Core 2 Duo @2.66 GHz<br />
* Memory: 8.00 GB <br />
* Storage 2 x 500GB SATA Disk<br />
* System Model: MACmini server (mid 2010)<br />
<br />
MACmini Backup <br />
<br />
* Processor: Quad-Core Intel Xeon @ 2 x 2.20GHz<br />
* Memory: 6GB 1066 MHz DDR3 ECC<br />
* Storage: 2 x 500.00 GB SATA Disk<br />
* System Model: MACmini Server<br />
<br />
= Services =</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=Heimdall&diff=1080Heimdall2020-02-27T03:21:15Z<p>Ebrownthunder: </p>
<hr />
<div>[[File:Heimdall Armor DW.jpg|left|thumb|463x463px]]<br />
<br />
==What is Heimdall?==<br />
<br />
Heimdall is the server that hosts all of our virtual machines for the networking back room it runs an operating system called ESXi. [[OpenGear Console Server Documentation]] and the [[IOLan Documentation]] are the two console servers for connecting to the networking equipment themselves. In short, there are 24 virtual machines, assigned to 24 vlans, and each vlan is assigned a port on the patch panel in the networking room, which is then able to pass through to the ports on the walls. The server is connected to the patch panel with two gigabit connections that are nic-teamed, and is connected to the internet with two gigabit connections that are also nic-teamed. The virtual machines do not have access to the internet, as their connection just passes through to their port and nowhere else.<br />
<br />
= System information =<br />
<br />
* Processor: Intel Xeon CPU E5-2690 v2 @3.00 GHz<br />
* Memory: 255.92 GB<br />
* Storage 923.75<br />
* Operating System: ESXi Version 6.7.0 - (Build 8169922)<br /><br />
<br />
= Services =<br />
Heimdall is currently used for the Virtual Machines and keeps them open for everyone to access them.<br />
<br />
* HyperV Manager<br />
* Open Gear Console Server Documentation<br />
* IOLan Documentation <br />
<br />
==How to Connect to Heimdall==<br />
<br />
To connect to the ESXi server, go to 10.21.25.8 in a web browser to get to the login. Login using the same credentials you use for the domain.<br />
<br />
(Will look like the image on the right)<br />
<br />
[[File:ESXi Login.PNG|thumb|350x450px]]<br />
<br />
===The Host Page===<br />
<br />
After logging in, you will be brought to the host page. This gives all sorts of info about Heimdall, such as specs like RAM and CPU, and overall load. You can also restart or shutdown the server by clicking the buttons at the top.<br />
<br />
==Connecting to Virtual Machines==<br />
<br />
To connect to the virtual machines, click the "Virtual Machines" tab on the left. This will bring up the list of all the virtual machines. You can select some, or all, and power them on or shut them down from here. Or you can click on the name of the virtual machine to bring up more information about it, connect, and do more detailed things.<br />
<br />
Once in a virtual machine's page, you can power it on or shut it down, view ram and processor usage, network info, storage, connect to the VM, and edit it's settings. We really should only need to power on/off, connect, and occasionally restore the virtual machine from snapshots if something goes wrong.<br />
<br />
To connect, a virtual machine must be powered on. Once it is powered on, click on the "Console" button at the top left. This will give you some options to connect. You can open it as a window in the ESXi console with "open browser console", or you can open it in a new browser tab or window with the new tab or new window links. You can also use VMRC, which is a proprietary connection made by VMWare, this has not been tested on our servers at the time of writing.<br />
<br />
===Restoring from a Snapshot===<br />
<br />
To restore a virtual machine from a snapshot, you must be in the virtual machine's page (by clicking it's name in the list of virtual machines), then click actions. Then click snapshots from the dropdown, and then restore snapshot. It will ask you if you want to restore from the latest one, and click restore if the newest one works (We currently only have one snapshot saved for all of them, which is confirmed good).<br />
<br />
To manually pick a snapshot to restore from, choose manage snapshots instead of restore snapshots, and it will take you to the list of snapshots. At the time of writing the "Original" snapshot is the only one that exists, which is the first snapshot that we made after creating. This is the one to go to if all else fails, and will probably be the only snapshot.<br />
<br />
When you know which one you want to choose from the list, click the name, then click restore snapshot from the top of the popup window. Then confirm by clicking restore.<br />
<br />
==ESXI==<br />
<br />
[[https://www.vmware.com/products/esxi-and-esx.html ESXI Page]]<br />
<br />
[[https://my.vmware.com/en/web/vmware/evalcenter?p=free-esxi6 Download and How to Install]]</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=Loki&diff=1079Loki2020-02-26T18:47:06Z<p>Ebrownthunder: </p>
<hr />
<div>=About Loki=<br />
<br />
Loki is one of the main servers on the [[CISCOACA.local]] domain. It is the main servers for [[Active Directory]], [[Group Policy]], [[DNS]], and [[DHCP]]. This makes Loki one of our most important servers that needs to stay up all the time, along with [[Logan]]. To learn more about those functions, go to their respective pages. Loki is the main servers for all of these functions, and [[Logan]] is on hot standby as a backup in case of emergency.<br />
Loki is also the server that hosts our shared drives, which allows us to share files throughout the classroom.<br />
=System information=<br />
Loki runs the Windows Server 2016 Standard Edition OS Version 10.0 Build 14393, has 16.0 GB of memory available. Processor is Intel Core Xeon CPU E5-2620 @ 2.10GHz (16CPUs). <br />
<br />
= Services =<br />
Loki helps run multiple services which include: <br />
<br />
* DHCP<br />
* DNS<br />
* Active Directory<br />
* Audit Policies<br />
* GPOs<br />
<br />
= Programs =<br />
These applications were installed onto Loki to help support and secure the network even further.<br />
<br />
* BeyondTrust Network scanner<br />
<br />
=Domain Controller=<br />
<br />
Loki is the main domain controller, with [[Logan]] as a backup. This means it does [[DNS]], [[DHCP]], [[Active Directory]], [[Group Policy]] and the [[Security Policy]].<br />
<br />
=Shared Drives=<br />
<br />
The shared drives are the drives called Shared Storage and Cisco Curriculum and EZNews</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=Loki&diff=1078Loki2020-02-26T18:43:34Z<p>Ebrownthunder: </p>
<hr />
<div>=About Loki=<br />
<br />
Loki is one of the main servers on the [[CISCOACA.local]] domain. It is the main servers for [[Active Directory]], [[Group Policy]], [[DNS]], and [[DHCP]]. This makes Loki one of our most important servers that needs to stay up all the time, along with [[Logan]]. To learn more about those functions, go to their respective pages. Loki is the main servers for all of these functions, and [[Logan]] is on hot standby as a backup in case of emergency.<br />
Loki is also the server that hosts our shared drives, which allows us to share files throughout the classroom.<br />
<br />
=Domain Controller=<br />
<br />
Loki is the main domain controller, with [[Logan]] as a backup. This means it does [[DNS]], [[DHCP]], [[Active Directory]], [[Group Policy]] and the [[Security Policy]].<br />
<br />
=Shared Drives=<br />
<br />
The shared drives are the drives called Shared Storage and Cisco Curriculum and EZNews</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=Logan_(Retired)&diff=1075Logan (Retired)2020-02-21T20:23:54Z<p>Ebrownthunder: </p>
<hr />
<div>==General Overview==<br />
Logan (10.21.25.10) 1 out of 2 of the Dell PowerEdge R430's that we have in Mr. Chamberlain's room. It primarily functions as a print server, BDC (backup domain controller, a host for our DHCP/DNS backups, and a WAMP (Apache) server. <br />
<br />
== System information ==<br />
Logan runs the Windows Server 2016 Standard Edition OS Version 10.0 Build 14393, has 16.0 GB of memory available. Processor is Intel Core Xeon CPU E5-2620 @ 2.10GHz (16CPUs). <br />
<br />
== Services ==<br />
Since Logan is one of our Domain Controllers, there are services that Logan runs in order to keep everything running smoothly. Services include:<br />
<br />
DHCP<br />
<br />
DNS<br />
<br />
Active Directory<br />
<br />
IDRAC<br />
<br />
Apache<br />
<br />
Parsoid<br />
<br />
== Programs ==<br />
These applications were installed onto Logan to help support and secure the network even further.<br />
<br />
BeyondTrust Network Scanner<br />
<br />
DCdiag<br />
<br />
Spiceworks<br />
<br />
LoganWeb<br />
<br />
Hyper-V Manager<br />
<br />
==Startup==<br />
There is currently only 1 file in the startup folder which is a visual basic script to start up the Parsoid server. The code for that can be seen as follows:<pre><br />
set w = CreateObject("WScript.Shell")<br />
w.Run chr(34) & "C:\Program Files\nodejs\parsoid\parsoid.bat" & chr(34), 0<br />
set w = Nothing<br />
</pre><br />
<br />
==Print Services==<br />
There are currently 2 active print servers on Logan: one for the <code>Brother HL-4570CDW</code> printer, and one for the <code>HP LaserJet P4014 UPD PCL 6</code> printer.<br />
<br />
[[File:Logan_PrintAllPrinters.png]]<br />
<br />
Below is the advanced configuration page for both of the main printers.<br />
<br />
[[File:Printers-advanced_logan.png|frameless|600x600px]]<br />
<br />
==Backup Domain Controller==<br />
Logan is a backup domain controller for Loki, meaning it is on hot standby for [[DNS]] and [[Active Directory]].<br />
<br />
==DHCP==<br />
Logan runs as a backup [[DHCP]] server for [[Loki]].<br />
<br />
==LEMP Stack (Nginx Server)==<br />
Everything you need to know about our web server can be found on the [http://wiki.24pin.tech/index.php?title=Nginx Nginx] page. It covers everything ranging from installation to configuration, and covers the basics to troubleshooting.</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=Logan_(Retired)&diff=1074Logan (Retired)2020-02-20T20:20:27Z<p>Ebrownthunder: </p>
<hr />
<div>==General Overview==<br />
Logan (10.21.25.10) 1 out of 2 of the Dell PowerEdge R430's that we have in Mr. Chamberlain's room. It primarily functions as a print server, BDC (backup domain controller, a host for our DHCP/DNS backups, and a WAMP (Apache) server. <br />
<br />
==Startup==<br />
There is currently only 1 file in the startup folder which is a visual basic script to start up the Parsoid server. The code for that can be seen as follows:<pre><br />
set w = CreateObject("WScript.Shell")<br />
w.Run chr(34) & "C:\Program Files\nodejs\parsoid\parsoid.bat" & chr(34), 0<br />
set w = Nothing<br />
</pre><br />
<br />
==Print Services==<br />
There are currently 2 active print servers on Logan: one for the <code>Brother HL-4570CDW</code> printer, and one for the <code>HP LaserJet P4014 UPD PCL 6</code> printer.<br />
<br />
[[File:Logan_PrintAllPrinters.png]]<br />
<br />
Below is the advanced configuration page for both of the main printers.<br />
<br />
[[File:Printers-advanced_logan.png|frameless|600x600px]]<br />
<br />
==Backup Domain Controller==<br />
Logan is a backup domain controller for Loki, meaning it is on hot standby for [[DNS]] and [[Active Directory]].<br />
<br />
==DHCP==<br />
Logan runs as a backup [[DHCP]] server for [[Loki]].<br />
<br />
==LEMP Stack (Nginx Server)==<br />
Everything you need to know about our web server can be found on the [http://wiki.24pin.tech/index.php?title=Nginx Nginx] page. It covers everything ranging from installation to configuration, and covers the basics to troubleshooting.</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=MACmini_Servers&diff=1069MACmini Servers2020-02-20T20:04:11Z<p>Ebrownthunder: Created page with "MACmini SERVERS"</p>
<hr />
<div>MACmini SERVERS</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=SURTR&diff=1057SURTR2020-01-15T18:14:23Z<p>Ebrownthunder: Created page with "SURTR SERVER"</p>
<hr />
<div>SURTR SERVER</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=Freyr&diff=1055Freyr2020-01-14T20:29:59Z<p>Ebrownthunder: Created page with "FREYR SERVER"</p>
<hr />
<div>FREYR SERVER</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=User:Freyes&diff=1054User:Freyes2020-01-14T20:29:30Z<p>Ebrownthunder: </p>
<hr />
<div>amdfsianhsuian dsakmbdfsakmbg,h[[File:CIJH0069.jpg|thumb]]</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=User_talk:Ebrownthunder&diff=1053User talk:Ebrownthunder2020-01-14T20:27:44Z<p>Ebrownthunder: </p>
<hr />
<div><br />
<br />
== epic ==<br />
<br />
now this is epic</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=User_talk:Ebrownthunder&diff=1052User talk:Ebrownthunder2020-01-14T20:27:36Z<p>Ebrownthunder: /* epic */ new section</p>
<hr />
<div>now this is epic<br />
<br />
== epic ==<br />
<br />
now this is epic</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=User_talk:Ebrownthunder&diff=1051User talk:Ebrownthunder2020-01-14T20:19:32Z<p>Ebrownthunder: Created page with "now this is epic"</p>
<hr />
<div>now this is epic</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=Odin_(Retired)&diff=1045Odin (Retired)2020-01-14T19:56:51Z<p>Ebrownthunder: Ebrownthunder moved page Odin to Odin (Retired): We no longer use the Odin server anymore.</p>
<hr />
<div><br />
[[File:Owodin.jpg|thumb|picture of an HP ProLiant DL380 G5]]<br />
== General Overview ==<br />
Odin (10.21.25.9) is a HP ProLiant DL380 G5 server that is used primarily for Spiceworks, but has some other services running.<br />
<br />
== Spiceworks ==<br />
(an excerpt from the Spiceworks page)<br />
<br />
Spiceworks is a work order management system and ticketing system utilized by 24PinTech. The software uses applications like NMap to find issues and vulnerabilities in the network and systems on it in order to better protect itself and the business. Spiceworks also sends email alerts to all members including alerts about specific hardware in the netspace.<br />
<br />
You can find more information about Spiceworks and how to use it and more installation for the installer using the buttons below.<br />
<br />
<br />
<span style="padding: 10px 15px; color: rgba(0, 0, 0, 1); background-color: rgba(0, 0, 0, 0.1); border: 1px solid rgba(0, 0, 0, 0.7); border-radius: 3px;"><strong>[[Spiceworks]]</strong></span> <span style="padding: 10px 15px; color: rgba(0, 0, 0, 1); background-color: rgba(55, 201, 255, 0.1); border: 1px solid rgba(55, 201, 255, 0.7); border-radius: 3px;"><strong>[[Spiceworks Installation]]</strong></span> <br />
<br />
== EZ News ==<br />
I was told by Chamberlain not to worry about documenting this part as it's an incredibly convoluted process to install, and it was also discontinued. Just know that at one point it was on this server. <br />
<br />
== Print Services ==<br />
Odin is a backup print server for [http://wiki.24pin.tech/index.php/Logan Logan] visit its documentation to see the configuration running on it.</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=Social_Media_and_Marketing&diff=975Social Media and Marketing2019-08-19T20:13:45Z<p>Ebrownthunder: </p>
<hr />
<div>==Social Media Account Info==</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=24PinTech_Apps&diff=96924PinTech Apps2019-08-14T18:32:26Z<p>Ebrownthunder: </p>
<hr />
<div>==What are 24pintech Apps?==<br />
24pintech apps is a folder that is located in the Shared Storage drive in the [http://wiki.24pin.tech/index.php?title=Loki Loki] server. The folders inside have multiple apps that we have used over the years that are useful on running 24pintech. Each of the applications are used to either, open Virtual Machines, ISO folders, terminal editors, antivirus etc. \\loki\shared storage\24pintech apps <br />
<br />
==Why are these applications important?==<br />
These applications are very useful to an average technician who needs to use certain tools to make something easier.<br />
<br />
==Terminal Editor Software==<br />
PuTTY, SecureCRT, and TeraTerm are all open-sourced terminal editors, which give you access to [http://wiki.24pin.tech/index.php?title=OpenGear_Console_Server_Documentation OpenGear] and let you edit configurations that are in the terminal. We use these applications for our servers which keep the 24pintech website up and running.</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=24PinTech_Apps&diff=96824PinTech Apps2019-08-14T18:29:00Z<p>Ebrownthunder: </p>
<hr />
<div>==What are 24pintech Apps?==<br />
24pintech apps is a folder that is located in the Shared Storage drive in the [http://wiki.24pin.tech/index.php?title=Loki Loki] server. The folders inside have multiple apps that we have used over the years that are useful on running 24pintech. Each of the applications sed to either, open Virtual Machines, ISO folders, terminal editors, antivirus etc. \\loki\shared storage\24pintech apps <br />
<br />
==Why are these applications important?==<br />
These applications are very useful to an average technician who needs to use certain tools to make something easier.<br />
<br />
==Terminal Editor Software==<br />
PuTTY, SecureCRT, and TeraTerm are all open-sourced terminal editors, which give you access to [http://wiki.24pin.tech/index.php?title=OpenGear_Console_Server_Documentation OpenGear] and let you edit configurations that are in the terminal. We use these applications for our servers which keep the 24pintech website up and running.</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=24PinTech_Apps&diff=96724PinTech Apps2019-08-14T18:24:05Z<p>Ebrownthunder: </p>
<hr />
<div>==What are 24pintech Apps?==<br />
24pintech apps is a folder that is located in the Shared Storage drive in the [http://wiki.24pin.tech/index.php?title=Loki Loki] server. The folders inside have multiple apps that we have used over the years that are useful on running 24pintech. Each of the applications sed to either, open Virtual Machines, ISO folders, terminal editors, antivirus etc. \\loki\shared storage\24pintech apps <br />
<br />
==Why are these applications important?==<br />
These applications are very useful to an average technician who needs to use certain tools to make something easier.<br />
<br />
==Terminal Editor Software==<br />
PuTTY, SecureCRT, and TeraTerm are all open-sourced terminal editors, which give you access to [http://wiki.24pin.tech/index.php?title=OpenGear_Console_Server_Documentation OpenGear]</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=24PinTech_Apps&diff=96624PinTech Apps2019-08-14T18:23:37Z<p>Ebrownthunder: </p>
<hr />
<div>==What are 24pintech Apps?==<br />
24pintech apps is a folder that is located in the Shared Storage drive in the [http://wiki.24pin.tech/index.php?title=Loki Loki] server. The folders inside have multiple apps that we have used over the years that are useful on running 24pintech. Each of the applications sed to either, open Virtual Machines, ISO folders, terminal editors, antivirus etc. \\loki\shared storage\24pintech apps <br />
<br />
==Why are these applications important?==<br />
These applications are very useful to an average technician who needs to use certain tools to make something easier.<br />
<br />
==Terminal Editor Software==<br />
PuTTY, SecureCRT, and TeraTerm are all open-sourced terminal editors, which give you access to [[OpenGear Console Server Documentation|OpenGear]]</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=24PinTech_Apps&diff=96524PinTech Apps2019-08-13T20:28:11Z<p>Ebrownthunder: </p>
<hr />
<div>==What are 24pintech Apps?==<br />
24pintech apps is a folder that is located in the Shared Storage drive in the [[Loki]] server. The folders inside have multiple apps that we have used over the years that are useful on running 24pintech. Each of the applications sed to either, open Virtual Machines, ISO folders, terminal editors, antivirus etc. <br />
<br />
==Why are these applications important?==<br />
These applications are very useful to an average technician who needs to use certain tools to make something easier.<br />
<br />
==Terminal Editor Software==<br />
PuTTY, SecureCRT, and TeraTerm are all open-sourced terminal editors, which give you access to [[OpenGear Console Server Documentation|OpenGear]]</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=24PinTech_Apps&diff=96424PinTech Apps2019-08-13T20:27:45Z<p>Ebrownthunder: </p>
<hr />
<div>==What are 24pintech Apps?==<br />
24pintech apps is a folder that is located in the Shared Storage drive in the [[Loki]] server. The folders inside have multiple apps that we have used over the years that are useful on running 24pintech. Each of the applicatoins are used to either, open Virtual Machines, ISO folders, terminal editors, antivirus etc. <br />
<br />
==Why are these applications important?==<br />
These applications are very useful to an average technician who needs to use certain tools to make something easier.<br />
<br />
==Terminal Editor Software==<br />
PuTTY, SecureCRT, and TeraTerm are all open-sourced terminal editors, which give you access to [[OpenGear Console Server Documentation|OpenGear]]</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=24PinTech_Apps&diff=96324PinTech Apps2019-08-13T20:27:01Z<p>Ebrownthunder: </p>
<hr />
<div>==What are 24pintech Apps?==<br />
24pintech apps is a folder that is located in the Shared Storage drive in the Loki server. The folders inside have multiple apps that we have used over the years that are useful on running 24pintech. Each of the applicatoins are used to either, open Virtual Machines, ISO folders, terminal editors, antivirus etc. <br />
<br />
==Why are these applications important?==<br />
These applications are very useful to an average technician who needs to use certain tools to make something easier.<br />
<br />
==Terminal Editor Software==<br />
PuTTY, SecureCRT, and TeraTerm are all open-sourced terminal editors, which give you access to [[OpenGear Console Server Documentation|OpenGear]]</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=24PinTech_Apps&diff=96224PinTech Apps2019-08-13T20:24:11Z<p>Ebrownthunder: </p>
<hr />
<div>==What are 24pintech Apps?==<br />
24pintech apps is a folder that is located in the Shared Storage drive in the Loki server. The folders inside have multiple apps that we have used over the years that are useful on running 24pintech. Each of the applicatoins are used to either, open Virtual Machines, ISO folders, terminal editors, antivirus etc. <br />
<br />
==Why are these applications important?==<br />
These applications are very useful to an average technician who needs to use certain tools to make something easier.<br />
<br />
==Terminal Editor Software==<br />
PuTTY, SecureCRT, and TeraTerm are all open-sourced terminal editors, which give you access to [[OpenGear Console Server Documentation|OpenGear]] and PuTTY</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=24PinTech_Apps&diff=96124PinTech Apps2019-08-13T20:20:45Z<p>Ebrownthunder: </p>
<hr />
<div>==What are 24pintech Apps?==<br />
24pintech apps is a folder that is located in the Shared Storage drive in the Loki server. The folders inside have multiple apps that we have used over the years that are useful on running 24pintech. Each of the applicatoins are used to either, open Virtual Machines, ISO folders, terminal editors, antivirus etc. <br />
<br />
==Why are these applications important?==<br />
These applications are very useful to an average technician who needs to use certain tools to make something easier.<br />
<br />
==Terminal Editor Software==<br />
PuTTY, SecureCRT, and TeraTerm are all open-sourced terminal editors, which give you access to [[OpenGear Console Server Documentation|OpenGear]] and</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=24PinTech_Apps&diff=96024PinTech Apps2019-08-13T20:20:31Z<p>Ebrownthunder: </p>
<hr />
<div>==What are 24pintech Apps?==<br />
24pintech apps is a folder that is located in the Shared Storage drive in the Loki server. The folders inside have multiple apps that we have used over the years that are useful on running 24pintech. Each of the applicatoins are used to either, open Virtual Machines, ISO folders, terminal editors, antivirus etc. <br />
<br />
==Why are these applications important?==<br />
These applications are very useful to an average technician who needs to use certain tools to make something easier.<br />
<br />
==Terminal Editor Software==<br />
PuTTY, SecureCRT, and TeraTerm are all open-sourced terminal editors, which give you access o [[OpenGear Console Server Documentation|OpenGear]] and</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=24PinTech_Apps&diff=95924PinTech Apps2019-08-13T20:19:52Z<p>Ebrownthunder: Terminal Editor Software</p>
<hr />
<div>==What are 24pintech Apps?==<br />
24pintech apps is a folder that is located in the Shared Storage drive in the Loki server. The folders inside have multiple apps that we have used over the years that are useful on running 24pintech. Each of the applicatoins are used to either, open Virtual Machines, ISO folders, terminal editors, antivirus etc. <br />
<br />
==Why are these applications important?==<br />
These applications are very useful to an average technician who needs to use certain tools to make something easier.<br />
<br />
== Terminal Editor Software ==<br />
PuTTY, SecureCRT, and TeraTerm are all open-sourced terminal editors, which give you acces to OpenGear and</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=24PinTech_Apps&diff=95824PinTech Apps2019-08-13T20:17:15Z<p>Ebrownthunder: Why are these applications important?</p>
<hr />
<div>==What are 24pintech Apps?==<br />
24pintech apps is a folder that is located in the Shared Storage drive in the Loki server. The folders inside have multiple apps that we have used over the years that are useful on running 24pintech. Each of the applicatoins are used to either, open Virtual Machines, ISO folders, terminal editors, antivirus etc. <br />
<br />
== Why are these applications important? ==<br />
These applications are very useful to an average technician who needs to use certain tools to make something easier.</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=24PinTech_Apps&diff=95724PinTech Apps2019-08-13T20:09:14Z<p>Ebrownthunder: /* What are 24pintech Apps? */</p>
<hr />
<div>==What are 24pintech Apps?==<br />
24pintech apps is a folder that is located in the Shared Storage drive in the Loki server. The folders inside have multiple apps that we have used over the years that are useful on running 24pintech.</div>Ebrownthunderhttps://wiki.24pin.tech/index.php?title=24PinTech_Apps&diff=95624PinTech Apps2019-08-09T20:17:48Z<p>Ebrownthunder: Added a new header for information</p>
<hr />
<div>== What are 24pintech Apps? ==</div>Ebrownthunder