https://wiki.24pin.tech/api.php?action=feedcontributions&feedformat=atom&user=KWahl 2026-05-08T13:17:34Z User contributions MediaWiki 1.37.1 https://wiki.24pin.tech/index.php?title=WordPress&diff=1096 2021-01-14T21:59:32Z

<p>KWahl: </p> <hr /> <div>==Introduction==<br /> [[File:Wp-admin.png|thumb|screenshot of the WordPress admin dashboard]]<br /> [https://wordpress.org/ WordPress] is a content management system (CMS) that is functions primarily serve our [http://24pin.tech/ homepage] to users that would like to get help or discover more about the program. It's a very powerful platform that grants administrators creative freedom over whatever they want on their website.<br /> <br /> ==Installation==<br /> The installation for WordPress is really simple. All you have to do is download the compressed file for the installation and extract it in the directory that you'd want to install it to. You can either download it from their [https://wordpress.org/download/ website here] or alternatively you can download it using &lt;code&gt;wget&lt;/code&gt;. The command would be &lt;code&gt;sudo wget &lt;nowiki&gt;https://wordpress.org/latest.tar.gz&lt;/nowiki&gt;&lt;/code&gt; on UNIX systems (if you're using aptitude for your package manager.) Once you've downloaded the file, run &lt;code&gt;sudo tar -xzvf latest.tar.gz&lt;/code&gt; to extract it.<br /> <br /> .<br /> <br /> Once you've downloaded and extracted the file, visit your web server to continue with the installation process. From here you must create a Database for WordPress, we use MySQL the instructions for creating a database within MySQL goes as follows. <br /> <br /> ===Accessing MySQL===<br /> First of all log onto your webserver. (Logan is 24PinTech's webserver)<br /> <br /> Once in the webserver and you have access to the command line use this command to go into the MySQL command prompt &lt;code&gt;mysql -u &lt;admin username&gt; -p&lt;/code&gt; then type in the password associated with your admin user. Upon success you should see a prompt that looks like such:<br /> Welcome to MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 5340 to server version: 3.23.54 . Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br /> Run the following commands to create the database, &lt;code&gt;CREATE DATABASE &lt;database name&gt;;&lt;/code&gt; then, &lt;code&gt;GRANT ALL PRIVLEGES ON &lt;database name&gt;.* TO &quot;&lt;wordpress username&gt;&quot;@&quot;&lt;host name&gt;&quot;&lt;/code&gt; Replace wordpress username and host name with the desired names. Do the same when it asks for a password. <br /> <br /> To finish the creation of the database run these two commands &lt;code&gt;FLUSH PRIVILEGES;&lt;/code&gt; and &lt;code&gt;EXIT;&lt;/code&gt;then the MySQL monitor will personally say bye to you.<br /> <br /> ===Setting up the wp-config.php file===<br /> You can either create and edit the &lt;code&gt;wp-config.php&lt;/code&gt; file yourself, or you can skip this step and let WordPress try to do this itself when you run the installation script. (not recommended) <br /> <br /> Follow these instructions if you wish to edit the file manually. Navigate to your domain's home directory then copy the &lt;code&gt;wp-config-sample.php&lt;/code&gt;file and rename the copy to &lt;code&gt;wp-config.php&lt;/code&gt; You can do this using the &lt;code&gt;cp&lt;/code&gt; command within Linux, or running &lt;code&gt;sudo cp wp-config-sample.php wp-config.php&lt;/code&gt; in your domain's home directory. Edit it using &lt;code&gt;sudo vim wp-config.php&lt;/code&gt; press &lt;code&gt;i&lt;/code&gt; to enter insert mode and change the following values. &lt;blockquote&gt;'''DB_NAME''' use the name of your database&lt;/blockquote&gt;&lt;blockquote&gt;'''DB_USER''' use the username of your database&lt;/blockquote&gt;&lt;blockquote&gt;'''DB_PASSWORD''' use the password of your database&lt;/blockquote&gt;&lt;blockquote&gt;'''DB_HOST''' use the hostname you determined for your database, whish is usually &lt;code&gt;localhost&lt;/code&gt;&lt;/blockquote&gt;Then you must enter your secret key values. (good luck) To get your secret key values visit this website [https://api.wordpress.org/secret-key/1.1/salt/ here] then go down to where the website matches the file. Enter your 8 unique keys by hand, make sure each character matches exactly, and you use the correct key for the correct slot. ie. &lt;code&gt;AUTH_KEY&lt;/code&gt; goes with &lt;code&gt;AUTH_KEY&lt;/code&gt; etc. <br /> <br /> '''SAVE SAVE SAVE PLEASE''', you should also save while you are editing the file periodically. Save by pressing &lt;code&gt;esc&lt;/code&gt; then typing &lt;code&gt;:w&lt;/code&gt; and exit by pressing &lt;code&gt;esc&lt;/code&gt; and typing &lt;code&gt;:q&lt;/code&gt; , alternatively you can save and exit by pressing &lt;code&gt;esc&lt;/code&gt; and typing &lt;code&gt;:wq&lt;/code&gt;. <br /> <br /> ===Finishing Up===<br /> You might have to move all of your WordPress files out of the WordPress directory into your domain's home directory. Do this with the &lt;code&gt;mv&lt;/code&gt; command ie. &lt;code&gt;sudo mv wp-config.php /var/www/example.ms&lt;/code&gt;.<br /> <br /> Visit your webpage to finish the WordPress installation and to make a WordPress account. <br /> <br /> ====Links For Extra Explanations====<br /> [https://wordpress.org/support/article/how-to-install-wordpress/#step-3-set-up-wp-config-php Installing WordPress]<br /> <br /> [https://wordpress.org/support/article/creating-database-for-wordpress/ Creating a Database for WordPress]<br /> <br /> ==Management==<br /> WordPress was created with the user's experience in mind. The dashboard is very intuitive, and the community is large enough to have answers to most questions/problems. In order to manage a WordPress powered website, you need to use the admin dashboard. In order to get to it, go to the WordPress installation's root directory and then navigate to the &lt;code&gt;/wp-admin&lt;/code&gt; directory (i.e. website.com/wp-admin). From there, you can edit posts, the theme, pages, plugins, and more. If you don't know how to do something, Google it! The WordPress community has been around since 2003, so your question has most likely been asked and answered before.<br /> <br /> ===Logging In===<br /> In order to log into WordPress, go to website.com'''/wp-admin''' (replace website.com with your domain).<br /> [[File:W1.png|left|frameless|208x208px|screenshot of the login page]]<br /> <br /> [[File:W2.png|left|thumb|150x150px|the ''Users'' tab on the sidebar in the dashboard]]<br /> <br /> ===Creating Accounts===<br /> If you need to create an account, go to '''Users → Add New''' from the WordPress dashboard. From there, fill out all of the information for the new account and press the ''Add New User'' button.<br /> <br /> If you need to edit any of the users (change username, reset password, etc), navigate to '''Users → All Users''' and click on the one that you need to modify.<br /> <br /> ===Adding Menu Items===<br /> Before you can add an item to your primary menu, you need to have a new (or preexisting) page. If you need to create one, go to '''Pages → Add New''' and create it. Once it's created, navigate to '''Appearance → Menus''' and draw your attention to the ''Add Menu Items'' section. Find your new page in the list and click on the checkbox and click ''Add To Menu''.<br /> [[File:W3.png|left|thumb|204x204px|adding an item to the ''Menu structure'' section]]<br /> <br /> ===Editing Page Contents===<br /> lksjdfladsjf<br /> [[File:W4.png|left|thumb|what it should look like when trying to create a dropdown menu]]<br /> <br /> ===Adding/Modifying Themes===<br /> adfadfasdf<br /> <br /> ===Uploading Images===<br /> ldkfjalkdfj<br /> <br /> ==Troubleshooting==<br /> f after an installation you get prompted for FTP credentials, add the following line to the wp-config.php file in the directory that WordPress was installed <br /> define(“FS_METHOD”, “direct”);</div>

KWahl https://wiki.24pin.tech/index.php?title=WordPress&diff=1095 2020-12-31T21:11:47Z

<p>KWahl: Added a better explanation on how to install WordPress ps. stinky Tyler :P</p> <hr /> <div>==Introduction==<br /> [[File:Wp-admin.png|thumb|screenshot of the WordPress admin dashboard]]<br /> [https://wordpress.org/ WordPress] is a content management system (CMS) that is functions primarily serve our [http://24pin.tech/ homepage] to users that would like to get help or discover more about the program. It's a very powerful platform that grants administrators creative freedom over whatever they want on their website.<br /> <br /> ==Installation==<br /> The installation for WordPress is really simple. All you have to do is download the compressed file for the installation and extract it in the directory that you'd want to install it to. You can either download it from their [https://wordpress.org/download/ website here] or alternatively you can download it using &lt;code&gt;wget&lt;/code&gt;. The command would be &lt;code&gt;sudo wget &lt;nowiki&gt;https://wordpress.org/latest.tar.gz&lt;/nowiki&gt;&lt;/code&gt; on UNIX systems (if you're using aptitude for your package manager.) Once you've downloaded the file, run &lt;code&gt;sudo tar -xzvf latest.tar.gz&lt;/code&gt; to extract it.<br /> <br /> .<br /> <br /> Once you've downloaded and extracted the file, visit your web server to continue with the installation process. From here you must create a Database for WordPress, we use MySQL the instructions for creating a database within MySQL goes as follows. <br /> <br /> === Accessing MySQL ===<br /> First of all log onto your webserver. (Logan is 24PinTech's webserver)<br /> <br /> Once in the webserver and you have access to the command line use this command to go into the MySQL command prompt &lt;code&gt;mysql -u &lt;admin username&gt; -p&lt;/code&gt; then type in the password associated with your admin user. Upon success you should see a prompt that looks like such:<br /> Welcome to MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 5340 to server version: 3.23.54 . Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br /> Run the following commands to create the database, &lt;code&gt;CREATE DATABASE &lt;database name&gt;;&lt;/code&gt; then, &lt;code&gt;GRANT ALL PRIVLEGES ON &lt;database name&gt;.* TO &quot;&lt;wordpress username&gt;&quot;@&quot;&lt;host name&gt;&quot;&lt;/code&gt; Replace wordpress username and host name with the desired names. Do the same when it asks for a password. <br /> <br /> To finish the creation of the database run these two commands &lt;code&gt;FLUSH PRIVILEGES;&lt;/code&gt; and &lt;code&gt;EXIT&lt;/code&gt;then the MySQL monitor will personally say bye to you.<br /> <br /> === Setting up the wp-config.php file ===<br /> You can either create and edit the &lt;code&gt;wp-config.php&lt;/code&gt; file yourself, or you can skip this step and let WordPress try to do this itself when you run the installation script. (not recommended) <br /> <br /> Follow these instructions if you wish to edit the file manually. Navigate to your domain's home directory then copy the &lt;code&gt;wp-config-sample.php&lt;/code&gt;file and rename the copy to &lt;code&gt;wp-config.php&lt;/code&gt; You can do this using the &lt;code&gt;cp&lt;/code&gt; command within Linux, or running &lt;code&gt;sudo cp wp-config-sample.php wp-config.php&lt;/code&gt; in your domain's home directory. Edit it using &lt;code&gt;sudo vim wp-config.php&lt;/code&gt; press &lt;code&gt;i&lt;/code&gt; to enter insert mode and change the following values. &lt;blockquote&gt;'''DB_NAME''' use the name of your database&lt;/blockquote&gt;&lt;blockquote&gt;'''DB_USER''' use the username of your database&lt;/blockquote&gt;&lt;blockquote&gt;'''DB_PASSWORD''' use the password of your database&lt;/blockquote&gt;&lt;blockquote&gt;'''DB_HOST''' use the hostname you determined for your database, whish is usually &lt;code&gt;localhost&lt;/code&gt;&lt;/blockquote&gt;Then you must enter your secret key values. (good luck) To get your secret key values visit this website [https://api.wordpress.org/secret-key/1.1/salt/ here] then go down to where the website matches the file. Enter your 8 unique keys by hand, make sure each character matches exactly, and you use the correct key for the correct slot. ie. &lt;code&gt;AUTH_KEY&lt;/code&gt; goes with &lt;code&gt;AUTH_KEY&lt;/code&gt; etc. <br /> <br /> '''SAVE SAVE SAVE PLEASE''', you should also save while you are editing the file periodically. Save by pressing &lt;code&gt;esc&lt;/code&gt; then typing &lt;code&gt;:w&lt;/code&gt; and exit by pressing &lt;code&gt;esc&lt;/code&gt; and typing &lt;code&gt;:q&lt;/code&gt; , alternatively you can save and exit by pressing &lt;code&gt;esc&lt;/code&gt; and typing &lt;code&gt;:wq&lt;/code&gt;. <br /> <br /> === Finishing Up ===<br /> You might have to move all of your WordPress files out of the WordPress directory into your domain's home directory. Do this with the &lt;code&gt;mv&lt;/code&gt; command ie. &lt;code&gt;sudo mv wp-config.php /var/www/example.ms&lt;/code&gt;.<br /> <br /> Visit your webpage to finish the WordPress installation and to make a WordPress account. <br /> <br /> ==== Links For Extra Explanations ====<br /> [https://wordpress.org/support/article/how-to-install-wordpress/#step-3-set-up-wp-config-php Installing WordPress]<br /> <br /> [https://wordpress.org/support/article/creating-database-for-wordpress/ Creating a Database for WordPress]<br /> <br /> ==Management==<br /> WordPress was created with the user's experience in mind. The dashboard is very intuitive, and the community is large enough to have answers to most questions/problems. In order to manage a WordPress powered website, you need to use the admin dashboard. In order to get to it, go to the WordPress installation's root directory and then navigate to the &lt;code&gt;/wp-admin&lt;/code&gt; directory (i.e. website.com/wp-admin). From there, you can edit posts, the theme, pages, plugins, and more. If you don't know how to do something, Google it! The WordPress community has been around since 2003, so your question has most likely been asked and answered before.<br /> <br /> ===Logging In===<br /> In order to log into WordPress, go to website.com'''/wp-admin''' (replace website.com with your domain).<br /> [[File:W1.png|left|frameless|208x208px|screenshot of the login page]]<br /> <br /> [[File:W2.png|left|thumb|150x150px|the ''Users'' tab on the sidebar in the dashboard]]<br /> <br /> ===Creating Accounts===<br /> If you need to create an account, go to '''Users → Add New''' from the WordPress dashboard. From there, fill out all of the information for the new account and press the ''Add New User'' button.<br /> <br /> If you need to edit any of the users (change username, reset password, etc), navigate to '''Users → All Users''' and click on the one that you need to modify.<br /> <br /> ===Adding Menu Items===<br /> Before you can add an item to your primary menu, you need to have a new (or preexisting) page. If you need to create one, go to '''Pages → Add New''' and create it. Once it's created, navigate to '''Appearance → Menus''' and draw your attention to the ''Add Menu Items'' section. Find your new page in the list and click on the checkbox and click ''Add To Menu''.<br /> [[File:W3.png|left|thumb|204x204px|adding an item to the ''Menu structure'' section]]<br /> <br /> ===Editing Page Contents===<br /> lksjdfladsjf<br /> [[File:W4.png|left|thumb|what it should look like when trying to create a dropdown menu]]<br /> <br /> ===Adding/Modifying Themes===<br /> adfadfasdf<br /> <br /> ===Uploading Images===<br /> ldkfjalkdfj<br /> <br /> ==Troubleshooting==<br /> f after an installation you get prompted for FTP credentials, add the following line to the wp-config.php file in the directory that WordPress was installed <br /> define(“FS_METHOD”, “direct”);</div>

KWahl https://wiki.24pin.tech/index.php?title=Nginx&diff=1092 2020-12-31T18:40:34Z

<p>KWahl: fixed Tyler's very rare mistakes</p> <hr /> <div>==About==<br /> Nginx (pronounced engine-x) is web server which can also be used proxy, load balancer, mail proxy and HTTP cache. It's also a modern alternative to something like Apache, IIS, or Caddy.<br /> <br /> ==Prerequisites==<br /> An nginx installation should be pretty accessible regardless of your OS. This guide is specifically written for Ubuntu Server 18.04 LTS, but should work on any other type of Unix operating system. The setup that we're using is commonly referred to as a LEMP stack (Linux, nginx, MySQL, PHP.)<br /> <br /> *nginx/1.14.0 (Ubuntu)<br /> *PHP 7.2.10-0ubuntu0.18.04.1 (cli)<br /> *MySQL v14.14 Distribution 5.7.24<br /> <br /> If you've just installed a new operating system, you'll want to update your local package index by running &lt;code&gt;sudo apt-get update&lt;/code&gt;, and then add the Universe repository by running &lt;code&gt;sudo apt-add-repository universe&lt;/code&gt;.<br /> <br /> ==Installing nginx==<br /> To start, you're going to want to install nginx using the aptitude package manager. You can do this by running &lt;code&gt;sudo apt-get install nginx&lt;/code&gt;. Once you run that, you'll want to go through the configuration prompt that appears.<br /> <br /> .<br /> <br /> After nginx and its subsequent dependencies have finished installing, you'll want to let it through the firewall by running &lt;code&gt;sudo ufw allow 'Nginx HTTP'&lt;/code&gt;. Check what your current IP is by running &lt;code&gt;ifconfig&lt;/code&gt;, and then look for whatever interface looks correct. In this instance, the proper interface is &lt;code&gt;eth0&lt;/code&gt;.<br /> <br /> .<br /> <br /> [[File:Ifconfig-example.png|left|frame|an example of the results from ifconfig]]<br /> After running the command, the first indented line should say '''''inet''''' and then an IP address afterwards. Verify functionality of nginx by going to your web browser and typing &lt;code&gt;&lt;nowiki&gt;http://{ip}/&lt;/nowiki&gt;&lt;/code&gt; where &lt;code&gt;{ip}&lt;/code&gt; is what follows after '''''inet'''''.<br /> <br /> If the default nginx page displays, continue to the next section.<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> ==Installing MySQL==<br /> The process of installing MySQL is fairly similar to installing nginx, although MySQL does require a little bit of configuration before it will function properly. Start off by running &lt;code&gt;sudo apt-get install mysql-server&lt;/code&gt;, and then once it finishes run the setup script by typing &lt;code&gt;sudo mysql_secure_installation&lt;/code&gt;.<br /> <br /> .<br /> <br /> The first thing that the installations script will ask you is if you'd like to enable the &lt;code&gt;VALIDATE PASSWORD PLUGIN&lt;/code&gt;, but don't. If you don't care about why, then skip to the next paragraph, but if you do, keep reading. Essentially, the plugin throws errors if passwords don't meet specific criteria. This causes issues if you either a.) use weak passwords, or b.) install a package that automatically compiles and creates a default account with basic credentials. '''It is always good practice to use strong passwords for everything, and database credentials are no exception.'''<br /> <br /> .<br /> <br /> Say yes to the rest of the questions and use good judgement if it asks something that requires anything other than a Y/N input.<br /> <br /> ==Installing PHP==<br /> Again, installing PHP is very similar to two sections preceding this one. Start off by installing the &lt;code&gt;php-fpm&lt;/code&gt; and &lt;code&gt;php-mysql&lt;/code&gt; packages by running &lt;code&gt;sudo apt-get install php-fpm php-mysql&lt;/code&gt;. After it installs, you'll want to edit &lt;code&gt;php.ini&lt;/code&gt; by running &lt;code&gt;sudo vim /etc/php/7.2/fpm/php.ini&lt;/code&gt;.<br /> <br /> .<br /> <br /> '''''Note:''' If the file isn't found, check'' the directory path by using the &lt;code&gt;cd&lt;/code&gt; command and seeing where something doesn't exist.<br /> <br /> .<br /> <br /> If you're using Vim, type a &lt;code&gt;?&lt;/code&gt; and search for &lt;code&gt;cgi.fix_pathinfo&lt;/code&gt;. You should be taken to a line that's commented out and says &lt;code&gt;;cgi.fix_pathinfo=0&lt;/code&gt; or something similar. Press the &lt;code&gt;i&lt;/code&gt; key to start editing and remove the &lt;code&gt;;&lt;/code&gt; to uncomment it. If the variable is set to 1, change it to 0. Press the &lt;code&gt;escape&lt;/code&gt; key and type &lt;code&gt;:wq&lt;/code&gt; to save and quit your changes. If you didn't run Vim as a superuser (if you didn't run the command with &lt;code&gt;sudo&lt;/code&gt;), it will throw and error and the file won't save.<br /> <br /> .<br /> <br /> Once the file saves, run &lt;code&gt;sudo systemctl restart php7.2-fpm&lt;/code&gt; to restart PHP.<br /> <br /> ==Configuring nginx==<br /> The configuration for nginx is a little different compared to anything you might be used to. To start, there are two directories: &lt;code&gt;sites-available&lt;/code&gt; and &lt;code&gt;sites-enabled&lt;/code&gt;. The former directory actually contains the configuration files, while the latter contains symbolic links to the configuration files and enables them.<br /> <br /> .<br /> <br /> To start, lets say that we wanted to configure our nginx server to work with the domain &lt;code&gt;example.ms&lt;/code&gt;. First, we'd want to verify that the directory &lt;code&gt;/var/www/example.ms&lt;/code&gt; exists. Move to the &lt;code&gt;sites-available&lt;/code&gt; directory by entering the command &lt;code&gt;cd /etc/nginx/sites-available&lt;/code&gt;. Next, you'll want to create a new configuration file with the name of the domain. You can either by running &lt;code&gt;sudo touch example.ms &amp;&amp; sudo vim example.ms&lt;/code&gt; or simply by running &lt;code&gt;sudo vim example.ms&lt;/code&gt; since Vim creates the file if it doesn't exist. Again, press &lt;code&gt;i&lt;/code&gt; to edit the file. Once you're in edit mode, you'll want the contents to look something like this:&lt;pre&gt;<br /> server {<br /> listen 80;<br /> listen [::]:80;<br /> <br /> # this is a comment! you don't have to include this, but if you're not<br /> # going to be using a domain, then you can replace it with an IP<br /> server_name example.ms;<br /> <br /> root /var/www/example.ms;<br /> index index.php index.html index.htm;<br /> <br /> location = /favicon.io {<br /> log_not_found off;<br /> access_log off;<br /> }<br /> <br /> location = /robots.txt {<br /> allow all;<br /> log_not_found off;<br /> access_log off;<br /> }<br /> <br /> location / {<br /> try_files $uri $uri/ /index.php$args;<br /> }<br /> <br /> location ~ \.php$ {<br /> include snippets/fastcgi-php.conf;<br /> fastcgi_intercept_errors on;<br /> fastcgi_pass unix:/run/php/php7.2-fpm.sock;<br /> }<br /> <br /> location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {<br /> expires max;<br /> log_not_found off;<br /> }<br /> }<br /> &lt;/pre&gt;'''''Tip:''' You can periodically save your configuration file by pressing &lt;code&gt;escape&lt;/code&gt;, typing &lt;code&gt;:w&lt;/code&gt; , and then pressing &lt;code&gt;i&lt;/code&gt; again to edit the file.''<br /> <br /> ''.''<br /> <br /> Once you're completely done editing, save and quit the file by pressing the escape key and typing &lt;code&gt;:wq&lt;/code&gt;. Finally, you can check your configuration file for errors by running &lt;code&gt;sudo nginx -t&lt;/code&gt;. If there are any errors, refer back to your configuration file and see where you went wrong. In the event that nginx threw an error, review your configuration file and look for any missing &lt;code&gt;{&lt;/code&gt;, &lt;code&gt;}&lt;/code&gt;, or &lt;code&gt;;&lt;/code&gt;. Every line that doesn't have curly brackets should end in a semicolon, which is probably the issue. If that isn't, then refer to your favorite search engine and start researching.<br /> <br /> .<br /> <br /> If nothing went wrong, and your configuration file is completely free of errors, run &lt;code&gt;cd ../sites-enabled&lt;/code&gt; to move to the sites-enabled directory. Finally, to enable your website, run &lt;code&gt;sudo ln -s /etc/nginx/sites-available/example.ms ./&lt;/code&gt; to create the symbolic link to your configuration file, and then run &lt;code&gt;sudo systemctl restart nginx&lt;/code&gt; to restart nginx and make your changes go live.<br /> <br /> ==Verifying Functionality==<br /> Of course, you'll want to make sure that everything you just did actually works. Run &lt;code&gt;cd /var/www/example.ms &amp;&amp; sudo vim info.php&lt;/code&gt; to move to your websites home directory and create the file &lt;code&gt;info.php&lt;/code&gt;. Inside of the file, type the following:&lt;pre&gt;<br /> &lt;?php<br /> phpinfo();<br /> ?&gt;<br /> &lt;/pre&gt;... and then save and quit the file by pressing &lt;code&gt;escape&lt;/code&gt; and typing &lt;code&gt;:wq&lt;/code&gt;. Now, go to &lt;code&gt;&lt;nowiki&gt;http://example.ms/info.php&lt;/nowiki&gt;&lt;/code&gt;. If you didn't configure the nameservers for your domain to point to your new nginx server, then just replace the domain name with the IP of the server (refer to the &lt;code&gt;ifconfig&lt;/code&gt; part of the [[Nginx#Installing nginx|Installing nginx]] section if you don't know how.)<br /> <br /> .<br /> <br /> If everything worked properly, you should see a PHP information page with a bunch of library authors and enabled modules. If it doesn't, research!<br /> <br /> ==Subdomains==<br /> Adding subdomains is really easy and doesn't require a lot of effort. You'll just need to remember the general process from the [[Nginx#Configuring nginx|Configuring nginx]] section.<br /> <br /> .<br /> <br /> To start, navigate to the &lt;code&gt;sites-available&lt;/code&gt; directory by running &lt;code&gt;cd /etc/nginx/sites-available&lt;/code&gt;. Then, you can either copy a pre-existing configuration by running &lt;code&gt;sudo cp example.ms subdomain.example.ms&lt;/code&gt; or creating a new file by running &lt;code&gt;sudo vim subdomain.example.ms&lt;/code&gt;. If you copied it, edit the file by running &lt;code&gt;sudo vim subdomain.example.ms&lt;/code&gt;.<br /> <br /> ===What needs to be changed===<br /> The only important things that need to be changed are the &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;server_name&lt;/code&gt; variables. Press &lt;code&gt;i&lt;/code&gt; to start editing the file in Vim, and then find where the variables are located. Change the &lt;code&gt;root&lt;/code&gt; variable to an updated path where the contents for the subdomain can be found. Generally, good practice for this is to create a new folder in the primary domains path with the name of the subdomain. So, if we were trying to create &lt;code&gt;subdomain.example.ms&lt;/code&gt;, we'd create a new folder by running the command &lt;code&gt;sudo mkdir /var/www/example.ms/subdomain&lt;/code&gt;. Then, we'd modify our &lt;code&gt;root&lt;/code&gt; variable to look something like this:&lt;pre&gt;<br /> # before<br /> root /var/www/example.ms;<br /> <br /> # after<br /> root /var/www/example.ms/subdomain;<br /> &lt;/pre&gt;The &lt;code&gt;server_name&lt;/code&gt; variable is just as simple. Just add the subdomain prefix to the beginning of your domain:<br /> # before<br /> server_name example.ms;<br /> <br /> # after<br /> server_name subdomain.example.ms;<br /> Once you've made the proper changes, save and quit the file by pressing &lt;code&gt;escape&lt;/code&gt; and typing &lt;code&gt;:wq&lt;/code&gt;. Then, run &lt;code&gt;cd ../sites-enabled &amp;&amp; sudo ln -s /etc/nginx/sites-available/subdomain.example.ms ./&lt;/code&gt; and restart nginx by running &lt;code&gt;sudo systemctl restart nginx&lt;/code&gt;.<br /> <br /> ==Adding other domains (that aren't subdomains)==<br /> The process is exactly the same as adding a subdomain, except instead of adding a prefix the value of &lt;code&gt;server_name&lt;/code&gt; you'll just completely change the domain. Again, don't forget to create the symbolic link to the configuration file and ''especially'' don't forget to restart nginx after saving the config/creating the symbolic link. When you're creating the folder to contain the contents for the server, create a new folder that has the name of the domain. So, for instance, if I was creating example2.ms, I'd run &lt;code&gt;sudo mkdir /var/www/example2.ms&lt;/code&gt;.<br /> <br /> ==Conclusion==<br /> By now, your nginx server should be up and fully operational. As always, if you're having any issues please STFW before you ask people for advice!<br /> <br /> .<br /> <br /> Thank you,<br /> <br /> - Tyler</div>

KWahl https://wiki.24pin.tech/index.php?title=DHCP&diff=1072 2020-02-20T20:09:05Z

<p>KWahl: added freyrweb</p> <hr /> <div>=Our DHCP Setup=<br /> <br /> 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.<br /> <br /> ==Address Pool==<br /> <br /> 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. The following chart represents our current setup...<br /> <br /> ===Hostname IP address===<br /> Gateway 10.21.25.1<br /> <br /> Surtr 10.21.25.2<br /> <br /> Loki (PDC) 10.21.25.3<br /> <br /> Fog 10.21.25.4<br /> <br /> Freyr 10.21.25.5<br /> <br /> MacMini 10.21.25.6<br /> <br /> MediaXserve 10.21.25.7<br /> <br /> Heimdall (ESXI VM's) 10.21.25.8<br /> <br /> FreyrWeb (VM on Freyr) 10.21.25.9<br /> <br /> Logan (BDC) 10.21.25.10<br /> <br /> LoganWeb (VM on Logan) 10.21.25.11<br /> <br /> Macmini Backup 10.21.25.15<br /> <br /> NAS 24PinTech 10.21.25.16<br /> <br /> Perle IOLAN Console Serv 10.21.25.17<br /> <br /> Opengear 10.21.25.18<br /> <br /> ==Address Leases==<br /> <br /> These are all of the current DHCP releases that the DHCP servers have put out that are active.<br /> <br /> ==Reservations==<br /> <br /> 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.<br /> <br /> ==Scope Options==<br /> <br /> This is where we configure our DHCP options. To configure options that we don't already have set, right click &quot;Scope Options&quot; and click on &quot;Configure Options&quot; and configure what you need. Below are the options we already have set:<br /> <br /> [[File:DHCP_Options.PNG]]<br /> <br /> 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]].<br /> <br /> ==Policies==<br /> <br /> These are settings that are applied to certain devices based off of rules defined by the policy, like IP address range, vendor, etc.<br /> <br /> 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.<br /> <br /> ==Server Options==<br /> <br /> This is where settings can be configured globally across the whole DHCP server. We have none of these currently configured.<br /> <br /> ==Policies (Not within scope)==<br /> <br /> Same as above policies but global, we do not have this configured.<br /> <br /> ==Filters==<br /> <br /> This allows you to block or allow certain MAC addresses from receiving DHCP addresses.</div>

KWahl https://wiki.24pin.tech/index.php?title=Welcome_to_the_24PinTech_Wiki!&diff=1042 2020-01-10T20:13:22Z

<p>KWahl: updated the &quot;Social Media Stuff&quot;</p> <hr /> <div>[[File:Logo-extended.jpg|733x188px|center]]<br /> <br /> __NOTOC__<br /> <br /> ==Who are we?==<br /> The 24PinTech team consists of a group of students all currently attending Maricopa High School. We are all extremely enthusiastic about all things technological based, which prompted us to create the company. The company will allow students to be able to gain experience in Information Technology, thus preparing them for future careers within the technology industry. As part of the training program, employees will be certified in various courses, including but not limited to, the A+ Certificate, CCNA certification and multiple TestOut Course certifications. We also partner with [https://www.azstrut.org/ AZStRUT] to help them repair old computers which will be given back out, giving employees great hands-on hardware repair and software diagnosis experience.<br /> <br /> [https://youtu.be/LWSuHAxm-n8 24PinTech Commercial]<br /> <br /> ==What do we do?==<br /> Computer Service Technicians assets, repair, and maintain computers for companies, businesses, or consumers.<br /> <br /> ==What are our obligations?==<br /> Service Technicians are responsible for installing and repairing internal and external components, implementing proper security settings and programs, installing operating systems and software, making a system’s performance efficient and smooth, and helping customers better understand how to maintain their system(s).<br /> <br /> ==What are our skills?==<br /> <br /> *'''Analytical Skills:''' Computer repair technicians need to be able to solve issues that might not have a clear solution. Being able to experiment and use trial and error is important.<br /> *'''Troubleshooting:''' Computer repair technicians must be able to diagnose, repair and test computer problems as they arise<br /> *'''Communication:''' Computer repair technicians have to ask questions and listen to customers in order to find out the issue, explain the problem in a clear and understandable way, and give them options for repair or replacement.<br /> *'''IT Skills:''' Using diagnostic tools to assess or monitor computer systems requires knowledge of IT skills.<br /> *'''Dexterity:''' Computer repair technicians use their hands to manipulate objects within the computer.<br /> <br /> ==Social Media Stuff!==<br /> <br /> *'''Website:''' [http://24pin.tech/ 24pin.tech]<br /> *'''Twitter:''' [https://twitter.com/24pinTech?s=20 @24PinTech]<br /> *'''Instagram:''' [https://www.instagram.com/24pin.tech/ @24pintech]</div>

KWahl https://wiki.24pin.tech/index.php?title=Migrating_Spiceworks_(Retired)&diff=1031 2019-12-11T18:30:58Z

<p>KWahl: Added captions to the pictures.</p> <hr /> <div>==Introduction==<br /> Spiceworks is the site at which 24PinTech can access all work orders that have been assigned to a technician. Once a technician is logged in, they can view, edit, and comment about their work order as well as complete any documentation that is affiliated with the work order. For whatever reason Spiceworks may need to get migrated to another server. <br /> <br /> ==Prep==<br /> Make sure you have access to the following utilities.<br /> <br /> *A New Server<br /> *A Flash Drive<br /> *A Spiceworks Installation usually found at, &lt;nowiki&gt;https://www.spiceworks.com/download&lt;/nowiki&gt; (note this site will immediately start downloading the Spiceworks Installer)<br /> <br /> ==Backups==<br /> [[File:Migrating Wiki 1.png|left|thumb|387x387px|Navigate to the Spiceworks Settings drop-down menu, and select Global settings.]]<br /> In the old server with your current Spicework installation, you will need to sign in using your account and navigate to the settings tab, which would like this (red circle)...<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> [[File:Migrating Wiki 2.png|left|thumb|390x390px|Highlighting the Edit option to change where the Back-up is saved.]]<br /> Then click on ‘Global Settings’ in the drop down menu. Open up the ‘Backup Configuration’ menu. If you haven't already, insert your Flash Drive into the server. Find the ‘Backup Locations’ menu and change the current path to a path leading to your Flash Drive. Once selected click ‘Backup Now’ at the bottom. (red circle)<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> Eject the Flash Drive and head over to your new server.<br /> <br /> ==Installing Spiceworks and Transplanting the Data==<br /> Once on the new server use the link provided to download the Spiceworks Installer. Make sure the ports mimic the ports of your old server. When given the option Install NMAP and WinPCap through Spiceworks. Once done run the Installer, but '''MAKE SURE''' you '''DO NOT''' start Spiceworks itself, just have it installed. Make sure Spiceworks is completely stopped by checking to see if all the services are stopped. Below are the services. <br /> &gt; spiceworks.exe <br /> <br /> &gt; spicetray.exe  <br /> <br /> &gt; spiceworks-finder.exe  <br /> <br /> &gt; spiceworks-httpd.exe  <br /> <br /> &gt; spiceworks-httpd.exe<br /> [[File:Migrating Wiki 3.png|left|thumb|340x340px|Highlighting the Folders that need to be transferred.]]<br /> If they are all stopped then you can continue with the migration. Find the installation files and open them in File Explorer. Delete the ‘data’ and ‘db’ folders, make sure it is '''ONLY''' these folders that get deleted. <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> Now access the Backup files on your Flash Drive and extract them right into the Spiceworks Installation folder. If everything went well new ‘data’ and ‘db’ folders should appear. <br /> <br /> ==Starting Spiceworks==<br /> [[File:Migrating Wiki 4.png|left|thumb|342x342px|Highlighting the Application file needed to properly start Spiceworks.]]<br /> Navigate to the application titled ‘spiceworks_desktop’ and run it. (red circle)<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> [[File:Migrating Wiki 5.png|left|thumb|340x340px|The final login-screen for Spiceworks.]]<br /> <br /> Spiceworks should now say something like ‘'''''HEATING UP'''''’ or something rather. This might take a few minutes, so just wait. Once it is done ‘'''''HEATING UP'''''’ it should load into a login screen, shown to the left. <br /> <br /> If everything went swimmingly you should be able to login using the same credentials from your old Spiceworks server. <br /> <br /> ==='''''Congrats!'''''===<br /> Now you just need to disable the Windows Firewall, and add it onto the domain, which is CiscoACA.local for us. Now just test functionality by copying the same URL and entering it on another system, and your good. <br /> <br /> -Your Welcome, Koby</div>

KWahl https://wiki.24pin.tech/index.php?title=NIC_Teaming&diff=1029 2019-12-11T18:25:20Z

<p>KWahl: added captions to the pictures.</p> <hr /> <div>==Introduction==<br /> NIC Teaming is using two or more Ethernet ports simultaneously in a team as a ambiguate. An ambiguate is a sort of situation in which something is getting labeled as ambiguous, a NIC Team is making the wired connection to the internet ambiguous for security reasons. This is very useful for servers where constant web services are required, just in case one fails another one is already set up. <br /> <br /> ==Creating or Editing a NIC Team==<br /> [[File:Snip -1.png|thumb|Server Manager Window, the NIC Teaming option is available here.]]<br /> In Windows Server open the “Server Manager” window and navigate to the “Local Server” category. Look for the “NIC Teaming” option and it will either say “Disabled” or “Enabled” click on this to open the “NIC Teaming” window.<br /> <br /> ==='''    Editing'''===<br /> Click on an existing NIC Team and edit the options to fit your needs, see '''Options and What to Use''' heading. <br /> <br /> ===    '''Creating a New Team'''===<br /> Click on the “Tasks” drop-down menu next to the Teams category. Select the “New Team” option, this will open a new window. The available Ethernet Adapters will be shown on the bottom left corner. Make sure all of them are connected to a router and have connectivity.<br /> <br /> Select the Ethernet Adapters you would like to use, make sure you select two or more for an effective NIC Team. Once selected give the team an appropriate name and then select the appropriate options for the team under the Additional Properties tab. See '''Options and What to Use''' for help on these options. Once all are set, press “OK” and verify connectivity. <br /> <br /> ===    '''Verifying Connectivity'''===<br /> [[File:Snip -2.png|thumb|Control Panel window showing the configured NIC Team for verifying connectivity.]]<br /> Navigate to Control Panel, Then click on “Network and Internet”, then “Networking and Sharing Center”, then next to Connections click on “Ethernet” or Hopefully the name assigned to your NIC Team will show up. If the name of your NIC Team shows up then connectivity is established. If not click on it and a “Properties” window should pop up. Use this window to verify connectivity, if not plausible do basic networking troubleshooting for the NIC Team.<br /> <br /> ==Options and What to Use==<br /> <br /> ==='''Teaming Mode'''===<br /> Two available options, Switch Dependent and Switch Independent. <br /> <br /> With Switch Independent mode, the switch or switches to which the NIC Team members are connected are unaware of the presence of the NIC team and do not determine how to distribute network traffic to NIC Team members - instead, the NIC Team distributes inbound network traffic across the NIC Team members. <br /> <br /> With Switch Dependent modes, the switch to which the NIC Team members are connected determines how to distribute the inbound network traffic among the NIC Team members. The switch has complete independence to determine how to distribute the network traffic across the NIC Team members.<br /> <br /> ==='''Load Balancing Mode'''===<br /> Three Available options, Address Hash, Hyper-V Port, and Dynamic.<br /> <br /> With Address Hash, this mode creates a hash based on address components of the packet, which then get assigned to one of the available adapters. Usually, this mechanism alone is sufficient to create a reasonable balance across the available adapters. The TCP ports hash creates the most granular distribution of traffic streams, resulting in smaller streams that can be independently moved between NIC team members. However, you cannot use the TCP ports hash for traffic that is not TCP or UDP-based, or where the TCP and UDP ports are hidden from the stack, such as with IPsec-protected traffic. In these cases, the hash automatically uses the IP address hash or, if the traffic is not IP traffic, the MAC address hash is used.<br /> <br /> With Hyper-V Port, NIC Teams configured on Hyper-V hosts give VMs independent MAC addresses. The VMs MAC address or the VM ported connected to the Hyper-V switch, can be used to divide network traffic between NIC Team members. You cannot configure NIC Teams that you create within VMs with the Hyper-V Port load balancing mode. Instead, use the Address Hash mode. Because the adjacent switch always sees a particular MAC address on one port, the switch distributes the ingress load (the traffic from the switch to the host) on multiple links based on the destination MAC (VM MAC) address. This is particularly useful when Virtual Machine Queues (VMQs) are used because a queue can be placed on the specific NIC where the traffic is expected to arrive. However, if the host has only a few VMs, this mode might not be granular enough to achieve a well-balanced distribution. This mode will also always limit a single VM (i.e., the traffic from a single switch port) to the bandwidth that is available on a single interface. NIC Teaming uses the Hyper-V Virtual Switch Port as the identifier instead of using the source MAC address because, in some instances, a VM might be configured with more than one MAC address on a switch port. <br /> <br /> With Dynamic, outbound loads are distributed based on a hash of the TCP ports and IP addresses. Dynamic mode also rebalances loads in real-time so that a given outbound flow may move back and forth between team members. Inbound loads, on the other hand, get distributed the same way as Hyper-V Port. In a nutshell, Dynamic mode utilizes the best aspects of both Address Hash and Hyper-V Port and is the highest performing load balancing mode. When you use Switch Independent mode with Dynamic distribution, the network traffic load is distributed based on the TCP Ports address hash as modified by the Dynamic load balancing algorithm. The Dynamic load balancing algorithm redistributes flows to optimize team member bandwidth utilization so that individual flow transmissions can move from one active team member to another. The algorithm takes into account the small possibility that redistributing traffic could cause out-of-order delivery of packets, so it takes steps to minimize that possibility.<br /> <br /> ==='''Standby Adapter'''===<br /> None or a certain selection based on the NIC Adapters selected. <br /> <br /> Just simply select a standby(s) and then proceed with the rest of the Options. No standby has to selected, but it is recommended if you have extra Ethernet Adapters available.<br /> <br /> If you have a two-NIC team and you choose to configure one NIC as a Standby adapter, you lose the bandwidth aggregation advantages that exist with two active NICs. You do not need to designate a Standby Adapter to achieve fault tolerance; fault tolerance is always present whenever there are at least two network adapters in a NIC Team.<br /> <br /> ==='''Primary Team Interface'''===<br /> The options are a Default setting, or either a Custom VLAN. <br /> <br /> If you are using a VLAN then select Custom VLAN and input the VLAN number.<br /> <br /> ==Citations==<br /> &lt;blockquote&gt;https://docs.microsoft.com/en-us/windows-server/networking/technologies/nic-teaming/nic-teaming&lt;/blockquote&gt;</div>

KWahl https://wiki.24pin.tech/index.php?title=NIC_Teaming&diff=1024 2019-12-10T19:49:01Z

<p>KWahl: Added definition for ambiguate.</p> <hr /> <div>==Introduction==<br /> NIC Teaming is using two or more Ethernet ports simultaneously in a team as a ambiguate. An ambiguate is a sort of situation in which something is getting labeled as ambiguous, a NIC Team is making the wired connection to the internet ambiguous for security reasons. This is very useful for servers where constant web services are required, just in case one fails another one is already set up. <br /> <br /> ==Creating or Editing a NIC Team==<br /> [[File:Snip -1.png|thumb]]<br /> In Windows Server open the “Server Manager” window and navigate to the “Local Server” category. Look for the “NIC Teaming” option and it will either say “Disabled” or “Enabled” click on this to open the “NIC Teaming” window.<br /> <br /> ==='''    Editing'''===<br /> Click on an existing NIC Team and edit the options to fit your needs, see '''Options and What to Use''' heading. <br /> <br /> ===    '''Creating a New Team'''===<br /> Click on the “Tasks” drop-down menu next to the Teams category. Select the “New Team” option, this will open a new window. The available Ethernet Adapters will be shown on the bottom left corner. Make sure all of them are connected to a router and have connectivity.<br /> <br /> Select the Ethernet Adapters you would like to use, make sure you select two or more for an effective NIC Team. Once selected give the team an appropriate name and then select the appropriate options for the team under the Additional Properties tab. See '''Options and What to Use''' for help on these options. Once all are set, press “OK” and verify connectivity. <br /> <br /> ===    '''Verifying Connectivity'''===<br /> [[File:Snip -2.png|thumb]]<br /> Navigate to Control Panel, Then click on “Network and Internet”, then “Networking and Sharing Center”, then next to Connections click on “Ethernet” or Hopefully the name assigned to your NIC Team will show up. If the name of your NIC Team shows up then connectivity is established. If not click on it and a “Properties” window should pop up. Use this window to verify connectivity, if not plausible do basic networking troubleshooting for the NIC Team.<br /> <br /> ==Options and What to Use==<br /> <br /> ==='''Teaming Mode'''===<br /> Two available options, Switch Dependent and Switch Independent. <br /> <br /> With Switch Independent mode, the switch or switches to which the NIC Team members are connected are unaware of the presence of the NIC team and do not determine how to distribute network traffic to NIC Team members - instead, the NIC Team distributes inbound network traffic across the NIC Team members. <br /> <br /> With Switch Dependent modes, the switch to which the NIC Team members are connected determines how to distribute the inbound network traffic among the NIC Team members. The switch has complete independence to determine how to distribute the network traffic across the NIC Team members.<br /> <br /> ==='''Load Balancing Mode'''===<br /> Three Available options, Address Hash, Hyper-V Port, and Dynamic.<br /> <br /> With Address Hash, this mode creates a hash based on address components of the packet, which then get assigned to one of the available adapters. Usually, this mechanism alone is sufficient to create a reasonable balance across the available adapters. The TCP ports hash creates the most granular distribution of traffic streams, resulting in smaller streams that can be independently moved between NIC team members. However, you cannot use the TCP ports hash for traffic that is not TCP or UDP-based, or where the TCP and UDP ports are hidden from the stack, such as with IPsec-protected traffic. In these cases, the hash automatically uses the IP address hash or, if the traffic is not IP traffic, the MAC address hash is used.<br /> <br /> With Hyper-V Port, NIC Teams configured on Hyper-V hosts give VMs independent MAC addresses. The VMs MAC address or the VM ported connected to the Hyper-V switch, can be used to divide network traffic between NIC Team members. You cannot configure NIC Teams that you create within VMs with the Hyper-V Port load balancing mode. Instead, use the Address Hash mode. Because the adjacent switch always sees a particular MAC address on one port, the switch distributes the ingress load (the traffic from the switch to the host) on multiple links based on the destination MAC (VM MAC) address. This is particularly useful when Virtual Machine Queues (VMQs) are used because a queue can be placed on the specific NIC where the traffic is expected to arrive. However, if the host has only a few VMs, this mode might not be granular enough to achieve a well-balanced distribution. This mode will also always limit a single VM (i.e., the traffic from a single switch port) to the bandwidth that is available on a single interface. NIC Teaming uses the Hyper-V Virtual Switch Port as the identifier instead of using the source MAC address because, in some instances, a VM might be configured with more than one MAC address on a switch port. <br /> <br /> With Dynamic, outbound loads are distributed based on a hash of the TCP ports and IP addresses. Dynamic mode also rebalances loads in real-time so that a given outbound flow may move back and forth between team members. Inbound loads, on the other hand, get distributed the same way as Hyper-V Port. In a nutshell, Dynamic mode utilizes the best aspects of both Address Hash and Hyper-V Port and is the highest performing load balancing mode. When you use Switch Independent mode with Dynamic distribution, the network traffic load is distributed based on the TCP Ports address hash as modified by the Dynamic load balancing algorithm. The Dynamic load balancing algorithm redistributes flows to optimize team member bandwidth utilization so that individual flow transmissions can move from one active team member to another. The algorithm takes into account the small possibility that redistributing traffic could cause out-of-order delivery of packets, so it takes steps to minimize that possibility.<br /> <br /> ==='''Standby Adapter'''===<br /> None or a certain selection based on the NIC Adapters selected. <br /> <br /> Just simply select a standby(s) and then proceed with the rest of the Options. No standby has to selected, but it is recommended if you have extra Ethernet Adapters available.<br /> <br /> If you have a two-NIC team and you choose to configure one NIC as a Standby adapter, you lose the bandwidth aggregation advantages that exist with two active NICs. You do not need to designate a Standby Adapter to achieve fault tolerance; fault tolerance is always present whenever there are at least two network adapters in a NIC Team.<br /> <br /> ==='''Primary Team Interface'''===<br /> The options are a Default setting, or either a Custom VLAN. <br /> <br /> If you are using a VLAN then select Custom VLAN and input the VLAN number.<br /> <br /> ==Citations==<br /> &lt;blockquote&gt;https://docs.microsoft.com/en-us/windows-server/networking/technologies/nic-teaming/nic-teaming&lt;/blockquote&gt;</div>

KWahl https://wiki.24pin.tech/index.php?title=NIC_Teaming&diff=1023 2019-12-10T19:44:26Z

<p>KWahl: Added Link for citations.</p> <hr /> <div>==Introduction==<br /> NIC Teaming is using two or more Ethernet ports simultaneously in a team as a ambiguate. This is very useful for servers where constant web services are required, just in case one fails another one is already set up. <br /> <br /> ==Creating or Editing a NIC Team==<br /> [[File:Snip -1.png|thumb]]<br /> In Windows Server open the “Server Manager” window and navigate to the “Local Server” category. Look for the “NIC Teaming” option and it will either say “Disabled” or “Enabled” click on this to open the “NIC Teaming” window.<br /> <br /> ==='''    Editing'''===<br /> Click on an existing NIC Team and edit the options to fit your needs, see '''Options and What to Use''' heading. <br /> <br /> ===    '''Creating a New Team'''===<br /> Click on the “Tasks” drop-down menu next to the Teams category. Select the “New Team” option, this will open a new window. The available Ethernet Adapters will be shown on the bottom left corner. Make sure all of them are connected to a router and have connectivity.<br /> <br /> Select the Ethernet Adapters you would like to use, make sure you select two or more for an effective NIC Team. Once selected give the team an appropriate name and then select the appropriate options for the team under the Additional Properties tab. See '''Options and What to Use''' for help on these options. Once all are set, press “OK” and verify connectivity. <br /> <br /> ===    '''Verifying Connectivity'''===<br /> [[File:Snip -2.png|thumb]]<br /> Navigate to Control Panel, Then click on “Network and Internet”, then “Networking and Sharing Center”, then next to Connections click on “Ethernet” or Hopefully the name assigned to your NIC Team will show up. If the name of your NIC Team shows up then connectivity is established. If not click on it and a “Properties” window should pop up. Use this window to verify connectivity, if not plausible do basic networking troubleshooting for the NIC Team.<br /> <br /> ==Options and What to Use==<br /> <br /> ==='''Teaming Mode'''===<br /> Two available options, Switch Dependent and Switch Independent. <br /> <br /> With Switch Independent mode, the switch or switches to which the NIC Team members are connected are unaware of the presence of the NIC team and do not determine how to distribute network traffic to NIC Team members - instead, the NIC Team distributes inbound network traffic across the NIC Team members. <br /> <br /> With Switch Dependent modes, the switch to which the NIC Team members are connected determines how to distribute the inbound network traffic among the NIC Team members. The switch has complete independence to determine how to distribute the network traffic across the NIC Team members.<br /> <br /> ==='''Load Balancing Mode'''===<br /> Three Available options, Address Hash, Hyper-V Port, and Dynamic.<br /> <br /> With Address Hash, this mode creates a hash based on address components of the packet, which then get assigned to one of the available adapters. Usually, this mechanism alone is sufficient to create a reasonable balance across the available adapters. The TCP ports hash creates the most granular distribution of traffic streams, resulting in smaller streams that can be independently moved between NIC team members. However, you cannot use the TCP ports hash for traffic that is not TCP or UDP-based, or where the TCP and UDP ports are hidden from the stack, such as with IPsec-protected traffic. In these cases, the hash automatically uses the IP address hash or, if the traffic is not IP traffic, the MAC address hash is used.<br /> <br /> With Hyper-V Port, NIC Teams configured on Hyper-V hosts give VMs independent MAC addresses. The VMs MAC address or the VM ported connected to the Hyper-V switch, can be used to divide network traffic between NIC Team members. You cannot configure NIC Teams that you create within VMs with the Hyper-V Port load balancing mode. Instead, use the Address Hash mode. Because the adjacent switch always sees a particular MAC address on one port, the switch distributes the ingress load (the traffic from the switch to the host) on multiple links based on the destination MAC (VM MAC) address. This is particularly useful when Virtual Machine Queues (VMQs) are used because a queue can be placed on the specific NIC where the traffic is expected to arrive. However, if the host has only a few VMs, this mode might not be granular enough to achieve a well-balanced distribution. This mode will also always limit a single VM (i.e., the traffic from a single switch port) to the bandwidth that is available on a single interface. NIC Teaming uses the Hyper-V Virtual Switch Port as the identifier instead of using the source MAC address because, in some instances, a VM might be configured with more than one MAC address on a switch port. <br /> <br /> With Dynamic, outbound loads are distributed based on a hash of the TCP ports and IP addresses. Dynamic mode also rebalances loads in real-time so that a given outbound flow may move back and forth between team members. Inbound loads, on the other hand, get distributed the same way as Hyper-V Port. In a nutshell, Dynamic mode utilizes the best aspects of both Address Hash and Hyper-V Port and is the highest performing load balancing mode. When you use Switch Independent mode with Dynamic distribution, the network traffic load is distributed based on the TCP Ports address hash as modified by the Dynamic load balancing algorithm. The Dynamic load balancing algorithm redistributes flows to optimize team member bandwidth utilization so that individual flow transmissions can move from one active team member to another. The algorithm takes into account the small possibility that redistributing traffic could cause out-of-order delivery of packets, so it takes steps to minimize that possibility.<br /> <br /> ==='''Standby Adapter'''===<br /> None or a certain selection based on the NIC Adapters selected. <br /> <br /> Just simply select a standby(s) and then proceed with the rest of the Options. No standby has to selected, but it is recommended if you have extra Ethernet Adapters available.<br /> <br /> If you have a two-NIC team and you choose to configure one NIC as a Standby adapter, you lose the bandwidth aggregation advantages that exist with two active NICs. You do not need to designate a Standby Adapter to achieve fault tolerance; fault tolerance is always present whenever there are at least two network adapters in a NIC Team.<br /> <br /> ==='''Primary Team Interface'''===<br /> The options are a Default setting, or either a Custom VLAN. <br /> <br /> If you are using a VLAN then select Custom VLAN and input the VLAN number.<br /> <br /> == Citations ==<br /> &lt;blockquote&gt;https://docs.microsoft.com/en-us/windows-server/networking/technologies/nic-teaming/nic-teaming&lt;/blockquote&gt;</div>

KWahl https://wiki.24pin.tech/index.php?title=NIC_Teaming&diff=1022 2019-12-09T20:27:17Z

<p>KWahl: Created the NIC Teaming documentation.</p> <hr /> <div>== Introduction ==<br /> NIC Teaming is using two or more Ethernet ports simultaneously in a team as a ambiguate. This is very useful for servers where constant web services are required, just in case one fails another one is already set up. <br /> <br /> == Creating or Editing a NIC Team ==<br /> [[File:Snip -1.png|thumb]]<br /> In Windows Server open the “Server Manager” window and navigate to the “Local Server” category. Look for the “NIC Teaming” option and it will either say “Disabled” or “Enabled” click on this to open the “NIC Teaming” window.<br /> <br /> === '''    Editing''' ===<br /> Click on an existing NIC Team and edit the options to fit your needs, see '''Options and What to Use''' heading. <br /> <br /> ===    '''Creating a New Team''' ===<br /> Click on the “Tasks” drop-down menu next to the Teams category. Select the “New Team” option, this will open a new window. The available Ethernet Adapters will be shown on the bottom left corner. Make sure all of them are connected to a router and have connectivity.<br /> <br /> Select the Ethernet Adapters you would like to use, make sure you select two or more for an effective NIC Team. Once selected give the team an appropriate name and then select the appropriate options for the team under the Additional Properties tab. See '''Options and What to Use''' for help on these options. Once all are set, press “OK” and verify connectivity. <br /> <br /> ===    '''Verifying Connectivity''' ===<br /> [[File:Snip -2.png|thumb]]<br /> Navigate to Control Panel, Then click on “Network and Internet”, then “Networking and Sharing Center”, then next to Connections click on “Ethernet” or Hopefully the name assigned to your NIC Team will show up. If the name of your NIC Team shows up then connectivity is established. If not click on it and a “Properties” window should pop up. Use this window to verify connectivity, if not plausible do basic networking troubleshooting for the NIC Team.<br /> <br /> == Options and What to Use ==<br /> <br /> === '''Teaming Mode''' ===<br /> Two available options, Switch Dependent and Switch Independent. <br /> <br /> With Switch Independent mode, the switch or switches to which the NIC Team members are connected are unaware of the presence of the NIC team and do not determine how to distribute network traffic to NIC Team members - instead, the NIC Team distributes inbound network traffic across the NIC Team members. <br /> <br /> With Switch Dependent modes, the switch to which the NIC Team members are connected determines how to distribute the inbound network traffic among the NIC Team members. The switch has complete independence to determine how to distribute the network traffic across the NIC Team members.<br /> <br /> === '''Load Balancing Mode''' ===<br /> Three Available options, Address Hash, Hyper-V Port, and Dynamic.<br /> <br /> With Address Hash, this mode creates a hash based on address components of the packet, which then get assigned to one of the available adapters. Usually, this mechanism alone is sufficient to create a reasonable balance across the available adapters. The TCP ports hash creates the most granular distribution of traffic streams, resulting in smaller streams that can be independently moved between NIC team members. However, you cannot use the TCP ports hash for traffic that is not TCP or UDP-based, or where the TCP and UDP ports are hidden from the stack, such as with IPsec-protected traffic. In these cases, the hash automatically uses the IP address hash or, if the traffic is not IP traffic, the MAC address hash is used.<br /> <br /> With Hyper-V Port, NIC Teams configured on Hyper-V hosts give VMs independent MAC addresses. The VMs MAC address or the VM ported connected to the Hyper-V switch, can be used to divide network traffic between NIC Team members. You cannot configure NIC Teams that you create within VMs with the Hyper-V Port load balancing mode. Instead, use the Address Hash mode. Because the adjacent switch always sees a particular MAC address on one port, the switch distributes the ingress load (the traffic from the switch to the host) on multiple links based on the destination MAC (VM MAC) address. This is particularly useful when Virtual Machine Queues (VMQs) are used because a queue can be placed on the specific NIC where the traffic is expected to arrive. However, if the host has only a few VMs, this mode might not be granular enough to achieve a well-balanced distribution. This mode will also always limit a single VM (i.e., the traffic from a single switch port) to the bandwidth that is available on a single interface. NIC Teaming uses the Hyper-V Virtual Switch Port as the identifier instead of using the source MAC address because, in some instances, a VM might be configured with more than one MAC address on a switch port. <br /> <br /> With Dynamic, outbound loads are distributed based on a hash of the TCP ports and IP addresses. Dynamic mode also rebalances loads in real-time so that a given outbound flow may move back and forth between team members. Inbound loads, on the other hand, get distributed the same way as Hyper-V Port. In a nutshell, Dynamic mode utilizes the best aspects of both Address Hash and Hyper-V Port and is the highest performing load balancing mode. When you use Switch Independent mode with Dynamic distribution, the network traffic load is distributed based on the TCP Ports address hash as modified by the Dynamic load balancing algorithm. The Dynamic load balancing algorithm redistributes flows to optimize team member bandwidth utilization so that individual flow transmissions can move from one active team member to another. The algorithm takes into account the small possibility that redistributing traffic could cause out-of-order delivery of packets, so it takes steps to minimize that possibility.<br /> <br /> === '''Standby Adapter''' ===<br /> None or a certain selection based on the NIC Adapters selected. <br /> <br /> Just simply select a standby(s) and then proceed with the rest of the Options. No standby has to selected, but it is recommended if you have extra Ethernet Adapters available.<br /> <br /> If you have a two-NIC team and you choose to configure one NIC as a Standby adapter, you lose the bandwidth aggregation advantages that exist with two active NICs. You do not need to designate a Standby Adapter to achieve fault tolerance; fault tolerance is always present whenever there are at least two network adapters in a NIC Team.<br /> <br /> === '''Primary Team Interface''' ===<br /> The options are a Default setting, or either a Custom VLAN. <br /> <br /> If you are using a VLAN then select Custom VLAN and input the VLAN number.</div>

KWahl https://wiki.24pin.tech/index.php?title=File:Snip_-2.png&diff=1021 2019-12-09T20:25:18Z

<p>KWahl: </p> <hr /> <div>Showing the NIC Team successfully funning.</div>

KWahl https://wiki.24pin.tech/index.php?title=File:Snip_-1.png&diff=1020 2019-12-09T20:22:17Z

<p>KWahl: </p> <hr /> <div>Shows the NIC Teaming option.</div>

KWahl https://wiki.24pin.tech/index.php?title=NIC_Teaming&diff=1019 2019-12-09T20:18:43Z

<p>KWahl: Created blank page</p> <hr /> <div></div>

KWahl https://wiki.24pin.tech/index.php?title=DHCP&diff=1017 2019-11-26T19:43:08Z

<p>KWahl: Add Surtr to the list</p> <hr /> <div>=Our DHCP Setup=<br /> <br /> 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.<br /> <br /> ==Address Pool==<br /> <br /> 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. The following chart represents our current setup...<br /> <br /> ===Hostname IP address===<br /> Gateway 10.21.25.1<br /> <br /> Surtr 10.21.25.2<br /> <br /> Loki (PDC) 10.21.25.3<br /> <br /> Fog 10.21.25.4<br /> <br /> Freyr 10.21.25.5<br /> <br /> MacMini 10.21.25.6<br /> <br /> MediaXserve 10.21.25.7<br /> <br /> Heimdall (ESXI VM's) 10.21.25.8<br /> <br /> Logan (BDC) 10.21.25.10<br /> <br /> LoganWeb (VM on Logan) 10.21.25.11<br /> <br /> Macmini Backup 10.21.25.15<br /> <br /> NAS 24PinTech 10.21.25.16<br /> <br /> Perle IOLAN Console Serv 10.21.25.17<br /> <br /> Opengear 10.21.25.18<br /> <br /> ==Address Leases==<br /> <br /> These are all of the current DHCP releases that the DHCP servers have put out that are active.<br /> <br /> ==Reservations==<br /> <br /> 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.<br /> <br /> ==Scope Options==<br /> <br /> This is where we configure our DHCP options. To configure options that we don't already have set, right click &quot;Scope Options&quot; and click on &quot;Configure Options&quot; and configure what you need. Below are the options we already have set:<br /> <br /> [[File:DHCP_Options.PNG]]<br /> <br /> 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]].<br /> <br /> ==Policies==<br /> <br /> These are settings that are applied to certain devices based off of rules defined by the policy, like IP address range, vendor, etc.<br /> <br /> 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.<br /> <br /> ==Server Options==<br /> <br /> This is where settings can be configured globally across the whole DHCP server. We have non of these currently configured.<br /> <br /> ==Policies (Not within scope)==<br /> <br /> Same as above policies but global, we do not have this configured.<br /> <br /> ==Filters==<br /> <br /> This allows you to block or allow certain MAC addresses from receiving DHCP addresses.</div>

KWahl https://wiki.24pin.tech/index.php?title=DHCP&diff=1016 2019-11-26T19:37:13Z

<p>KWahl: Added the Static IP for Freyr.</p> <hr /> <div>=Our DHCP Setup=<br /> <br /> 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.<br /> <br /> ==Address Pool==<br /> <br /> 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. The following chart represents our current setup...<br /> <br /> ===Hostname IP address===<br /> Gateway 10.21.25.1<br /> <br /> Loki (PDC) 10.21.25.3<br /> <br /> Fog 10.21.25.4<br /> <br /> Freyr 10.21.25.5<br /> <br /> MacMini 10.21.25.6<br /> <br /> MediaXserve 10.21.25.7<br /> <br /> Heimdall (ESXI VM's) 10.21.25.8<br /> <br /> Odin (Spiceworks) 10.21.25.9<br /> <br /> Logan (BDC) 10.21.25.10<br /> <br /> LoganWeb (VM on Logan) 10.21.25.11<br /> <br /> Macmini Backup 10.21.25.15<br /> <br /> NAS 24PinTech 10.21.25.16<br /> <br /> Perle IOLAN Console Serv 10.21.25.17<br /> <br /> Opengear 10.21.25.18<br /> <br /> ==Address Leases==<br /> <br /> These are all of the current DHCP releases that the DHCP servers have put out that are active.<br /> <br /> ==Reservations==<br /> <br /> 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.<br /> <br /> ==Scope Options==<br /> <br /> This is where we configure our DHCP options. To configure options that we don't already have set, right click &quot;Scope Options&quot; and click on &quot;Configure Options&quot; and configure what you need. Below are the options we already have set:<br /> <br /> [[File:DHCP_Options.PNG]]<br /> <br /> 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]].<br /> <br /> ==Policies==<br /> <br /> These are settings that are applied to certain devices based off of rules defined by the policy, like IP address range, vendor, etc.<br /> <br /> 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.<br /> <br /> ==Server Options==<br /> <br /> This is where settings can be configured globally across the whole DHCP server. We have non of these currently configured.<br /> <br /> ==Policies (Not within scope)==<br /> <br /> Same as above policies but global, we do not have this configured.<br /> <br /> ==Filters==<br /> <br /> This allows you to block or allow certain MAC addresses from receiving DHCP addresses.</div>

KWahl https://wiki.24pin.tech/index.php?title=WordPress&diff=1000 2019-09-30T19:16:45Z

<p>KWahl: </p> <hr /> <div>==Introduction==<br /> [[File:Wp-admin.png|thumb|screenshot of the WordPress admin dashboard]]<br /> [https://wordpress.org/ WordPress] is a content management system (CMS) that is functions primarily serve our [http://24pin.tech/ homepage] to users that would like to get help or discover more about the program. It's a very powerful platform that grants administrators creative freedom over whatever they want on their website.<br /> <br /> ==Installation==<br /> The installation for WordPress is really simple. All you have to do is download the compressed file for the installation and extract it in the directory that you'd want to install it to. You can either download it from their [https://wordpress.org/download/ website here] or alternatively you can download it using &lt;code&gt;wget&lt;/code&gt;. The command would be &lt;code&gt;sudo wget &lt;nowiki&gt;https://wordpress.org/latest.tar.gz&lt;/nowiki&gt;&lt;/code&gt; on UNIX systems (if you're using aptitude for your package manager.) Once you've downloaded the file, run &lt;code&gt;sudo tar -xzvf latest.tar.gz&lt;/code&gt; to extract it.<br /> <br /> .<br /> <br /> Once you've downloaded and extracted the file, visit your web server to continue with the installation process. The rest of the instructions are on the page of the web installer. <br /> <br /> ==Management==<br /> WordPress was created with the user's experience in mind. The dashboard is very intuitive, and the community is large enough to have answers to most questions/problems. In order to manage a WordPress powered website, you need to use the admin dashboard. In order to get to it, go to the WordPress installation's root directory and then navigate to the &lt;code&gt;/wp-admin&lt;/code&gt; directory (i.e. website.com/wp-admin). From there, you can edit posts, the theme, pages, plugins, and more. If you don't know how to do something, Google it! The WordPress community has been around since 2003, so your question has most likely been asked and answered before.<br /> <br /> ===Logging In===<br /> In order to log into WordPress, go to website.com'''/wp-admin''' (replace website.com with your domain).<br /> [[File:W1.png|left|frameless|208x208px|screenshot of the login page]]<br /> <br /> [[File:W2.png|left|thumb|150x150px|the ''Users'' tab on the sidebar in the dashboard]]<br /> <br /> ===Creating Accounts===<br /> If you need to create an account, go to '''Users → Add New''' from the WordPress dashboard. From there, fill out all of the information for the new account and press the ''Add New User'' button.<br /> <br /> If you need to edit any of the users (change username, reset password, etc), navigate to '''Users → All Users''' and click on the one that you need to modify.<br /> <br /> ===Adding Menu Items===<br /> Before you can add an item to your primary menu, you need to have a new (or preexisting) page. If you need to create one, go to '''Pages → Add New''' and create it. Once it's created, navigate to '''Appearance → Menus''' and draw your attention to the ''Add Menu Items'' section. Find your new page in the list and click on the checkbox and click ''Add To Menu''.<br /> [[File:W3.png|left|thumb|204x204px|adding an item to the ''Menu structure'' section]]<br /> <br /> ===Editing Page Contents===<br /> lksjdfladsjf<br /> [[File:W4.png|left|thumb|what it should look like when trying to create a dropdown menu]]<br /> <br /> ===Adding/Modifying Themes===<br /> adfadfasdf<br /> <br /> ===Uploading Images===<br /> ldkfjalkdfj<br /> <br /> ==Troubleshooting==<br /> f after an installation you get prompted for FTP credentials, add the following line to the wp-config.php file in the directory that WordPress was installed <br /> define(“FS_METHOD”, “direct”);</div>

KWahl https://wiki.24pin.tech/index.php?title=WordPress&diff=999 2019-09-30T19:15:50Z

<p>KWahl: fixed a Minor Command issue</p> <hr /> <div>==Introduction==<br /> [[File:Wp-admin.png|thumb|screenshot of the WordPress admin dashboard]]<br /> [https://wordpress.org/ WordPress] is a content management system (CMS) that is functions primarily serve our [http://24pin.tech/ homepage] to users that would like to get help or discover more about the program. It's a very powerful platform that grants administrators creative freedom over whatever they want on their website.<br /> <br /> ==Installation==<br /> The installation for WordPress is really simple. All you have to do is download the compressed file for the installation and extract it in the directory that you'd want to install it to. You can either download it from their [https://wordpress.org/download/ website here] or alternatively you can download it using &lt;code&gt;wget&lt;/code&gt;. The command would be &lt;code&gt;sudo wget &lt;nowiki&gt;https://wordpress.org/latest.tar.gz&lt;/nowiki&gt;&lt;/code&gt; on UNIX systems (if you're using aptitude for your package manager.) Once you've downloaded the file, run &lt;code&gt;tar -xzvf latest.tar.gz&lt;/code&gt; to extract it.<br /> <br /> .<br /> <br /> Once you've downloaded and extracted the file, visit your web server to continue with the installation process. The rest of the instructions are on the page of the web installer. <br /> <br /> ==Management==<br /> WordPress was created with the user's experience in mind. The dashboard is very intuitive, and the community is large enough to have answers to most questions/problems. In order to manage a WordPress powered website, you need to use the admin dashboard. In order to get to it, go to the WordPress installation's root directory and then navigate to the &lt;code&gt;/wp-admin&lt;/code&gt; directory (i.e. website.com/wp-admin). From there, you can edit posts, the theme, pages, plugins, and more. If you don't know how to do something, Google it! The WordPress community has been around since 2003, so your question has most likely been asked and answered before.<br /> <br /> ===Logging In===<br /> In order to log into WordPress, go to website.com'''/wp-admin''' (replace website.com with your domain).<br /> [[File:W1.png|left|frameless|208x208px|screenshot of the login page]]<br /> <br /> [[File:W2.png|left|thumb|150x150px|the ''Users'' tab on the sidebar in the dashboard]]<br /> <br /> ===Creating Accounts===<br /> If you need to create an account, go to '''Users → Add New''' from the WordPress dashboard. From there, fill out all of the information for the new account and press the ''Add New User'' button.<br /> <br /> If you need to edit any of the users (change username, reset password, etc), navigate to '''Users → All Users''' and click on the one that you need to modify.<br /> <br /> ===Adding Menu Items===<br /> Before you can add an item to your primary menu, you need to have a new (or preexisting) page. If you need to create one, go to '''Pages → Add New''' and create it. Once it's created, navigate to '''Appearance → Menus''' and draw your attention to the ''Add Menu Items'' section. Find your new page in the list and click on the checkbox and click ''Add To Menu''.<br /> [[File:W3.png|left|thumb|204x204px|adding an item to the ''Menu structure'' section]]<br /> <br /> ===Editing Page Contents===<br /> lksjdfladsjf<br /> [[File:W4.png|left|thumb|what it should look like when trying to create a dropdown menu]]<br /> <br /> ===Adding/Modifying Themes===<br /> adfadfasdf<br /> <br /> ===Uploading Images===<br /> ldkfjalkdfj<br /> <br /> ==Troubleshooting==<br /> f after an installation you get prompted for FTP credentials, add the following line to the wp-config.php file in the directory that WordPress was installed <br /> define(“FS_METHOD”, “direct”);</div>

KWahl https://wiki.24pin.tech/index.php?title=Migrating_Spiceworks_(Retired)&diff=998 2019-09-30T18:35:55Z

<p>KWahl: </p> <hr /> <div>==Introduction==<br /> Spiceworks is the site at which 24PinTech can access all work orders that have been assigned to a technician. Once a technician is logged in, they can view, edit, and comment about their work order as well as complete any documentation that is affiliated with the work order. For whatever reason Spiceworks may need to get migrated to another server. <br /> <br /> ==Prep==<br /> Make sure you have access to the following utilities.<br /> <br /> *A New Server<br /> *A Flash Drive<br /> *A Spiceworks Installation usually found at, &lt;nowiki&gt;https://www.spiceworks.com/download&lt;/nowiki&gt; (note this site will immediately start downloading the Spiceworks Installer)<br /> <br /> ==Backups==<br /> [[File:Migrating Wiki 1.png|left|thumb|387x387px]]<br /> In the old server with your current Spicework installation, you will need to sign in using your account and navigate to the settings tab, which would like this (red circle)...<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> [[File:Migrating Wiki 2.png|left|thumb|390x390px]]<br /> Then click on ‘Global Settings’ in the drop down menu. Open up the ‘Backup Configuration’ menu. If you haven't already, insert your Flash Drive into the server. Find the ‘Backup Locations’ menu and change the current path to a path leading to your Flash Drive. Once selected click ‘Backup Now’ at the bottom. (red circle)<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> Eject the Flash Drive and head over to your new server.<br /> <br /> ==Installing Spiceworks and Transplanting the Data==<br /> Once on the new server use the link provided to download the Spiceworks Installer. Make sure the ports mimic the ports of your old server. When given the option Install NMAP and WinPCap through Spiceworks. Once done run the Installer, but '''MAKE SURE''' you '''DO NOT''' start Spiceworks itself, just have it installed. Make sure Spiceworks is completely stopped by checking to see if all the services are stopped. Below are the services. <br /> &gt; spiceworks.exe <br /> <br /> &gt; spicetray.exe  <br /> <br /> &gt; spiceworks-finder.exe  <br /> <br /> &gt; spiceworks-httpd.exe  <br /> <br /> &gt; spiceworks-httpd.exe<br /> [[File:Migrating Wiki 3.png|left|thumb|340x340px]]<br /> If they are all stopped then you can continue with the migration. Find the installation files and open them in File Explorer. Delete the ‘data’ and ‘db’ folders, make sure it is '''ONLY''' these folders that get deleted. <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> Now access the Backup files on your Flash Drive and extract them right into the Spiceworks Installation folder. If everything went well new ‘data’ and ‘db’ folders should appear. <br /> <br /> ==Starting Spiceworks==<br /> [[File:Migrating Wiki 4.png|left|thumb|342x342px]]<br /> Navigate to the application titled ‘spiceworks_desktop’ and run it. (red circle)<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> [[File:Migrating Wiki 5.png|left|thumb|340x340px]]<br /> <br /> Spiceworks should now say something like ‘'''''HEATING UP'''''’ or something rather. This might take a few minutes, so just wait. Once it is done ‘'''''HEATING UP'''''’ it should load into a login screen, shown to the left. <br /> <br /> If everything went swimmingly you should be able to login using the same credentials from your old Spiceworks server. <br /> <br /> ==='''''Congrats!'''''===<br /> Now you just need to disable the Windows Firewall, and add it onto the domain, which is CiscoACA.local for us. Now just test functionality by copying the same URL and entering it on another system, and your good. <br /> <br /> -Your Welcome, Koby</div>

KWahl https://wiki.24pin.tech/index.php?title=Migrating_Spiceworks_(Retired)&diff=997 2019-09-30T18:35:35Z

<p>KWahl: </p> <hr /> <div>==Introduction==<br /> Spiceworks is the site at which 24PinTech can access all work orders that have been assigned to a technician. Once a technician is logged in, they can view, edit, and comment about their work order as well as complete any documentation that is affiliated with the work order. For whatever reason Spiceworks may need to get migrated to another server. <br /> <br /> ==Prep==<br /> Make sure you have access to the following utilities.<br /> <br /> *A New Server<br /> *A Flash Drive<br /> *A Spiceworks Installation usually found at, &lt;nowiki&gt;https://www.spiceworks.com/download&lt;/nowiki&gt; (note this site will immediately start downloading the Spiceworks Installer)<br /> <br /> ==Backups==<br /> [[File:Migrating Wiki 1.png|left|thumb|387x387px]]<br /> In the old server with your current Spicework installation, you will need to sign in using your account and navigate to the settings tab, which would like this (red circle)...<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> [[File:Migrating Wiki 2.png|left|thumb|390x390px]]<br /> Then click on ‘Global Settings’ in the drop down menu. Open up the ‘Backup Configuration’ menu. If you haven't already, insert your Flash Drive into the server. Find the ‘Backup Locations’ menu and change the current path to a path leading to your Flash Drive. Once selected click ‘Backup Now’ at the bottom. (red circle)<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> Eject the Flash Drive and head over to your new server.<br /> <br /> ==Installing Spiceworks and Transplanting the Data==<br /> Once on the new server use the link provided to download the Spiceworks Installer. Make sure the ports mimic the ports of your old server. When given the option Install NMAP and WinPCap through Spiceworks. Once done run the Installer, but '''MAKE SURE''' you '''DO NOT''' start Spiceworks itself, just have it installed. Make sure Spiceworks is completely stopped by checking to see if all the services are stopped. Below are the services. <br /> &gt; spiceworks.exe <br /> <br /> &gt; spicetray.exe  <br /> <br /> &gt; spiceworks-finder.exe  <br /> <br /> &gt; spiceworks-httpd.exe  <br /> <br /> &gt; spiceworks-httpd.exe<br /> [[File:Migrating Wiki 3.png|left|thumb|340x340px]]<br /> If they are all stopped then you can continue with the migration. Find the installation files and open them in File Explorer. Delete the ‘data’ and ‘db’ folders, make sure it is '''ONLY''' these folders that get deleted. <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> . <br /> <br /> Now access the Backup files on your Flash Drive and extract them right into the Spiceworks Installation folder. If everything went well new ‘data’ and ‘db’ folders should appear. <br /> <br /> ==Starting Spiceworks==<br /> [[File:Migrating Wiki 4.png|left|thumb|342x342px]]<br /> Navigate to the application titled ‘spiceworks_desktop’ and run it. (red circle)<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> .<br /> <br /> [[File:Migrating Wiki 5.png|left|thumb|340x340px]]<br /> <br /> Spiceworks should now say something like ‘'''''HEATING UP'''''’ or something rather. This might take a few minutes, so just wait. Once it is done ‘'''''HEATING UP'''''’ it should load into a login screen, shown to the left. <br /> <br /> If everything went swimmingly you should be able to login using the same credentials from your old Spiceworks server. <br /> <br /> ==='''''Congrats!'''''===<br /> Now you just need to disable the Windows Firewall, and add it onto the domain, which is CiscoACA.local for us. Now just test functionality by copying the same URL and entering it on another system, and your good. <br /> <br /> -Your Welcome, Koby</div>

KWahl https://wiki.24pin.tech/index.php?title=Migrating_Spiceworks_(Retired)&diff=996 2019-09-30T18:33:45Z

<p>KWahl: </p> <hr /> <div>==Introduction==<br /> Spiceworks is the site at which 24PinTech can access all work orders that have been assigned to a technician. Once a technician is logged in, they can view, edit, and comment about their work order as well as complete any documentation that is affiliated with the work order. For whatever reason Spiceworks may need to get migrated to another server. <br /> <br /> ==Prep==<br /> Make sure you have access to the following utilities.<br /> <br /> *A New Server<br /> *A Flash Drive<br /> *A Spiceworks Installation usually found at, &lt;nowiki&gt;https://www.spiceworks.com/download&lt;/nowiki&gt; (note this site will immediately start downloading the Spiceworks Installer)<br /> <br /> ==Backups==<br /> [[File:Migrating Wiki 1.png|left|thumb|387x387px]]<br /> In the old server with your current Spicework installation, you will need to sign in using your account and navigate to the settings tab, which would like this (red circle)...<br /> <br /> [[File:Migrating Wiki 2.png|left|thumb|390x390px]]<br /> Then click on ‘Global Settings’ in the drop down menu. Open up the ‘Backup Configuration’ menu. If you haven't already, insert your Flash Drive into the server. Find the ‘Backup Locations’ menu and change the current path to a path leading to your Flash Drive. Once selected click ‘Backup Now’ at the bottom. (red circle)<br /> <br /> Eject the Flash Drive and head over to your new server.<br /> <br /> ==Installing Spiceworks and Transplanting the Data==<br /> Once on the new server use the link provided to download the Spiceworks Installer. Make sure the ports mimic the ports of your old server. When given the option Install NMAP and WinPCap through Spiceworks. Once done run the Installer, but '''MAKE SURE''' you '''DO NOT''' start Spiceworks itself, just have it installed. Make sure Spiceworks is completely stopped by checking to see if all the services are stopped. Below are the services. <br /> &gt; spiceworks.exe <br /> <br /> &gt; spicetray.exe  <br /> <br /> &gt; spiceworks-finder.exe  <br /> <br /> &gt; spiceworks-httpd.exe  <br /> <br /> &gt; spiceworks-httpd.exe<br /> [[File:Migrating Wiki 3.png|left|thumb|340x340px]]<br /> If they are all stopped then you can continue with the migration. Find the installation files and open them in File Explorer. Delete the ‘data’ and ‘db’ folders, make sure it is '''ONLY''' these folders that get deleted. <br /> <br /> Now access the Backup files on your Flash Drive and extract them right into the Spiceworks Installation folder. If everything went well new ‘data’ and ‘db’ folders should appear. <br /> <br /> ==Starting Spiceworks==<br /> [[File:Migrating Wiki 4.png|left|thumb|342x342px]]<br /> Navigate to the application titled ‘spiceworks_desktop’ and run it. (red circle)<br /> <br /> [[File:Migrating Wiki 5.png|left|thumb|340x340px]]<br /> <br /> Spiceworks should now say something like ‘'''''HEATING UP'''''’ or something rather. This might take a few minutes, so just wait. Once it is done ‘'''''HEATING UP'''''’ it should load into a login screen, shown to the left. <br /> <br /> If everything went swimmingly you should be able to login using the same credentials from your old Spiceworks server. <br /> <br /> ==='''''Congrats!'''''===<br /> Now you just need to disable the Windows Firewall, and add it onto the domain, which is CiscoACA.local for us. Now just test functionality by copying the same URL and entering it on another system, and your good. <br /> <br /> -Your Welcome, Koby</div>

KWahl https://wiki.24pin.tech/index.php?title=Migrating_Spiceworks_(Retired)&diff=995 2019-09-30T18:31:16Z

<p>KWahl: Made a page documenting the process Migrating Spiceworks.</p> <hr /> <div>== Introduction ==<br /> Spiceworks is the site at which 24PinTech can access all work orders that have been assigned to a technician. Once a technician is logged in, they can view, edit, and comment about their work order as well as complete any documentation that is affiliated with the work order. For whatever reason Spiceworks may need to get migrated to another server. <br /> <br /> == Prep ==<br /> Make sure you have access to the following utilities.<br /> <br /> * A New Server<br /> * A Flash Drive<br /> * A Spiceworks Installation usually found at, &lt;nowiki&gt;https://www.spiceworks.com/download&lt;/nowiki&gt; (note this site will immediately start downloading the Spiceworks Installer)<br /> <br /> == Backups ==<br /> [[File:Migrating Wiki 1.png|left|thumb|387x387px]]<br /> In the old server with your current Spicework installation, you will need to sign in using your account and navigate to the settings tab, which would like this (red circle)...<br /> <br /> [[File:Migrating Wiki 2.png|left|thumb|390x390px]]<br /> Then click on ‘Global Settings’ in the drop down menu. Open up the ‘Backup Configuration’ menu. If you haven't already, insert your Flash Drive into the server. Find the ‘Backup Locations’ menu and change the current path to a path leading to your Flash Drive. Once selected click ‘Backup Now’ at the bottom. (red circle)<br /> <br /> Eject the Flash Drive and head over to your new server.<br /> <br /> == Installing Spiceworks and Transplanting the Data ==<br /> Once on the new server use the link provided to download the Spiceworks Installer. Make sure the ports mimic the ports of your old server. When given the option Install NMAP and WinPCap through Spiceworks. Once done run the Installer, but '''MAKE SURE''' you '''DO NOT''' start Spiceworks itself, just have it installed. Make sure Spiceworks is completely stopped by checking to see if all the services are stopped. Below are the services. <br /> &gt; spiceworks.exe <br /> <br /> &gt; spicetray.exe  <br /> <br /> &gt; spiceworks-finder.exe  <br /> <br /> &gt; spiceworks-httpd.exe  <br /> <br /> &gt; spiceworks-httpd.exe<br /> [[File:Migrating Wiki 3.png|left|thumb|340x340px]]<br /> If they are all stopped then you can continue with the migration. Find the installation files and open them in File Explorer. Delete the ‘data’ and ‘db’ folders, make sure it is '''ONLY''' these folders that get deleted. <br /> <br /> Now access the Backup files on your Flash Drive and extract them right into the Spiceworks Installation folder. If everything went well new ‘data’ and ‘db’ folders should appear. <br /> <br /> == Starting Spiceworks ==<br /> [[File:Migrating Wiki 4.png|left|thumb|342x342px]]<br /> Navigate to the application titled ‘spiceworks_desktop’ and run it. (red circle)<br /> <br /> [[File:Migrating Wiki 5.png|left|thumb|340x340px]]<br /> <br /> Spiceworks should now say something like ‘'''''HEATING UP'''''’ or something rather. This might take a few minutes, so just wait. Once it is done ‘'''''HEATING UP'''''’ it should load into a login screen, shown to the left. <br /> <br /> If everything went swimmingly you should be able to login using the same credentials from your old Spiceworks server. <br /> <br /> === '''''Congrats!''''' ===<br /> Now you just need to disable the Windows Firewall, and add it onto the domain, which is CiscoACA.local for us. Now just test functionality by copying the same URL and entering it on another system, and your good. <br /> <br /> -Your Welcome, Koby</div>

KWahl https://wiki.24pin.tech/index.php?title=File:Migrating_Wiki_5.png&diff=994 2019-09-30T18:25:13Z

<p>KWahl: </p> <hr /> <div>More Context</div>

KWahl https://wiki.24pin.tech/index.php?title=File:Migrating_Wiki_4.png&diff=993 2019-09-30T18:23:23Z

<p>KWahl: </p> <hr /> <div>More Context</div>

KWahl https://wiki.24pin.tech/index.php?title=File:Migrating_Wiki_3.png&diff=992 2019-09-30T18:21:32Z

<p>KWahl: </p> <hr /> <div>More Context</div>

KWahl https://wiki.24pin.tech/index.php?title=File:Migrating_Wiki_2.png&diff=991 2019-09-30T18:12:44Z

<p>KWahl: </p> <hr /> <div>More Context</div>

KWahl https://wiki.24pin.tech/index.php?title=File:Migrating_Wiki_1.png&diff=990 2019-09-30T18:11:09Z

<p>KWahl: </p> <hr /> <div>An Image for context to see where the button may be.</div>

KWahl https://wiki.24pin.tech/index.php?title=Migrating_Spiceworks_(Retired)&diff=989 2019-09-30T18:03:19Z

<p>KWahl: Created page with &quot;yes&quot;</p> <hr /> <div>yes</div>

KWahl https://wiki.24pin.tech/index.php?title=Spiceworks_(Retired)&diff=988 2019-09-30T17:55:18Z

<p>KWahl: Changed the URL to match our new URL.</p> <hr /> <div>==Accessing and Using Spiceworks==<br /> <br /> '''What is Spiceworks?'''<br /> <br /> Spiceworks is the site at which 24PinTech can access all work orders that have been assigned to a technician. Once a technician is logged in, they can view, edit, and comment about their work order as well as complete any documentation that is affiliated with the work order.<br /> <br /> '''Accessing Spiceworks'''<br /> <br /> Any computer in the 24PinTech classroom can access the Spiceworks service. To access the 24PinTech's reserved section in Spiceworks type the upcoming URL into the address bar and it will take you to the login screen for Spiceworks.<br /> &lt;pre&gt;<br /> http://surtr/pro_users/login<br /> &lt;/pre&gt;<br /> <br /> '''Assigning Work Orders (Manager)'''<br /> <br /> #Log into Spiceworks using your email and password.<br /> #Towards the top left of the screen you will see a drop down box with “Inventory,&quot; click to drop down other options and navigate to the tab that is labeled “Help Desk.&quot;<br /> #To enter a work order process into Spiceworks click on “New Ticket” found towards the top middle of the screen.<br /> #Using information found in the Google work order spreadsheet, give the ticket a name that is related to the customer. In the description text field, include the customer's name, email address and brief breakdown of the issue. Then assign the ticket to a technician (make sure the assigned technician is the same as the one assigned in the google sheets).<br /> ##Under the comments, enter the client's email address that the technician should use to contact.<br /> #Inform the technician that they have a new ticket.<br /> <br /> '''Adding a New User to Spiceworks'''<br /> <br /> #Log into Spiceworks using your email and password.<br /> #Navigate to the &quot;Help Desk&quot; section.<br /> #On the right-hand side of the screen you will see a box labeled &quot;Settings&quot;. Click on it.<br /> #On the left side of the web page under help desk, you will see “User Accounts.&quot; Click on it and it will take you to all the users available on Spiceworks.<br /> #Towards the right side of the screen you will see “Add Users,&quot; click on it.<br /> #Fill out the invitation with first and last names and the email the technician uses most often. Assign them a proper role in Spiceworks. (Put billing rate as $0.00)<br /> #Send invitation<br /> <br /> '''Checking Tickets'''<br /> <br /> #Log into Spiceworks<br /> #Towards the top left of the screen you will see a drop down box with “Inventory,&quot; click to drop down other options and navigate to the tab that is labeled “Help Desk.&quot;<br /> #Next to “Tickets” there is a gray drop down box. The default is labeled “Unassigned Tickets.&quot; Click the drop down box and navigate to “My Tickets.&quot;<br /> #You will see your assigned work order, with a description and the customer's contact information.</div>

KWahl