SMB Community Podcast copertina

SMB Community Podcast

SMB Community Podcast

Di: Dave Sobel
Ascolta gratuitamente

Offerte di stagione | 0,99 €/mese per i primi 3 mesi

A seguire 9,99 €/mese – si applicano condizioni. Puoi disdire mensilmente.
Podcasts, articles, and reference materials for Managed Service Providers. Produced by MSP RadioMSP Radio Economia Gestione e leadership Leadership Politica e governo
  • Can Employers Require Employees to Use AI Tools Like Copilot in the Workplace?
    Oct 8 2026

    The episode addresses the push for mandatory adoption of artificial intelligence (AI) tools among employees in MSP and IT service environments, citing cases where use of products like Microsoft Copilot is being enforced under threat of termination. Contributors emphasize that while AI proficiency is becoming a key factor for employability in the technology sector, mandating use through ultimatums is likely to provoke resistance and undermine change efforts. The consensus is that sustainable progress depends on providing structured training and fostering a collaborative culture rather than imposing requirements.

    Supporting discussion points include the importance of intentional staff development and recognizing parallels to previous technology shifts, like the migration to cloud services. Resistance to learning new tools can result in employee attrition, reinforcing the need for ongoing education and active change management. Companies are advised to educate and incentivize employees, creating an environment where continuous upskilling is the norm.

    Secondary topics include recent Microsoft incentive program adjustments. Panelists note reductions in partner margins for lower-tier licenses, while incentives remain for Business Premium and enterprise plans. New AI-related incentives, such as Copilot bonuses, now require a minimum of 50 users, which may prevent smaller MSPs from participating. The conversation also explores the spread of AI-generated language into everyday business communication and shares practical security incidents observed in the field.

    MSPs and IT leaders are advised to manage AI adoption through robust training, transparent communication, and regular review of changing vendor incentive structures. Shifts in vendor programs and rapid technological change require proactive workforce planning, risk mitigation, and careful attention to evolving operational and compliance demands.

    Should I force my employees to start using AI?
    1. Show Rundown & Banter: Amy is back from ChannelCon.
    2. Question of the Week: Should I force employees to use AI? Discuss technology laggards, employee adoption, and whether forced AI use is really the right approach.
    3. In the Economy: 29,000 jobs and 2.2% growth — what does the economy mean for MSPs?
    4. Microsoft Incentive Changes: Microsoft is reducing incentives on many cloud programs while rewarding usage growth and partner skills. What does this mean for MSP margins?
    5. Are AI Chatbots Changing the Way We Speak? “LLMisms” like “It’s worth noting,” “Here’s the thing,” and “This is the key takeaway” are showing up more in workplace communication.
      https://www.wsj.com/tech/ai/claude-chatgpt-ai-speak-chatbot-cb804933
    6. Tales from the Field: Another Tale of Espionage — a former employee continued accessing company systems and transferring client data to a new employer.

    Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

    Mostra di più Mostra meno
    19 min
  • How AI Is Transforming Vulnerability Management and Patching for MSPs
    Oct 1 2026

    The episode scrutinized the operational impact of accelerated patch velocity, largely attributed to AI-driven vulnerability discovery. Microsoft’s patch release cadence has intensified, as evidenced by the increase from 200 patches in June to 900 patches in September. Despite this uptick, panelists noted that patch delivery is now consolidated—vulnerabilities are addressed through a single cumulative update per cycle rather than via hundreds of discrete patches. This structural change reduces exposure to widespread outages, but risk must still be evaluated based on deployment timing and organizational context.

    Delaying patch deployment by at least one week post-release was advocated as a harm-reduction strategy. The rationale is that “dead body Wednesday”—the day following Patch Tuesday—commonly reveals unforeseen operational disruptions. Forum monitoring and the identification of industry-specific tolerances are recommended, supported by the observation that most incidents arise from edge cases or latent infrastructure flaws exposed by reboot cycles rather than patch malfunction itself. The role of Microsoft in acknowledging and remediating issues was discussed, with a particular emphasis on the lag between incident emergence and vendor acknowledgment.

    A secondary focus addressed the expanded risk surface beyond Windows, emphasizing IoT, networking, and edge devices. The lack of standardized, automated patching for non-Windows assets, such as security cameras, printers, and other IoT endpoints, multiplies the challenge for practitioners. Neither firmware nor update methodologies are unified, necessitating manual intervention and physical connectivity in many cases. The episode further touched on IT governance concerns, particularly around excessive permissioning, data management, and the tendency for access requests to escalate rather than contract over time, exacerbating organizational risk.

    For MSPs and IT service providers, key implications center on risk-managed operations. Patch deployment processes should be routinely assessed and customized based on client risk profiles, infrastructure complexity, and historic pain points. Increased vulnerability discovery via AI necessitates enhanced organizational discipline around both patch timing and post-patch monitoring. Security governance—especially regarding permissions scopes, data segmentation, and the extensibility of third-party integrations—was underscored as an operational priority. Comprehensive asset management and organizational awareness of fragmented patch ecosystems, especially in IoT and edge contexts, will be essential for maintaining resilience and accountability.

    What should I do differently now that AI is throwing us so many patches?
    1. Show Rundown & Banter: Amy is joined by longtime Microsoft MVP Susan Bradley, the “Patchaholic,” to discuss Microsoft updates, patching, and what IT professionals need to watch.
    2. Question of the Week: How should MSPs change their patching strategy in the age of AI? Microsoft’s updated guidance calls for short quality-update deferrals and faster installation deadlines.
      https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/references/policies-quality-updates

    Tales from the Field: When reimaged machines started failing — Susan shares a story involving Dell machines and unexpected failures.

    Links mentioned in this episode:

    Question of the Week
    - Microsoft: Windows Autopatch quality update policies (deferral and deadline guidance)
    https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/references/policies-quality-updates
    - Microsoft Mechanics: Deploy Windows updates to counter AI-discovered threats
    https://techcommunity.microsoft.com/blog/microsoftmechanicsblog/deploy-windows-updates-to-counter-ai-discovered-threats/4534505

    Resources
    - AskWoody, Susan Bradley's newsletter
    https://www.askwoody.com/
    - Third Tier, Amy Babinchak's patching series
    https://www.thirdtier.net/?s=patch ← swap in Amy's exact link


    Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

    Mostra di più Mostra meno
    26 min
  • Public Speaking Skills and AI Monetization Tips for MSPs
    Sep 24 2026

    Public speaking for technical professionals and the development of practical business process automation using AI were identified as areas with tangible operational impacts for MSPs. Structured preparatory practices, such as rehearsals and simulated audiences, were described as beneficial for reducing employee apprehension and improving presentation quality, according to Amy Babinchak. Applying a process-oriented approach, including content development and reference to audience-specific expertise, can support staff development, help mitigate presentation anxiety, and promote more effective communication of technical concepts.

    Process automation and AI monetization were explored through concrete examples. Amy Babinchak outlined several applications, including contract obligation tracking through AI agents, automated identification and drafting of overdue invoice notifications via read-only accounting system access, and AI-driven verification of job site photographs. Each was presented as a method for improving operational efficiency and reducing manual workload, with an emphasis on direct business outcomes such as time savings and risk reduction. The discussion cautioned that routine use of generative AI for basic tasks like search and email drafting does not readily produce measurable value unless integrated into broader workflow optimizations.

    The episode also addressed marketing tactics relevant to year-end business cycles and inventory management. James Kernan recommended executing inventory reduction campaigns, such as open-box or scratch-and-dent sales, to address stock overages. The timing of client upgrade campaigns was connected to product end-of-life events, specifically referencing Windows Server 2016 and SQL Server 2016, as opportunities to drive sales while reducing client risk associated with unsupported software. The conversation further covered managed service delivery models, identifying potential risks and tradeoffs in offshoring, automation, and outsourcing core client-facing services.

    For MSPs and IT leaders, the operational implications are clear: public speaking proficiency and client communication should be built intentionally, involving structured practice to reduce risk of poor delivery. AI and automation initiatives should prioritize process alignment and quantifiable outcomes, not just adoption for novelty’s sake. Inventory and lifecycle management present opportunities for improving both sales and client relationships, but require a disciplined approach to timing and messaging. Regular review of outsourced or automated functions is encouraged, with attention to maintaining a personal client interface and managing the organizational and reputational risks of dehumanized service.

    How can I become a better public speaker?
    1. Show Rundown & Banter: What’s new?
    2. Question of the Week: How can I become a better public speaker? Focus on preparation, simple slides, eye contact, pauses, practice, breathing, and handling mistakes.
    3. AI Interest to AI Impact: Help clients move from experimenting with AI to delivering measurable results.
      https://www.channele2e.com/perspective/msps-need-to-push-clients-past-ai-experimentation
    4. Marketing Tips – Year-End Campaigns: Promote open-box/year-end projects, address Microsoft end-of-support deadlines, follow up with late payers, and host casual client events.
      https://learn.microsoft.com/en-us/lifecycle/end-of-support/end-of-support-2026
    5. Outsourcing Service Delivery: What should MSPs outsource — answering calls, dispatch, L1/L2 support, L3 escalation, or out-of-state projects?
    6. GTIA Acquires ASCII: What does the acquisition mean for the MSP community and channel?
    7. NinjaOne Browser Security: Discuss NinjaOne’s new browser-based security offering and what it could mean for MSPs.
    8. Tales from the Field: Timing is Everything.

    Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

    Mostra di più Mostra meno
    21 min
adbl_web_anon_alc_button_suppression_t1
Ancora nessuna recensione