BES Client Helper Service
Log In or Register to download the BES file, and more.

1 Votes

Description


This analysis contains status information about the BES Client Helper Service. The BES Client Helper will monitor and restart the BES Client service and can be installed with the task .

After activating this analysis, a new Health Check will appear in the Deployment Health Checks Dashboard and the following properties will be created.

The BES Client Helper Service will first attempt a simple restart the BES Client if it is not running. If that does not work, it will try to fix the Revocations files as a troubleshooting step. If that does not work, it will attempt to remove the entire BES Client data directory. If that does not work, a restart failure is recorded.

  • BES Client Helper Status
  • Number of BES Client Restart Failures
  • Number of Data Directory Failures
  • Number of Revocations Failures
  • Number of Times Restarted

Note: All properties will be listed under the 'BES Client Helper Service' category.


Property Details

ID28
TitleBES Client Helper Service
KeywordsBES Client Helper Service Failures
Added by on 10/17/2012 1:16:36 PM
Last Modified by on 10/17/2012 1:16:36 PM
Counters 6446 Views / 17 Downloads
User Rating 1 star 2 star 3 star 4 star 5 star * Average over 1 rating. ** Log In or Register to add your rating.

Properties

BES Client Helper Service::BES Client Helper Status
Period Every Report
 
  * Session Relevance
Show indented relevance
if (not exists key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\BESClientHelper" whose (exists value "Status" of it) of registry) then "No BES Client Restarts" else (value "Status" of key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\BESClientHelper" of registry) as string
BES Client Helper Service::Number of BES Client Restart Failures
Period Every Report
 
  * Results in a "string"/number
Show indented relevance
if (not exists key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\BESClientHelper" whose (exists value "TimesFailed" of it) of registry) then "0" else (value "TimesFailed" of key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\BESClientHelper" of registry) as string
BES Client Helper Service::Number of Data Directory Failures
Period Every Report
 
  * Results in a "string"/number
Show indented relevance
if (not exists key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\BESClientHelper" whose (exists value "TimesDataDirFixed" of it) of registry) then "0" else (value "TimesDataDirFixed" of key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\BESClientHelper" of registry) as string
BES Client Helper Service::Number of Revocations Failures
Period Every Report
 
  * Results in a "string"/number
Show indented relevance
if (not exists key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\BESClientHelper" whose (exists value "TimesRevocationsFixed" of it) of registry) then "0" else (value "TimesRevocationsFixed" of key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\BESClientHelper" of registry) as string
BES Client Helper Service::Number of Times Restarted
Period Every Report
 
  * Results in a "string"/number
Show indented relevance
if (not exists key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\BESClientHelper" whose (exists value "TimesRestarted" of it) of registry) then "0" else (value "TimesRestarted" of key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\BESClientHelper" of registry) as string

Relevance

Used in 255 fixlets and 9 analyses   * Results in a true/false
Show indented relevance
name of operating system as lowercase starts with "win"
Used in 12 fixlets and 2 analyses   * Results in a true/false
Show indented relevance
name of operating system != "WinME" AND name of operating system != "Win98" AND name of operating system != "Win95"
Used in 91 fixlets and 24 analyses   * Results in a true/false
Show indented relevance
version of client >= "5.1"
Used in 3 fixlets and 3 analyses   * Results in a true/false
Show indented relevance
exists service "BESClientHelper"

Sharing

Social Media:
Share this page on Yammer

Comments

Log In or Register to leave comments!
MarkMacherey -
Only about 10 to 20 percent of my clients that have issues are actually stopped, the rest of the systems that have issues just stop communicating and stop generating a log file. The think a nice addition to the besclienthelper service would be to check for a current log and then kill and restart the client if a log doesn't exist for more then a day...