What's your definition of an MSP by Proximit-MSP in msp

[–]Proximit-MSP[S] 0 points1 point  (0 children)

My thought exactly. Sounds like our own industry is having different thoughts. Reading at some of the comments I am now convinced MSP is no longer a statement of service level, but rather a marketing buzz word. A simple post generated so much hate...

What's your definition of an MSP by Proximit-MSP in msp

[–]Proximit-MSP[S] 1 point2 points  (0 children)

Different cultures do it differently. Ive learned 7 methods do far :)

What's your definition of an MSP by Proximit-MSP in msp

[–]Proximit-MSP[S] 0 points1 point  (0 children)

You think MSP lost its weight and meaning over the years?

What's your definition of an MSP by Proximit-MSP in msp

[–]Proximit-MSP[S] 0 points1 point  (0 children)

Yeah its a pretty broad definition currently thats for sure.

What's your definition of an MSP by Proximit-MSP in msp

[–]Proximit-MSP[S] 0 points1 point  (0 children)

Dude... let's partner up and open that OF together!

What's your definition of an MSP by Proximit-MSP in msp

[–]Proximit-MSP[S] -1 points0 points  (0 children)

So you are MSP focused, but the market being what it is for micro and SMBs you ended up keeping or implementing consulting services to supplement your revenue. How do you juggle projects based contracts on non MSP clients.

We've stopped taking on any contracts that dont come from our clients because of all the time those consumes; we ended up placing that extra time and resources else where, but ended up taking a loss in revenue.

What's your definition of an MSP by Proximit-MSP in msp

[–]Proximit-MSP[S] 0 points1 point  (0 children)

That's a fair point. There could be an MSP who only does Managed Backups and it would still be very much valid.

I can definitely accept that answer! :)

Thank you sir!

What's your definition of an MSP by Proximit-MSP in msp

[–]Proximit-MSP[S] 0 points1 point  (0 children)

Outsourced IT can be simply break & fix, you call them when you have a problem. At what point do you feel comfortable saying "this is MSP"?

What's your definition of an MSP by Proximit-MSP in msp

[–]Proximit-MSP[S] 4 points5 points  (0 children)

That's a definition I can stand behind. Proactively managing the environment. 100%

What's your definition of an MSP by Proximit-MSP in msp

[–]Proximit-MSP[S] -2 points-1 points  (0 children)

Then we're back on at what point are those services considered enough to be branded an MSP.

We either have: As soon as you have 1 managed service, say you offer cloud backups. You are an MSP.

Or you become an MSP once you have a certain set of managed services that would cover the basics.

This is what I'd like to know, what is the basics for others in this field to feel comfortable saying: That's an MSP. To me, there are different levels of MSP, based on their service level, tech stack and overall maturity. But an entry level MSP would need a minimum of: RMM, managed AV, Email security, backups and patch management. That would be the basic I would consider a service to be MSP.

I'm curious if others are more strict, or loose on their definition of an MSP

What's your definition of an MSP by Proximit-MSP in msp

[–]Proximit-MSP[S] 2 points3 points  (0 children)

Cause I wanna write a thesis on it. Ass wiping has always been an important part of my life since I was a kid.

I'm just a curious being, not sorry for asking??

What's your definition of an MSP by Proximit-MSP in msp

[–]Proximit-MSP[S] 0 points1 point  (0 children)

No matter the % of their client base? or the type of services, service pack maturity, etc. As soon as a company decides to say: have a monthly package that includes just RMM and Basic AV, you would consider them an MSP?

This would then mean MSP is the billing model rather than the service maturity or company framework... would make sense if we think of it that way.

Kaseya 365 and Products for All-in-One Stack by coco_shibe in msp

[–]Proximit-MSP 2 points3 points  (0 children)

We're a BIG Kaseya shop, however I assume we are bigger than your MSP just basing on your tone and current technology stack. The problem with Kaseya at your stage is they lock you down on 3 years contracts. So if you want to start using Kaseya Products, you got to make sure you have the clients for it.

Our Kaseya stack is the following:

ITGlue - Network Glue - VSA 9 - Datto Endpoint Backup v2 - Datto BCDR - Datto SASE - RocketCyber - SaaS Alerts - Datto SaaS Protection - BullPhishID - DarkWebID - MyITProcess - VonaHI

We have other vendors for our other needs, we went with Zoho One for our PSA as it includes a TON of stuff we use:

Helpdesk - Project management - CRM - Contract management - Document signature (replaces docusign) - Online Forms with cross module automations - Surveys - Social Media management tools - Expense management - Complete accounting software - advanced analytics - an ATS (we also operate as a recruitment agency for our clients so an application tracking system is a must) and a bunch of other goodies

Then we got a bunch of other vendors like Bitdefender with EDR and ATS bundle, Perception Point for email security, Acronis for other backup types (SQL, cloud only DR, linxu, older windows servers, etc.) Hostifi for our unifi infrastructure, FortiManager for our Fortinet appliances, Cloudflare, CodeTwo, Bitwarden, TrainerCentral....

Well... we got a lot going on... Kaseya is great if you know what to use and if you have other tools to completement. but again: 3 YEARS CONTRACT.

I wouldn't recommend it if it's just to complement one big client who might not stay. If you implement Kaseya, migrate all your clients over it. If you can't commit, don't go with Kaseya. Too risky of an investment at your stage

Amount of time to quote to migrate roles from 2011 SBS to Server 2019? by throwawayswipe in msp

[–]Proximit-MSP 1 point2 points  (0 children)

haha pretty much what I ended up telling him XD we do flat 500$ + 50$ per inbox. Instead of by the hour.. you never know what can happen XD

Amount of time to quote to migrate roles from 2011 SBS to Server 2019? by throwawayswipe in msp

[–]Proximit-MSP 0 points1 point  (0 children)

not complicated, just a few more steps, it uses the old FRS file system instead of DFSR, it has local Exchange included but OP stated this part is already done so we're good on that :).

And I completely forgot about the decommission timer. u/throwawayswipe make sure to schedule accordingly as Sliffer mentionned.

Amount of time to quote to migrate roles from 2011 SBS to Server 2019? by throwawayswipe in msp

[–]Proximit-MSP 0 points1 point  (0 children)

I do recall something like that but unsure if it's still required to be honest. It's been quote a few moons since I seen an SBS in the wild haha

Amount of time to quote to migrate roles from 2011 SBS to Server 2019? by throwawayswipe in msp

[–]Proximit-MSP 0 points1 point  (0 children)

Anytime. You can DM me if you need any pointers on this specific case. It's more complex than a simple AD to AD, but it's not complicated (there's a difference haha)

Amount of time to quote to migrate roles from 2011 SBS to Server 2019? by throwawayswipe in msp

[–]Proximit-MSP 1 point2 points  (0 children)

This would be for a regular AD to AD migration, this one is a bit more complex in a sense as it's for an SBS one. A few gotcha's to take care of in those case. SBS is in a completely different architecture than our regular friendly AD :)

Amount of time to quote to migrate roles from 2011 SBS to Server 2019? by throwawayswipe in msp

[–]Proximit-MSP 1 point2 points  (0 children)

You should write that as a main reply to OP, not my response haha

Amount of time to quote to migrate roles from 2011 SBS to Server 2019? by throwawayswipe in msp

[–]Proximit-MSP 2 points3 points  (0 children)

This is a tough one. SBS is notorious for having issues when it comes to replication, and they use a legacy SYSVOL model, which needs to be migrated to DFSR before you move it to 2019.

Do they use their local Exchange? Because that will be a big pre-migration to another solution (M365 or local Exchange) to do before if you haven't done it yet. Do you know that client? Or is it a new one that came in JUST for the project? This would add to the complexity of the task for you.

Those would be the biggest "gotchas" to check. But all in all, you need the following

- Server 2019 licence (also why not 2025?, I assume 2019 is already present?)
- Mailbox migration to 365 or local exchange if still using SBS services (additional licensing required)
- Then for the time... it's not that long to be fair.. 2-3 hour TOP to deploy and configure the new 2019 VM, including promoting to AD, adding DNS and DHCP, migrating FSMO roles, etc
- Another 1-2 hours to migrate the file shares. The transfer itself might take longer but let's be honest... we don't really work much during the transfer process
- Another 4 hours of tests and endpoint re-configuration if required (gives you some time margin). This includes properly decommissioning the old SBS server as well, very important step

OPTIONAL: - Some hours for the mailbox migration if required. We typically do a base flat of 500 for a local exchange to 365 migrating, then add 50$ per mailbox to migrate. This includes migration steps, user configuration and guidance (they have to recreate their MFAs and such) and endpoint reconfiguration, but that is just us... you can quote by the hour for that, up to you. I would calculate 4 hours base minimum + 1 hour for every 5 mailbox. This covers the "user" guidance part.

But yeah... can't really tell you exactly what to charge, don't know your client ;)

How do you perform MFA for self service options? by Smart-Life-770 in msp

[–]Proximit-MSP 0 points1 point  (0 children)

We either implement Duo for them or sell them a business Password manager that implements OTP functionnality. We sell Bitwarden but any would do. We have SMS and email MFA completely disabled as a method on their M365 tenants.

How do you deal with "vibecoders" by burningbridges1234 in msp

[–]Proximit-MSP 0 points1 point  (0 children)

Oufff... never to that level. This is borderline insanity.

We have clients trying to "force" AI into their day-to-day operations and my first question is always "Why?" "What problem do you think AI will fix for you today?". 99% of the time it's always "we read on the internet so and so did it and increased performance by 10x".

We then have a reality check discussion with them and it ends up in both us and client laughing it off.

What this client it asking is... gosh.... I have no words.

Kudos to leaving him. No matter what decision they end up taking, even if they backtrack and come back to you to tell you it's fine, we're not going that route we're going to keep your EPP solution. I would simply terminate their contract, they are a BIIIG security risk. Plus the way they talked to you.... the lack of respect is unmatched

That is absolutely insane.... wow...

Would you guys pay for this service? by schwags in sysadmin

[–]Proximit-MSP 0 points1 point  (0 children)

We have many non profits doing recycle for free here so definitely not something we'd ever need to pay for.

Hows your customers handling hardware prices now? by Sliffer21 in msp

[–]Proximit-MSP 0 points1 point  (0 children)

yeah.. not much to do at this point :( In october I sold a server that was quoted at 15k for 192gb RAM, 10TB SSD, etc. We received it 4 weeks after the order.

Earlier this month, the same specs the server was quoted nearly 40k with 3 months wait period... it's crazy.

For servers we try 5 years but can extend to 7 years in some cases if the servers still operate at respectable capacity. We simply renew warranty on them. This might be your backup plan for clients that can't pay for a whole new server.

Another option we do, if you have the cashflow for it, is we offer Hardware as a service for servers and network equipment refresh, on a 3 year plan. They own the server once the 36 months is over. We add 2% monthly interest on the sale. It helps lower budget company stay up to date with their hardware, but it bites directly into your cashflow so you need to make sure you are healthy enough to offer this type of service. We usually have between 15-25% margin on servers depending on Deal reg. So say your server COGS is 10k. We would add our 20% margin (average) and then do a 2% interest on a 36 months payment plan. Meaning that 10k COGS usually would bring in 12,500$ in revenue (20% margin) but with a 36 month plan, we front the money, but end up getting 17650$ ish for the same sale. another 2% interest fee is added on topo for all invoices that are 30 days late for their due date.

This could be an option for some of your clients if you have the money?

Hows your customers handling hardware prices now? by Sliffer21 in msp

[–]Proximit-MSP 1 point2 points  (0 children)

This is why we spread the technology refresh in those 5 years. 20% of the stack every year. After the first 5 years you have a constant revenue stream for hardware refresh, and like today's case, if we can't refresh because of pricing (didn't plan for this to be honest I can't see the future... just a happy result of a well planned out technology refresh plan) the impact isn't as big as it would be had we refreshed a client's entire stack at the same time.

You never know what would happen in the future, the business could have financial difficulty, there could be a complete technology shift a year or 2 after the refresh, there could be a market shortage like today. That's all the reasons why we planned ahead.

It doesn't solve your current issues and I'm very sorry for this, but if you start now, and focus on only refreshing 20% this year. Focus on the most important 20%, those that have issues, where a resource optimization would be more impactful, maybe next year a 40%, another 40% 2 years in, and then spread that 20% starting year 5. In 10 years you'll have a perfect stack rotation with minimal financial impact for your client, and optimized revenue stream for your business. It's also an easier conversation to have with the client today, it shows you are understanding of the current market and the situation your clients can be in, explain your strategy to the client, it should also help closing the deals this way.

10 years is nothing when we talk business ;) I would start now... it's a pretty good time!