Do you have any video about the costs of using around 2TB of information on Azure file share instead of having all my file server within a VM? I would like to know more about it.

how to upgrade in place SQL Server Standard 2019 to SQL Server Standard 2022?

It is always pretty much interesting to know things behind the scenes… an another great efforts from you unmask things ..

How do you revert back, if the upgrade fail ???

Can you do the same for Windows 10/11 Pro/Ent/Multi-session 21H2/22H2/23H2 to 24H2 ???

Very well explained. Thanks a lot!

Express route

On prem clients still saving to on prem file server. This on prem file server is syncing to the Azure files cloud share. How do your users running in Azure access the synced data. Do you just map azure clients a drive to the azure file share that is being synced with on prem. Any issues with multi direction sync between these two locations?

What will be the cost for fallback from Azure to on Prem for the same VM scenario that you have chosen in this video.?

For fallback from Azure to on prem would that cost as well. ALSO bandwidth cost would down after initial replication after initial replication ?

IT everywhere swooned, laughed, then cried after learning about this. It really is coming for our jobs 😅

Copilot for Azure is a great way to understand your Azure costs in a simple conversational way.

Looks like a handy tool for people who want to save some money on infrastructure

🤔 Promo>SM

Please do more on az140

So how does one with an AAD joined machine access Azure files when NOT on a company LAN but on the road or at home? I thought SMB's generally block SMB over the internet.

THanks for sharing the videos :) , Very Useful , appreciate it

📌 Continuing with Microsoft's suggestions, it's more efficient to distribute users across multiple smaller VMs instead of a few large ones. This strategy improves performance and conserves resources. 💾 Premium SSD storage is a must for production workloads with SLA requirements. And if you're dealing with graphics-intensive programs, consider GPUs! hashtag#ResourceManagement hashtag#Performance

📌 Based on Microsoft's recommendations for sizing virtual machines in Remote Desktop Services, it's suggested to have at least two physical CPU cores per VM in single-session scenarios, typically four vCPUs with hyper-threading. 🖥 For multi-session scenarios, more than two cores ensure stability and a better user experience. ✅ Remember, exceeding 32 cores in VMs can increase synchronization overhead. hashtag#Microsoft hashtag#VirtualMachines

looking forward to seeing how to configure and deploy avds

📌 Creating a golden image for your Azure Virtual Desktop deployment can simplify your virtual environment management. Here's a quick guide: 1. Start by creating an Azure VM - this will serve as the base for your golden image. 2. Optimize your VM - ensure it operates smoothly by applying necessary patches and updates. 3. Capture the state of your VM - this saves the current configuration and allows you to replicate it for other deployments. 4. Once your golden image is set up, you can use it to quickly deploy new, identical VMs. This process not only saves time but also ensures consistency across your virtual environment. For more detailed instructions, check out this informative article from Microsoft: learn.microsoft.com/en-us/azure/virtual-desktop/set-up-golden-image #Azure #VirtualDesktop #GoldenImage

Thanks for this informative video

📌 Insights from the video 👀 : 1⃣ Pooled Desktops: Multiple users share a VM, perfect for those who don't need admin access. It uses a recommended image that includes Windows 10 Enterprise multisession, exclusive to Azure Virtual Desktop. 🌐👥 2⃣ Personal Desktops: Each user gets their own dedicated VM and typically has local admin rights. Ideal for installing/uninstalling apps without impacting others. 💻🔐 3⃣ Customization: Personal desktops allow users to customize their environment including user-installed applications and saving files within the desktop environment. 🖥🎨 4⃣ Dedicated Resources: Personal desktops can assign dedicated resources to specific users - a boon for certain manufacturing or development use cases. 🏭👩‍💻 Ep04 coming soon: Service updates for Azure Virtual Desktop desktops ! 🚀💯

👉2nd Video in the Series: Azure Virtual Desktop Components: kzbin.info/www/bejne/mXS2Yal3jsZ0o80

📌 Missed the 1st video in the series on unit Azure Virtual Desktop for Enterprise? Check it out: kzbin.info/www/bejne/jorLfX2kbLdqjZY

📌 Highlights from the video: Microsoft's Azure Virtual Desktop 🖥 is a complete desktop & app virtualization service in the ☁! Microsoft-managed Components: 🌐 Web Access: Access via any HTML5 web browser. 🚪 Gateway: Connects remote users globally. 🔄 Connection Broker: Manages user connections. 🔍 Diagnostics: Event-based aggregator for user actions. ⚙ Extensibility components: Managed via PowerShell or REST APIs. User-managed Components: 🌐 Azure Virtual Network: VMs communicate privately. 🔒 Azure AD: For identity & access management. 📂 AD DS: VMs must join an AD DS service. 🖥 Session hosts: Supports various OS including Windows 10/11 Enterprise (single and multisession), Windows Server 2012 R2 & above, and custom images. 📚 Workspace: To manage & publish resources. #Azure #VirtualDesktop #CloudComputing #Microsoft 💻☁🌐

📌 7 insights about Azure Hub & Spoke virtual networking: 1. A hub-and-spoke network topology is an efficient model for managing common communication or security requirements. 2. It allows centralized services that can be shared by multiple workloads, like network virtual appliances (NVAs) and DNS servers, saving on costs and management effort. 3. Peering workload virtual networks from different subscriptions to a central hub can overcome azure subscription limits for large azure environments. 4. This model allows for a separation of concerns: You can deploy individual workloads between central IT teams and workload teams. 5. The hub-and-spoke topology gives your IT department an effective way to enforce security policies in a central location, reducing the potential for misconfiguration and exposure. 6. The role of each spoke can be to host different types of workloads, providing a modular approach for repeatable deployments of the same workloads. 7. The hub deployment is bound to a specific Azure subscription, which has restrictions and limits. When limits might be an issue, you can scale up the architecture by extending the model to a cluster of hubs and spokes.

Informative !! thanks .Please keep making the series .

📌 Highlights from the unit: AVD is a comprehensive, cloud-based solution that gives you the power to build desktop infrastructure at an enterprise scale - catering to over 1,000 virtual desktops and beyond! 📊 It's accessible across devices - Windows, Mac, iOS, Android, and Linux - and accessible through most modern browsers. This ensures seamless access to remote desktops and apps, anytime, anywhere. 💼 Demand for such robust virtual desktop solutions stems from sectors requiring stringent security and regulatory compliance like financial services, healthcare, and government. It also caters to elastic workforce needs arising from remote work situations, M&A activities, short-term employees, contractors, and partner access. 👥 Specific employee groups such as BYOD and mobile users, call centers, branch workers, and even specialized workloads like design, engineering, legacy apps, and software development tests can greatly benefit from AVD. 🏗 The architecture of Azure Virtual Desktop integrates seamlessly with your on-premises network via ExpressRoute and Azure AD Connect. You manage your AD DS and Azure AD, Azure subscriptions, virtual networks, Azure Files or Azure NetApp Files, and the AVD host pools and workspaces.