Ram – Page 14 – How To HelpDesk

February 6, 2019March 14, 2019

How to upgrade osTicket to 1.10.4

The osTicket is a great truly open source ticket system, you can customize to fit your business needs. If you are running an older version of osTicket, it’s best to keep up to date with stable releases to keep your ticket system protected. If you wait too long for an upgrade and newer version have many changes then it would get harder. The upgrade process is about the same for most version unless major version which might have database changes and it will run the upgrade script. Here is how to upgrade from version 1.10.1 to 1.10.4

Make sure you have a good backup of Database and files of osTicket
Then put the system in the offline mode: by going to /scp/settings.php
Download the new version from https://osticket.com/download/ and choose the osTicket Core, v1.10.4 (Latest Release)
Upload to your server v. 1.10.4 and replace current files/folders from Upload folder from your downloaded, and exclude the script folder/files
Make sure you have the correct permission, then go to the URL/SCP of the osTicket system and login
Delete the /setup folder and update any customization you may have, once all is good you can put system back online

That’s it, if customized PHP core files, those needs to be re-applied after the upgrade. If are using plugins, make sure it supports the new version. Most if not all open source project is fully customizable and downside to is keeping up to date with any customization been done to the core system. You will find many solutions to the problem in a forum where people report and help out each other. Please read your error message and logs of your system web server, PHP, osTicket, it gives many ideas about why things are not working. Many of them due to PHP version not supported. If you were to get help from the forum, please include your system information, like osTicket, PHP version, web server, and remember forum support is free, so don’t order/demand to fix your issues.

Note because 1.10.1 to 1.10.4 upgrade did not have any database changes so you will not see the upgrader screen. If you want you can run manually upgrader: /scp/upgrade.php, most likely you will see the message: “Nothing to do! System already upgraded to v1.10.4 with no pending patches to apply. ”

Common issues/solution:

error: Valid CSRF Token Required
solution: edit include/class.ostsession.php line around 191

catch (DoesNotExist $e) {
$this->data = new SessionData([‘session_id’ => $id]);
+ $this->data->session_data = “”;

February 5, 2019February 5, 2019

Update UniFi Wi-Fi Cloud controller key firmware

Ubiquiti UniFi wireless network is great for home, small, or even large business. It’s very easy to dashboard to over view of your whole network. Easy to manage and updates, once in while you might have issues if you are updating the firmware remotely and would not be able to log back into the dashboard. Here is how to update and be able to fix your issues, in case you looking around for solution.

It’s always a good idea to do any firmware update on site. if you are not onsite and started the firmware update you might not be able to access the dashboard and you will need to restart the key manually, in order to bring back online. Here is what it looks like after firmware upgraded and Lauch is grayedout.

You have two option, one if you still have access to site and using PoE switches, you can toggle the UniFi key port, so it will restart. Second option is have someone manually unplug UniFi key and plug it back in.

How to upgrade firmware?

Make sure you have good backup and you are onsite, or have backup route to get into network or have someone on site to help out if you can’t access it.

Then check for update and then apply update

It will start download, install, then restart automatically, Your access points still be working fine, you will not be able to manage until controller comes back online

once it’s finish you should see Up To Date, you may need to refresh page and login.

Then you can update the access points or other devices, you should see upgrade option.

If there are no upgrade then you should see in Action to Locate/Restart

That’s it, make sure you do NOT stop the update process in the middle, otherwise you will not be able to use the device at all.

February 4, 2019February 4, 2019

Nagios network monitor upgrade to Version 4.4.3

Nagios is a great open source network monitor released new version 4.4.3 last month. It’s a great free tool, you can customize to fit your network and monitor live. Know the issues before your user’s reports to you, you can see the history of your network health, so you know your network is stable or find out if you are having some issues in some part of your network. So keeping up with the newest version to monitor your network is very important. Let’s get started first, make sure you have a good backup and check your Nagios config if you have any errors correct it first. Also, if you are using any plugin make sure they support the new version too. I am using Ubuntu server and Apache for a web server.

To check the Nagios health:

Command: nagios -v /usr/local/nagios/etc/nagios.cfg

Your path to Nagios might be different and unless you are sudo user you will need to use sudo command. You may have some warning of deprecated, you can update it and fix it before the update something like this:

WARNING: The retry_check_interval attribute is deprecated and will be removed in future versions. Please use retry_interva l instead.

If everything looks good, then next download new version of Nagios. You can download the Nagios core from https://www.nagios.org/downloads

at download page choose Nagios Core, then new version: 4.4.3

Update process:

Extract: tar –zxvf nagios-4.4.3.tar.gz
switch to the directory: cd nagios-4.4.3/
Stop Nagios service: service nagios stop
Run command to check: ./configure –with-command-group=nagios
If everything is fine: make all
Then install it: make install

Check Nagios config: nagios -v / usr/local/nagios/etc/nagios.cfg

If any errors found then fix it and re-run the check config until no errors found, then start Nagios service: service nagios start

You might need to restart the apache2 service or whatever your web server is: service apache2 restart

That’s it

Resources:

Nagios Core Manuals

February 1, 2019February 1, 2019

Clean up Windows 10 updates

Microsoft Windows 10 updates are trying it’s best to keep the user system protected, but user system drives are loosing about 5 GB-30 GB of their hard drive space. If you have a smaller drive and need to clean up Windows updates, you can by deleting old system files. You can also clean up old programs you no longer need and empty out recycle bin.

Here is example of about 100 GB drive and 35 GB taking up by Windows, it’s not all Windows update

How to clean up system files

Open Windows Explorer and right click on the system drive (normal default C drive), then select Properties (or you can search for “disk cleanup” or type in run command:cleanmgr.exe )

Then click on Disk clean up

Then click on Clean up system files

Then select the check box Windows update Cleanup then click on ok, that should give you back your hard disk space.

Here is couple different computer Windows 10 update clean up about 6 GB to 10 GB

That’s it, there are other check boxes you can check off to clean up more. You can click on each one it will give you more information about it, most if not all can be checked and clean out, unless you want for logs or recover your system.

January 31, 2019January 31, 2019

Increase allowed maximum attachment size

On exchange 2010 or may be applied to other versions of on-premise exchange. You have maximum attachment size setting to allow people to send to other users and there are many causes based on settings of, database, mailbox, email spam system, firewall, etc… Also, there is one more on Active sync, which is by default is 10 MB, so it does not matter, if you have allowed bigger attachment. When using the smartphone you will see the server rejected message when your attachment is larger than 10 MB.

You can Open the web.config settings of the Microsoft Active Sync

Then edit the httpRuntime maxRequestLength to whatever you like

After the change is been made, you will need to restart the IIS service to take effect of your new settings. Then you should be able to send bigger attachments from your smartphone. Some other things to be noted, if your mail server allowing bigger attachment that does not mean other mail server will accept bigger attachment. Most spam system scanner inside your attachments and can block if something inside attachment have strange type of content.