Skip to content
Branch: master
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
AnotherRelevanceTester.ojo Update AnotherRelevanceTester.ojo Sep 10, 2018
AnotherSessionRelevanceTester.ojo Update AnotherSessionRelevanceTester.ojo Sep 10, 2018
BaselineStatusResults.ojo
BigFixGlobalSearch.ojo Update BigFixGlobalSearch.ojo Jan 31, 2017
BigFixGlobalSearchListJS.ojo Update BigFixGlobalSearchListJS.ojo Jul 7, 2017
ClientSettingsManager.ojo Update ClientSettingsManager.ojo Feb 8, 2017
ComputerGroupTemp.ojo Add files via upload Aug 30, 2018
ComputerSummary.ojo Update ComputerSummary.ojo Jan 27, 2017
Computer_Comments.ojo
Computer_Filter_Search.ojo Update Computer_Filter_Search.ojo Sep 5, 2018
Dashboard_Variables.ojo Update Dashboard_Variables.ojo Oct 3, 2018
DeleteCommonShortcuts.ojo Update DeleteCommonShortcuts.ojo Oct 23, 2018
DockItemManager.ojo
GenericDataTables.ojo Update GenericDataTables.ojo Nov 27, 2018
HelloWorld_template.ojo Update HelloWorld_template.ojo Oct 29, 2018
HiddenContentAudit.ojo Update HiddenContentAudit.ojo Jul 8, 2017
IE11_DashboardTemplate.ojo
IntelVproStatus.ojo Update IntelVproStatus.ojo Jan 13, 2017
JavascriptDebugging.ojo Update JavascriptDebugging.ojo Jan 19, 2017
JavascriptDebuggingIE11error.ojo Add files via upload Feb 1, 2017
LargeContent.ojo Update LargeContent.ojo Jun 28, 2017
PropertyEvaluationAudit.ojo Update PropertyEvaluationAudit.ojo Dec 21, 2017
README.md
RelayCacheSizing.ojo Update RelayCacheSizing.ojo Jul 8, 2017
ReportingPieCharts.ojo Update ReportingPieCharts.ojo Jan 12, 2017
Screenshots.ojo Update Screenshots.ojo Nov 8, 2018
SessionRelevanceInspectors.ojo
SessionRelevanceProperties.ojo add SessionRelevanceProperties.ojo May 15, 2019
SlickGridExample.ojo Update SlickGridExample.ojo Oct 16, 2018
StopOpenCompletedActions.ojo Update StopOpenCompletedActions.ojo Jan 12, 2017
about_blank[1].html Create about_blank[1].html Oct 29, 2018

README.md

Try these self directed Dashboard Labs:

This is probably the quickest way to get started with Dashboards and learn about them.

Example Dashboards:

This folder contains Dashboards / Wizards for the BigFix Console.

What is a Dashboard?

What is a Wizard?

How are they different than a Custom Web Report?

  • They are all basically the exact same thing.
  • Any Custom Web Report could be a Dashboard or Wizard
  • Any Dashboard or Wizard that primarily uses reports could be a Custom Web Report.
  • The main difference is that a Wizard is expected to have multiple "Pages" and "Steps" that are separate HTML documents internally. Dashboards and Custom Web Reports are expected to be a single HTML document, but through use of JavaScript, that single HTML document could have a wizard within it, or some other method for emulating multiple "Steps", though it could also be anything else.
  • a Custom Web Report is within a WebReports context, while Dashboards & Wizards are within a slightly different BigFix Console context. This means there are a few things that work in one and not the other. Generally Dashboards & Wizards are more capable than Custom Web Reports.

How are all of the above different than a Client UI Dashboard?

  • The most significant difference about a Client UI Dashboard vs the others is that the Client UI Dashboard can only work with the single computer that it is running on, and cannot use Session Relevance. While the others (Dashboard/Wizard/WebReport) can provide summary results from multiple computers, they don't have to, which means if you have one that displays data from a single computer, then it is nearly identical to a Client UI Dashboard. The real power of Dashboards/Wizards/WebReports is that they can work with results across multiple computers, so using them for a single computer is a very simplified use case, but that doesn't change the fact that you could have a single unified view of a single computer across all of them, including a Client UI Dashboard.
  • In order for this to really be the same, the Dashboard or WebReport would have to provide a way to pick a single computer to view the data, while the Client UI Dashboard would only work with the computer it is on.
  • The other part that is needed is that the Client UI Dashboard would be powered by client relevance while the Dashboard or WebReport would have to rely on Session Relevance from Properties that use the same underlying client relevance behind the scenes.
  • The computer summary view within the BigFix Console is effectively an example of a single computer view "Dashboard" or "WebReport" that could just as easily also be a Client UI Dashboard. Similar can be said of the similar views within Bricks or the Computer Browser.

What about the BigFix Console? How is it similar to the above?

  • The Windows BigFix Console is a mix of native views and HTML views wrapped up in a complicated application.
  • It can almost be thought of as a Dashboard of Dashboards.

Options for using Dashboards:

  • Put the dashboard files in a folder, then load dynamically using the Console's Load Wizard option in the Debug Menu.
    • Placing the files in a folder before loading with the console is important, because the console will copy the entire contents of the folder.
  • Add the dashboard files to a custom site.

Get fully rendered HTML for debugging:

Important files for Dashboards:

  • C:\Program Files (x86)\BigFix Enterprise\BES Console\Reference\wizards.js
  • C:\Program Files (x86)\BigFix Enterprise\BES Console\reference\common.js
  • C:\Program Files (x86)\BigFix Enterprise\BES Console\Reference\BESOJO.xsd

Load javascript libraries from CDN with fallback:

<script src="//ajax.googleapis.com/ajax/libs/jquery/1.5.1/jquery.min.js"></script>
<script>window.jQuery || document.write('<script src="js/libs/jquery-1.5.1.min.js">\x3C/script>')</script>

An even better option: https://github.com/jgstew/bigfix-content/tree/master/fixlet/javascript

Dashboard Ideas:

  • Delete help duplicate computers
  • Remote Command-Line
    • select computer to target
    • take input of arbitrary commands
    • output results to file
    • attempt to send back results using cURL / WebSocket
    • read back results using BFQuery and/or Analysis
    • Very Similar idea as https://github.com/jgstew/remote-relevance
  • Dashboard to help write session relevance for computer reporting: https://bigfix.me/relevance/details/3020326
  • Deploy any fixlet or task or baseline with gradual roll out relevance added automatically
  • MO Console Operator Management
    • help disable users that have not logged in over X days
    • delete console users that have been disabled for X days
    • help manage roles
    • help provision users
    • help with computer assignments
  • Improved Fixlet Maker Dashboard - something to make content from templates
  • Dashboard to help make parameterized fixlets
  • "Computer Controller" - pick a particular computer from a table, then control it specifically
    • get state from analyses and BFQuery
    • check state changes using BFQuery and/or notify client forcerefresh
    • provide feedback on time of last update of displayed data, calculate age in JS, allow refresh with BFQuery if older than X time.
    • some basic computer info
    • some info on: current user / apparent primary user / assigned user
    • shutdown
    • restart
    • mute/unmute/volume
    • screen brightness
    • screenshot
    • RDP/VNC?
    • log collection & troubleshooting
  • Recently Modified Custom Content

References:

Examples:

Related

You can’t perform that action at this time.