Hesk/Help Desk
About
HESK is a basic, lightweight, help desk program that we use to process our work orders for 24PinTech. We downloaded the software from HESK.COM and it fully integrated with our 24Pin.tech website. The URL to access the new software is at service.24pin.tech.
Installation
Version 3.4.2
(Note:
Conditions:
- This version of HESK was installed on a VM. It was not tested on the actual webserver.
- We installed a basic LEMP stack on the VM before installing HESK. See the addendum included in Nginx.
- We implemented PuTty to deal with our vm.
Step 1
Inside command line, navigate to etc/nginx/sites-available
and create a new config file. This will be the service.24pin.tech file that will house the HESK program.
Step 2
Download HESK 3.4.2 from hesk.com. Open the installation guide and begin following the instructions. Keep in mind that the installation asks you to obtain your MySQL database name, user and password.
Step 3
Download and install Filezilla. It can be found in shared storage under 24pintech Apps:
- Create a site using the ip address as the host and the username and address for the server (we're connecting to the server's to access its files from filezilla) - we used port 22 because it was teh same port we used to access the server through PuTty
- (Note - the filezilla application is in the shared storage under >24pintech > apps > Filezilla)
- Move the downloaded hesk file (unzipped) into the config file you created n the webserver.
- (Note - after completing the steps to install the LEMP stack in VM, the folder we used were under /var/www/(public folder you created - ex. hesktest.24pin.tech)
Step 4
Navigate to the new hesk website created after installing the file by typing in your URL - website-name/install
Step 5
Follow the instructions given on the new website. Make sure to delete the install folder in filezilla before closing the program.
Contextual Circumstances:
- The version is HESK version 3.2.2.
The installation of HESK required a download from hesk.com. We downloaded and installed HESK 3 (version 3.2.2) The installation was somewhat problematic due to lack of documentation regarding the installation process for Nginx. I used the following documents to piece together the process.
- https://www.hesk.com/demo/docs/step-by-step-guide.html
- https://www.digitalocean.com/community/questions/how-to-create-subdomain-with-nginx-server-in-the-same-droplet
Step 1
Download Hesk 3.2.2 (or latest version) to a known directory.
Step 2
This step will use a tool called PuTTY 64x86 which can be downloaded from their website. After installing you will open a new CMD window and navigate to the PuTTY install directory. My command... cd C:\Program Files\PuTTY
. Once you have successfully navigated to the installation directory you will enter the command to send the zip to the webserver... pscp.exe <LocalFilePath> <user>@<RemoteHost>:<RemoteDirectory>
... pscp.exe ZIP_FILE_LOCATION [/cdn-cgi/l/email-protection [email protected]]:/home/pintech
. The zip has to be placed in the users home due to permission issues.
Step 3
Navigate to etc/nginx/sites-available
and create a new config in nginx. In this instance I will be creating the service.24pin.tech file. Use an editor like nano or vim to edit the config file. Here is an example sudo nano service.24pin.tech
OR sudo nano /etc/nginx/sites-available/service.24pin.tech
. Once in the editor create a config file, see the nginx article in this wiki in the section Configuring Nginx for assistance.
Step 4
At this point you should be on step 4 of the HESK install file. The URL may be slightly different than what is used on the document.
Step 5
During the HESK install you will be asked to set up a MySQL database for HESK. You will use phpMyAdmin to accomplish this. You will naviagate to the phpMyAdmin URL and log in. Get the credentials from Chamberlain. Once logged in you will navigate to the Databases page. Type in the name of your new database and use that name when prompted to during the HESK install.
IMPORTANT: MAKE SURE YOU ARE CREATING A NEW DATABASE AND NOT USING AN OLD DATABASE!!!
Updating HESK
Requirements
- FileZilla
- Access to ESXI
- Basic Linux knowledge
Step 1 (preparations)
Log into the Admin page on HESK and go to any of the settings tabs, if it is out of date it will tell you on the right and give you a link to update it, grab the update files from said link and extract them.
Log into ESXI and go into the Logan VM MAKE A SNAPSHOT
Open FileZilla and connect to 10.21.25.11 using the pintech login
Step 2
Using FileZilla make a directory in the pintech home directory and give it a simple name (e.x. HESKUPDATE) then move all the update files into it
On the VM go into root by using "su" and locate both the update files and the HESK server "/var/www/SERVERURL"
Step 3
Using the mv (move) command or the cp (copy) command to move/copy the contents of the update directory with a * after the directory (e.x. /home/pintech/HESKUPDATE/*) you created to the HESK server with the overwriting any files
Step 4
After the files have been moved/copied into the HESK server, you can close both the VM and FileZilla
On your browser of choice go to "service.24pin.tech/install" and click the update button and let it update
You have successfully update the HESK Server and can continue onto the next step
Troubleshooting/Final steps
Any errors will go to the error logs located in "/var/logs/nginx" and will be "error.log" you can use either nano to read it or FileZilla to copy it to your desktop and open it with notepad
When updating HESK from one version to the next please make sure to update the general settings. There is a section in there where you have to put in our specific URL information for our website and domain. See the photo.
Sometimes the submit_tickets.php breaks and can usually be attributed to a single line of code (usually 211) and can either be made into a comment by using # at the beginning of the string or by just deleting the entire line
HESK Admin Information
Initial Login:
- Navigate to https://service.24pin.tech/admin
- User name: First Name and First Letter of last name (ex: Todd H)
- Password: MHSschool
Ticket
- Main Page
- You can see it in the tickets area with different information
- Changing information about the ticket, as well as assigning, is below the tickets to the right
- You can change information or reply to the customer when clicking on the ticket ID and subject area in main menu
- You can view certain types of tickets
- You can find specific ticket based on certain information
- Under a ticket
- You can look at the message/description they give about their device
- Below the description you can add a hidden note
- You can reply to the customer (do not use this, use it through your email)
- You can choose not to send the email with assigning the ticket, and changing priority
- After the changes you can change ticket status, category, priority, and assignee
- Finally there is ticket internal information, like tracking ID, date it as introduced, that cannot be changed except due date
Categories:
- Function:
- Categories allow customers to choose what kind of device they have and is apart of the ticket creation process they do
- They choose this option first when submitting a ticket
- Changing:
- Each category has a set priority, and type if needed to change
- To create a new category click “New Category” in the top right and choose a name, set priority, and whether it is a public or private option
- Public is for the customer choosing the category
- Private is for 24PinTech if needed to change to a specific category
Team (Users):
Creating Users
- In the top left click new Team member and fill out basic information
- Under Permissions put everyone as staff except the people who require all access.
- Every permission can be left to default or give access to specific areas. Which can allow for allocation within the system.
- Signatures are unneeded. It is just an end of a message
- Preferences are unneeded. Keep default
- Notifications can vary. keep default for everyone
- You can only finish creating a user under the notification tab
User Editing
- Admin can edit anything about a user but are very few
- Normal users can edit anything except permissions about their account. Permissions allow the user access specific areas of HESK
- Staff member editing access
- In the top right of the site click their name then click view profile
- Then edit profile
- Under profile information in the password subsection the user can change their password to their preferred password
- You can only save the settings in the notifications tab
Tools
Ban Emails
- This will be a section where it is Forbidden to ban an account without explicit permission.
- Do not add/change
Ban IPs
- This will be a section that Administrators can never touch under no circumstance.
- Do not add/change
Service Messages
- Display a service message in the customer area, for example to notify them about known issues and important news.
- The Service message can be any of the following: Success, info, notice, or error. in the setting sections
- The service messages will be about something that is unavailable with our services.
Email Templates
- The email templates allow you to change/modify emails that are sent to customers and staff members.
- There is nothing able to change in this section.
- To create a canned response go under the Template section under responses .
Custom Fields
- This section is used to add custom fields to require additional information from the customer through the ticket process.
- Creating a field:
- This is a new field for information that the customer has to fill out
- Everything is self explanatory except category
- If only a specific device needs it the categories are listed and get rid of the unwanted device
Statuses
- This section is used to create new ticket statuses.
- Allows viewing of all tickets and where they fall within the different statuses.
- Creating statuses:
- Choose the name, color and if customer want to change the status (do not let customers change statuses
Settings
General
- General Settings:
- Allows you to change the website title, URL, and Email center.
- These should never change under any circumstances, or if CEO of 24PinTech requires
- Language:
- Allows multiple language access
- Language folders are required to add different languages but must be through the server sides of things and not The website
- Data Base:
- This is about the server hosting of Hesk
- DO NOT CHANGE
Help Desk
- Help Desk Settings:
- This is where the storage on the server of tickets and customizing the message of ticket responses
- It customizes the home look of tickets from the admin view
- Change only if necessary
- Features:
- This is the requirements of filling out a ticket on the customer side
- It also allows ticket auto-assigning, but it is unnecessary
- Change only if necessary
- SPAM Prevention:
- SPAM prevention does what it says, prevents SPAM
- There can be different types of SPAM prevention, even custom ones
- Some troubleshooting methods if it does not work: https://www.hesk.com/knowledgebase/index.php?article=27
- Change only if needed
- Security:
- This is about the login and having staff users when logging in
- View tickets is for customers seeing their ticket without requiring their email, but they still need ticket ID
- DO NOT CHANGE FROM FRAMES ONWARD
- Attachments:
- This allows customers to attach any attachments if they want
Knowledgebase
- This can make HESK an information base instead of a ticketing system
- DO NOT CHANGE
- Email:
- This changes the type of emailing system that is used
- When and who Hesk sends emails: https://www.hesk.com/knowledgebase/index.php?article=94
- DO NOT CHANGE
- Email Loops:
- Changes the responding time of emails
- DO NOT CHANGE
- Detect Email Typos:
- Self explanatory
- Add any emails that would be used but are not listed
- Notify Customers:
- Self explanatory
- Other:
- This is minor things about email filling out whether logged in the setting or filling out a ticket
- Change only if necessary
Ticket List
- Fields in Ticket List:
- This is what categories are on the ticket page when viewing tickets
- Other:
- Both things under this section are about the date and time formats of a ticket
Misc
- Date and Format:
- This is the format of the Date and Time shown anywhere
- Change if necessary
- Other:
- IP WHOIS shows the IP address of the customer, The customer will not be able to see it
- Maintenance mode will turn off the ticketing system for customers
- Admin link is to see an admin link on the customer request form
- Submit notice will let the customer see their IP address and warn them it will be tracked
- DO NOT CHANGE
- Users online let you see what users are on and how long ago they were online
- Updates: Self Explanatory