ManageEngine: Inline images dropped

In ManageEngine ServiceDeskPlus MSP it is notifying receipients and senders when an inline image is dropped/not processed. To disable this notification, perform the following steps to update the database.

Run the query on the database. If using Postgres bundled with ME SDP MSP, this is the query.

update GlobalConfig set paramvalue='false' where category like 'EMAIL_PROCESSING' and parameter like 'sendAttachmentStrippedNotification';

To use Postgres, navigate to your ME SDP MSP installation location in a command prompt, for example C:\ManageEngine\ServiceDeskPlus-MSP and into sub-folder pgsql\bin.

pgsql -h 127.0.0.1 -U sdpadmin -p 65432 -d servicedesk

It will prompt for the database password. If you do not know this password, you can decrypt it using ME tool found in your ME SDP MSP bin folder, for example, C:\ManageEngine\ServiceDeskPlus-MSP\bin\decryptPostgresPassword.bat. Make sure to record the password in a safe location.

Uninstall ManageEngine DesktopCentral Agent

Here are some methods to remove the ManageEngine DesktopCentral Agent.

@echo OFF
Rem Manage Engine Desktopcentral Agent Uninstallation String
Rem This bat file will uninstall the Desktopcentral Agent
%SystemRoot%\system32\msiexec.exe /x{6AD2231F-FF48-4D59-AC26-405AFAE23DB7} MSIRESTARTMANAGERCONTROL=Disable REBOOT="ReallySuppress" /qn 

Agent Uninstall Tool

https://www.manageengine.com/products/desktop-central/desktop_agent_uninstallation.html

Local Copy:

Agent Uninstall VBScript

'Manage Engine Desktopcentral Agent .

'Script to Clean up ManageEngine Desktop Central Agent from Add remove programs .
'================================================================================

On Error Resume Next

Set WshShell = WScript.CreateObject("WScript.Shell")
   WshShell.RegRead("HKEY_CLASSES_ROOT\Installer\Products\F1322DA684FF95D4CA6204A5AF2ED37B\SourceList\Net\")
   WshShell.RegDelete "HKEY_CLASSES_ROOT\Installer\Products\F1322DA684FF95D4CA6204A5AF2ED37B\SourceList\Net\"
   WshShell.RegDelete "HKEY_CLASSES_ROOT\Installer\Products\F1322DA684FF95D4CA6204A5AF2ED37B\SourceList\Media\"
   WshShell.RegDelete "HKEY_CLASSES_ROOT\Installer\Products\F1322DA684FF95D4CA6204A5AF2ED37B\SourceList\"
   WshShell.RegDelete "HKEY_CLASSES_ROOT\Installer\Products\F1322DA684FF95D4CA6204A5AF2ED37B\"

'Uninstall Agent and Remote Control Service
'==========================================
WshShell.Run "%windir%\system32\sc stop "   &Chr(34)& "ManageEngine Desktop Central - Agent"  &Chr(34),1,True
WshShell.Run "%windir%\system32\sc delete " &Chr(34)& "ManageEngine Desktop Central - Agent"  & Chr(34),1,True
WshShell.Run "%windir%\system32\sc stop "   &Chr(34)& "ManageEngine Desktop Central - Remote Control"  &Chr(34),1,True
WshShell.Run "%windir%\system32\sc delete " &Chr(34)& "ManageEngine Desktop Central - Remote Control"  & Chr(34),1,True

'**********************************************************************************************************************

Block Windows 11 Update

The easiest way to block the Windows 11 update on a Windows 10 system is by adding a policy via the Registry.

In HKEY_LOCAL_MACHINE, navigate to SOFTWARE\Policies\Microsoft\Windows

Create a new Key named WindowsUpdate

Add the following items in the WindowsUpdate key:

  • REG_DWORD named TargetReleaseVersion with a value of 1
  • REG_SZ named TargetReleaseVersionInfo with a value of 21H2
  • REG_SZ named ProductVersion with a value of Windows 10

Below is a registry file example. You can also download a copy if you’d like.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"TargetReleaseVersion"=dword:00000001
"TargetReleaseVersionInfo"="21H2"
"ProductVersion"="Windows 10"

If you are using ManageEngine’s Desktop Central, you can create a configuration to deploy to computers with the Desktop Central agent. Here’s an example of the configuration in the Manage Engine Desktop Central web administration panel.

ManageEngine SupportCenter Plus: Changing Request Starting ID

How to change the starting request ID number in ManageEngine SupportCenter Plus. For ServiceDesk Plus MSP, see ManageEngine ServiceDesk Plus MSP.

In the ManageEngine installation directory, I’ll assume C:\ManageEngine\SupportCenter

For MySQL

  1. C:\ManageEngine\SupportCenter\mysql\bin\mysql.exe -u root -P 33356 supportcenter
  2. mysql> insert into workorder (WORKORDERID,REQUESTERID,DEPARTMENTID) values (4999,2,1);
    Where request ID is 4999, Requesterid is 2 and Department ID is 1
  3. Restart SupportCenter service

For MSSQL

  1. insert into workorder (WORKORDERID,REQUESTERID,CREATEDTIME,DUEBYTIME,DEPARTMENTID) values (4999,2,0,0,1);
  2. Restart SupportCenter service

For Postgres

  1. C:\ManageEngine\SupportCenter\pgsql\bin\psql.exe -U postgres -p 65432 -d supportcenter
  2. postgres# insert into workorder (WORKORDERID,REQUESTERID,CREATEDTIME,DUEBYTIME,DEPARTMENTID) values (4999,2,0,0,1);
  3. Restart SupportCenter service

ManageEngine ServiceDeskPlus MSP: Change Starting Request ID (Postgres)

The procedure to change the request ID for ServiceDeskPlus MSP product (v10.5 and later) is outlined below.

Navigate to the location of ServiceDeskPlus MSP installation and change into the pgsql\bin directory in a command prompt.

C:\ManageEngine\ServiceDeskPlus-MSP\pgsql\bin> psql -U sdpadmin -p 65432 -d servicedesk -h 127.0.0.1 

Enter the password sdp@123

Queries for the respective modules:

REQUEST

insert into workorder(workorderid,requesterid,createdtime,respondedtime,duebytime,completedtime,timespentonreq,isparent,is_catalog_template,fr_duetime,haschange,hascausedbychange,hasproblem,surveystatus,hasdraft,resolvedtime) values (3000,1,0,0,0,0,0,true,false,0,false,false,false,0,false,0); 

PROBLEM

insert into problem (problemid,title,reportedtime,updatedtime,duebytime,closedtime,isread,notespresent) values(3000,’title’,0,0,0,0,false,false); 

CHANGE

insert into changedetails (changeid,title,createdtime,scheduledstarttime,scheduledendtime,completedtime,notespresent) values(3000,’title’,0,0,0,0,false); 

Use \q to exit postgresql commandline and restart the ServiceDeskPlus MSP service. On Windows this is servicedeskmsp.

Try creating a new ticket to check the ID series.