Larry Karatsoreos

Knowing what devices are present, how they connect, and what is changing can help MSPs spot trouble earlier and spend less time reacting to client complaints. They make the point through both a concrete list of monitoring capabilities and a humorous first-person account of learning that a successful ping is not the same as real visibility.

One post lists network mapping, device monitoring, alerts, configuration backups, remote troubleshooting, and management across multiple client environments.

• In another, Larry Karatsoreos recalls thinking that pinging devices meant he had good visibility, then describes finding rogue devices and spending less time firefighting with Auvik.
• Together, the posts make the case in practical and personal terms.

The two posts share a priority but differ in emphasis: one explains platform capabilities; the other uses a personal story and jokes to make the visibility gap memorable.

Read original · Original 2

Standardizing equipment can make configuration, troubleshooting, and technician onboarding easier; paying less up front is no saving if outages or extra hands-on work raise the long-term cost. They distinguish the general principle from any one vendor recommendation.

Karatsoreos contrasts a firewall designed for a 20-user office with the demands of a multi-site setup using heavy VPN traffic, and warns that branch-office switches can bottleneck a growing campus. They also cite monitoring-tool compatibility as a reason to favor equipment with useful visibility, mentioning Auvik as one example while noting the principle stands on its own.

Read original

The audience may be MSPs and IT leaders making service or licensing decisions, or a broader audience learning basic security habits. A light hook can introduce the lesson, but the post should also say what readers can do or reconsider.

For password security, Karatsoreos uses the reported Louvre password story to introduce unique passwords, multi-factor authentication, and team training. On Microsoft's announced Teams licensing change, they explain the implications for customer choice, pricing conversations, integrations, and global policy management.

The password post targets more than IT professionals, while the licensing post speaks directly to MSPs and IT leaders. The five posts show a shift in audience and subject, not a documented change in views.

Read original · Original 2

It answers the question newcomers ask first: does this person teach infrastructure decisions, or just repost vendor material? Here, the answer is a five-point framework you can apply the same afternoon.

Karatsoreos argues that buying firewalls, routers, switches, and wireless gear is less about brand names than visibility, compatibility, and long-term manageability.

• The post lays out five rules: match equipment to the environment rather than the reverse (a firewall built for a 20-user office will struggle in a multi-site deployment with heavy VPN use); standardisation is not restriction, because narrowing vendors simplifies configuration, shortens troubleshooting, and speeds up onboarding for new technicians; compatibility and visibility determine whether a network is understandable when something breaks; don’t lead with price, since cheap gear costs more through outages and hands-on maintenance; and plan for growth from day one with spare switch ports, scalable firewalls, and WLAN that does not require re-architecting.
• Auvik appears once, in parentheses, as an example of visibility across mixed hardware; Karatsoreos says the principle stands on its own without it.
• The closing checklist: reliable performance, strong security, clear visibility, easy management, and support.

For brands planning a campaign

A network visibility or monitoring vendor can commission a practical equipment-selection checklist or audit template, not a product pitch.

• The post earns attention with advice readers can use without the sponsor’s tool.
• It also shows Karatsoreos can mention a platform as one option while keeping the argument independent—a fit for credibility-first collaborations.

The post shows how a sponsored capability piece works when the practitioner knows the buyer.

The post opens with the core promise of managed services—clients should not be the ones who find network problems—then lists what Auvik does for an MSP: automatically map and document client networks; monitor routers, switches, firewalls, and wireless; send alerts before issues become outages; back up and track device configurations; troubleshoot remotely with traffic insights and secure access; manage multiple client environments from one platform; and integrate with PSA and RMM tools.

• It closes by inviting anyone seeking better visibility, shorter troubleshooting, or a wider service offering to connect.
• Unlike the equipment post, this is a direct platform-capability list with a call to action.

For brands planning a campaign

Karatsoreos offers a clear example of straightforward vendor-capability content for MSP buyers, with feature bullets and a contact invitation. It fits product launches or co-marketing campaigns aimed at managed service providers who know the category and want a concrete feature list.

They carry a sponsor's message in a light, first-person voice rather than a feature list—a useful fit for briefs that should feel like a practitioner's story instead of an advertisement.

Karatsoreos admits they once thought they had good network visibility because they could ping things and they usually replied, then credits Auvik with changing that.

• The humour is specific: networks have "more secrets than a reality TV cast," and the old approach is mocked as "have you tried turning it off and on again" as a life philosophy.
• The benefits: seeing the whole network, catching problems before they disrupt the day, stopping the search for cables "like you're on an IT safari," and spending less time firefighting.
• The hashtag set is heavy and includes Auvik's own brand tags alongside MSP, managed services, network security, and reduce-MTTR terms.

For brands planning a campaign

A good fit for awareness-stage campaigns aimed at recognition rather than feature comparison: the sponsor's name is central, the tone is disarming, and the post reads as a personal conversion narrative rather than a case study with metrics. Expect brand-heavy tagging, which helps sponsored discovery if that is the objective.

Karatsoreos turns a news story into a short, non-technical lesson—the format most likely to travel beyond an MSP audience.

Karatsoreos uses a reported breach at the Louvre, where the password was reportedly the museum's own name, as a hook for basic password hygiene.

• The joke quickly gives way to three takeaways: use complex, unique passwords; turn on multi-factor authentication, described as a digital seatbelt; and train teams, because one weak password can open the door for a real-world heist.
• The post says cybersecurity is not only for IT professionals.
• It attributes the breach claim as reported and offers no technical analysis or vendor product.

For brands planning a campaign

Suited to security-awareness and identity campaigns—password managers, MFA vendors, or training providers—where a memorable news hook and three plain-language actions are enough. It is a weaker fit for deep technical launches because the post stays at a general-audience level and names no tooling.

It is the most news-driven of the five posts and shows the commercial framing they bring to a channel announcement.

Karatsoreos reports that from November 1, 2025 Microsoft will again include Teams in Microsoft 365 and Office 365 Enterprise suites globally, then translates the change into four consequences for MSPs and IT leaders: customers can choose suites with or without Teams; new tiers are meant to simplify licensing conversations and align cost with value; enhanced APIs and developer resources strengthen third-party app support and open room for differentiated services; and removing region-specific licensing differences simplifies management for global customers.

• The takeaway: more control for customers and an opening for MSPs to revisit collaboration, pricing, and integration conversations.
• The post tags two named people and invites anyone affected to connect.

For brands planning a campaign

Useful for channel-facing campaigns tied to a licensing, bundling, or platform change, where the value lies in translating the change into implications for a provider's service catalogue and pricing conversations. The post comments on a vendor announcement rather than presenting original research, so pair it with a source the campaign can point to.

One lists the capabilities a monitoring platform should cover: automatic mapping and documentation of client networks; monitoring of routers, switches, firewalls and wireless gear; intelligent alerts before issues become outages; device configuration backup; remote troubleshooting with traffic insights; multi-client management from one console; and integration with PSA and RMM tools.

• The other describes the same shift from the opposite direction: pinging devices and getting a reply used to pass for visibility, but continuous mapping and monitoring can surface rogue devices and reduce time spent firefighting.
• Auvik is the recurring example in both.

One post presents a capability list; the other tells a first-person before-and-after story. Together, they make the same argument as both a checklist and a persuasion narrative.

For brands planning a campaign

A monitoring, documentation or RMM vendor can ask Larry to demonstrate a process in a real MSP environment: mapping mixed hardware, cutting troubleshooting time, or syncing with PSA and RMM tools. The strongest hook is measurable time saved before an outage; both posts frame visibility as a way to keep clients from finding problems first.

Examples: Source 1 · Source 2

Each principle comes with a concrete consequence: a firewall sized for a 20-user office failing under heavy multi-site VPN use, branch switches bottlenecking a growing campus, cheaper hardware paying for itself only through stability, and hardware chosen without extra ports or scalable wireless forcing a later rebuild. The post closes with a five-point test: reliable performance, strong security, clear visibility, easy management, and support.

Numbered principles, each paired with a failure example showing what goes wrong when it is ignored.

For brands planning a campaign

A hardware or network-management vendor can use the five criteria as a ready-made content outline. A collaboration would be strongest with deployment data or lab results to support a principle — such as compatibility with monitoring tools or lifetime cost — with evidence rather than assertion.

Examples: Source 1

It recommends three actions: complex unique passwords, multi-factor authentication, and team training.

• One weak password can open the door.
• The tone is deliberately light — the hacker trying the obvious password first, the Mona Lisa needing better security — keeping the advice readable for people outside IT.

A real incident hooks readers, humour holds their attention, and a short numbered checklist gives them actions to take.

Unlike the network-operations posts, this one targets a broad audience rather than an MSP buyer and names no product.

For brands planning a campaign

Security awareness and identity vendors can build on the format: one real incident, a plain-language explanation, and three specific actions. The post shows Larry can deliver a general-audience security message without turning it into a product pitch, making it a fit for awareness campaigns and training launches.

Examples: Source 1

It ends by inviting readers to discuss the impact on their business or clients.

A news announcement becomes a short numbered list of business consequences, followed by a direct invitation to discuss.

This is the only post in the set responding to a dated industry event rather than offering standing advice.

For brands planning a campaign

A cloud, licensing or collaboration vendor can work with Larry on a customer-facing explainer: what changed, what it means for MSP pricing conversations, and which integrations or APIs are worth revisiting. The post also offers a way to start lead conversations through comments and direct invitations rather than a link.

Examples: Source 1

One post describes Auvik as the point when the writer moved beyond ping-based visibility, with networks kept mapped and monitored instead of guessed at.

• Another presents Auvik as an example of full visibility across mixed hardware environments.
• The posts invite readers to connect about network visibility or managed services.
• The commercial relationship is unstated; ask whether this is sponsorship, employment, reseller work or unpaid advocacy.

View example

It outlines the implications for MSPs: suites with or without Teams, simpler licensing tiers, new APIs and developer resources for third-party apps, and consistent licensing across regions.

• The post tags two people and offers to discuss the business impact.
• It reports a vendor policy change, not a partnership or commercial tie.

View example

Williams walks through Active Directory group design, role-based access control and delegating local administrator rights, using the same principle-and-consequence approach Karatsoreos takes to network monitoring and equipment choice.

Williams documents a staged home-lab build and asks readers which phase to tackle next, making the posts a portfolio of learning rather than buyer-facing advice. Karatsoreos writes for teams running client networks and shopping for tools, using vendor platforms as working examples.

Read original · Original 2

Collins’s quarterly business review guide covers business updates, executive summaries, security reviews, service experience, roadmap progress, risks and recommendations, in the same structured style Karatsoreos uses for equipment criteria and network visibility.

Collins covers the commercial side of managed services: account management, renewals, sales resilience and growing a client into a strategic account.

• Karatsoreos focuses on technical infrastructure, deciding what to monitor and what gear to buy.
• Collins’s career-story post about rejection has no equivalent in the material here.

Read original · Original 2

McMillan’s identity work—standardized attributes driving dynamic groups, with conditional access deployed in report-only mode first—matches Karatsoreos’s practice of explaining why a design choice matters before naming a product.

McMillan describes rebuilding a specific environment, detailing its migration, policies and measured ticket results, and argues for designing a business that needs less support. Karatsoreos offers general buying and operating advice for MSPs serving many clients, with Auvik as a recurring example rather than a single in-house system.

Read original · Original 2

Williams's two posts document a Proxmox-based Active Directory home lab in sequence: Phase 3 provisions 23 user accounts by hand and builds nested departmental OUs under MelvinLab_users; Phase 4 moves to identity and access control with global security groups such as GS_IT_Staff and GS_HR_Staff for role-based access, then delegates local administrator rights on a Windows 11 workstation without granting domain-wide control. If a vendor wants its product shown inside a lab environment that doubles as portfolio material for someone entering the field, that’s the shape Williams already writes in.

The audience is candidates and career-changers, not MSP technicians or the people who sign off on tooling budgets, so the same spend buys a different reader.

• The work is a personal lab rather than client environments, and neither post evaluates network monitoring or equipment; the subjects are directory structure, group strategy, and least privilege.
• Written as a learning log, the posts close by asking readers what to tackle next, presenting practice rather than a concluded recommendation.
• Ask for follower, engagement, and audience-composition figures before comparing reach.

Examples: Source 1 · Source 2

Collins's 2026 post lays out a complete quarterly business review framework in seven parts: business update, executive summary, security review, service experience review, roadmap progress, quantified risk, and recommendations for the next 90 days and 12 months.

• It argues a QBR is now a business strategy meeting led by technology, and frames the payoff as turning a $3,000-a-month client into a $10,000-a-month strategic account.
• Collins's other post is a first-person sales-career narrative about a rejection email, coming back to N-able, and landing the most new products as a midmarket account executive.
• A vendor that wants its tooling positioned as a line item in a client strategy conversation has a ready template here.

The posts do not cover infrastructure: no networks, equipment, monitoring, or identity work appears, so a campaign that needs technician-level detail would be buying strategy framing instead.

• The sales-career post is personal narrative and carries no vendor-relevant method a sponsor could attach to.
• The reader is the MSP's commercial leadership, which overlaps only partly with the technician audience a monitoring platform usually wants to reach.
• Both posts are standalone pieces, with no series structure.
• Ask for audience-size and engagement figures, plus commercial terms, before committing.

Examples: Source 1 · Source 2

One post describes moving away from a reseller-managed Microsoft 365 licence, then building identity in Entra ID and Intune on standardised attributes and dynamic groups, with Intune enrolment, BitLocker, Defender, firewall policies, update rings, Windows LAPS, and conditional access deployed in report-only first, all backed by documented standards and change control.

• The other describes running IT alone for 150 users across multiple sites with no MSP, replacing manual triage with centralised intake and automation, and reporting about four times the ticket volume, roughly 90% faster initial response, and about 60% less time to resolution — the same material was presented to a room of VP and director-level IT leaders.
• A campaign that needs an enterprise-cloud operating story with numbers attached fits better here than with Karatsoreos.

There is no MSP content and no network monitoring or equipment selection in the posts, so a network-visibility vendor would be reaching internal IT rather than the channel that resells its product.

• The performance figures are the author's own account of one environment, not audited or comparative data; do not quote them as benchmarks.
• Both posts are first-person deployment or operating narratives, with no directory of comparisons, third-party tool evaluation, or format beyond text.
• Ask for audience-size and engagement data, and commercial terms, before committing.

Examples: Source 1 · Source 2