My Biztalk Tools blog

MBV 13 is now available and fully compatible with BizTalk 2013 !

2013-05-20T09:07:00Z

Hello to the BizTalk community !

The last time I updated that blog to provide a new version of MBV is far but it took me a while to update MBV for BizTalk 2013 and collect ideas of new queries and rules to add.

For your information, a first version of MBV 13 is already provided in the support Tools folder of BizTalk 2013 !
I worked indeed with my US peers (a big thank to Mike Shea who is BizTalk Escalation Engineer in US) to produce that new version and we collaborated with the BizTalk Product group to integrate MBV in BizTalk 2013.

A first release of MBV 13 was so sent to the Product group well before the BizTalk 2013 release and since that time we continued to update the tool with additional queries and rules, and we had to fix some queries to make MBV fullly compatible with the final version of BizTalk 2013.
It is this last version of MBV 13 which is now available on my blog, and new update of MBV should be also available in each next BizTalk CUs.

MBV 13 provides the new features below :

MBV is now fully compatible with BizTalk 2013

MBV detects the new adapters provided and the additional BizTalk version, checks the build number features specific to BizTalk 2013.

New simplified UI

The graphic version of MBV was refreshed and its main window was reorganized to be smaller and easier to use.
The interface is more "flat" than before and provides so better clarity.

The format of output files changed

MBV is generating now by default a subfolder for each collect containing HTML files (and the XML and TXT ones depending of the selected options).
The output file named "MBVOutputMAINPAGE.html" is the main file to open to start the analyse of an MBV report and is composed of four frames : two of them present the list of the main report sections and the query categories, and the two remaining present the content of the selected section or query category.
This new format makes much more easy the analyze of an MBV report.

Additional queries and rules

Additional queries were added in MBV 13 about CUs, SQL, BAM, ESB, EDI, etc...
These queries and rules come from all the BizTalk community at Microsoft and my experience working with my own customers, but also from customers themselves who suggested me some ideas.
You are of course welcome to contact me to suggest queries and rules if I think they are pertinent for all the BizTalk community.

You can find this new version attached in that post.

I will continue updating MBV and its query repository,following the CUs update cycle and adding some critical rules when needed. The pertinence of MBV analyze is the key of success of that tool and comes from its queries and rules.

As usual, feel free to report me your feedbacks or submit any issues,questions or suggestions you could have about MBV.

Thanks !

Jean-Pierre Auconie
Premier Mission Critical Engineer and BizTalk Escalation Engineer
MCROSOFT FRANCE
jpierauc@microsoft.com l

MsgBoxViewer 12 is available !

2012-05-29T08:21:00Z

Hello BizTalk community !

long time I did not write a post on my MBV blog and update the tool ! I was indeed quite busy in my new role helping SharePoint developers but I always kept an eye on the BizTalk business and maintained strong relationships inside MS with BizTalk Support and Field/Consultants engineers.

Some of them reported me some MBV warnings about SQL versions which were not anymore accurate because of new SQL updates.
I also found myself the need to update rules checking the Cumulative Upates presence for BizTalk itself, BizTalk Adapter Pack, or HIS layer.
Finally, I received also requests to reduce some latency when opening large MBV report files in IE.

I decided so to work on a new major MBV version, implementing first a mechanism to generate multiple output files, updating its repository (rules and queries), its warning event mechanism , and finally fixing an issue with the MBV MMC Snapin :

1) This new version provides now a global option (in MBV GUI)  allowing to split the output report into sub-reports file and using frames for .HTML files; that option is disabled by default to keep generating a single report file (like in previous MBV versions).
When that option is enabled , MBV will create a sub-folder for each new collect with the current date/time as name and will generate in that folder several .HTML files (also  .TXT and .XML if you selected to also produce them).
Each .HTML file corresponds to a section of a single MBV report and they will be loaded in the MAINPAGE.HTML containing 4 frames :

- top left frame to diplay a list of main sub-reports to load in the top right frame
- top right frame which can change depending of which sub-report you selected in the top left frame
- bottom left frame to diplay the query categories list to load in the bottom right frame
- bottom right frame which will contain all the time the queries report.

By default I display in the top right frame the Warnings sub-report and when we click in a warning to be redirected to a query report, I just expand the corresponding query in the bottom right rame so it is a very fast link and make the analyze more comfortable.
A text status file containing all the collect activity and the errors met.will also be generated in the sub-folder.
Console version of MBV, MBVConsole.exe, provides now two options, /MRF and /SRF to produce either Multiple Report Files or a Single Report File.
If you need so to generate multiple output files and analyze the output using the frame-based page, just set the global option “Generate Multiple Files” to True in MBV GUI or use MBVConsole with the option /MRF   (Multiple Report File)

2) As requested by a major customer using MBV to monitor their BizTalk group, I updated the MBV rule engine to implement Event IDs for each warning generated as an event.
MBV provides indeed a global option (in its GUI version) to generate Application events for its warnings, but until now all the events generated had 0 as ID value; this MBV update will generate now for each warning raised a unique ID with a base event ID range that you can choose in the GUI version of MBV.

3) Finally I fixed an important issue occuring with the MBV MMC Snapin.
I recall that MBV MMC is an MMC snapin to start the BizTalk "MsgBoxViewer" tool from an MMC console and display directly inside the console the generated reports with their different sections.
MBVMMC would allow for example a BizTalk administrator to have his own custom MMC console (.MSC) integrating both the BizTalk Snap-in and the MBV one.
If yoo look indeed at the file behind the BizTalk Administration console, you can see that it is an .msc file containing both the Microsoft BizTalk Server MMC Snap-in and the Event Viewer one, so if you add in a same .msc both the Biztalk MMC snapin and the MBV one and save the MMC into the existing file “BTSmmc.msc” in the BizTalk install folder, you will see the MBV MMC in the BizTalk Admin console ;-)

This is below so a summary of the main changes made in that MBV version :

- Possibility now to generate multiple output file and display the reports in a frame-based maain page
-  Updated the BizTalk CUs rule
-  Updated the BizTalk BAP CUs rule
- Added  rukes to check for  HIS kinstalltion and HIS Cumulative Updates
- Added more KB rules in the events query (select the ”Max Events..” query to see all its rules)
-  The “Max events.. » query targets now ALL the BTS in the group and not only the server where MBV is running
-  The “Network drivers » query targets now also the BTS servers
- Added a query to get the operation history of BAM
- Added a rule checking for the failure of the BizTalk monitor job and suggesting to install CU 1 if not installed
- Updated the query to get versions of important dlls to get version of MQSeries, mqagent2, mqac.sys, etc…
- Adding two optional queries (in the “BT DBs Details” category) to get DTA tracking info per orch and per port
- Generate now a unique ID for each rule raising a warning in the Event log
- MBV MMC Snapin was fixed

you can find this new version here :

http://blogs.technet.com/b/jpierauc/archive/2007/12/18/msgboxviewer.aspx

Even if BizTalk is not anymore my core business, I want to continue updating the tool at least to follow the CUs update cycle and adding some critical rules when needed

As usual, feel free to report me your feedbacks or submit any issues or questions you could have about MBV

Thanks !

Jean-Pierre Auconie
EMEA SharePoint Development Escalation Engineer
Former EMEA BizTalk Technical lead & BizTalk Escalation Engineer
MCROSOFT FRANCE
jpierauc@microsoft.com

Integrate or Schedule MBV reports

2011-10-19T20:29:00Z

Hello BizTalk users !

long time I did not write a post on my MBV blog ! ;-)

Indeed, as mentioned in my previous blog I moved one year ago to SharePoint development business assisting my customers in their development around SharePoint, and also debugging and interacting with our SharePoint Product group to push for some hotfixes when needed, and I was very busy with that new job . Another wide product so for me to learn but the same type of challenges than for BizTalk ! ;-)

Coming back to MBV blog and this post, I thought it was needed to update more frequently my blog and talk for example today about the way to automate or schedule MBV reports, and also discuss about its possible integration with other products.

Schedule MBV reports

Maybe you don't know but MBV is provided in two modes : a GUI mode and a console one.

The filename for the GUI application is MsgBoxViewer.exe, just like the name of my tool, and the filename for the Console application is MBVConsole.exe and, as the name implies, represents the console version of MBV tool.

Knowing that the console version starts immediatelty by executing its queries and rules (without so pressing any button or validation process), you can realize that it is easy to spawn or trigger MBV from another tool, or even to schedule MBV to start it periodically using for example the Windows Scheduler or any other scheduler tool.

MBVConsole.exed provides some optional parameters to specify for example the output directory, or if you want also generate .XML file,etc...
Just type "MBVConsole /?" to display the list of possible options.

Let me clarify now the way MBV manages its settings :

MBV is keeping all its settings (global options) and also the list of selected queries and rules in a file named MBVSettings.xml.
Both Console and GUI applications will generate this file on their exit but only the GUI MBV application allows in its UI interface to modify MBV options (listed in the tab "global properties") and allows to choose the query and rules to execute.
Open that file to give you an idea of the type of properties MBV is keeping there.

Because both the Console version and the GUI one load the same settings file when found in the MBV folder, you can use so GUI application to configure the options and select the queries you want and updating the MBVSettings.xl file, and then MBVConsole can reuse it to run only the queries you selected ;-) just be sure howeever that the MBVSettings.xml file is present in the same folder than MBVConsole.exe so it can find and load it.

As I said above, you can so now start MBV from a parent tool or include MBV execution in some batch file, or even schedule it.

Read for example the interesting blog of Richard Hallgren http://www.richardhallgren.com/receiving-scheduled-msgboxviewer-reports-via-e-mail/ to receive scheduled MBV reports via e-mail.
At the time Richard wrote his post, MBV console filename was btsdbcollect.exe so you will have to replace it with its new name MBVConsole.exe

Integrate MBV reports

I notice that there is some more and more demand to integrate MBV output (the Warning sections of its html report for example) in other tools.

- If you don't use already that option, I would like to let you know that MBV offers you the posibility to generate all its warnings in the Application Event log of the server executing MBV, just read one of my previous posts detailing that option :

HOW TO use MBV as a periodic Monitoring tool alerting user of warnings
http://blogs.technet.com/b/jpierauc/archive/2009/03/23/mbv-how-to-use-mbv-as-a-periodic-monitoring-tool-alerting-user-of-warnings.aspx

- Using the "Generate XML" global option of MBV, you can ask MBV (in both the GUI and Console Applications) to generate also its reports in .XML format using a specific schema, and you can then develop any parsing tools you want to parse the .XML and produce the output you want in your own tool.
If you want to see now a great example of a such nice integration of MBV reports in another tool, I would personnally recommend to have a look on BizTalk360 product : http://www.biztalk360.com and read specially this article from Saravana :

Message Box Viewer - BizTalk360 Integration
htttp://blogs.digitaldeposit.net/saravana/post/2011/10/11/Message-Box-Viewer-BizTalk360-Integration.aspx

Well, I finished that post and I hope that it can help you or give you some idea in some possible MBV integration or MBV automation.

I admit that I did not touch my blog for a while but keep an eye on it as I will inform you there of an upcoming next build of MBV with some additional rules

Thanks !

MsgBoxViewer 11 - Compatible for BizTalk 2010

2010-09-23T16:22:00Z

Hello

A long time I did not update my blog to announce a new version of my tool ! :-)

One of the reason is that I just changed of business to become an Escalation Engineer in SharePoint Developement Support; a lot of work and topics to learn in perspective so but I wanted to enlarge my skills set.
I change of business but I still continue to have an eye on BizTalk of course :-)

I also spent some time these past months with my former BizTalk colleagues to try to identify a process and people responsible for futur MBV updates, and help for quick and easy next updates of MBV.
I had so to change the MBV architecture and redesign completly my tool MBVQueryBuilder to make the query or rules update a task much more easy.
Next MBV updates might be done so mainly by the Biztalk Support team with my contribution.

Finaly I spent time to update MBV to make it compatible for BizTalk 2010 (the Class Settings query reported indeed wrong changes for example) and this is this new version that I put here

This version brings also two major changes :

1) MBV is compiled now to target .NET 2

You can ask yourself why MV was targeting until now only .NET 1.x ?? it is for the simple reason that MBV remained always compatible for BizTalk 2004 and that it should be able to run on BizTalk Server 2004 Servers where only .NET 1.x could be installed

This change means so that it can not run anymore on a BT 2004 box with ONLY .NET 1.X installed, but honestly do we meet frequently such configs now ? :-) and anyway you know that you can run MBV on any type of Servers and not only BT ones

2) MBV is not anymore a single .EXE but it is composed now of the following files:

o   MYHC.DLL : Implement my custom Health Check engine

o   MYHCQUERIES_MBVQUERIES.DLL : Contains the entire MBV repository and custom Query functions to analyze a BizTalk Group

o   MSGBOXVIEWER.EXE : GUI MBV Client tool

o   MBVCONSOLE.EXE : Console MBV Client tool

Reasons for this split are mainly the following ones:

o   Query repository grow too quickly, need so to separate it from the clients .exe
o   Health Check engine should be updated w/o the client tools using it
o   Need to update easily MBV Repository w/o recompiling the client tools
o   As MBV is just a client tool of my generic health Check engine, it can load any type of Query repository (DLL or XML) and not only the BizTalk one

You have the right to prefer the single binary version so in this case I can only suggest you to keep using the old build :-) but you will not benefit of additional rules and queries

you can find this new version here :

http://blogs.technet.com/b/jpierauc/archive/2007/12/18/msgboxviewer.aspx

As usual, feel free to report in this blog your feedbacks on the tool, your suggestions for new features or improvements, and any kind of problems you could meet using MBV

and many thanks to all of you who already sent me good feedbacks ! ;-)

New Features :

-          Compatible for incoming BizTalk 2010
-          Add additional query to get retrieve part of Biztalk 2010 Dashboard Settings
-          Detect if CU3 is installed on each BT Server
-          Get Perfmon counters for ALL BT Servers (and not only the local server)
-          Get Perfmon counters for MsgBox Db SQL Servers (SQL General statisitcs, SQL locks, SQL Databases)
-          Add order delivery and other port settings in the "Send ports" query
-          Add query to get custom settings of each Send Port: Not checked by default
-          Add query to get custom settings of each Receive Location: Not checked by default
-          Check for small or default value in WCF ReceiveTimeout binding property
-          Check for MQS port configured w/o Tx
-          Check for WMI prop “ClearAfter” too large value : Error CLSID_PropertBag
-          Format better BAM config info report output
-          Added Latest new MSDTC /COM+ packages version info
-          Get Last X rows from Spool and Instances tables : rows number is configurable as a query property
-          Raise a warning in MBV if the CustomSD key is found under HKLM\System\Current Control Set\Services\Eventlog\Application
-          Rule to check for KB 980560
-          Rule to check for KB 979709
-          Rule to check for KB 979095
-          Add more info in the “BizTalk Group” category of the SUMMARY REPORT section
-          Improved query to get sucessfully all GAC assemblies
-          Updated Latest BT Mgmt Pack version check
-          Get Pipeline ID in Pipeline Query Report
-          Get the Transport Type used in “WCF Custom” port
-          Redesigned the DialogBox UI to add custom Rules and be able to raise different type of actions
-          Redesigned the main dialogbox of MsgBoxViewer.exe (gui version)

New MBV builds : Lot of additional queries and fixes

2009-12-07T17:32:00Z

Hello,

I updated today a new build of MBV.

With the previous one published few weeks ago, MBV brings now lot of new interesting queries and fixes (see below the complete list).

As interesting new query, MBV is parsing now your SQL Error logs for critical errors and raise corresponding warnings if found.

MBV is reporting now also the SQL agent log containg any errors if the BizTalk jobs are failing.

MBV includes also now the "tempdb" inf Db analyzed so you can see quickly in MBV report the size and files info about your temp. Knowing as important the tempdb is, it can be useful to have this info in report as well.
I added also again some new parsing rules for the Eventlog query identifying so possible know issues bases on the event source, event ID, and the event message contain.

Feel free so to use now latest version on my blog (http://blogs.technet.com/jpierauc/pages/msgboxviewer.aspx) containing these features and report me your comment or bugs found

Thanks !

New Features:

- Include "Tempdb" info on the "Dbs infos", "Dbs Files", and "Dbs Space" queries
- Query to get list of IIS App pools with their owning Applications and check if an Application is a BizTalk Receive Location
- Query to get list of Web sites with all their propertes App pools with their owning Applications and check if an application is a BizTalk Receive Location
- Get list of active global SQL Trace flags
- Query to get the SQL agent log
- Changed the KB linked to the warning message when AllowOnlySecureRpcCalls is not set correctly on cluster
- Fixed HotFix queries to get also the 32 bits installed on a X64 machine
- Display now HotFix file(s) with their version
- Fixed the .NET config files to have also the ones from 64 bits version of the Framework
- Get also BTSNTSVC64.exe.Config if found
- Order by DESC the Most recent records in TDDSFailedTRRackingData table for both DTA and BAM dbs
- Fixed an HTML display issue (report can be expanded correctly ) when we fail to connect to some Dbs
- Added Autogrow rules for the "DBs File" query to check the current auto grow of BizTalk Dbs against our recommendations for MDF and LOG files- New query in “Server Info” category: “NET Config files” on all BT servers - not checked by default
- New query in “Server Info”: “Running Processes” on all servers
- New query in “Advanced DB Info” category: “Tracking tables Sequence Number” - not checked by default
- New query in “Advanced DB Info” category: “Tracking tables Sequence Number gaps” - not checked by default
- New query in “Advanced DB Info” category : “Tracking tables Sequence Large BLOBs” - not checked by default
- Provides a rule raising a warning if large table “NotEqualPredicateTables” found (known issue)
- Provides additional EventsLog rules
- Improves MsgBox Database naming convention in some Summary Report categories to be unique in multiple MsgBox scenarios
- Provides “Total Q rows” entry in the “MsgBox Table” Summary Report category
- "Current Error Log" query is modified to list entries in Descendant order
- Provides some rules to the "Current Error Log" query to check for Disk space errors, Db Integrity or Fatal errors, and raise warnings if found
- "Error Log.1" request in now moved into its dedicated query - not Checked by default
- Host instance "Start time" is now added in Topology Report "Running Host instance" category
- System Variables are added in Topology Report

Webcast MsgBoxViewer

2009-10-24T08:24:00Z

Hello,

I did recently a webcast about MBV for the UK SOA/BPM User Group (SBUG)

Link to the video is available here : http://geekswithblogs.net/michaelstephenson/archive/2009/10/13/135448.aspx

I would like to thank Michael Stephenson for this web cast invitation which was a good opportunity for me to explain MBV goal and its usage and do some Q&A with participants !

Fixed a regression issue found in MsgBoxViewer 10.15 and implemented Query Timeout for .VBS queries

2009-10-09T16:23:00Z

Several customers and MS engineers reported me recently some very long collect statements scenarios using version 10.15 and sometimes infinite ones.

1) Some bugs were indeed identified in some VBS queries which might create looping scenarios in some VBS query execution .
These bugs were so fixed.

2) A long collect statement can occur also when .VBS queries (belonging mainly to the “Server Info” query category) are running too long time.

MBV 10.15 enumerates indeed in some .VBS queries some registry keys or registry values, and when targeting several remote servers of the BizTalk group it can be sometimes long.

I decided so to implement a timeout mecanism to stop a VBS, .BAT, or .CMD query after 30 secs by default.
This timeout value can be changed of course in the MBV UI via the "VBS/BAT/CMD Query Timeout" Global Option.

3) When you have a long query situation or infinite one, please do the following :

- Note in the status bar of MBV UI the pending query (it will be also logged in the Status log file)

- Kill MBV (as stopping via the UI the collect statement during a query execution will NOT work, I don’t want to kill my query execution thread)

- Keep the generated status log file and send it to me later (it is precious for me to know what happened before MBV was killed)

- Restart MBV and then uncheck the queries which seem to run too long or infinite and then start a new collect statement (usually these queries should belong to the “Server Info” category) to exclude them from the collect statement

Current build 10.15.7777 available on this blog contain both the VBS queries fix and the VBS Query Timeout implementation.

Sorry for these introduced regressions and continue to send me your feedbacks or possible bugs found

JP.

MsgBoxViewer 10.15 now available

2009-10-05T22:32:00Z

Hello,

I just made available version 10.15 of MBV : http://blogs.technet.com/jpierauc/pages/msgboxviewer.aspx

This build fixes some bugs of version 10.14 of course but provides also lot of new queries & rules and use now some VBS queries like "MSDTC Setting" , "RPC Settings"', 'TCP Settings", etc...

Using VBS script with WMI calls in these queries allow to target correclty this time 64bits registries on 64 bits Servers.
As you probably now, a 32 bits tool like MBV using .NET remote registry functions can target only the 32 bits version of registry on a 64 bit server (by design with .NET) , so until now MBV returned sometimes invalid MSDTC settings for example when targeting 64 bits servers.
Using WMI in VBS script can workaround this limitation specifying the type of provider to load (32 bits or 64 bits).

I added also some new queries and one interesting query I added is the "Artifacts per host" one which list all artifacts used by each host.
For our Support teams for example, it is indeed critical to see very quickly which host manage which type of artifacts.

I also identify now what we name COM+ or MSDTC "Rollup package" from the software layers found on each server. We have again some dependencies with COM+ and obviously MSDTC so it is is important to know which COM+ or MSDTC version is installed on each server before to decide to apply possible COM+/MSDTC hotfixes.

You will find the list of new features in this version here : http://blogs.technet.com/jpierauc/pages/msgboxviewer.aspx

Feel free to report me your comments, suggestions, and of course the bug you could find ;-)

Thanks

MBVMMC - Latest Version

2009-08-16T11:03:00Z

Version 1.10

New features :

- Allow to generate also automatically and periodically MBV reports by creating a Windows Scheduled Task

- Group now the MBV reports per targeted BT group

- Display an exclamation mark in node for MBV Reports having Red Warnings

- Use now File Notification Services to detect new or deleted MBV reports in monitored output folder

Version 1.0

Features :

- Allow to generate manually MBV reports by running in hidden mode the console version of MBV (BTSDBCOLLECT.EXE)

- Create nodes list corresponding to generated MBV reports found in the monitored output folder

- For each MBV report node, sub nodes are created to represent each section of an MBV report

- Allow to access directly to a MBV report Section like the "Warnings" one

- For each selected section node, right view in the MMC show the corresponding MBV report section in HTML format

MMC Snap-in for MBV now available !

2009-07-15T11:03:00Z

Hello.

As I announced in a previous post, I just released a MMC Snap-in for MBV.

To be honest, I did not have ideas about really new useful features I could add in MBV itself or around MBV but reading some posts on other blogs talking about BizTalk Admin and suggestions of a better integration with MBV, I thouht : eh maybe I could integrate MBV in an MMC !

Doing that will allow so any BizTalk administrator to have for example his own custom MMC console (.MSC) by adding the BizTalk Snap-in and the MBV one !

If yoo look at the file behind the BizTalk Administration console, you can see that it is an .msc file containing both the Microsoft BizTalk Server MMC Snap-in and the EventViewer one; so you could create easily for example your own .msc adding BizTalk Snap-in, the Eventlog one, and MBV Snap-in

So I created a MMC snap-in for MBV in C# using the MMC 3.0 SDK: what is easier to develop an MMC Snap-in using .NET ! :-)

Setup:

just run the setup.exe on your machine to register the snap-in automatically

This snap-in use .NET 2 so on a BizTalk 2K4 machine, the setup can propose you to download the .NET 2. framework.

This snap-in use Microsoft Mgmt Console 3.00 framework on a W2K3 machine,you may have also to install KB 907265 :

http://www.microsoft.com/downloads/details.aspx?FamilyID=4c84f80b-908d-4b5d-8aa8-27b962566d9f&displaylang=en

One the setup finished, open MMC console and choose to add a Snap-in.
You should see in the list "MBV Snapin".

The first version of this MBV snap-in I release allow to run a collect statement in the MMC by starting in an hidden mode the console version of MBV tool : "BTSDBCOLLECT.EXE".

When you add first time the Snap-in, a dialogbox will be displayed inviting you to specify local path of MBV Console tool BTSDBCOLLECT.EXE.
Once it is one, you can also select the profile to use among the profiles present (created by GUI version of MBV) and then the MBV Snap-in will be added in the MMC console.

'MsgBoxViewer' Node

The 'MsgBoxViewer' MMC node will then allow you to start a Collect statement, change settings, open status file or History File or delete all HTML reports appearing as childre nodes.
This node display also as children nodes the existing HTML reports found in the HTML folder (either the one configured in selected profile file 'MBVSettings....XML' or by default the folder of MBV tool).

Starting a Collect statement

When you put the focus on 'MsgBoxViewer' node, right-click on it and start a collect statement, the MMC display in the right pane the resulting cmd line executed, and the status bar will show all the steps of the Collect statement.

At the end of the collect statement, the MMC will add in the left pane a children node representing the MBV HTML file produced and will show this file in the right pane.

Complete status of the collect is displayed in the right pane when selecting back the node 'MsgBoxViewer'.

Open an existing HTML MBV Report

Once you clicked a section (sub-node) of an HTML report node in the treeview of the left pane, you have immedialtely on the right pane of the MMC the selected sectioj of HTML MBV report displayed like in the Internet Browser.
You can so display quickly a Warning Report sectrion of an existing HTML Report.

Change Settings

Right-cliking on 'MsgBoxViewer' node and selecting the 'Settings" action, you can change the global settings and for example selectb the MBV profile to use for the collect, that you have prepared before with gui version of MBV.
Selecting a profile in the snap-in allow so to run only the queries you selected with also the global options you configured in the gui version of MBV.

Download here latest version :
http://blogs.technet.com/jpierauc/archive/2009/08/16/mbvmmc-latest-version.aspx

Let me know please your comments and questions on this Snap-in and any bugs you could find

Thanks !