24PinTech Wiki - User contributions [en]

FOG

2019-10-24T22:16:11Z

Bsanders: THE CURE ALL

==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]

=== Setting up FOG to be Used on Another Network ===

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.

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.

'''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.

==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

== DHCP Setup ==
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.
[[File:DHCP Scope Options Fog.png|left|thumb|520x520px]]

Here are some helpful links from the Fog Wiki to assist you.

[https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence BIOS and UEFI Co-Existence]

[https://wiki.fogproject.org/wiki/index.php?title=Windows_DHCP_Server Windows DHCP Server]

==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: [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].

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

==="What if FOG is blocked?" (During Installation)===
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.

=== The Sanders-Cure-All ===

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.

''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.''

==== Step One ====

First we run the manual kernel update script, to ensure that all our kernels aren't broke and are the latest version:

<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>

==== Step Two ====

Now we delete everything that has to do with FOG from the MySQL server. Cause MySQL hates us so we fight fire with fire.

<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>

==== Step Three ====

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.

<code>sudo rm -r /opt/fog</code>

''(This doesn't delete any settings or images don't worry''

==== Step Four ====

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'''

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

If there isn't a new version and the FOG files are still in the downloads folder, then you can skip this step.

==== Step Five ====

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.''

''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.''

==== Step Six ====

Now FOG may have changed some passwords. Yeah, it can do that.

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].

'''''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.'''''

==== Step Seven ====

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.

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.

==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]]

Group Policy

2019-08-24T05:08:32Z

Bsanders: ooops

= Our Group Policy Setup =

Group Policy is what allows us to configure settings that will be propagated by [[Active Directory]] to the appropriate computers and servers. It allows us to have direct control over windows and how the computers will behave in their different environments. It is where all of our [[Security Policy]] presides as well, as Group Policy is where all password and security settings are configured, as they are security settings in Windows.

To view Group Policy settings and configurations, login to one of the domain controllers and open Group Policy Management.

== Chrome Settings ==

This sets security settings and basic delegation for chrome. to view exactly what this does, click on Chrome Settings, and click on the settings tab. You can then click the drop down to view what it changes. This policy specifically is old, and only really affects older devices.

== Default Domain Controllers Policy ==

This policy sets all of our domain controller settings, including who is able to access them. This is one of the most important and most detailed policies. To view all of it's changes, click on it and click settings, then use the dropdowns.

== Default Domain Policy ==

This policy defines our main domain policies for [[CISCOACA.local]], it mostly sets our password/lockout policies along with encryption settings. To view all of it's changes, click on it and click settings, then use the dropdowns.

== Disable Roaming Profiles ==

This policy disables the roaming profiles that will exist in user's folders. These profiles are popular for viruses to run as, as they have high rights and are old/deprecated. To view how it makes these changes, click on it and click settings, then use the dropdowns.

== IE, Mapping ==

This maps our network drives and also sets all of our Internet Explorer security settings. Please don't use Internet Explorer though. The network drives are where we are able to store all of our shared files, and hosts our documents folders to make sure they are backed up on the network and easily accessible from every computer. This does not map the documents folder though. To view all of it's changes, click on it and click settings, then use the dropdowns.

== Map My Documents ==

This redirects the documents folder to be stored on a shared folder in Loki. It also sets the security settings so only the correct person can access their documents folder. It also configures internet explorer and start menu policies that are affected by this change. To view all of it's changes, click on it and click settings, then use the dropdowns.

== Mapping EZNews ==

This maps a network drive for the program EZNews. This was used for journalism class. This is old and we don't use it anymore, but the program was expensive so we are using this there. To view how it changes, click on it and click settings, then use the dropdowns.

== Network Printers ==

This policy automatically registers our network's printers with all of our domain computers. This lets us all print without having to set things up. To view all of it's changes, click on it and click settings, then use the dropdowns.

== Security Policy ==

Visit [[Security Policy]] for more info on this. It is what sets most of our security settings.

== Time Sync ==

This configures all of our domain computers to talk to the correct NTP server to ensure that everything is synced with the correct time. It also defines the ADMX files that affect how group policy is received. This lets us all print without having to set things up. To view all of it's changes, click on it and click settings, then use the dropdowns.

== Web Applications Certificate Installer ==

This sets all of the affected computers so that they are able to receive web application certificates from programs like Sophos. This lets us all print without having to set things up. To view all of it's changes, click on it and click settings, then use the dropdowns.

Group Policy

2019-08-24T05:08:00Z

Bsanders: Copied page from old wiki

FOG

2019-08-24T04:58:25Z

Bsanders: /* The Initial Steps */ removed old link

==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]

=== Setting up FOG to be Used on Another Network ===

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.

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.

'''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.

==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

== DHCP Setup ==
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.
[[File:DHCP Scope Options Fog.png|left|thumb|520x520px]]

Here are some helpful links from the Fog Wiki to assist you.

[https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence BIOS and UEFI Co-Existence]

[https://wiki.fogproject.org/wiki/index.php?title=Windows_DHCP_Server Windows DHCP Server]

==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: [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].

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

==="What if FOG is blocked?" (During Installation)===
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]]

Heimdall

2019-07-27T19:21:43Z

Bsanders: Less repetitive

[[File:Heimdall Armor DW.jpg|left|thumb|463x463px]]

== What is Heimdall? ==

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.

== How to Connect to Heimdall ==

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.

(Will look like the image on the right)

[[File:ESXi Login.PNG|thumb|350x450px]]

=== The Host Page ===

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.

== Connecting to Virtual Machines ==

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.

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.

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.

=== Restoring from a Snapshot ===

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).

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.

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.

== ESXI ==

[[https://www.vmware.com/products/esxi-and-esx.html ESXI Page]]

[[https://my.vmware.com/en/web/vmware/evalcenter?p=free-esxi6 Download and How to Install]]

Heimdall

2019-07-17T21:04:44Z

Bsanders: Added links

[[File:Heimdall Armor DW.jpg|left|thumb|463x463px]]

== What is Heimdall? ==

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.

== How to Connect to Heimdall ==

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 login you use for the domain.

(Will look like the image on the right)

[[File:ESXi Login.PNG|thumb|350x450px]]

=== The Host Page ===

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.

== Connecting to Virtual Machines ==

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.

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.

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.

=== Restoring from a Snapshot ===

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).

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.

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.

== ESXI ==

[[https://www.vmware.com/products/esxi-and-esx.html ESXI Page]]

[[https://my.vmware.com/en/web/vmware/evalcenter?p=free-esxi6 Download and How to Install]]

Heimdall

2019-07-17T20:57:19Z

Bsanders: Formatting

[[File:Heimdall Armor DW.jpg|left|thumb|463x463px]]

== What is Heimdall? ==

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.

== How to Connect to Heimdall ==

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 login you use for the domain.

(Will look like the image on the right)

[[File:ESXi Login.PNG|thumb|350x450px]]

=== The Host Page ===

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.

== Connecting to Virtual Machines ==

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.

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.

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.

=== Restoring from a Snapshot ===

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).

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.

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.

Heimdall

2019-07-17T20:56:43Z

Bsanders: Added all info to the page

[[File:Heimdall Armor DW.jpg|left|thumb|463x463px]]

== What is Heimdall? ==

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.

== How to Connect to Heimdall ==

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 login you use for the domain.

(Will look like the image on the right)

[[File:ESXi Login.PNG|thumb|350x450px]]

=== The Host Page ===

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.

== Connecting to Virtual Machines ==

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.

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.

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.

=== Restoring from a Snapshot ===

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).

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.

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.

File:ESXi Login.PNG

2019-07-17T20:30:03Z

Bsanders: It's the login page boyo

== Summary ==
It's the login page boyo

OpenGear Console Server Documentation

2019-07-17T19:42:15Z

Bsanders:

==OpenGear Console Server==
======================================================================== praise allah ========================================================================
The OpenGear console server is a device that allows 48 connections to network devices through one point on the network, allowing access to multiple devices over the network. This allows technicians to make configuration changes to devices on the console server for lab purposes.

== OpenGear and Back Room Setup ==
The console server is mounted on the rack with a Cisco 2960 Switch and 2 patch panels. The upper patch panel for cables running from the console server to the upper junction boxes. Currently 42 ports are in use; the ports of the upper junction boxes are labeled to correspond to the ports of the console server. The pods that connect to the OpenGear console server are all pods that are not wired into the IOLan console server. The lower set of junction boxes are for the 24 VMs that are hosted on [[Heimdall]] (10.21.25.8) and are connected to the lower patch panel that wires into the 2960 Switch. The switch is connected to 2 wall jacks in the ROTC room that run to the patch panel in the IDF, this is an EtherChannel trunk link that allows the 24 VMs hosted on [[Heimdall]] to be trunked to the lower junction boxes. This allows for 3 VMs per pod for testing connectivity in a lab setting.

== Accessing the OpenGear ==
There are 2 methods to access the console server to configure devices: web terminal sessions or PuTTY sessions.

* The console server can be reached at 10.21.25.18. When you type this into your search bar, be sure to type it in as follows: https://10.21.25.18
* You will be brought to this page, click advanced and click "Proceed to 10.21.25.18 (unsafe)".[[File:Getting to OpenGear.png|none|thumb|600x600px]]
* You will be brought to the OpenGear login screen, where you will be prompted to enter credentials to access the ports of the console server. Username: root Password: superuser[[File:OpenGear login.png|none|thumb|600x600px]]
* When you access the console server

Heimdall

2019-07-17T19:34:03Z

Bsanders: Added the best photo

[[File:Heimdall Armor DW.jpg|left|thumb|463x463px]]

File:Heimdall Armor DW.jpg

2019-07-17T19:33:01Z

Bsanders:

It's Heimdall my dudes

FOG

2019-05-31T17:30:11Z

Bsanders: /* Setting up FOG to be Used on Another Network */ more info

==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]

=== Setting up FOG to be Used on Another Network ===

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.

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.

'''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.

==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

== DHCP Setup ==
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.
[[File:DHCP Scope Options Fog.png|left|thumb|520x520px]]

Here are some helpful links from the Fog Wiki to assist you.

[https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence BIOS and UEFI Co-Existence]

[https://wiki.fogproject.org/wiki/index.php?title=Windows_DHCP_Server Windows DHCP Server]

==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].

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

==="What if FOG is blocked?" (During Installation)===
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]]

FOG

2019-05-31T17:22:42Z

Bsanders: How to configure FOG for a different network

==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]

=== Setting up FOG to be Used on Another Network ===

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.

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.

==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

== DHCP Setup ==
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.
[[File:DHCP Scope Options Fog.png|left|thumb|520x520px]]

Here are some helpful links from the Fog Wiki to assist you.

[https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence BIOS and UEFI Co-Existence]

[https://wiki.fogproject.org/wiki/index.php?title=Windows_DHCP_Server Windows DHCP Server]

==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].

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

==="What if FOG is blocked?" (During Installation)===
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]]

Logan (Retired)

2019-05-10T20:15:15Z

Bsanders: /* Backup Domain Controller */ Updated with cross links

== General Overview ==
Logan (10.21.25.11) 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.

== Startup ==
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>
set w = CreateObject("WScript.Shell")
w.Run chr(34) & "C:\Program Files\nodejs\parsoid\parsoid.bat" & chr(34), 0
set w = Nothing
</pre>

== Print Services ==
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.

[[File:Logan_PrintAllPrinters.png]]

Below is the advanced configuration page for both of the main printers.

[[File:Printers-advanced_logan.png|frameless|600x600px]]

== Backup Domain Controller ==
Logan is a backup domain controller for Loki, meaning it is on hot standby for [[DNS]] and [[Active Directory]].

=== DHCP ===
Logan runs as a backup [[DHCP]] server for [[Loki]].

==WAMP Stack (Apache Server) ==
Everything you need to know about our web server can be found on the [http://wiki.24pin.tech/index.php/Apache Apache] page. It covers everything ranging from installation to configuration, and covers the basics to troubleshooting.

Loki

2019-05-08T19:25:21Z

Bsanders: Added domain controller and finished shared drives

= About Loki =

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.
Loki is also the server that hosts our shared drives, which allows us to share files throughout the classroom.

= Domain Controller =

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]].

= Shared Drives =

The shared drives are the drives called Shared Storage and Cisco Curriculum and EZNews

Group Policy

2019-05-08T19:20:46Z

Bsanders: Finished page

Group Policy

2019-05-08T18:50:22Z

Bsanders: Finished some more sections. Added some more title sections

Group Policy

2019-05-08T16:39:39Z

Bsanders: Added a lot of our policies.

Loki

2019-05-06T13:19:36Z

Bsanders: /* Shared Drives */ started section

= About Loki =

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.
Loki is also the server that hosts our shared drives, which allows us to share files throughout the classroom.

= Shared Drives =

The shared drives are the drives called Shared Storage and

Loki

2019-05-06T13:18:50Z

Bsanders: /* About Loki */ Finished about Loki, started shared drives section

Loki

2019-05-06T13:13:38Z

Bsanders: Started putting actual content on the damn page

ITop

2019-05-06T13:01:20Z

Bsanders: /* What is iTop? */ Capitalization

== What is iTop? ==
iTop is a software for managing IT services/tickets and resources, and keeping track of end users and devices and their status. It is similar to Spiceworks, if you have used that software.

Here is its full official description:

iTop is a complete, OpenSource, IT Operational Portal.

It includes:
* A complete CMDB (Configuration Management Database) to document and manage the IT inventory.
* An Incident management module to track and communicate about all issues occurring in the IT.
* A change management module to plan and track the changes to the IT environment.
* A known error database to speed up the resolution of incidents.
* An outage module to document all planned outages and notify the appropriate contacts.
* Dashboards to quickly get an overview of your IT.
All the modules can be setup, step by step, indepently of each other.

iTop is service provider oriented, it allows IT engineers to manage easily multiple customers or organizations.
iTop, delivers a feature-rich set of business processes that:
* Enhances IT management effectiveness
* Drives IT operations performance
* Improves customer satisfaction and provides executives with insights into business performance.

iTop is completely open to be integrated within your current IT Management infrastructure.

Adopting this new generation of IT Operational portal will help you to:
* Better manage a more and more complex IT environment.
* Implement ITIL processes at your own pace.
* Manage the most important asset of your IT: Documentation.

== Initial Setup ==

=== Prerequisites ===

First you must install a web server software. Use whatever you are most comfortable or familiar with. We usually use Apache, and we will be using a Ubuntu machine (17.10 server with a gui installed. Can be downloaded [https://www.ubuntu.com/download/server here].
You will also need to install PHP, graphviz, and MySQL to run iTop.

Here are the commands you need to run if you are using a version of Ubuntu 16.04 or Higher:

<code> apt-get install apache2 </code>

<code> apt-get install mysql-server </code>

<code> apt-get install php php-mysql php-ldap php-mcrypt php-cli php-soap php-json graphviz </code>

<code> apt-get install php-xml php-gd php-zip libapache2-mod-php </code>

''IMPORTANT: The commands are different for other versions of linux, including pre-16.04 versions of Ubuntu. And the installation process if very different for a Windows host''

=== Installing iTop ===

You will need to download the iTop .zip file, which is currently located [https://sourceforge.net/projects/itop/files/itop/ here]. Download the latest version.

You now need to unzip the file, and in Linux (at least Ubuntu), you need to install a program to do so. The recommended program is zip, which can be installed by typing this command: <code> sudo apt-get install zip </code>.

''TIP: You may need to run <code> sudo apt-get update </code> before trying to install zip''

Then to unzip the file run <code> unzip (file_name_here).zip </code>.

You know need to make the install directory for iTop. This can be done by running this command: <code> mkdir /var/www/html/itop </code>

Then move the content of the "web" directory just created from the unzip to the itop directory you just created. This can be done with these commands here:

<code> cd /var/www/html/itop </code>

<code> cp -r /Downloads/web/* . </code>

''IMPORTANT: The last command is dependent on where you unzipped the iTop .zip file.''

Now you will open a web browser and go to the IP of the host computer, with the ending of /itop (for example, localhost/itop if on the host or 10.21.25.60/itop). This will send you to the installation wizard if everything is properly configured. Follow the directions on the installation wizard, and if you need help it can be found [https://www.itophub.io/wiki/page?id=2_4_0%3Ainstall%3Ainstall_wizard here]. But the things the wizard asks for are very dependent on your configuration.

=== Official Instructions ===

The official directions can be found [https://www.itophub.io/wiki/page?id=2_4_0%3Ainstall%3Astart here].

== Connecting to iTop ==

Go to the ip address of the device hosting it, with the extension /itop. Then login. For our iTop server, it is 10.21.25.80/itop.

== Inventory ==

Keeping an accurate inventory is extremely important to help keep track of all devices that we use or may need information on later. We could use this to keep track of all specs, warranties, locations, etc..., of devices for the CTE department. Inventory is done in the [http://wiki.24pin.tech/index.php/ITop#Configuration_Management Configuration Management] section.

When inventorying a device, you should also appropriately create the location so that we know where it should be located, whether that is a room or a cart, you must input the location. To create a location go [http://wiki.24pin.tech/index.php/ITop#Locations here.] '''You should create the location first, or see if the location is already created, then create the device.'''

=== Exporting Inventory Datasheets ===

To export our inventory information into a sheet that can be managed with Excel or as an easy to look at PDF, it is built straight into ITop.

Go to the page you would like to export, for example, Configuration Management (Overview section).

Then click on either the pencil icon [insert here] or the tools icon [insert here] in the top right.

There is an option to export. The smaller pages will give you multiple export options like to PDF or Excel, while large pages will only give you the "export to a file option." This option just exports to a .xml Excel file due to the assumed size. For example, if you export the Overview page of Configuration Management, it will only be possible in .xml.

== The Welcome Page ==

After you have successfully installed iTop and logged in, and click okay on the description popup, you will reach the home/welcome page. From here you can access to all of the different functionalities of iTop.

You can travel back here by clicking the Welcome tab on the left and click the blue Welcome link.

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

=== Configuration Items ===

In this section, you can edit and view business processes, application solutions, contacts, locations, contracts, servers, and network devices.

==== Business Processes ====

A business process is a series of tasks that need to be completed to achieve a goal/larger task for the company. A business process can be attached to certain contacts, organizations, documents, application solutions, and active tickets.

To view all of your business processes, click on the hard hat or on the text that says business process. To create a business process, click the link below the hard hat that is labeled "Create a new Business Process". To search for a business process, click the link below the former, labeled "Search for Business Process objects".

When searching, you can search by production date, name, organization, and priority for the business.

===== Creating a Business Process =====

When creating a business process, there are five tabs in the creation screen that give a variety of options for creating a business process.

First you must add a name for the process, then specify the organization that it affects.

Then, you can set the status (active or inactive) and also how critical it is to the business (low, medium, high). You can also set a production date for it to be completed by. You can also add a description if you'd like.

Then on the Contacts tab you can add contacts to be associated with this process.

You can attach useful/necessary documents using the Documents tab.

Using the Application Solutions tab, you can attach related application solutions to the business process.

And finally, you can attach current tickets/work orders to the business process using the active tickets tab.

Once you are done configuring the business process to your liking, click create at the bottom to create the business process.

==== Application Solutions ====

To view application solutions, click the application solutions icon or text. This will take you to the application solutions page.

You can search application solutions by clicking the "Search for Contact objects" link on the Welcome page.

===== Creating an Application Solution =====

You must set the name of the solution, and the organization it is associated with. You must also set the status and business criticity.

You can also set the production date that the solution should be moved to.

While not necessary, you should write a description.

You can also set associated contacts in the contacts tab by clicking the "Add Contacts' button. Documents, business processes, provider contacts, and services by following the same procedure, except with their respective names.

On the CIs tab you can add CIs by following the same procedures as the previous step, but you can set the solution to be active depending on the status of the connected CIs.

There are three options: If all CIs are up, the solution is up, If at least so many CIs are active, the solution is up, and if a certain percentage of CIs are up then the solution will be up.

Once done configuring, click create.

==== Contacts ====

iTop has a directory of contacts that you can populate so you can more easily contact people in your organization.

To access contacts, click the image of two people that says Contact next to it. This will show the directory of contacts. It will show that person's name, status, organization, email, phone, and their functions in the organization. At the top you can click the Search button to search for someone using the variables previously listed.

You can also search from the Welcome screen by clicking the Search for Contact Objects link underneath the contacts link.

===== Creating a New Person Contact =====

To create a new contact, you can click the Create a New Contact link under the Contact link, or in the Contacts directory click the orange New button at the top right.

On the Properties tab, you will need to input their name (first and last) and select their organization. You need to set their status as well. You can then set their location, function, manager, employee number, email, notifications, and phone numbers.

===== Creating a New Team Contact =====

You must set the name of the team, as well as status and organization. You can also set email, phone, if they get notified, and their function.

You can also assign members and CIs while creating a team. After the team is created and tickets have been added to the team, you can view their tickets here as well.

Then click create when done.

==== Locations ====

Click on the map or the text that says "Locations", and you will be sent to the list of locations that are currently documented on the ITop server. This page is where you can manage locations. Locations are useful for documentation of devices as then you can more easily know where the device is located. You set a device's location during its creation. Contacts can also be attached to a location.

You can search locations by clicking the "Search location objects" link underneath the location icon.

===== Creating a Location =====

While in the locations page, click the "New" button to create a new location. Or you can click the "Create a new location" link at the Welcome page underneath the map/location icon.

After entering the creation interface, you must tell it the name of the location. You can also tell whether or not the location is active, and give its specific address.

There are also tabs to connect contacts and devices that have already been created to the location you are creating.

When you are done, click create.

==== Contracts ====

In this section you can see all of your customer and provider contracts, and create new ones. Access this section by clicking the contract icon or text.

You can search contracts by clicking the "Search for Contract objects" link.

===== Creating a Customer Contract =====

Create a customer contract by clicking the "Create a new Contract" link on the Welcome page or by clicking the new or create button on the contracts page. Then select Customer Contract from the dropdown, and choose apply.

You must set the name of the contract, and set the customer that the contract is for you must also set the provider at the bottom.

You can write the description of the contract, and set the dates that this contract will be active.

You can also set the cost of this contract, and the currency that this contract will be using (dollars and euros). You can also set the billing frequency and cost unit.

You should set the status of the contract, and can also set the contract type.

The contacts tab lets you associate contacts with the contract by clicking the "add contacts" button.

The documents tab '''should be used for contracts''' as it is a contract after all, and a copy should be added by clicking the "add documents" button.

Services can also be associated with the contract by clicking the services tab and the "add services button".

Any of the contacts, documents, and services added can easily be un-added by by clicking their respective check box and the "remove selected objects button".

When done, click the create button.

===== Creating a Provider Contract =====

Instead of choosing "customer contract" from the dropdown after choosing to create a new contract, choose "provider contract".

Provider contracts only have a few minor differences, it asks for the SLA and Service hours, and does not allow services to be connected to it. It does allow for CIs to be added by clicking the respective tab and clicking the "Add Functional CIs" button. They are removed following the same process as document and contact removal.

When done, click the create button.

===== Creating a Contract Type =====

When creating a contract, there is an option to choose the type of contract that the contract should be set as. By default there are no contract types.

To create a new contract type, enter the configuration for a contract either new or existing, and click the plus sign next to the "contract type" dropdown. This will open the contract type creation GUI.

You will then need to type the name, and click create. You now have a new contract type.

==== Servers ====

To view the server list, click the server icon or text. You will then be at the servers page. It is very useful to keep track of all of your servers and their appropriate locations, and what they are all doing.

You can search servers by clicking the "Search for Server objects" link on the Welcome page.

===== Creating a Server =====

To create a new server, you can click the "Create a new Server" link on the Welcome page or click the new button at the top right of the server page. If you have no servers, the server page will display a link to allow you to create your first one.

You must set the name of the server, organization, status, and business criticity. It is recommended you also set the location, rack, and enclosure it is in to help you locate the server later.

You can also set the Brand, Model, OS family, OS version, Management ip, OS licence, CPU, RAM, Rack units, Serial number, Asset number. It is recommended you fill out as much of this information as possible.

'''To add a server to a rack or enclosure, you must create them in this order or you have to go back and edit the server configuration: enclosure, rack, and then server.'''

Dates for when the server was purchased and when it went into production can also be entered. '''The end of the warranty should be entered.'''

You can also select power sources, but they need to be created beforehand.

You can also add a description, recommended.

You can add specific software, contacts, documents, application solutions, network interfaces, FC ports, network devices, SANs (storage area networks), logical volumes, provider contacts, and services, that are currently related to the server. Each can be added by clicking their respective tab and clicking the Add * button (it will have the name of what you're adding on the button after add i.e. Add Logical Volumes).

There is also a tab to view active tickets that involve the server, but will be empty during creation as the server hasn't been added to tickets yet.

==== Network Devices ====

ITop also allows you to add your network devices that you use in your facility. To access the network devices page, click the picture of a switch or the text that says "Network Device". You can search for a network device specifically by clicking the "Search for Network Device objects" link.

===== Creating a Network Device =====

'''You should create the connected devices first so that you can add them all to the network device during creation.'''

To create a network device, click the "Create a new Network Device" link on the Welcome page, click the "Create a new Network Device" link on the network device page (only appears if you don't have any created yet), or click the new button at the top right.

You must give the network device the following: Name, Organization, Status, Business criticity, Location, Rack, and Enclosure. These are all in the General information section.

You should give the following information about the network device: Network type, Brand, Model, IOS version, Management ip, RAM, Rack units, Serial number, and Asset number. You should give all the information you can.

You can also give information about when it will go into production, and the purchase date. '''The end of warranty date should be added.'''

Power supplies can also be added to the server, but must be created beforehand.

You can also add a description, which is recommended.

You can also add contacts, documents, application solutions, network interfaces, devices (connected ones), provider contracts, and services. To add any of these, click the respective tab and click the "Add *" button and follow any necessary GUI.

There is also a tab to view active tickets involving this network device, but it will be empty during the creation process as the network device doesn't exist on the server yet.

=== Helpdesk ===

The helpdesk is accessible from this section, which allows the editing of work orders. To learn more, click [http://wiki.24pin.tech/index.php/ITop#Helpdesk_2 here.]

== Configuration Management ==

The configuration management section of ITop is meant for managing the physical and software configuration of devices in ITop's system. In other words, it is a very in-depth inventory system that if done properly, can inventory almost everything that 24Pin works with.

=== Overview ===

The overview page is pretty self explanatory, it is accessed from the configuration management drop down on the left of the ITop page, and shows an overview of all devices and software we have inventoried.

The overview page is split into three sections: Infrastructure, virtualization, end user devices, software and applications, and miscellaneous.

It is organized this way to make it easier to view, as one large list of devices would be difficult to manage. You can click the links under each icon/name for a device/software to create a new one of those devices, or to search for one of them.

==== Infrastructure ====
Infrastructure is what it sounds - physical infrastructure. Racks, enclosures, servers, network devices, etc. To find more info on creating these types of devices, follow the server instruction for a basic rundown [http://wiki.24pin.tech/index.php/ITop#Servers here.] Everything in ITop follows the same procedure, but if you do find something odd or out of order, add it to the wiki.

==== Virtualization ====

The virtualization section is very self explanatory, it is the section for inputting virtualized computers and the systems that they are running on. '''You must create the server farm or hypervisor first, then create the virtual machine''' so that you can choose the virtual host section while creating the virtual machine it ITop. The creation besides that is the same as creating any other object in ITop. Fill in all of the dropdowns and blanks you can, then click create.

''TIP: We don't have a server farm so don't make one.''

==== End User Devices ====

This is where we will input all of the end user devices used or managed by 24Pin. PCs, phones, IP phones, peripherals, etc..., are all inputted here. They follow the same process as adding everything else, fill in all blanks and dropdowns that you can and click create. This will be the largest section due to the amount of PCs.

==== Software and Applications ====

And here (as you probably could have guessed) is where all of the software and applications that we use go. All of the web servers will be documented here, along with any database servers and schemas, licenses, and any other software will be documented here. It is documented the same as other things, but you '''should create the host systems first''' to make the documentation faster and easier as it does ask for the system during creation.

==== Miscellaneous ====

Here is where all of the odds and ends are documented. VLANs, subnets, network interfaces, logical volumes, business processes (For more info go [http://wiki.24pin.tech/index.php/ITop#Business_Processes here.]), application solutions (For more info go [http://wiki.24pin.tech/index.php/ITop#Application_Solutions here].), and groups are all here. ''Tip: ''' You must create the device, then the network interface(s), the subnets, and then the VLANs to make life easier.'''''

Network devices also allow you to document there interfaces. To create a network device to go with your interfaces (like router or switch) go [http://wiki.24pin.tech/index.php/ITop#Network_Devices here].

=== Contacts ===

For more detailed contacts management, I recommend following the previous directions in the [http://wiki.24pin.tech/index.php/ITop#Contacts Contacts] section.

=== Locations ===

Configuration management has a link on the left to access the locations area of ITop. To find more info about creating and managing locations go [http://wiki.24pin.tech/index.php/ITop#Locations here.]

== Helpdesk ==

The helpdesk is where we will process work orders in ITop. Click the Helpdesk header on the left to show the different helpdesk subpages.

=== Overview ===
The overview section is the main homepage of the ITop helpdesk. It shows a graph of requests made over the past two weeks on a per day basis/per type basis. It also displays open requests in four different organized tables.

[[File:HelpdeskOverview.PNG|600px]]

=== New User Request ===

New user requests can be created by clicking on the new user request link ok the left side underneath the Helpdesk section.

It is similar to creating other objects in the configuration sections of ITop.

Fill out all of the things possible, and make sure to assign it to the proper person after creating.

To learn more about how to create and fill out things in ITop, I recommend reading over the [http://wiki.24pin.tech/index.php/ITop#Configuration_Management Configuration Management] section.

=== Search for User Requests ===

This allows for you to search for user requests, and allows for you to search using many different identifying items for search.

=== Shortcuts ===

Helpdesk has some shortcuts below this section to access different portions more quickly.

==== Requests assigned to me ====

This allows the user to easily view all requests that have been assigned to the current account that they have signed in as (This is referring to requests like help desk tickets).

== Admin Tools ==

This is where all of the tools for administration of ITop are located. Only people who have the rights to use these tools will have access to them.

=== Adding New Accounts ===

''TIP: You should create a contact for a user first, then make a user as during user creation you can connect the two. You can create a contact during user creation, but it creates a GUI over a GUI and makes things more complicated.''

While logged in as an admin, go to the Welcome screen and click on the Admin Tools tab on the left. Then click on the User Accounts link. Once on the User Accounts page, click the orange "new" tab at the top right.

You can create an External User, LDAP User, or iTop user. In this we will be creating an iTop user.

First you will select a contact for the new user if necessary (recommended), and set their username and password. You can also set the language they will be using, and if their account is currently enabled. If a contact has not been created and you want to connect one, click the plus sign to create the contact.

Then in the Profiles tab, you can add a user profile to the person to tell iTop what rights they should have (i.e. Administrator or Portal User). You can also explain why they need those rights in the reason section.

Then in the Allowed Organizations tab, you can choose what organizations they can see information from. If they are not specified to a different organization, they have no restriction.

== xRDP ==

This is a very useful tool that is currently installed on our ITop 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 ITop IP, and when prompted type in the login.

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

== Important Links ==

[https://www.combodo.com/itop-193 Official Combodo ITop link]

[https://www.itophub.io/wiki/page Official Wiki] ''This is very complex and in-depth documentation as they would rather you pay for official training, so their wiki isn't the most user friendly.''

[https://www.youtube.com/watch?v=OLiaOlTDQEI Video on how to install ITop in five minutes.]

Group Policy

2019-05-06T12:56:37Z

Bsanders: Finished description section

FOG

2019-05-05T16:44:29Z

Bsanders: /* "What if FOG is blocked?" */ Updated header for more detail

CISCOACA.local (Retired)

2019-05-05T16:21:19Z

Bsanders: /* Group Policy */ Added security policy links, added explanation for page separation

= Our Domain Setup =

The CISCOACA.local domain is setup to run off of the servers called [[Loki]] and [[Logan]]. The both run [[Active Directory]], [[DNS]], and [[DHCP]]. [[Loki]] is configured as the main server by default, and [[Logan]] is configured as the hot standby. They will failover or trade roles if there is ever an issue. [[Logan]] may also occasionally switch to the main server leaving [[Loki]] as the hot standby, which is fine as they will still have redundancy. [[Logan]] is the default standby, as [[Logan]] also runs the web server VMs so it has more load already.

To learn more about any of these things, click their respective links throughout this page.

== Active Directory ==

[[Active Directory]] controls who gets all of our [[Group Policy]]/[[Security Policy]] and how they are applied. Basically, [[Active Directory]] controls how all of the computers in our domain behave, and is what allows us to have our unique logins that work on every computer. Without it, we are unable to login, we lose our shared folders, and we lose all our [[Security Policy]].

== Domain Name Services ==

Domain Name Services (or [[DNS]]) is what translates website names to IP addresses (like 24pin.tech to our public IP to Logan). Without it, accessing the internet and other computers on the network would require us to have all of the IPs memorized. That is bad. We like [[DNS]]. [[DNS]] is also needed for things to function properly since our network is in the middle of MUSD.local's things, so we need to forward properly through them.

== DHCP ==

[[DHCP]] is run on [[Loki]] as the main server, and [[Logan]] is the hot standby. Our [[DHCP]] setup is fairly basic, but we do have special settings configured for [[FOG]] and for our servers and printers we have [[DHCP]] reservations.

== Group Policy ==

[[Group Policy]] is where all of the settings and changes that we want to make to all of the computers in our network are made. Pretty much every Windows setting you have ever heard of, and many you haven't heard of, can be changed here and applied to some or all of the computers or servers in our network. We have different [[Group Policy]] settings set for our normal computers than the servers, and different ones are applied to computers that may run through our [[Active Directory]] but are in different rooms. Our [[Security Policy]] is part of [[Group Policy]] but has it's own page, as it is very important to keep things controlled and needed more of an explanation than other parts of [[Group Policy]].

Surface USB/PXE

2019-04-30T21:03:05Z

Bsanders: Added header

= This process is for a Surface Pro 2 device =

== Step One ==

Disable secure boot by booting the device while holding the volume up button, and release the power button when the Surface logo appears.

== Step Two ==

Insert a bootable USB or USB to ethernet adapter. If you are using an ethernet adapter you must boot into the os first (if possible) or at least attempt to boot with the ethernet adapter plugged in to allow for driver initialization.

Then boot the Surface by holding the power button and volume down and it will boot into the USB or PXE device.

== The Setup USB ==

The setup USB is not a normal Windows 8.1 install USB, and will boot into a blue screen that gives you different options. If you wish to "reinstall" Windows on a Surface, you must choose troubleshoot and reset device.

== Other Surface Related Links ==

[https://support.microsoft.com/en-us/help/4023511/surface-boot-surface-from-a-usb-device Microsoft Boot Instructions]

= This process is for a Surface Pro 3 device =

==Step One==

Download the image and set up the bootable USB
[https://support.microsoft.com/en-us/surfacerecoveryimage]

==Step Two==

Use the drive to restore the surface
[https://www.cocosenor.com/articles/surface/reinstall-surface-with-usb-drive.html]
https://support.microsoft.com/en-us/surfacerecoveryimage

== More Info About FOG ==

[[FOG]]

ITop

2019-04-30T20:54:06Z

Bsanders: /* Requests assigned to me */ Finished this section

== What is iTop? ==
iTop is a software for managing IT services/tickets and resources, and keeping track of end users and devices and their status. It is similar to Spiceworks, if you have used that software.

Here is its full official description:

iTop is a complete, OpenSource, IT Operational Portal.

It includes:
* A complete CMDB (Configuration management database) to document and manage the IT inventory.
* An Incident management module to track and communicate about all issues occurring in the IT.
* A change management module to plan and track the changes to the IT environment.
* A known error database to speed up the resolution of incidents.
* An outage module to document all planned outages and notify the appropriate contacts.
* Dashboards to quickly get an overview of your IT.
All the modules can be setup, step by step, indepently of each other.

iTop is service provider oriented, it allows IT engineers to manage easily multiple customers or organizations.
iTop, delivers a feature-rich set of business processes that:
* Enhances IT management effectiveness
* Drives IT operations performance
* Improves customer satisfaction and provides executives with insights into business performance.

iTop is completely open to be integrated within your current IT Management infrastructure.

Adopting this new generation of IT Operational portal will help you to:
* Better manage a more and more complex IT environment.
* Implement ITIL processes at your own pace.
* Manage the most important asset of your IT: Documentation.

== Initial Setup ==

=== Prerequisites ===

First you must install a web server software. Use whatever you are most comfortable or familiar with. We usually use Apache, and we will be using a Ubuntu machine (17.10 server with a gui installed. Can be downloaded [https://www.ubuntu.com/download/server here].
You will also need to install PHP, graphviz, and MySQL to run iTop.

Here are the commands you need to run if you are using a version of Ubuntu 16.04 or Higher:

<code> apt-get install apache2 </code>

<code> apt-get install mysql-server </code>

<code> apt-get install php php-mysql php-ldap php-mcrypt php-cli php-soap php-json graphviz </code>

<code> apt-get install php-xml php-gd php-zip libapache2-mod-php </code>

''IMPORTANT: The commands are different for other versions of linux, including pre-16.04 versions of Ubuntu. And the installation process if very different for a Windows host''

=== Installing iTop ===

You will need to download the iTop .zip file, which is currently located [https://sourceforge.net/projects/itop/files/itop/ here]. Download the latest version.

You now need to unzip the file, and in Linux (at least Ubuntu), you need to install a program to do so. The recommended program is zip, which can be installed by typing this command: <code> sudo apt-get install zip </code>.

''TIP: You may need to run <code> sudo apt-get update </code> before trying to install zip''

Then to unzip the file run <code> unzip (file_name_here).zip </code>.

You know need to make the install directory for iTop. This can be done by running this command: <code> mkdir /var/www/html/itop </code>

Then move the content of the "web" directory just created from the unzip to the itop directory you just created. This can be done with these commands here:

<code> cd /var/www/html/itop </code>

<code> cp -r /Downloads/web/* . </code>

''IMPORTANT: The last command is dependent on where you unzipped the iTop .zip file.''

Now you will open a web browser and go to the IP of the host computer, with the ending of /itop (for example, localhost/itop if on the host or 10.21.25.60/itop). This will send you to the installation wizard if everything is properly configured. Follow the directions on the installation wizard, and if you need help it can be found [https://www.itophub.io/wiki/page?id=2_4_0%3Ainstall%3Ainstall_wizard here]. But the things the wizard asks for are very dependent on your configuration.

=== Official Instructions ===

The official directions can be found [https://www.itophub.io/wiki/page?id=2_4_0%3Ainstall%3Astart here].

== Connecting to iTop ==

Go to the ip address of the device hosting it, with the extension /itop. Then login. For our iTop server, it is 10.21.25.80/itop.

== Inventory ==

Keeping an accurate inventory is extremely important to help keep track of all devices that we use or may need information on later. We could use this to keep track of all specs, warranties, locations, etc..., of devices for the CTE department. Inventory is done in the [http://wiki.24pin.tech/index.php/ITop#Configuration_Management Configuration Management] section.

When inventorying a device, you should also appropriately create the location so that we know where it should be located, whether that is a room or a cart, you must input the location. To create a location go [http://wiki.24pin.tech/index.php/ITop#Locations here.] '''You should create the location first, or see if the location is already created, then create the device.'''

=== Exporting Inventory Datasheets ===

To export our inventory information into a sheet that can be managed with Excel or as an easy to look at PDF, it is built straight into ITop.

Go to the page you would like to export, for example, Configuration Management (Overview section).

Then click on either the pencil icon [insert here] or the tools icon [insert here] in the top right.

There is an option to export. The smaller pages will give you multiple export options like to PDF or Excel, while large pages will only give you the "export to a file option." This option just exports to a .xml Excel file due to the assumed size. For example, if you export the Overview page of Configuration Management, it will only be possible in .xml.

== The Welcome Page ==

After you have successfully installed iTop and logged in, and click okay on the description popup, you will reach the home/welcome page. From here you can access to all of the different functionalities of iTop.

You can travel back here by clicking the Welcome tab on the left and click the blue Welcome link.

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

=== Configuration Items ===

In this section, you can edit and view business processes, application solutions, contacts, locations, contracts, servers, and network devices.

==== Business Processes ====

A business process is a series of tasks that need to be completed to achieve a goal/larger task for the company. A business process can be attached to certain contacts, organizations, documents, application solutions, and active tickets.

To view all of your business processes, click on the hard hat or on the text that says business process. To create a business process, click the link below the hard hat that is labeled "Create a new Business Process". To search for a business process, click the link below the former, labeled "Search for Business Process objects".

When searching, you can search by production date, name, organization, and priority for the business.

===== Creating a Business Process =====

When creating a business process, there are five tabs in the creation screen that give a variety of options for creating a business process.

First you must add a name for the process, then specify the organization that it affects.

Then, you can set the status (active or inactive) and also how critical it is to the business (low, medium, high). You can also set a production date for it to be completed by. You can also add a description if you'd like.

Then on the Contacts tab you can add contacts to be associated with this process.

You can attach useful/necessary documents using the Documents tab.

Using the Application Solutions tab, you can attach related application solutions to the business process.

And finally, you can attach current tickets/work orders to the business process using the active tickets tab.

Once you are done configuring the business process to your liking, click create at the bottom to create the business process.

==== Application Solutions ====

To view application solutions, click the application solutions icon or text. This will take you to the application solutions page.

You can search application solutions by clicking the "Search for Contact objects" link on the Welcome page.

===== Creating an Application Solution =====

You must set the name of the solution, and the organization it is associated with. You must also set the status and business criticity.

You can also set the production date that the solution should be moved to.

While not necessary, you should write a description.

You can also set associated contacts in the contacts tab by clicking the "Add Contacts' button. Documents, business processes, provider contacts, and services by following the same procedure, except with their respective names.

On the CIs tab you can add CIs by following the same procedures as the previous step, but you can set the solution to be active depending on the status of the connected CIs.

There are three options: If all CIs are up, the solution is up, If at least so many CIs are active, the solution is up, and if a certain percentage of CIs are up then the solution will be up.

Once done configuring, click create.

==== Contacts ====

iTop has a directory of contacts that you can populate so you can more easily contact people in your organization.

To access contacts, click the image of two people that says Contact next to it. This will show the directory of contacts. It will show that person's name, status, organization, email, phone, and their functions in the organization. At the top you can click the Search button to search for someone using the variables previously listed.

You can also search from the Welcome screen by clicking the Search for Contact Objects link underneath the contacts link.

===== Creating a New Person Contact =====

To create a new contact, you can click the Create a New Contact link under the Contact link, or in the Contacts directory click the orange New button at the top right.

On the Properties tab, you will need to input their name (first and last) and select their organization. You need to set their status as well. You can then set their location, function, manager, employee number, email, notifications, and phone numbers.

===== Creating a New Team Contact =====

You must set the name of the team, as well as status and organization. You can also set email, phone, if they get notified, and their function.

You can also assign members and CIs while creating a team. After the team is created and tickets have been added to the team, you can view their tickets here as well.

Then click create when done.

==== Locations ====

Click on the map or the text that says "Locations", and you will be sent to the list of locations that are currently documented on the ITop server. This page is where you can manage locations. Locations are useful for documentation of devices as then you can more easily know where the device is located. You set a device's location during its creation. Contacts can also be attached to a location.

You can search locations by clicking the "Search location objects" link underneath the location icon.

===== Creating a Location =====

While in the locations page, click the "New" button to create a new location. Or you can click the "Create a new location" link at the Welcome page underneath the map/location icon.

After entering the creation interface, you must tell it the name of the location. You can also tell whether or not the location is active, and give its specific address.

There are also tabs to connect contacts and devices that have already been created to the location you are creating.

When you are done, click create.

==== Contracts ====

In this section you can see all of your customer and provider contracts, and create new ones. Access this section by clicking the contract icon or text.

You can search contracts by clicking the "Search for Contract objects" link.

===== Creating a Customer Contract =====

Create a customer contract by clicking the "Create a new Contract" link on the Welcome page or by clicking the new or create button on the contracts page. Then select Customer Contract from the dropdown, and choose apply.

You must set the name of the contract, and set the customer that the contract is for you must also set the provider at the bottom.

You can write the description of the contract, and set the dates that this contract will be active.

You can also set the cost of this contract, and the currency that this contract will be using (dollars and euros). You can also set the billing frequency and cost unit.

You should set the status of the contract, and can also set the contract type.

The contacts tab lets you associate contacts with the contract by clicking the "add contacts" button.

The documents tab '''should be used for contracts''' as it is a contract after all, and a copy should be added by clicking the "add documents" button.

Services can also be associated with the contract by clicking the services tab and the "add services button".

Any of the contacts, documents, and services added can easily be un-added by by clicking their respective check box and the "remove selected objects button".

When done, click the create button.

===== Creating a Provider Contract =====

Instead of choosing "customer contract" from the dropdown after choosing to create a new contract, choose "provider contract".

Provider contracts only have a few minor differences, it asks for the SLA and Service hours, and does not allow services to be connected to it. It does allow for CIs to be added by clicking the respective tab and clicking the "Add Functional CIs" button. They are removed following the same process as document and contact removal.

When done, click the create button.

===== Creating a Contract Type =====

When creating a contract, there is an option to choose the type of contract that the contract should be set as. By default there are no contract types.

To create a new contract type, enter the configuration for a contract either new or existing, and click the plus sign next to the "contract type" dropdown. This will open the contract type creation GUI.

You will then need to type the name, and click create. You now have a new contract type.

==== Servers ====

To view the server list, click the server icon or text. You will then be at the servers page. It is very useful to keep track of all of your servers and their appropriate locations, and what they are all doing.

You can search servers by clicking the "Search for Server objects" link on the Welcome page.

===== Creating a Server =====

To create a new server, you can click the "Create a new Server" link on the Welcome page or click the new button at the top right of the server page. If you have no servers, the server page will display a link to allow you to create your first one.

You must set the name of the server, organization, status, and business criticity. It is recommended you also set the location, rack, and enclosure it is in to help you locate the server later.

You can also set the Brand, Model, OS family, OS version, Management ip, OS licence, CPU, RAM, Rack units, Serial number, Asset number. It is recommended you fill out as much of this information as possible.

'''To add a server to a rack or enclosure, you must create them in this order or you have to go back and edit the server configuration: enclosure, rack, and then server.'''

Dates for when the server was purchased and when it went into production can also be entered. '''The end of the warranty should be entered.'''

You can also select power sources, but they need to be created beforehand.

You can also add a description, recommended.

You can add specific software, contacts, documents, application solutions, network interfaces, FC ports, network devices, SANs (storage area networks), logical volumes, provider contacts, and services, that are currently related to the server. Each can be added by clicking their respective tab and clicking the Add * button (it will have the name of what you're adding on the button after add i.e. Add Logical Volumes).

There is also a tab to view active tickets that involve the server, but will be empty during creation as the server hasn't been added to tickets yet.

==== Network Devices ====

ITop also allows you to add your network devices that you use in your facility. To access the network devices page, click the picture of a switch or the text that says "Network Device". You can search for a network device specifically by clicking the "Search for Network Device objects" link.

===== Creating a Network Device =====

'''You should create the connected devices first so that you can add them all to the network device during creation.'''

To create a network device, click the "Create a new Network Device" link on the Welcome page, click the "Create a new Network Device" link on the network device page (only appears if you don't have any created yet), or click the new button at the top right.

You must give the network device the following: Name, Organization, Status, Business criticity, Location, Rack, and Enclosure. These are all in the General information section.

You should give the following information about the network device: Network type, Brand, Model, IOS version, Management ip, RAM, Rack units, Serial number, and Asset number. You should give all the information you can.

You can also give information about when it will go into production, and the purchase date. '''The end of warranty date should be added.'''

Power supplies can also be added to the server, but must be created beforehand.

You can also add a description, which is recommended.

You can also add contacts, documents, application solutions, network interfaces, devices (connected ones), provider contracts, and services. To add any of these, click the respective tab and click the "Add *" button and follow any necessary GUI.

There is also a tab to view active tickets involving this network device, but it will be empty during the creation process as the network device doesn't exist on the server yet.

=== Helpdesk ===

The helpdesk is accessible from this section, which allows the editing of work orders. To learn more, click [http://wiki.24pin.tech/index.php/ITop#Helpdesk_2 here.]

== Configuration Management ==

The configuration management section of ITop is meant for managing the physical and software configuration of devices in ITop's system. In other words, it is a very in-depth inventory system that if done properly, can inventory almost everything that 24Pin works with.

=== Overview ===

The overview page is pretty self explanatory, it is accessed from the configuration management drop down on the left of the ITop page, and shows an overview of all devices and software we have inventoried.

The overview page is split into three sections: Infrastructure, virtualization, end user devices, software and applications, and miscellaneous.

It is organized this way to make it easier to view, as one large list of devices would be difficult to manage. You can click the links under each icon/name for a device/software to create a new one of those devices, or to search for one of them.

==== Infrastructure ====
Infrastructure is what it sounds - physical infrastructure. Racks, enclosures, servers, network devices, etc. To find more info on creating these types of devices, follow the server instruction for a basic rundown [http://wiki.24pin.tech/index.php/ITop#Servers here.] Everything in ITop follows the same procedure, but if you do find something odd or out of order, add it to the wiki.

==== Virtualization ====

The virtualization section is very self explanatory, it is the section for inputting virtualized computers and the systems that they are running on. '''You must create the server farm or hypervisor first, then create the virtual machine''' so that you can choose the virtual host section while creating the virtual machine it ITop. The creation besides that is the same as creating any other object in ITop. Fill in all of the dropdowns and blanks you can, then click create.

''TIP: We don't have a server farm so don't make one.''

==== End User Devices ====

This is where we will input all of the end user devices used or managed by 24Pin. PCs, phones, IP phones, peripherals, etc..., are all inputted here. They follow the same process as adding everything else, fill in all blanks and dropdowns that you can and click create. This will be the largest section due to the amount of PCs.

==== Software and Applications ====

And here (as you probably could have guessed) is where all of the software and applications that we use go. All of the web servers will be documented here, along with any database servers and schemas, licenses, and any other software will be documented here. It is documented the same as other things, but you '''should create the host systems first''' to make the documentation faster and easier as it does ask for the system during creation.

==== Miscellaneous ====

Here is where all of the odds and ends are documented. VLANs, subnets, network interfaces, logical volumes, business processes (For more info go [http://wiki.24pin.tech/index.php/ITop#Business_Processes here.]), application solutions (For more info go [http://wiki.24pin.tech/index.php/ITop#Application_Solutions here].), and groups are all here. ''Tip: ''' You must create the device, then the network interface(s), the subnets, and then the VLANs to make life easier.'''''

Network devices also allow you to document there interfaces. To create a network device to go with your interfaces (like router or switch) go [http://wiki.24pin.tech/index.php/ITop#Network_Devices here].

=== Contacts ===

For more detailed contacts management, I recommend following the previous directions in the [http://wiki.24pin.tech/index.php/ITop#Contacts Contacts] section.

=== Locations ===

Configuration management has a link on the left to access the locations area of ITop. To find more info about creating and managing locations go [http://wiki.24pin.tech/index.php/ITop#Locations here.]

== Helpdesk ==

The helpdesk is where we will process work orders in ITop. Click the Helpdesk header on the left to show the different helpdesk subpages.

=== Overview ===
The overview section is the main homepage of the ITop helpdesk. It shows a graph of requests made over the past two weeks on a per day basis/per type basis. It also displays open requests in four different organized tables.

[[File:HelpdeskOverview.PNG|600px]]

=== New User Request ===

New user requests can be created by clicking on the new user request link ok the left side underneath the Helpdesk section.

It is similar to creating other objects in the configuration sections of ITop.

Fill out all of the things possible, and make sure to assign it to the proper person after creating.

To learn more about how to create and fill out things in ITop, I recommend reading over the [http://wiki.24pin.tech/index.php/ITop#Configuration_Management Configuration Management] section.

=== Search for User Requests ===

This allows for you to search for user requests, and allows for you to search using many different identifying items for search.

=== Shortcuts ===

Helpdesk has some shortcuts below this section to access different portions more quickly.

==== Requests assigned to me ====

This allows the user to easily view all requests that have been assigned to the current account that they have signed in as (This is referring to requests like help desk tickets).

== Admin Tools ==

This is where all of the tools for administration of ITop are located. Only people who have the rights to use these tools will have access to them.

=== Adding New Accounts ===

''TIP: You should create a contact for a user first, then make a user as during user creation you can connect the two. You can create a contact during user creation, but it creates a GUI over a GUI and makes things more complicated.''

While logged in as an admin, go to the Welcome screen and click on the Admin Tools tab on the left. Then click on the User Accounts link. Once on the User Accounts page, click the orange "new" tab at the top right.

You can create an External User, LDAP User, or iTop user. In this we will be creating an iTop user.

First you will select a contact for the new user if necessary (recommended), and set their username and password. You can also set the language they will be using, and if their account is currently enabled. If a contact has not been created and you want to connect one, click the plus sign to create the contact.

Then in the Profiles tab, you can add a user profile to the person to tell iTop what rights they should have (i.e. Administrator or Portal User). You can also explain why they need those rights in the reason section.

Then in the Allowed Organizations tab, you can choose what organizations they can see information from. If they are not specified to a different organization, they have no restriction.

== xRDP ==

This is a very useful tool that is currently installed on our ITop 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 ITop IP, and when prompted type in the login.

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

== Important Links ==

[https://www.combodo.com/itop-193 Official Combodo ITop link]

[https://www.itophub.io/wiki/page Official Wiki] ''This is very complex and in-depth documentation as they would rather you pay for official training, so their wiki isn't the most user friendly.''

[https://www.youtube.com/watch?v=OLiaOlTDQEI Video on how to install ITop in five minutes.]

DHCP

2019-04-29T20:02:26Z

Bsanders: Finished DHCP page

= Our DHCP Setup =

Our DHCP is run on [[Loki]] mainly, but [[Logan]] is on hot standby. DHCP is what gives out the IP addresses to the devices on our network. Without it, we would have to use static IP addresses, or we would not be able to communicate properly. Both of the servers keep each other synced on what IP addresses have been given out to ensure there are no conflicts.

== Address Pool ==

Our scope is 10.21.25.0, as that is our network. The DHCP server only distributes addresses in from 10.21.25.20 to 10.21.25.247. The rest in the network are reserved for servers and printers, or anything else that needs a static IP.

== Address Leases ==

These are all of the current DHCP releases that the DHCP servers have put out that are active.

== Reservations ==

This is where all of our static DHCP-side reservations for our servers, printers, NAS, etc., are located. You can double click any of them to edit their specific settings.

== Scope Options ==

This is where we configure our DHCP options. To configure options that we don't already have set, right click "Scope Options" and click on "Configure Options" and configure what you need. Below are the options we already have set:

[[File:DHCP_Options.PNG]]

These options set where the computers will look for DNS, what our domain name is ([[CISCOACA.local]]) and the other options tell computers to PXE boot from [[FOG]] and configures the settings they need to boot from [[FOG]].

== Policies ==

These are settings that are applied to certain devices based off of rules defined by the policy, like IP address range, vendor, etc.

The only policy we have currently configured is called UEFI, which applies to network booting via UEFI. It sets options 66 and 67 to make sure devices will boot properly off of [[FOG]]. 67 is set to ipxe.efi, and 66 is set to 10.21.25.4.

== Server Options ==

This is where settings can be configured globally across the whole DHCP server. We have non of these currently configured.

== Policies (Not within scope) ==

Same as above policies but global, we do not have this configured.

== Filters ==

This allows you to block or allow certain MAC addresses from receiving DHCP addresses.

DHCP

2019-04-29T15:29:50Z

Bsanders: Options, reservations, and leases sections

File:DHCP Options.PNG

2019-04-29T15:23:05Z

Bsanders:

Security Policy

2019-04-29T01:41:35Z

Bsanders: Added preface section

= Group Policy =

Security Policy is done within [[Group Policy]]. If you are unsure what [[Group Policy]] is, or what it does, etc., visit the [[Group Policy]] page or the page on our domain: [[CISCOACA.local]] for more information.

= Global Security Policy =

Our Global security policy is located in the Group Policy Objects folder, and is named Security Policy. All of the configurations made by this are too long to list, but they are all located in <code>Computer Configuration/Policies/Windows Settings/Security Settings</code> within the object.

== Default Domain Controllers Policy ==

This policy controls the administration of the domain controllers. It has some security settings configured to disallow the Service Admins from accessing them.

These configuration items are located in: <code>Computer Configuration/Policies/Windows Settings/Security Settings/Local Policies/User Rights Assignment</code>

The configurations that stop Service Admins from accessing the servers are: Deny access to this computer from the network, deny log on locally, Deny log on through Remote Desktop Services.

=== Service Admins ===

This is a group that is within the Users folder in our active directory. It is used to define users that should have admin rights, but should not have access the the servers. Users put in this group also should be in the Domain Admins group.

==== Install ====

The install account is the one that we currently use for our service account, and should currently be the only one in the Service Admins group. The install account is located in the Admins folder in CiscoAcademy.

= Local Security Policy =

Locally on all of the servers, I have edited their settings to require auditing, this is done on the GPO security policy as well, but just in case some settings do not configure properly it will always audit what is happening to the server.

CISCOACA.local (Retired)

2019-04-29T01:39:21Z

Bsanders: /* Active Directory */ Added another link

CISCOACA.local (Retired)

2019-04-29T01:38:35Z

Bsanders: /* Active Directory */ Updated with links

= Our Domain Setup =

The CISCOACA.local domain is setup to run off of the servers called [[Loki]] and [[Logan]]. The both run [[Active Directory]], [[DNS]], and [[DHCP]]. [[Loki]] is configured as the main server by default, and [[Logan]] is configured as the hot standby. They will failover or trade roles if there is ever an issue. [[Logan]] may also occasionally switch to the main server leaving [[Loki]] as the hot standby, which is fine as they will still have redundancy. [[Logan]] is the default standby, as [[Logan]] also runs the web server VMs so it has more load already.

To learn more about any of these things, click their respective links throughout this page.

== Active Directory ==

[[Active Directory]] controls who gets all of our [[Group Policy]]/[[Security Policy]] and how they are applied. Basically, [[Active Directory]] controls how all of the computers in our domain behave, and is what allows us to have our unique logins that work on every computer. Without it, we are unable to login, we lose our shared folders, and we lose all our security settings.

== Domain Name Services ==

Domain Name Services (or [[DNS]]) is what translates website names to IP addresses (like 24pin.tech to our public IP to Logan). Without it, accessing the internet and other computers on the network would require us to have all of the IPs memorized. That is bad. We like [[DNS]]. [[DNS]] is also needed for things to function properly since our network is in the middle of MUSD.local's things, so we need to forward properly through them.

== DHCP ==

[[DHCP]] is run on [[Loki]] as the main server, and [[Logan]] is the hot standby. Our [[DHCP]] setup is fairly basic, but we do have special settings configured for [[FOG]] and for our servers and printers we have [[DHCP]] reservations.

== Group Policy ==

[[Group Policy]] is where all of the settings and changes that we want to make to all of the computers in our network are made. Pretty much every Windows setting you have ever heard of, and many you haven't heard of, can be changed here and applied to some or all of the computers or servers in our network. We have different [[Group Policy]] settings set for our normal computers than the servers, and different ones are applied to computers that may run through our [[Active Directory]] but are in different rooms.

Group Policy

2019-04-29T01:25:16Z

Bsanders: Created page and created header. Far from complete

= Our Group Policy Setup =

CISCOACA.local (Retired)

2019-04-29T01:24:49Z

Bsanders: /* Group Policy */ Fixed typo

= Our Domain Setup =

The CISCOACA.local domain is setup to run off of the servers called [[Loki]] and [[Logan]]. The both run [[Active Directory]], [[DNS]], and [[DHCP]]. [[Loki]] is configured as the main server by default, and [[Logan]] is configured as the hot standby. They will failover or trade roles if there is ever an issue. [[Logan]] may also occasionally switch to the main server leaving [[Loki]] as the hot standby, which is fine as they will still have redundancy. [[Logan]] is the default standby, as [[Logan]] also runs the web server VMs so it has more load already.

To learn more about any of these things, click their respective links throughout this page.

== Active Directory ==

[[Active Directory]] controls who gets all of our group policy/security settings and how they are applied. Basically, [[Active Directory]] controls how all of the computers in our domain behave, and is what allows us to have our unique logins that work on every computer. Without it, we are unable to login, we lose our shared folders, and we lose all our security settings.

== Domain Name Services ==

Domain Name Services (or [[DNS]]) is what translates website names to IP addresses (like 24pin.tech to our public IP to Logan). Without it, accessing the internet and other computers on the network would require us to have all of the IPs memorized. That is bad. We like [[DNS]]. [[DNS]] is also needed for things to function properly since our network is in the middle of MUSD.local's things, so we need to forward properly through them.

== DHCP ==

[[DHCP]] is run on [[Loki]] as the main server, and [[Logan]] is the hot standby. Our [[DHCP]] setup is fairly basic, but we do have special settings configured for [[FOG]] and for our servers and printers we have [[DHCP]] reservations.

== Group Policy ==

[[Group Policy]] is where all of the settings and changes that we want to make to all of the computers in our network are made. Pretty much every Windows setting you have ever heard of, and many you haven't heard of, can be changed here and applied to some or all of the computers or servers in our network. We have different [[Group Policy]] settings set for our normal computers than the servers, and different ones are applied to computers that may run through our [[Active Directory]] but are in different rooms.

CISCOACA.local (Retired)

2019-04-29T01:24:27Z

Bsanders: Added Group Policy section

= Our Domain Setup =

The CISCOACA.local domain is setup to run off of the servers called [[Loki]] and [[Logan]]. The both run [[Active Directory]], [[DNS]], and [[DHCP]]. [[Loki]] is configured as the main server by default, and [[Logan]] is configured as the hot standby. They will failover or trade roles if there is ever an issue. [[Logan]] may also occasionally switch to the main server leaving [[Loki]] as the hot standby, which is fine as they will still have redundancy. [[Logan]] is the default standby, as [[Logan]] also runs the web server VMs so it has more load already.

To learn more about any of these things, click their respective links throughout this page.

== Active Directory ==

[[Active Directory]] controls who gets all of our group policy/security settings and how they are applied. Basically, [[Active Directory]] controls how all of the computers in our domain behave, and is what allows us to have our unique logins that work on every computer. Without it, we are unable to login, we lose our shared folders, and we lose all our security settings.

== Domain Name Services ==

Domain Name Services (or [[DNS]]) is what translates website names to IP addresses (like 24pin.tech to our public IP to Logan). Without it, accessing the internet and other computers on the network would require us to have all of the IPs memorized. That is bad. We like [[DNS]]. [[DNS]] is also needed for things to function properly since our network is in the middle of MUSD.local's things, so we need to forward properly through them.

== DHCP ==

[[DHCP]] is run on [[Loki]] as the main server, and [[Logan]] is the hot standby. Our [[DHCP]] setup is fairly basic, but we do have special settings configured for [[FOG]] and for our servers and printers we have [[DHCP]] reservations.

== Group Policy ==

[[Group Policy]] is where all of the settings and changes that we want to make to all of the computers in our network are made. Pretty much every Windows setting you have ever heard of, and many you haven't heard of, can be changed here and applied to some or all of the computers or servers in our network. We have different [[Group Policy settings set for our normal computers than the servers, and different ones are applied to computers that may run through our [[Active Directory]] but are in different rooms.

FOG

2019-04-28T03:13:38Z

Bsanders: /* More Information on Surfaces and Other Special Device Booting */ Removed reference to deleted topic

DHCP

2019-04-26T17:28:33Z

Bsanders: added scope and more info

CISCOACA.local (Retired)

2019-04-26T17:02:13Z

Bsanders: Added DHCP section and added appropriate info.

DHCP

2019-04-26T16:52:40Z

Bsanders: Created page and main header

= Our DHCP Setup =

DNS

2019-04-26T16:49:31Z

Bsanders: Finished DNS page, added pics and finalized sections.

= Our DNS Setup =

DNS is what allows us to translate website names to IP addresses. We run our DNS on [[Loki]] and [[Logan]], with [[Logan]] being the hot standby. If you want to know more about our overall domain setup, visit [[CISCOACA.local]].

We have to have our DNS reference the DNS servers of the district as well to ensure everything forwards properly.

== Forward Lookup Zones ==

[[File:LookUpZonesForward.PNG]]

We have four forward lookup zones at the time of writing, these forward lookup zones are where the DNS server will look to reach different devices in the school networks. Two of them are for our network, the CISCOACA.local domain, and two of them are for musd.local/musd20.org. This has all of the devices we may want to reach. DNS populates itself for the most part, so we do not mess with it unless there is an issue.

== Reverse Lookup Zones ==

At the time of writing we have no reverse lookup zones configured

== Trust Points ==

At the time of writing we have no trust points configured.

== Conditional Forwarders ==

At the time of writing we have no conditional forwarders configured.

DNS

2019-04-26T15:25:15Z

Bsanders: Finished our DNS setup section, started forward lookup zones

CISCOACA.local (Retired)

2019-04-25T21:29:50Z

Bsanders: Updated with DNS link

= Our Domain Setup =

The CISCOACA.local domain is setup to run off of the servers called [[Loki]] and [[Logan]]. The both run [[Active Directory]], [[DNS]], and DHCP. v is configured as the main server by default, and [[Logan]] is configured as the hot standby. They will failover or trade roles if there is ever an issue. [[Logan]] may also occasionally switch to the main server leaving [[Loki]] as the hot standby, which is fine as they will still have redundancy. [[Logan]] is the default standby, as [[Logan]] also runs the web server VMs so it has more load already.

== Active Directory ==

[[Active Directory]] holds all of our group policy and security settings. [[Active Directory]] controls how all of the computers in our domain behave, and is what allows us to have our unique logins that work on every computer. Without it, we are unable to login, we lose our shared folders, and we lose all our security settings.

== Domain Name Services ==

Domain Name Services (or [[DNS]]) is what translates website names to IP addresses (like 24pin.tech to our public IP to Logan). Without it, accessing the internet and other computers on the network would require us to have all of the IPs memorized. That is bad. We like [[DNS]]. [[DNS]] is also needed for things to function properly since our network is in the middle of MUSD.local's things, so we need to forward properly through them.

DNS

2019-04-25T21:29:11Z

Bsanders: Created page and created header. Far from complete

= Our DNS Setup =

CISCOACA.local (Retired)

2019-04-25T21:28:30Z

Bsanders: Updated with AD link

= Our Domain Setup =

The CISCOACA.local domain is setup to run off of the servers called [[Loki]] and [[Logan]]. The both run [[Active Directory]], DNS, and DHCP. v is configured as the main server by default, and [[Logan]] is configured as the hot standby. They will failover or trade roles if there is ever an issue. [[Logan]] may also occasionally switch to the main server leaving [[Loki]] as the hot standby, which is fine as they will still have redundancy. [[Logan]] is the default standby, as [[Logan]] also runs the web server VMs so it has more load already.

== Active Directory ==

[[Active Directory]] holds all of our group policy and security settings. [[Active Directory]] controls how all of the computers in our domain behave, and is what allows us to have our unique logins that work on every computer. Without it, we are unable to login, we lose our shared folders, and we lose all our security settings.

== Domain Name Services ==

Domain Name Services (or DNS) is what translates website names to IP addresses (like 24pin.tech to our public IP to Logan). Without it, accessing the internet and other computers on the network would require us to have all of the IPs memorized. That is bad. We like DNS. DNS is also needed for things to function properly since our network is in the middle of MUSD.local's things, so we need to forward properly through them.

Active Directory

2019-04-25T21:27:41Z

Bsanders: Completed. Covers basics of AD setup

= Our Active Directory Setup =
If you are not sure how our domain works, start at the [[CISCOACA.local]] specific page.

Our active directory setup is quite simple, in our Active Directory, we just have the users that use the lab (which is organized into classes) and the computers we use that are on our domain. We have the computers also organized by room and number.

== Computers ==

In Active Directory Users and Computers, all of our computers are located in the "All Computers" folder. Within that folder they are organized by room, and also may be organized by number within that to make things easier to view.

The servers are located in the "Domain Controllers" section, separate from all of the other computers.

Different group policy settings are assigned to different folders. The "Domain Controllers" folder has different settings for the computers within than the "All Computers" folders for example. This is because different computers in different areas may need different settings.

=== Computer Groups ===
We have a few groups to help control computers in group policy.

==== Domain Computers ====

All of the computers except for domain controllers are in the Domain Computers group. This puts all of the settings that are created in group policy for the lab onto these computers based on the group's settings.

==== Domain Controllers ====

Our two domain controllers [[Loki]], and [[Logan]] are currently the only computers in this group. That is because computers that control the domain need separate settings and controls applied to them, so this helps ensure that.

CISCOACA.local (Retired)

2019-04-25T21:03:39Z

Bsanders: Finished DNS section

= Our Domain Setup =

The CISCOACA.local domain is setup to run off of the servers called [[Loki]] and [[Logan]]. The both run Active Directory, DNS, and DHCP. v is configured as the main server by default, and [[Logan]] is configured as the hot standby. They will failover or trade roles if there is ever an issue. [[Logan]] may also occasionally switch to the main server leaving [[Loki]] as the hot standby, which is fine as they will still have redundancy. [[Logan]] is the default standby, as [[Logan]] also runs the web server VMs so it has more load already.

== Active Directory ==

Active Directory holds all of our group policy and security settings. Active Directory controls how all of the computers in our domain behave, and is what allows us to have our unique logins that work on every computer. Without it, we are unable to login, we lose our shared folders, and we lose all our security settings.

== Domain Name Services ==

Domain Name Services (or DNS) is what translates website names to IP addresses (like 24pin.tech to our public IP to Logan). Without it, accessing the internet and other computers on the network would require us to have all of the IPs memorized. That is bad. We like DNS. DNS is also needed for things to function properly since our network is in the middle of MUSD.local's things, so we need to forward properly through them.

Logan (Retired)

2019-04-25T20:59:46Z

Bsanders: Moved DHCP

== General Overview ==
Logan (10.21.25.11) 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.

== Startup ==
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>
set w = CreateObject("WScript.Shell")
w.Run chr(34) & "C:\Program Files\nodejs\parsoid\parsoid.bat" & chr(34), 0
set w = Nothing
</pre>

== Print Services ==
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.

[[File:Logan_PrintAllPrinters.png]]

Below is the advanced configuration page for both of the main printers.

[[File:Printers-advanced_logan.png|frameless|600x600px]]

== Backup Domain Controller ==
Logan is a backup domain controller for Loki, meaning it is on hot standby for DNS and Active Directory

=== DHCP ===
Logan runs as a backup DHCP server for Loki.

==WAMP Stack (Apache Server) ==
Everything you need to know about our web server can be found on the [http://wiki.24pin.tech/index.php/Apache Apache] page. It covers everything ranging from installation to configuration, and covers the basics to troubleshooting.

Logan (Retired)

2019-04-25T20:59:12Z

Bsanders: Small Changes to increase accuracy and conciseness

== General Overview ==
Logan (10.21.25.11) 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.

== Startup ==
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>
set w = CreateObject("WScript.Shell")
w.Run chr(34) & "C:\Program Files\nodejs\parsoid\parsoid.bat" & chr(34), 0
set w = Nothing
</pre>

== Print Services ==
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.

[[File:Logan_PrintAllPrinters.png]]

Below is the advanced configuration page for both of the main printers.

[[File:Printers-advanced_logan.png|frameless|600x600px]]

== Backup Domain Controller ==
Logan is a backup domain controller for Loki, meaning it is on hot standby for DNS and Active Directory

==WAMP Stack (Apache Server) ==
Everything you need to know about our web server can be found on the [http://wiki.24pin.tech/index.php/Apache Apache] page. It covers everything ranging from installation to configuration, and covers the basics to troubleshooting.

== DHCP ==
Logan runs as a backup DHCP server for Loki.