Those commands return different data so that may be the difference you are seeing. Below is the description for those commands.
If you don't have any more questions, shall we close this post?
checkprocess
SUBMODE Set this to Name, ExecutablePath, or Commandline to determine if ARG1 and ARG3 matches against just the
process name (Default), the full path of the executable file, or the complete command line used to run the process.
ARG1 A regular expression to match against the process name, executable path or complete command line.
The matching processes are included in the resulting list. Use . alone to include all processes. Typically the process
- Executable Path is like DRIVE:PATH/PROCESSNAME eg C:/WINDOWS/system32/svchost.exe,
- Command Line is like DRIVE:PATH/PROCESSNAME PARAMETERS eg C:/WINDOWS/system32/svchost.exe -k LocalService
Use '/' (forward slash) instead of '\\' (backslash). eg "C:/Windows" or "C:/windows/system32"
Note: Any '/' in your regular expression will get converted to '\\'.
ARG2 Set this to 'Name' (Default), Executablepath or 'Commandline' to display the process names, executablepath or the
whole command line.
ARG3 A regular expression to match against the process name, executable path or complete command line.
The matching processes are excluded from the resulting list. This exclusion list is applied after the inclusion list.
For SUBMODE and ARG2 you only need to specify the minimum required to make it unique. Any of the following will work
-s e, -s exe, -s c, -s com, -o e, -o exe, -o c, -o com
WARN/CRIT can be used as described below.
Valid Warning/Critical Fields are: _ItemCount (Default), _NumExcluded
checkservice
ARG1 A regular expression that matches against the short or long service name that can be seen in the properties of the
service in Windows. The matching services are included in the resulting list. Use . alone to include all services.
Use Auto to check that all automatically started services are OK.
ARG2 A regular expression that matches against the short or long service name that can be seen in the properties of the
service in Windows. The matching services are excluded in the resulting list.
This exclusion list is applied after the inclusion list.
WARN/CRIT can be used as described below.
Valid Warning/Critical Fields are: _NumBad (Default), _NumGood, _NumExcluded, _Total