Has anyone experience with using MBAM with SCCM? Might want to pick your brains. There's plenty of documentation out for SCCM 2012 but very little for SCCM 2016. Also the UI for the configuration wizard isn't great. Form fields don't read very nicely. Why must all these teams in Microsoft reinvent the wheel? What was wrong with edit fields? Why did they feel the need to mess with a perfectly good standard? Surely they had better things to do with their time? Then the documentation. It's not so bad I suppose. But I'm giving it a domain account. Why can't it just provision the database and then the right permissions ofr that database. Why do I need to create the accounts then create the permissions that are needed on the database before the database is created. Seems like a waste of time for me. Given that even I could run up some code that creates a database then associates a domain account with that database while giving it just the permissions it is going to need. It seems like lazy development in my opinion. Sorry. I'm ranting. I read the MS documentation on why this is going to save me problems down the line and though to myself, why not. I'll quickly add this to my SCCM server. I didn't think I was going to have so many hoops to jump through. Anyone want to chime in? I'd be interested in your experiences with MBAM. Do I have much more of this messing to look forward to? Currently waiting on yet more validation on a configuration wizard. Darragh Daunted but not defeated by the Drudge of daily fighting with enterprise tech to make it do what I want.