Improve the hotfix and service pack install experience
For a hotfix, (such as dec 2016 update) customers have to UN-necessarily uninstall mbam server components on the MBAM server and ConfigMgr server and then go through the rigmarole of re-installing them, and that requires that all the data that is needed for the wizard must be re-entered again, this is painful and unnecessary
the mbam wizards should (imho) be clever enough to auto-populate the data that you entered previously and give you the change to confirm that data and even do it via PowerShell, this is such a time waster particularly when you have to do it on more than one server and a few months apart too (sep and dec releases)
Same thing with the Client utility, KB patch 2016 must be uninstalled, before installing KB patch 2017. This is headace for the SCCM distribution point of view.
Lee Witchey commented
Agree! You got my vote.
And the documentation must get better..
Nash Pherson [MVP] commented
Argh... that means if you installed on SQL 2014/earlier and upgraded to SQL 2016, you will end up hosed by the installer bug where they hard coded the sql version check instead of saying 'at least'. https://mbam.uservoice.com/forums/268571-microsoft-bitlocker-administration-and-monitoring/suggestions/17900854-add-support-for-installing-mbam-with-sql-server-20
John Bernas commented
Voted, thanks Niall.
Agree thanks for creating this. It is odd you have to rip out this product to update or patch.
Zeng Yinghua (Sandy) commented
Thanks Niall for creating this idea! It doesn't make any sense have to uninstall mbam server components when try to install hotfix.
Niall Brady commented
it's listed as supported here https://technet.microsoft.com/en-us/itpro/mdop/mbam-v25/mbam-25-supported-configurations
Can this integrate with CM if CM is on SQL 2016? I still don't think it can. For that matter can it run at all on SQL 2016?