Keith Smith - My Blog

• Identifying Weaknesses in Remote Connectivity
  • Security Review: Ensuring workers using personal devices to connect to organization resources are properly protected to ensure the organizations network is not exposed to outside threats.
  • Home Network Review: Reviewing remote worker home internet speed or hardware to get the best experience possible, especially over wireless. 
    
  
  
• Reviewing Workstation & Server Security
  • On Premise Security Review:  If your staff is working remotely, is your office protected from outside threats?  It's important to have multi-factor authentication into all systems when working remotely.
    
  • Regular Network Maintenance: Continued patching and maintenance of network hardware ensures your systems aren’t exposed to threats. 
  • Regular Device Maintenance: Workers on organization owned devices should have data encryption enabled, anti-virus installed and be fully patched with windows and third party updates.
  
  
• Maximizing Work from Home Efficiency
  • External Hardware Review: Identifying opportunities for remote workers to use additional hardware like printers and multiple monitors.
  • Communications Review: Ensuring phone, messaging and remote meeting access is available to allow for efficient communications.
  
  
• Controlling Costs
  • Licensing Review: Checking for unused licensing and software usage on monthly subscription costs can yield instant results to the bottom line with the IT budget.
  
  
• Reminding Employees of Security Awareness
  • Remote Patching Reminders: Reminding remote workers of the importance of following the normal method for ensuring updates are installed on their organization owned device and personal devices.
  • Email Security Review: Running phishing campaigns to expose training needs for staff in relation to handling malicious emails that harvest personal and organization data.
  
  
• IT Business Process
  • Business Continuity Planning: Create or refresh plans to continue access to key IT business resources and consider how that impacts keeping your business running if key staff are out sick or otherwise unavailable.
  • Password Management Review: Determine the current processes in place for sharing and storing passwords to ensure that other individuals have credentials in the case someone is out sick or unavailable.
  • Communications Review: Identify additional methods and tools you can use beyond email to communicate with workers

-End

-End

Open the virtual service then add the first SubVSs

The first subVS weight should be 1100 and Not Available Redirection Handling Error code set to 302 and the Redirect URL set to https://%h%s.

The second SubVS has a weight of 1000 and has the IIS server I use to create my Let's Encrypt certs set as the real server.

Create a content rule named Lets_Encrypt, Rule Type is Content Matching, Match Type is Regular Expression, Header Field is left blank, Matching String is /^\/.well-known/ and ignore case is checked.

Now enabled Content Switching at the VS. I then added all my Content rules for my domains to the first SubVS so they will be redirected to HTTPS then I added the Lets_Encrypt Content Rule to the second SubVS.

To download the exported file, visit my github repo https://github.com/KeithIT-Dev/Kemp

-End

1. Install the newest version of python on the server that has the ManageEngine ServiceDesk installed, be sure to click the custom installation option during the setup. You will need to install all the optional features along with all the advanced options during the setup.
   
2. Reboot the server
3. Clone or Download the master branch from the GitHub repo https://github.com/KeithIT-Dev/ManageEngineServiceDesk.git or run a git clone https://github.com/KeithIT-Dev/ManageEngineServiceDesk.git
4. Place all the files and folders from the python libs in the Python\Lib\site-packages folder on your server
5. Place KeithAutoShareRequest.py in the \ManageEngine\ServiceDesk\integration\custom_scripts folder on your server
6. Generate an api key that doesn't expire and copy it to notepad, you can generate this api key from within the ManageEngine ServiceDesk.
7. You need to edit the KeithAutoShareRequest.py, inside this script you need to add the api key you generated on line 17 and update line 13 with URL of your ServiceDesk instance.
   
8. Create a folder named request in \ManageEngine\ServiceDesk\integration\custom_scripts folder on your server
9. Now login to your ManageEngine ServiceDesk and go to the admin tab then click on the custom trigger under the helpdesk customizer
10. Click the add new action button
11. Match the settings as the same as the screen shot below
    

-End

-End