Microdyn Superuser1

How to debug problems with BOMGAR Components using a blog.ini file

Many BOMGAR Components like the Access & Rep-Console or the Jump Client & Customer Client installed on the endpoint can create a LOG-File for more in-deep investigations in connection with the use of BOMGAR Components and dependent systems.

If you want enable the creation of a Log-File for Bomgar Endpoint Components or Representative Side Software Components you can do that following this steps: 

1. open Notepad

2. copy the following text into your notepad:
[blog/debug]
output=C:\Temp\$COMPANY-$APP_NAME.log
category.All=All
flush_interval=0
file_size_limit=250M
file_size_limit_retain=10F
enabled=1

3. Save the new File as "blog.ini" on the desktop of the system where you want to turn logging on. 

4. Make sure you have a folder "c:\temp" cause this is the folder where the log-file will be written into. 

5. Start now an access console or a rep console and then a bomgar session to an endpoint and reproduce your problems. 

6. After closing the session and the console - you should find the log-file in the c:\temp folder. 

7. Don't forget to turn either logging off or to delete the blog.ini file from the desktop after your investigations are done. 

These log files are usually sent to the BOMGAR support along with a customer bug report.
 
Previous Article How to prepare and setup KERBEROS / SSO with BOMGAR PAM or RS
Next Article Cipher Suites configuration in BOMGAR Appliance to get A+ rating
Print
740 Rate this article:
4.5

Please login or register to post comments.

Name:
Email:
Subject:
Message:
x

disclaymer of warranties

All articles available under Microdyn-Wiki are published without guarantee for functionality. The published articles are intended for use by MICRODYN Employees. Use or disclosure at your own risk and danger. All manufacturers trademarks or products whitch are referred to in the wiki  are owned by their respective manufacturers.