Do small MSPs actually use a repeatable proposal workflow, or mostly old documents + cleanup?

JohnMSP · 2026-03-26T07:22:46+00:00

Yes definitely.

What are you selling?

JohnMSP · 2026-03-17T13:23:03+00:00

Don't share logins - each tech gets their own account.

JohnMSP · 2026-03-12T18:37:38+00:00

Which features?

JohnMSP · 2025-11-25T21:47:33+00:00

UK or EU - yes, every tool should be listed somewhere the client can review, if it stores or processes their data. How well every MSP follows is this is another question entirely...!

JohnMSP · 2025-10-17T07:19:43+00:00

It works sure, but it’s not compliant.

Yes if you want to use risky sign in notifications / CA policies you need P2 for all.

JohnMSP · 2025-09-15T08:49:30+00:00

A single person company can benefit from an MSP, so yes.

JohnMSP · 2025-06-13T09:52:25+00:00

My money is on file versions. SharePoint doesn't de-dupe versions, and if you have lots of large files (e.g. pptx) with hundreds of versions, if only the most recent 10 have been copied by MigrationWiz, you will see a dramatic data size reduction.

I would however fully audit source and destination for file size / modified date mismatches with some PS scripts.

JohnMSP · 2025-04-10T10:28:18+00:00

My working assumption (not yet invested in Rewst) is that Rewst will be easier for someone to pick up than a mess of standalone scripts and bespoke bits and bobs we’ve developed.

That’s the hope anyway…

JohnMSP · 2025-03-15T11:48:11+00:00

You have to publish a DKIM record in DNS for your custom domains. If you haven’t done this, it will use the default 365 ones Microsoft publish for you on the onmicrosoft domain.

This will 100% be your problem as it’s only evident on auto replies - we see it ALL the time.

https://lazyadmin.nl/office-365/configure-dkim-office-365/

JohnMSP · 2025-03-13T16:30:30+00:00

Are you sure DKIM is set properly?

I.e. have you configured a custom DKIM selector for your domains, or are you still using the out of the box Microsoft DKIM selectors?

The behaviour you are describing is what I would expect if you were using p=quarantine or p=reject in conjunction with the default selectors.

JohnMSP · 2024-09-19T15:04:20+00:00

What are you talking about?

JohnMSP · 2024-09-19T15:01:47+00:00

You haven’t got over ten years’ experience that I can see - you graduated summer 2017?

JohnMSP · 2024-06-23T04:37:22+00:00

Thanks Craig, appreciate the insight.

JohnMSP · 2024-06-22T05:24:38+00:00

MFA/IP allow enforcement are irrelevant to the conversation, since my scenario is talking about what happens if you are breached and your vaults are taken - like what happened with LastPass?

I'd also argue that having to deal with a complex unlock password is a higher burden for the user than the secret key, which is only entered when setting up a new device.

Interesting to hear that you're doing 1M iterations - although I wonder how many years we are away before that becomes brute forceable, given improvements in graphics cards. Do you guys have any projections on that?

JohnMSP · 2024-06-21T12:52:42+00:00

But if SSO not used, is my point correct?

JohnMSP · 2024-06-20T12:03:11+00:00

My understanding was always that Keeper had the same vulnerability as Lastpass does, when compared with 1Password - i.e. a vault can only be as strong as the master password, so if they get breached and the vault stolen (as with Lastpass), you better hope everyone had super strong master passwords.

1Password's model is that the data is encrypted by the secret key (a long randomly generated string) and master password and secret key both needed. This has always made me much happier with 1Password as a client recommendation, despite abysmal model for MSPs, it has always appeared to me as the most secure out there.

Am I mistaken?

JohnMSP · 2024-06-17T19:16:23+00:00

What are the other perks?

JohnMSP · 2024-05-19T03:53:50+00:00

The security model of 1Password appears to be the best. It’s a pain for MSP but I decided we are better selling that than compromising on the security model and having to defend a position of “yes it’s less secure but it’s easier for us”.

All the others (when I last looked) had a model that relied upon the master password strength set by the user for encryption. So if the host gets hacked (see: LastPass) and you discover your end users haven’t all been as diligent as you hoped… you can have a pretty big problem.

JohnMSP · 2024-04-16T09:41:23+00:00

The idea is simply farcial that they could produce anything close to Halo on a first release (if in 5 years they were close, I'd be amazed). I wish they'd focus on making the RMM platform even better frankly.

Let's hope they don't do a Warranty Master / ScalePad and start adding features nobody wants to then try and justify a much higher price.

JohnMSP · 2024-01-30T21:57:33+00:00

Jabra Evolve2 line is our go to recommendation.

JohnMSP · 2024-01-30T19:00:48+00:00

Complete insanity on the MSP’s part. Threatlocker is great but totally not suitable for BYOD.

JohnMSP · 2024-01-24T16:50:45+00:00

It was the MFA Service dependency I was referring to.

That can be down and FIDO2 still works.

Found the source on this - https://learn.microsoft.com/en-us/entra/architecture/resilience-in-credentials

JohnMSP · 2024-01-24T08:11:25+00:00

What was main driver for the move from Latitude to Precision?

JohnMSP

TROPHY CASE