Friday, October 9, 2020

ServiceDesk Plus - SSL Certificates and FQDN Redirect

 In our environment, we use ServiceDesk Plus (On-Prem) for the Helpdesk Ticketing System.

Our Active Directory Domain is single-forest, with Parent and Child Domain.  I am responsible for the Child domain, and that is where the SDP Web Server resides.

Users would access the helpdesk portal via http://hostname:8080.

I needed to install an SSL certificate on the site, which is covered in the SDP documentation: SSL Certificate Install.

Port redirect is also covered in the documentation: HTTP to HTTPS redirect.

However, one of the criteria for using an SSL certificate on a site is that it's signed for the FQDN. Therefore users would need to access the site via https://hostname.child.domain.com:8443. If the user would access the site with just the hostname - https://hostname:8443 the browser would throw a certificate warning.

The solution - not covered in the documentation, and not provided by ManageEngine support, is to edit one of the Tomcat web server configuration files:

Open the file named server.xml.

On my server it was located at: c:\manageengine\servicedesk\webapps\ROOT\WEB-INF

  1. Set the proxyName attribute of your Connector elements to the FQDN for your server.
  2. Add an alias element to your Host elements

For the full explanation, please see the blog post by @ https://roadha.us/2009/09/redirect-tomcat-to-fqdn.html

Tuesday, June 30, 2020

Wednesday, January 29, 2020

VMware vCenter Does Not Send Email Alerts

Environment: vCenter Server Appliance 6.5

Under vCenter > Configure > General > Mail the SMTP server and port are configured correctly
Event Log indicating alert emails are being sent, however in reality they are not.

Either via SSH/Console/WinSCP, login to the VCSA and navigate to /etc/mail
Make a backup of the file named submit.cf and then open it in an editor.
Scroll down to: # "Smart" relay host (may be null)
On the next line after DS enter the SMTP Server and save the file.
Reboot the vCenter Server Appliance



Thursday, May 2, 2019

Uninstalling MSI Fails

When trying to uninstall a program the following error occurss:

The feature you are trying to use is on a network resource that is unavailable

To fix this, you need to find the referenced MSI in the registry and delete the entry.

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products

For the complete instructions follow this guide:

https://www.thewindowsclub.com/the-feature-you-are-trying-to-use

Monday, February 5, 2018

Remove Hotfix from Unbootable OS


1. In the Windows 10 boot menu, go to Repair.
2. Go to Tools > Options to get a command prompt.
3. Confirm the drive letter for the Windows image (usually it is D:\).
4. Run dism /Image:D:\ /Get-Packages to view the installed packages along with their date of install and note the name of the rogue package.
5. Run the following command with the wanted package name dism.exe /image:d:\ /remove-package packagename:Package_for_KB4014329~31bf3856ad364e35~amd64~~10.0.1.0
Then just reboot the system normally, and you should be good to go!