Early Access for Microsoft User Actions Starts Soon!

Hello Syncro Community!

I am excited to announce that we are going to start Early Access for our next set of Microsoft User Actions! You will now be able to revoke active user sessions and block/unblock user sign-in directly in Syncro.

Early Access will begin early next week. Please use the Early Access interest form below to get started if you would like to get started with the next set of management actions!

2 Likes

Is this also for the new fancy plan only?

The Team Plan is required for Microsoft User Actions. If you’re not on the team plan, there is the option to trial before making any decisions.

Since Syncro has introduced customer classes (haves/have-nots), it’d be helpful to start mentioning those in product announcements.

We’re missing the days when the standard plan’s features got developer resources for fixes and improvements.

if you look at the roadmap there are plenty being added for the standard plan. Archive assets, SNMP3, and outbound email domains are not team specific. The QoL Updates are also across the board. Patching Dashboard is another.

The roadmap clearly mentions the “haves” and “have-nots” as you put it with the little *s I am on the teams plan so do not need to pay attention as I know things will be coming my way but on the webinars and on the website I have never been in doubt over what was in what plan.

I may not like how some features turn out but the comms from Syncro over the year plus I have been involved has been clear and reliable. If Dee or Andy mention something is coming then I am very sure it will arrive. This is different than my previous RMM and is very refreshing.

Looking forward to the Linux Agent arriving which is also slated for the standard plan.

(ps the sign up form did mention Team plan)

I’m glad it’s working out well for you, Des.
The roadmap certainly is rosy, and I’m hopeful for that Linux agent too. I remember N-able struggled for years to maintain multiple versions needed for the many distros, so I hope that Syncro has both better luck and a reasonable range of distro compatibilities.

And great hopes have been definitely well-communicated since Michael George’s start 18mos ago. But actually-delivered since then is exciting-but-half-baked flops (e.g. smart ticket search that still doesn’t understand word boundaries to find “Tom” among all the “To” fields), OR new bells/whistles for the fancy plan like this. All while the standard plan’s years-long list of languishing troubles isn’t getting fixed.

Interesting that you call out the new Patching Dashboard:

  • Yes, instead of fixing the broken Vulnerability Report, they’re trying a prototype datatable that looks like it could be good once finished. Unfortunately, unlike the Vulnerability Report, it itemizes per-patch-per-asset, so we get 1000+ pages.
    image
    We can filter and group that down, but it then won’t remember any of those settings, or layout sub-grouping well, or show any summary patch data, so it’s not really useful yet. Looks like you’ve more recently had struggles with it too.
  • And unfortunately Syncro’s reported patch data is untrustworthy anyway.
    Since March, we’ve been actively working with them to fix this. Among other things, it often fails to show Needed or Installed that the Windows Update subsystem definitely DOES see.
    To their credit, they do see and want to fix those breakdowns, but when we saw no imminent hope in April, we built a series of scripting/fields/columns/saved-searches to surface Microsoft’s own WU reporting.

While it’s cool that we CAN do that, the necessity is much too common and chronic. We should not need to keep making clever workarounds for core-platform problems that they’ve known about & neglected for years.
And the fancy plan getting bells/whistles while these stay broken just makes it worse.

Hi Rob, thanks for the detailed feedback. I appreciate you highlighting these challenges. I want to assure you and the rest of the community that we’re actively looking into the issues you’ve raised.

Regarding the agent not detecting all available patches in some cases, I’ve received your recent examples you shared with me last week and am escalating them to our engineering team for investigation. This will help us get to the root of the issue you’re experiencing.

Your feedback on the patching dashboard is also valuable and has been echoed by other partners. I’m making sure this is a priority as we plan for future updates to the patching dashboard.

I appreciate you taking the time to provide us with this kind of detailed, actionable feedback. It’s essential for us to improve the platform.

Thanks Lindsey, I’m glad you’re on the case.
I only responded to Des about that because it seemed like a particularly rough example.
I look forward to the logjams breaking.

I was not saying syncro was all rosy but I am appreciating some of the positives especially in comparison to where we were before.

But there are a lot of people on FB etc that raise the issue that everything is on the teams plan and nothing is being added to the non fancy plan. I just feel that is untrue and easy to challenge. The roadmap is being delivered. I may not describe them as half baked flops but yeah they are not all where I would want them to be hence the feedback on the patching dashboard.

The new Smart ticket layout is one of them in that poorly performs on grouped items but apart from that we are finding it works quite well. It came in as beta, remained beta but people did not consider it a beta so wanted it now :slight_smile: Thats just my take.

The QoL fixes appear to be delivering just what you’re asking for albeit not hitting your pain points.

I raised the patching issue as I think they are trying to fix it and resolve things and get the sense that there is a lot of legacy technical debt that they are working their way through. To be fair from my understanding most of the RMM platforms have their patching systems in a poor state. Our previous RMM used WU as the source of truth and when things did not match up then “it is just what MS give us” even though we were consistently getting patch info in Nordic languages :slight_smile:

Agree with you about the vulnerable systems report that it is a hot mess that is unworkable. A little bit of time on reports could help as well.

I do think they could do a bit better on the messaging about EA / Beta and live release for features. Plenty of people have moaned about things that are still actively in beta and can be turned off and go back to the old version. I did this with the smart ticket interface for a bit.

Hey Rob,

Not every business is the same, which is why virtually every SaaS product out there offers multiple plans to ensure you can choose the right one for your business needs. We’ve had two plans for over two years now, and when I first came to Syncro, we actually had three plans.

Over the years our customers have grown, quite drastically in many cases, and we’ve had to grow right along with them. Syncro’s Core plan is effectively our “starter” plan, while the Team plan has quickly transitioned into our base plan. This plan now accounts for the majority of new customers coming onto Syncro. That said, we will always continue to offer a starter plan for folks just getting off the ground, or for those emerging MSPs that find enough value in what the Core plan offers today they don’t feel a need to move on to the Team plan just yet.

We have been extremely diligent about offering new features consistently for both plans, and we have no intent to change that any time soon. For example, we currently have 13 items listed on our public roadmap between what’s in progress and what’s on deck. 10 of those items are coming to all plans, while 3 of them are slated for the Team plan.

1 Like