←
Ryan Mangan7,548 posts
Ryan Mangan avatar

Ryan Mangan

@RyMangan

Founder & CEO, EfficientEther. Double Microsoft MVP, FBCS CITP. Speaker. Cut Microsoft waste. Track every change. Find the AI nobody is watching.

◷ Joined February 2010▧ 2,963 Photos and videos
Ryan Mangan avatar
Ryan Mangan@RyMangan·Oct 30

Windows and Office CVEs rose 159% in a year, from 941 to 2,438. Average severity held at about 7.3. The ones scored 9.0 or above went from 11 to 60. New open research from @EfficientEther. How do you measure time to verified protection? Paper, data and scripts in the reply.

Ryan Mangan avatar
Ryan Mangan@RyMangan·Nov 3

Two weeks ago I asked what your plan is for App-V. Here's a place to start. Our free Forge course shows you how to convert App-V packages to MSIX. App-V server support runs to 2029, so there's time to do it properly. Your route: convert, App Attach, or something else?

0:29
Ryan Mangan avatar
Ryan Mangan@RyMangan·Oct 27

Free training is only worth it if you walk away with something. Ours: two study guides (254 pages), a certificate with your name, and a badge valid for 12 months. Pass the exam at 80% and they're yours. Stuck on a package: guide, forum or colleague first?

0:26
Ryan Mangan avatar
Ryan Mangan@RyMangan·Oct 22

If MSI is what you know, MSIX can feel unfamiliar. It works differently: the app runs in a container, installs per user, and updates in blocks. Once you see how, it makes sense. Start with MSIX Fundamentals. It's free. What caught you out first, moving from MSI?

0:32
Ryan Mangan avatar
Ryan Mangan@RyMangan·Oct 20

You've heard of MSIX. But could you explain how it works? App-V is end of life. What's your plan? We built free training to answer both: two courses, study guides to keep, a badge to prove it. Challenge: explain how an MSIX gets onto a device in one sentence.

0:48
Ryan Mangan avatar
Ryan Mangan@RyMangan·Oct 14

We've made our MSIX training free. Both courses, the exams and the certificates. Short video lessons, a study guide per course to keep, and a badge when you pass. If you package or deliver Windows apps, it's for you. Which MSIX topic should we explain next?

0:30
Ryan Mangan avatar
Ryan Mangan@RyMangan·Jun 21

ASK FOR THE SAVINGS REPORT FIRST Do not start with a clean-up project. Start with a savings report that shows what is still being paid for across Microsoft 365 and Azure, what is oversized or unused, and what can be fixed first. With #EtherInsights, the first step is low effort: - read-only visibility - no deployment - proof of unassigned licences, idle virtual machines, oversized resources and forgotten services - guided next actions, not another passive dashboard If you want a clear view of where spend has stopped earning its place, get your savings report. #CloudCostOptimisation #Microsoft365 #Azure

Post attachment
Ryan Mangan avatar
Ryan Mangan@RyMangan·Jun 9

RISK, RECOVERY AND COST NEED ONE DECISION A VDI exit stalls when risk, recovery and cost are argued in separate rooms. The next step should be one planning motion, not three parallel debates. The Windows 365 Migration Assessment: Risk, Recovery & TCO gives the buyer group a usable decision pack: - first-wave cohort shortlist - one-to-one versus Frontline recommendation - Microsoft Hosted Network versus ANC rule - recovery baseline for post-cutover support - TCO assumptions shaped by the estate mix That matters because standard desktops do not need edge-case architecture. Move the stable majority first. Keep networking simple by default. Prove the recovery path. Then model the numbers against the right desktop mix. #EtherInsights carries that into day two by keeping sizing, usage and ownership clear after cutover. If you want the assessment outline, comment Assessment. #Windows365 #VDI #DigitalWorkplace

Post attachment
Ryan Mangan avatar
Ryan Mangan@RyMangan·Jun 3

ETHERINSIGHTS SHOWS WHAT TO KEEP, FIX, OR REMOVE A cost view without a next move does not change the bill. That is why #EtherInsights is built as the visibility and action layer across Microsoft 365 and Azure. It helps teams see what is sitting in the estate, what is oversized, what is unused, and what has drifted away from value. - Expose idle and forgotten resources - Highlight oversized Azure capacity - Surface low-value or unused licences - Show spend with no clear owner - Turn findings into practical next steps Read-only access means no deployment work and no disruption to production. The result is proof in hours, not months, and a clearer route to a savings report that buyers can act on. #Azure #Microsoft365 #CloudCostVisibility

Post attachment
Ryan Mangan avatar
Ryan Mangan@RyMangan·May 25

SAVINGS REPORTS SHOULD SHOW WHAT IS STILL BILLED A savings report is only useful when it shows exactly what is still being paid for. #EtherInsights turns read-only tenant visibility into a report your team can review, challenge and act on. Key Features - Read-only visibility across Microsoft 365 and Azure - Unassigned licence analysis by SKU - Duplicate licence allocation detection - Idle and oversized Azure resource review - Costed findings with prioritised next actions - Output built for operational and commercial review Technical Benefits - Separates billed estate from active estate - Connects allocation, usage and spend in one view - Highlights shelfware and low-value capacity clearly - Gives buyers proof before broader optimisation work starts - Makes remediation easier to assign and validate Deployment fit & scope - Microsoft 365 licence estates - Azure subscriptions and resource groups - Read-only access model - No deployment-heavy change required - Suitable for IT, operations and finance stakeholders When the report shows what is unused, oversized or forgotten, the savings conversation becomes specific. Recovered budget can then be redirected with evidence, not assumption. #CloudCostVisibility #Microsoft365 #Azure

Post attachment
Ryan Mangan avatar
Ryan Mangan@RyMangan·May 22

ESTATE MIX SHAPES WINDOWS 365 TCO A TCO model fails when every desktop is treated as the same desktop. Key Features - Cohort-based estate modelling for the stable majority and genuine exceptions - One-to-one versus Frontline recommendation based on concurrency, not an average user profile - Microsoft Hosted Network as the default design, with Azure Network Connection separated as an exception path - EtherInsights as the assessment and day-two control layer for sizing, usage, ownership, and recovery - Open modelling of licence baseline, networking exceptions, and rollout assumptions Technical Benefits - Replaces blended desktop pricing with cohort-specific assumptions - Shows where Frontline share changes the estate shape - Prevents ANC exceptions being buried inside the default model - Connects failure domain decisions to recovery planning and operating ownership - Gives finance, architecture, and service teams one model to evaluate Deployment fit & scope - Enterprise or Business one-to-one for mainstream all-day users - Frontline dedicated for shift, part-time, and contingent users who need a personal desktop - Frontline shared for short task-based access with one user at a time - Microsoft Hosted Network first, Azure Network Connection only where controls or application reach require it - Source VDI estates under review: Citrix, VMware Horizon, on-premises pools, and IaaS-hosted desktops If the estate model is still split across separate spreadsheets, pilot notes, and architecture decks, the decision is still too loose. Start with the Windows 365 Migration Assessment: Risk, Recovery & TCO. #Windows365 #EUC #VDI

Post attachment
Ryan Mangan avatar
Ryan Mangan@RyMangan·May 19

THE PILOT NEEDS A RECOVERY SCORECARD A pilot is not credible until you can show the recovery path. The service desk does not sign off because a desktop launched. It signs off when a user can get back to work quickly after something breaks. For a Windows 365 pilot, prove recovery in a clear order: - Restart for routine stuck-session issues - Restore to a known-good earlier state where policy allows - Reprovision when the Cloud PC needs a clean rebuild Windows 365 gives teams a practical ladder here. - Enterprise supports point-in-time restore - Business uses defined restore point intervals - Action status for Restart, Restore and Reprovision can be tracked through the Cloud PC actions report Then publish the numbers that matter to service delivery: - P50 and P90 time to productivity by recovery action - Tickets per 100 users for desktop access and performance - Self-resolved restart rate - Action success rates by restart, restore and reprovision That is where the operating model changes in practice. - Recovery becomes part of the service, not a separate architecture exercise - Many single-user incidents avoid the old VDI cycle of recompose, pool rebuild or profile repair - Service desk leaders get evidence they can defend internally #EtherInsights helps teams make that proof usable. - Identify the stable majority to move first - Match one-to-one or Frontline to actual concurrency - Keep networking simple by default - Keep sizing, usage, ownership and recovery visible after cutover If you want the assessment structure we use before pilot design, comment Assessment. #Windows365 #EUC #ServiceDesk

Post attachment
Ryan Mangan avatar
Ryan Mangan@RyMangan·May 15

DO NOT DRAG VDI NETWORKING INTO WINDOWS 365 If every Cloud PC depends on customer routing, DNS and subnet hygiene by default, you have copied the old failure domain into a new service. Key Features - Microsoft Hosted Network as the default deployment path for most users - No need to build and maintain customer-managed VNets, firewalls, routing rules, or NAT gateways - Multi-region selection helps spread users so one regional issue affects only a fraction of the estate - Windows 365 Enterprise uses Intune for device management and Entra ID for identity and access control - Azure Network Connection stays available for genuine line-of-sight requirements - MHN and ANC can run side by side in the same estate Technical Benefits - Removes avoidable network complexity from standard desktop delivery - Reduces shared failure modes tied to customer DNS, IP capacity, routing, and sync timing - Shrinks the operational handoff between EUC, network, and platform teams - Supports a simpler management model centred on endpoint operations, not VDI platform engineering - Keeps Conditional Access close to the identity plane Deployment fit & scope - Use Microsoft Hosted Network for the stable majority of desktop users - Use ANC only where hybrid join, Kerberos or NTLM, SMB, or on-prem line-of-sight is genuinely required - Choose one-to-one Cloud PCs or Frontline from concurrency, not an average user profile - Assess legacy VDI pools separately so edge cases do not set the default architecture - Use #EtherInsights to prove who moves first, where ANC is truly needed, and how the estate should be controlled after cutover If you want a rules-based path that keeps the default simple and isolates the exceptions, ask for the Windows 365 Migration Assessment: Risk, Recovery & TCO. #Windows365 #EUC #DigitalWorkplace

Post attachment
Ryan Mangan avatar
Ryan Mangan@RyMangan·May 14

WASTE NEEDS A NAMED NEXT STEP Waste stays put when the next move is unclear. In Microsoft 365 and Azure, teams can usually spot the symptoms: - idle environments still running - oversized capacity after peak demand - old test and dev estates left in place - spend that nobody owns What is usually missing is the operational hand-off. #EtherInsights gives teams read-only visibility across the estate, then turns that proof into guided next actions: - show what is idle - show what is oversized - show who should act - provide guided fixes and ready-to-run scripts That is the difference between seeing waste and removing it. It is how visibility becomes a savings report buyers can use. #CloudOptimisation #AzureCostManagement #Microsoft365

Post attachment