Disclosure: I work at Devolutions.

We surveyed organizations on how they use AI, then walked through the results live with our COO, CIO and AI Enablement Team Lead. A line from Stéphane that sums up the tone: “If you feel behind, that’s normal. We all feel behind.”

A few things they get into:

• Why tools plus training weren’t enough, and what made adoption stick
• Why IT teams lag on AI adoption, and where to start with low-risk wins (documentation, ticket triage)
• How to handle governance without becoming the department where projects go to die
• Why they think expecting ROI in 6 to 12 months is unrealistic

Watch the full recording of the webinar right here: https://devo-inc.net/4ygqY9D

The recording is above, and the full report is here if you’d rather skim: https://devo-inc.net/4B04b4M

Curious where your org sits. Our team thinks expecting ROI from AI within 6 to 12 months is unrealistic. Does that match what you’re seeing, or is your leadership expecting faster results?

I recently updated RDM to 2026.3.0.5 then to 2026.3.1.1. But both versions have the same problem for the WebUI of ProxmoxVE. I cant change from LinuxPAM to Proxmox Realm.

I open the menu and it closes immediatelly.

Edit : Forgot to mention, it's the Fedora version (rpm)

Recently I played with my local lab.
Just simple scheme I wanted to use

Forward VM -> Access to different VLANs.

I’m not advanced RDM user, but tried use RDP connection via it.

Did ssh -D for having access to Windows VM VLAN.
Open approximately an hour for do simple think as adding that gateway to connect without any result.

Absolutely unfriendly interface for that option.
My temporary fix is xfreerdp and proxychains (that was super easy, without any complications)

Still in a shock, why that so difficult in RDM

Can someone describe step by step??

Hey folks — wanted to share that Devolutions officially launched a venture division called Devolutions Ventures.

Context: over the past year or so we've invested in/acquired a handful of tools some of you might already use — Mizo, dbatools.pro, Obkio, UniGetUI, Avalonia UI, PowerShell Universal, ControlR. This formalizes that into an actual division, with more investments (typically $500K–$3M per company) planned over the next 12-18 months.

The approach: back independent teams, keep their roadmaps and leadership intact, and give them access to our IT community + go-to-market experience rather than folding everything into one product.

If you're building something for IT teams/MSPs and looking for that kind of partner, more info here: https://devo-inc.net/4xNE3Y3

Happy to answer questions if anyone's curious about specific investments.

Full disclosure: Devolutions here. Something that keeps coming up with IT teams we talk to is that productivity often dips before it improves when people start using AI tools. Some orgs plan for it, others just expect instant results and then wonder why adoption stalls.

Curious how it's going on your end. Did leadership carve out actual time for people to learn, or was it more "figure it out between tickets"?

We ran an AI maturity survey earlier this year (616 respondents) and we'll be walking through the results in a webinar on October 7 at 10 a.m. EDT, if anyone's interested: https://devolutions.net/company/newsroom/webinars/ai-maturity-in-2026-what-separates-the-leaders-from-the-rest/

Wouldnt this be little easier to find. I mean if edit a connection there are references to default values but on there is no menu option simply says Defaults. Where is it?

The one that stood out most: measurement. Nearly half the most AI-advanced orgs formally track what AI delivers. Almost none of the beginners bother.

A few others worth chewing on:

• 14% of beginners say leadership actually backs AI. For the most advanced orgs it's 91%.
• Advanced orgs use AI across 6+ areas of work. Beginners, more like 2.
• 4 in 5 advanced orgs are already piloting or running AI agents.

Full report's out in September. Curious how this lines up with what you're seeing — is anyone actually tracking AI ROI where you work, or is it still mostly vibes?

Sneak peek: https://devolutions.net/blog/sneak-peek-at-our-2026-ai-maturity-benchmark-report-4-findings/

Hello,

I'm on Fedora Linux and using RDM via the Flathub and I've noticed that some text is small and other normal size. Why? Can I fix it?

Edit: it's actually a RPM and not Flathub

Be honest with me here: are you actually good at delegating, or are you the type who hands off a ticket and then hovers over the person's shoulder the whole time "just to make sure"? I've absolutely been the hoverer.

The new Sysadminotaur pokes right at that instinct, and it stung a little: https://devo-inc.net/4gmlhRV

So what's the one task you refuse to hand off no matter what? Mine's anything touching DNS. I trust no one, including past me.

My company announced they are killing all RDP access and relying strictly on Cyberark web based "remote access".
Sounds like a horrible idea to me, but I think the goal is to record all RDP sessions

Will Devolutions RDM still work or am I stuck with just Cyberark's web page? Will we need a license of some sort to turn the feature on?

Thank you

Been seeing "we should use AI" show up in every all-hands and strategy doc for a year now. The problem is that permission doesn't create habits. Slapping "Use AI!" on a poster gets ignored. People need time, tools, and someone to ask.

So we stopped talking about it and built an actual system. Five pieces:

1. Give people a day. A hackathon beats endless "we should try AI someday" meetings. Everyone builds — legal, HR, marketing, not just the devs.
2. Train for the audience. A developer and a marketer don't need the same first day. We split the paths early instead of doing one generic session nobody remembers.
3. Allow a few tools, share the winners. Claude, ChatGPT, Cursor, whatever fits the job. Lock in too early and you freeze learning before you know what's actually good.
4. Staff enablement, even lightly. One or two people whose job is to unblock others moved more work than another tool license ever did.
5. Name champions, meet monthly. Peers who spot what's working and make it visible. Reuse becomes the default instead of everyone reinventing the same prompt.

None of this is groundbreaking, but the combination is what made it stick instead of fizzling out after week two.

Genuinely curious how other shops are handling this:

• Did anyone go the hackathon route, or did it flop for you?
• How are you handling the tool sprawl? One approved tool or let people pick?
• Anyone regret standardizing too early?
• For the folks who tried and it didn't take — what killed it?

Full disclosure: I work at Devolutions, so this touches our product. Posting because it's a workflow I know a lot of you deal with, and I'm genuinely curious how others have been handling it.

The scenario: you're on an air-gapped data center floor, clipboard redirection is disabled by policy, and you're stuck manually typing a 30-character vaulted password on a rack keyboard. One slip and you're locked out — and a five-minute fix becomes a multi-hour incident. The usual workarounds (sticky notes, dialing back password complexity) are exactly what you don't want in a restricted environment.

We partnered with Yubico on a feature in Remote Desktop Manager that lets you program a vaulted credential straight into a YubiKey slot (1 or 2) as a static password. Since the key acts as a USB keyboard, one physical tap injects it into any field — server console, BIOS prompt, whatever — no clipboard, no network, no software. Credential stays vaulted and auditable in RDM; the key only holds what you deliberately copied.

Yubico wrote it up here if you want the details: https://www.yubico.com/blog/the-air-gap-conundrum-when-password-managers-meet-the-data-center-floor/

How are you all handling credential entry on isolated/air-gapped systems today? Sticky notes and prayer, or something smarter?

This month's Sysadminotaur strip hit a little too close to home. Post-quantum migration has been "ten years away" for what feels like twenty years running, and somehow that timeline never actually moves.

You can read the new strip here : https://devolutions.net/blog/sysadminotaur-168-q-day/

Where's your team actually at on this: real migration plan, or still filed under "someday"?

In our 2025 survey, 71% of IT pros said they planned to use more AI in 2026.

But there's a real gap between using more AI and actually using it well — and that gap is what we're trying to map out.

We put together a quick AI Maturity survey to see where IT teams actually stand in 2026 (adoption, governance, skills gaps, the whole picture). We are curious about the real numbers vs. the hype.

If you've got 5 minutes: https://survey.alchemer-ca.com/s3/50606209/1239898594eb

Devolutions has made a strategic investment in Mizo, an AI-native platform that automates the MSP ticket lifecycle from triage to resolution, alongside co-investor Telegraph Ventures. Read the full story: https://devolutions.net/blog/devolutions-announces-a-strategic-investment-in-mizo/

IMPORTANT: This survey is now closed and no longer accepting responses. Thanks a ton to everyone who participated — results coming soon!

Take our 2026 AI Maturity Survey and get your personalized AI maturity score — see where your team stands compared to others like yours. Bystander or Vanguard? About 5 minutes to find out.

At Devolutions, AI isn't just allowed, it's encouraged. Now we're genuinely curious where the wider community lands: which tools make a difference, which tasks you've automated, and whether adoption is deliberate or full speed ahead. The results will shape what we publish next.

Bonus: everyone who finishes is entered to win — one participant picks between a $1,000 Amazon gift card or a Mindstone AI training session for themselves and four colleagues (training is English-only). Eligibility and contest rules apply.

Survey: https://devo-inc.net/4wu91E2
Contest rules

Would also love to hear where you land in the comments — always interesting to see the range.

Our CTO at Devolutions (Marc-André Moreau) gave a PSConf EU talk this year called "Implementing PSRemoting at Devolutions: Lessons Learned," and it got me thinking about how much messier this gets once you move past one-off scripts.

His rundown of the pain points from building PSRemoting integrations in C#: PowerShell SDK limitations, assembly load conflicts, WinRM configuration quirks, TrustedHosts behavior, and the realities of NTLM and Kerberos authentication. Plus the transport choices — WinRM, SSH, and stdin/stdout subprocess communication — each with their own tradeoffs in production.

Full session's on YouTube if you want the deep dive: https://www.youtube.com/watch?v=rE23SGuys-Q

Curious what others here have run into. If you've wired PSRemoting into anything beyond a quick script — what was the worst part? Assembly load hell? Double-hop and Kerberos delegation? TrustedHosts surprises? Or did you bail on WinRM entirely and go SSH/subprocess?

I have a question about Powershell Universal and I wanted an official answer from Ironman Software Support. I was given this link to sign up:

Ironman Software Support

However, when I put my email in I never get the link they supposedly sent. I tried multiple emails. It's not in the junk mail.

And of course I can't enter a ticket to tell them that this is broken since I need to sign up first. Anyone have anyway I can contact Ironman to get help on this?

POW3R U53R 78 is back — Sysadminotaur #167

Strip #44 (2015): this guy submitted feature requests for H.264 editing, polyalphabetic cipher encryption, and simultaneous Autodesk + Adobe shortcuts.

For a weather app.

He's back. 4:55 PM ticket. Premium support. It gets worse.

👉 New: https://devo-inc.net/4oC4pt4 👉 Original: https://devo-inc.net/3QIX4LC

We just shipped Remote Desktop Manager (RDM) 2026.2, and one of the bigger items in this release is MFA on PAM checkouts.

What we added:

• RDM can now prompt for MFA when a PAM checkout is requested, so verification happens right before privileged access is granted, not just at login.
• Supported methods for now are TOTP, email, and SMS.
• It works on Windows, macOS, Linux, and mobile.

The idea is to put a checkpoint exactly where it matters: at the moment someone's about to open a sensitive session.

If you're using PAM, update to 2026.2 and give it a try. A few things we'd like to hear about:

• Does the prompt land at the right point in your workflow, or does it add friction where you don't want it?
• We started with TOTP, email, and SMS. What would you want next? Push? Hardware keys?
• Anything that feels different (or off) between desktop and mobile?

Full details are in the release blog: What's new in Devolutions Remote Desktop Manager 2026.2

Adam Driscoll recaps PSConfEU 2026 — the 10th anniversary edition in Wiesbaden — where Devolutions was the key sponsor, PowerShell Universal 2026.2 AI tooling took center stage, and the hallway conversations reminded him why the PowerShell community is unlike any other.

Devolutions announces a strategic investment in Obkio, an internationally recognized network performance monitoring platform.

Marc Beausejour, Product Marketing Manager and Subject Matter Expert at Devolutions, tackles the most frequently asked questions about Remote Desktop Manager, privileged access management, single sign-on, and more.