Update Session Hosts from Latest Image | Windows Virtual Desktop - #04
Вставка
- Опубліковано 1 сер 2024
- #TheAzureAcademy #WindowsVirtualDesktop #CustomImages
Learn how to use the Shared Image Gallery to update your WVD Session Hosts from the latest image today at The Azure Academy.
Shared Image Gallery is a service that helps you build structure and organization around your managed images. Using a Shared Image Gallery you can share your images to different users, service principals, or AD groups within your organization. Shared images can be replicated to multiple regions, for quicker scaling of your WVD deployments.
Subscribe TODAY aka.ms/AzureAcademy-Subscribe
0:00 Start
2:30 How Shared Image Gallery Works
3:25 Capture first Image
4:50 Import Image into the Gallery
7:20 New HostPool from the Gallery
11:30 Shadowing User Sessions
13:40 Create new Image version
16:43 Happy Learning!
📲 Follow Azure Academy
►Twitter: / msazureacademy
►LinkedIn: / dean-cefola-2902934b
►Facebook: / azure-academy-87979521...
💰 Support Azure Academy
►Patreon: / azureacademy
📡 Contact Azure Academy
►Email: Dean.Cefola@Microsoft.com
►MAIN Channel: / azureacademy
🤣Playlists
►Azure Governance: aka.ms/AzureAcademy-Governance
►Azure Fundamentals: aka.ms/AzureAcademy-Fundamentals
►Azure Blueprints: aka.ms/AzureAcademy-Blueprints
►Azure AD Series: aka.ms/AzureAcademy-AzureAD
►Azure ARM Templates: aka.ms/AzureAcademy-ARMTemplates
►Azure Automation: aka.ms/AzureAcademy-Automation
►Azure Networking: aka.ms/AzureAcademy-Networking
►Azure Migrations: aka.ms/AzureAcademy-Migrations
►Azure Backup: aka.ms/AzureAcademy-Backups
►Azure New Features: aka.ms/AzureAcademy-NewFeatures
►Windows Virtual Desktop: aka.ms/AzureAcademy-WVD
►Cloud Adoption Framework:aka.ms/AzureAcademy-CAF - Наука та технологія
This is the one I was waiting for :)
Awesome! Join us for the premiere Monday 12:00am EST
@@AzureAcademy Loving all the great videos. How about one around delegating different roles on the new ARM model? Would love to be able to delegate to the helpdesk to do things like disconnect user sessions and drain a server if there is an issue with that node when I'm not available.
understood Robert. I am writing a doc for the Product Group on WVD RBAC roles and permissions. I will include your thoughts as well....as soon as we are done with it I will see if there is enough here to make a video as well.
Azure Academy Great. Will that doc be available for customers and I’d be happy to test it for you.
awesome...thanks Robert!
High Quality - one of the best youtbube video style I have ever seen!
Wow, thanks Marcel
gracias por los videos, tus ejemplos me ayudaron a entender procesos que no encontraba, por la mucha información que requiere uno conocer de WVD.
Me alegro de poder ayudar y gracias por verlo.
Awesome video and hoping to get the more features soon.
(schedule power-up/down and auto scale)
Thanks...stay tuned for those other features!
Very helpful, Thank you very much
Watch the latest video on image building here
ua-cam.com/video/QxRb9sV3tHU/v-deo.html
Awesome video Dean. Thanks for sharing these videos. They have been tremendously helpful. By the way what does drain mode do?
Thanks Malcolm! Drain mode blocks users from signing in to the session host.
hi team , this is cool video for image updation. Was very difficult to manage via old method. awaiting your video on disk encryption feasible for wvd setup
Working on Disk Encryption now...stay tuned
Another excellent and quite helpful video, thanks for sharing it and yes - thanks a ton for that cool tip to shadow sessions, would surely be awesome if it is baked directly in to the Azure portal as a feature.
Thanks...I will pass on the feedback.
@@AzureAcademy would it be safe and advisable to delete the captured image once it is injected in the image definition as a version?
Yes, after you have captured the image version in the SIG you don't need the image anymore...
@@AzureAcademy would you need the public IP address on the session host instance in order to get the Shadowing working currently? Or can jump-box be leveraged to do same using instance's private IP address?
in WVD, you do not connect to the public IP address of the Session Host VMs...in fact generally speaking, the session host VMs should NOT have an Azure Public IP Resource at all.
You need the internal IP Address of the Session Host, for example: 192.168.0.15
you would start the shadow from another system but they need to be able to reach each other over the network.
So you could be on a VPN or another WVD session host or anywhere else...as long as you can RDP to the private IP of the session host like 192.168.0.15
Amazing stuff! Yes, please let the product group know regarding a shadow session option from the portal GUI :)
Thanks I will provide that as feedback
@@AzureAcademy tyvm. As you likely know this is a default feature for traditional RDS setup out of box. It has been really helpful for troubleshooting scenarios especially when users are increasingly remote now due to Covid-19. By the way, I came across your videos and I must say, they've been very informative and a life saver. We are deploying WVD (RemoteApps) for the first time as an enterprise level solution for 9000 users. Currently using Workspot (basically RDS technology). Exciting to move to the Azure counterpart. Thank you for sharing your knowledge!!!
That is Awesome! Thanks for letting me know.
@@AzureAcademy Easier access to shadow/control session would be wonderful! It would be great to see an auto-scale blade similar to Nerdio's UI, too.
agreed...like wouldn't it be great if shadow and remote control was built right into the WVD portal...if only, am I right! 😉
Hi Dean, I am following your videos like I am following a US TV Series, haha.
Wow...that is awesome, thanks!
This may be a dumb question, but after you choose to capture the image and delete the VM the separate managed disk is of course still left behind. Is it safe to delete that managed disk resource after creating the image, or even delete that image resource after adding in the Shared Image Gallery definition? I guess I'm just unsure if the Shared Image Gallery still needs those resources or does storage of its own with the replicate option.
Nope...once you have captured the image in the Shared Image Gallery you can delete the managed disks and image.
Would be nice to have this automated with an ARM template like in the old non-arm days :) Seems like a lot of hassle to, 1, enable drain mode on all existing hosts, 2 provsion new VMs, 3 deleting all VM, and finally delting the objects from AD DS.
You can automate this process but you need to do it from something like PowerShell that can reach all those different technologies.
PowerShell Can kick off the ARM template to build new VMs. select systems that match the right naming pattern, talk to WVD and put those session hosts into drain mode pause for however long you want then delete the old session hosts...finally clean up AD and Azure of the old artifacts
Hi Dean Thanks, I have replicated the image version from SIG to another region but could not locate it, I was able to see the status that its available in 2 regions though and what is the Limitation on number of machines per hostpool.
The image won’t visibly show in another region...it is in the SIG
Open the image version and look at its replication properties
It should show in l the regions you picked
Hi Dean, great video and any feature like the shadow option is a great addition for admins :)
Two questions, is it possible to create a follow-up video for the same subject but using automation instead of portal? Might be interesting to see this part too and also show the IaC part of azure.
The second question, any chance we can see implemented boot from image? Or this is unlikely feature to get in azure?
Cheers,
Ciprian
ARM Template implementation of WVD...sounds great! If I understand how boot from image works...no.
Azure doesn't boot VMs from images. Azure builds VMs from images...once built the VM has no relationship to the image.
Hi Dean, for boot from image i mean a feature similar to citrix PVS but i was expecting to be no.
Thank you for the reply!
Cheers,
Ciprian
anytime
It would be great if you can also create a similar video showcasing the licensing aspects in details covering how does it work in the actual production environment for both server as well as client OS types of host pool VMs. It is one of the quite confusing area with limited documentation around what sort of license is required for end users (Azure AD users), where it can be assigned, how it can be procured or if there is something specific that needs to be done for Host pool VMs once they are provisioned in production environment in order to be complaint from licensing perspective etc.
I agree that this is very...very important...however, I don't think this makes for a great video. in video and content creation it is ALWAYS better to show then tell...so Licensing documentation talks are not exciting to show. so I would direct you to the requirements doc or talk to a license expert / your account teams
docs.microsoft.com/en-us/azure/virtual-desktop/overview#requirements
@@AzureAcademy Makes sense! Looked at the documentation, it surely looks good! quick one - just for clarification - If you are creating a VM from marketplace Win10 Ent Multi-session and customizing it further to create your session hosts from it AND as long as users accessing remote apps or desktops having either of Microsoft 365 E3, E5, A3, A5, F3, Business Premium
, Windows E3, E5, A3, A5 license assigned to them - does this qualify to be called as a complaint setup?
based on the docs I would say YES...however I am not a license expert, so to be 100% sure I would check with them.
Hey, great video! The only thing I'm kinda missing is how to update the existing VM's in the hostpool with the new image. Is that just as easy?
Azure doesn’t work that way.
Once you create the VM it doesn’t have a relationship to the image...however you can do this yourself if you use snapshots and OS disk swaps like I showed in this video - ua-cam.com/video/PCWJEoG8X-I/v-deo.html
Deploy a new VM
Update it with patches etc.
Take a snapshot
Deploy a new disk from it
Do the OS disk swap
However it is easier to deploy a new VM from the latest image and throw the old VMs away
@@AzureAcademy Thanks for explaining!
anytime
Dean, Awesome video as usual. I love the rip and replace strategy. How could we automate cleaning up the active directory computer objects for the old VMs? Also how could we automate deleting the azure resources pertaining to the old VMs i.e Disk, NICs etc?
Thanks Mina! To do all of that you need to manage the script outside of the Azure imaging process. You could script the whole process through Azure Automation or Azure DevOps…or a management VM.
The other way to go is not delete the AD Computer objects, but reuse them.
@@AzureAcademy thanks dean 😀
👍👍
This is great! Assuming, you can change an older version to the 'latest' to allow you to rollback changes?
You can roll back with snapshots. But to be clear in Azure you don’t do rolling OS upgrades like you would on prem. Each VM disk has an OS version on it and it doesn’t change. This process puts a new disk from a new image on the VM. Is that what you had in mind?
@@AzureAcademy Yeah, when the image is updated, you set it to “Latest” so that the next host gets created with the latest image. I was wondering if you can change an older version back to latest to then create new hosts from that, ie if a update or patch didn’t go according to plan.
no and yes. NO you cannot change an older image to latest, however you can IF you deploy a VM from that old image...then capture the VM as a new image that you upload to the gallery and mark it as the latest image.
@@AzureAcademy So the recovery, would be deploy from an older version, ie it doesn’t have to be latest.
yes you can deploy an older version of the image or revert a single VM from a snapshot
Hi Dean, got one question. If I want to deploy new hosts to an AVD host pool from an Image stored in a SIG, does the image have to be in the same region as the host pool or it doesn't matter? Thanks!!
Yes, IF you want to deploy an image in east US, the SIG needs to have the image replicated into that region. This does not mean the image must be created in East US. But simply replicated to East us
Hi Dean, I was revisiting your WVD sessions recently, because there were so many updates.
I wonder what the disadvantages of using the first option, let the VM patch themselves. Is it version consistency or something else? We definitely need to spend some time monthly to do the RIP AND REPLACE strategy.
I am just recommending your video and methods to our customers, but I just cannot convince myself, is it worth the effort to do RIP AND REPLACE monthly.
Thanks
The main benefit of rip and replace over patching is speed agility and automation
You don’t have to manage a third-party system or have the skills since you wouldn’t be patching and you can become more dynamic and faster with a automation pipeline to manage your images and update your systems however I understand that every organization is not ready for that level of DevOps in mindset or toolset so do what’s right for you today and then plan on going this direction for tomorrow
@@AzureAcademy Thank you Dean, really helpful.
anytime!
Great video, just tried it myself but have hit an issue. So I have a Host Pool with 2 Session Hosts in it, WVD-W10-0 and WVD -W10-1, I used SIG and updated the image. I then added 2 session hosts based off the latest SIG Image to the same Host Pool. It created WVD-W10-2 and WVD-W10-3, But it only added WVD-W10-2 to the pool and left WVD-W10-0 behind. So now I only have WVD-W10-0 (on the old image still) and WVD-W10-2 (on the new image). I was expecting it to replace both with 2 and 3. What did I do wrong?
Sounds like you did the process correctly. Azure VMs DO NOT have a relationship to an image. When you update the image, you expected all the VMs that have been deployed from that image to also get updated. This is not the case in Azure today. The VM does not have a relationship to the image after it is deployed. This is NOT a WVD thing...this is how Azure works in general.
You would need to deploy 2 new VMs and throw the old ones away after the new ones are built.
Nice video! How do you address the limit on the number of times you can Sysprep the image?
because each version is it's own copy of the image this has not shown to be an issue.
@@AzureAcademy Thanks Dean, I was under the impression of minimizing the sysprep count , use the original image before syspreped(snapshot of parent image, create disk) make changes to it and create new version of it. But still we can use already sysprep image to create machine, again make changes and do sysprep again ..add version to shared gallery ?
Dean, Please help me out with the best method to follow, shall I just use share image gallery latest version to create vm out of it and make changes....add new version to SIG and update hostpool
Yes on the snapshot method
also newer versions of Windows can rearm sysprep 1001 times
docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep--generalize--a-windows-installation#limits-on-how-many-times-you-can-run-sysprep
Hey Dean. Is there a method for rolling your image back to a previous version if the latest version has issues that surface, say with a recently updated application?
I ask because your WVD Host Pool is set to deploy VMs using the ImageGallery\Latest flag, so it uses the latest image
So is there a way to roll back to the image 5.0.1 if 5.0.2 has issues?
Or is the only "process" to roll back, to get the snapshot that created your 5.0.1 and create a new image version 5.0.3 and deploy new VMs. So the image version increases, but the actual image has essentially been rolled back?
First off...I would test the image before I uploaded to the gallery...but if you already did and NOW you have found an issue.
There is no way to roll back the latest version.
I would delete the image version that has an issue and go back to the last known good image or snapshot of an image you have.
Then fix your issues and upload a new version of the image to the gallery.
@@AzureAcademy cool, pretty much what I expected, and a perfectly fine way to go about it
Thanks for replying to my incessant comments on all of your videos, it is much appreciated!
No worries...happy to help!
Is this method going to work for Server operating Systems ? i.e. 2016 OS RDS ?
great question CTX Shekhar! The WVD docs only refer to Windows 10 at this time - docs.microsoft.com/en-us/azure/virtual-desktop/teams-on-wvd#install-the-teams-desktop-app however I would suggest you test it on server...since server 2016 is an OS that TEAMS supports.
docs.microsoft.com/en-us/microsoftteams/get-clients#desktop-client
However, this is an Azure feature around WVD...so I would NOT expect support for an RDS environment
Instead of Rebuilding the Host Pool couldnt you just Deploy a new VM from the Image then add it to the host pool by using the WVD agent download?
Yes you can, that is a good way to do it.
Now there is even better integration with the shared image gallery and WVD making this a lot better
It would be Awesome if the mstsc shadow feature were baked into WVD
Yes...yes it would...stay tuned!!!
When moving to the new image version do we have to delete all our old VM's and recreate new VM's? Is it possible to keep the old VM's intact and just change the version on them?
In Azure VMs in general cannot recycle the VM and upgrade the OS…but something is coming soon to help with this…Stay Tuned!
Thanks Dean for this super informative video as always!
But how to we reimage in a production Host pool with 20 machines environment ?
What could be the approach as deleting machines will hamper the production and probably change in names will occur if we create extra machines.
Please share your insight.
Thanks in advance :)
A Vm OS Version can’t be updated like an on prem VM. You do need to deploy new VMs so you have more capacity then you need, then delete the old VMs.
YES, this approach would mean you get VMs with new names. Why is it important to keep the names?
@@AzureAcademy in a production environment name changes would be a great deal as therr will be appropriate approvals required every time.
Dean, can Shared image gallery solution work with Fall 19 aswell?
@@AzureAcademy Please let me know if this works with Classic WVD
yes, any Image can use the Shared Image Gallery
this can work in classic WVD as well...you just deploy a custom image and add the WVD agents to the VM...I would do it with a custom script extension.
Also...I suggest you migrate to the new ARM version of WVD...or build a new host pool...Classic is NOT getting new features. However it is still supported...think about it 😊
Hi,
Could you please clear my doubt.
To update the VDIs of an existing AVD pooled environment, the only option left to us is to update the image with required setting or app and then create new VDIs using it. Is that correct?
Regards,
Ashish Arya
As of today…yes. But stay tuned, something amazing is coming soon
Hi Dean, thank you for another nice video! I have a question concerning option "Add virtual machines to a host pool". Generally it's a bit disappointing that fields "ARM template file URL" and "ARM template parameter file URL" don't support URL with SAS token. Sometimes you might have something in the ARM template you don't want to expose to the public. Do you know if this is something on the product team's backlog for the future?
Thanks a lot
Rgs
Martin
Not that I heard of, but generally when I have something in a template that I want to protect I use Azure KeyVault. Put the reference in there and give ARM the keyvault reference, which it will look up and return the value during the build
@@AzureAcademy Hi Dean, absolutelly! The chellange is when you’re not allowed to store secrets in custemr tenant/subscription. I’m not sure if referencing keyvault/secret across tenant/subscription will work for this case. Therefore I just think that fields could support URL with embeeded SAS token. Seems like not a big deal as it looks like just a regex there that checks if provided URL ends by .json ;)
got it...that field in the portal is currently limited not allowing SAS at this point...but I will talk to the product group about your use case
@@AzureAcademy Thank you Dean, I appreciated!
anytime!
This may be a stupid question but how are SSUs CUs addressed for WVD images? I have to believe there is an automated way to patch these images and add them back in with an incremented version number all with minimal effort, yes? 🤙
great question Marc...check out my video on the Azure Image Builder to see how to update patching to your images with a single check - ua-cam.com/video/zIdOutv0doE/v-deo.html
@@AzureAcademy Thank you brother!! 🤙 I just started setting up an AIB lab earlier today after using the ol Google!! Totally going to watch this vid you referenced as all cuz your videos have been gold.... SOLID GOLD 🥇 🤙
👍👍
Are there any frontend Api's availiable to access the published apps in WVD , which we can use and integrate apps in our own environment ?
there are APIs...but the docs are not out yet so I can't point you towards anything yet...stay tuned
@@AzureAcademy Thanks for your update .. By when can i expect the apis to be available ? Any timelines we have ? And also one issue i faced with this shared gallery image VM creation is that - the VM is not shown inside the host pool after creation from image ..
It should be out at or before the new WVD Spring Update is generally available...which is going to be soon.
Was the WVD Agent installed on the VM When you captured it as an image?
If so it was already registered with a hostpool...so you would not see it again.
Remove the WVD Agent, Bootloader and all other WVD / remote desktop services apps before you capture
@@AzureAcademy Thanks alot for your help.. These details will be really helpful for our team in further development .
happy to help!
does Windows 10 Enterprise multi-session, Version 2004 + Office 365 ProPlus - Gen1 is supported or any one tested with SIG? I am facing issue with this version and unable to connect after login to RDS client (Web & Desktop). please advise.
There are no issues that I am aware of with Windows 10 2004 with SIG of WVD in any way.
Please verify that the RDS Bootloader service is set to automatic and is running
also that the RDS Networking SxS stack is installed as well.
+Muhammad Awais it is supported I am using it without issue. Are the WVD session hosts available or unavailable in the host pool?
+1 Shadow Sessions easily
Thanks TimTubed...I will pass it on
Shadow sessions with simple delegations is what we are after. Would love to be able to get the service desk to be able to do this without local admin
how about if there was a specific RBAC Group in Azure for shadowing sessions?
I like that idea.
cool...noted
So in the video, once you updated your image, you added a new machine and presumably deleted the old machine. Is there a way to make it work like existing systems where once you update the image and push it out, all of the existing machines get updated with that image? I know this is how Citrix does it, and it would save a bunch of time.
Yes with Automation or a Pipeline you can do this but it is not built into the WVD service...YET!
Stay Tuned!
@@AzureAcademy any idea of when we could see this functionality. I feel like the inability to automatically shut down and spin up vms as workload decreases partnered with the inability to update vm session host images makes jumping to wvd a little difficult for small companies / it departments
There is not anything I can share publicly but I will pass your comments to the product team
@@AzureAcademy can you also pass a desire to refresh session hosts with the latest image :)
Delete current and deploy new ones with the new image.
Tha k you so much for these videos dean. Incredibly useful!!!!
That is a great suggestion…stay tuned
Great video. Is a simpler method on the WVD roadmap? If you just want to apply monthly security updates this is a lot of steps. Would love to see Windows 10 Enterprise Multi-Session added to the Azure Update Automation Runbook.
Custom Image creation isn't planned to change. Even if you add automation to the process...you still need to do all the same steps.
Monthly patching process is something like...
1. build VM from existing base image
2. update and reboot...repeating until all patches are installed
3. sysprep image
4. upload image into shared image gallery
5. deploy updated VMs from the image
6. decommission old VMs
HOWEVER...if you use the Microsoft provided images from the Gallery...all this is done for you...up to you.
@@AzureAcademy If you use Microsoft provided images, will they be automatically patched and updated? I'm guessing the base image itself is "ready to go" but still need to deploy new machines and delete old ones, correct?
Great question jossemann! The images inside Azure's image repo are updated every month. However once you deploy a VM from that image, it is in your environment and you are responsible to patch it. In WVD I generally do not recommend patching...but rather, a RIP & REPLACE strategy. Then you keep you image up to date and push out new VMs from the image.
@@AzureAcademy Yeah, then it's what I expected. Thanks for the clarification.
Keep up the good work on these awesome videos!
@@AzureAcademy With the RIP & REPLACE strategy, do you foresee MSIX app attach being the primary delivery method for line-of-business apps? Until that is fully baked aren't you on the hook to install LOB apps on the image each time you rip and replace? Thank you!
A scenerio.. If we add a new session host to a hostpool with some new apps to it then how it will be reflected in the other session host available in the host pool... the new version image will just update the new session host. Then how other session hosts available in the host pool will reflect the changes ? If i add a new aap to the new version image .. that will be just available in the new session host. How here then other machines take up the request for it ...
The images do not have a relationship with the VMs. So you have to either patch existing VMs or deploy new VMs and throw old ones away
Great guide! Very helpfull.
But I have something stranges, when I add the new host VM's to the pool. The VM's are not added to the pool. The VM's are created, I can see them in the VM portal. But not under session host. Any idea?
Imaging and building VMs into your host pool are 2 separate things.
Normally you would NOT have the WVD agents in your image…did you try to have your WVD agents in your image?
@@AzureAcademy I have reinstalled the agents. After that the vm shows up. Thnx.
Yeah…I don’t recommend putting the agents in the images ☺️
@@AzureAcademy sorry but in your video, you create an image from a live host of the host pool that had the agent installed and working. Basically to manage the image (and versioning)to update an host pool is not possible to start from an active host, without doing some preparation stuff(ex. uninstall avd agent)other than sysprep, correct?
The best practice when creating an image is to remove the AVD agent, unjoin from the domains and remove all other unique I identifiers then SysPrep so the image is clean and ready to redeploy
this new shared image gallery will be used for new sessionhost vms, is there any features once you capture new image and place it under shared image gallery, then it should automatically update existing hostpools vms to latest image or there should be option on each existing hostpool to update all sessionHOsts vm to latest image.
currently i see you create new vm with latest image under hostpool.
it would be easy not to create new sessionHost vms but to update existing vm with same name with latest image!
No, Azure didn’t do that today.
Once the VM is created from the image there is no relationship with the image. If you update the image the VM does not get updated.
In a multi session windows 10 environment, if a user installs the app, does it persist even after vm reboot? Like in Citrix PVS, nothing gets saved and vm comes to a pristine state after reboot. Does WVD works like this in a multi session environment?
WVD VMs are normal computers. If you install an app it is persistent. WVD can also be done with stateless VMs...bur typically you want everything installed in your image for that to work. Check out the video I did on this here - ua-cam.com/video/GyXx5Er9jYo/v-deo.html
@@AzureAcademy Thank you for your response. I will go through the video but I am not sure yet if that has all the answers to the below questions. Could you please let me know if my below questions make any sense? Do all the apps installed by user get installed in a user profile? it results in inconsistency if user connects to a different session host next time (in a multi session pool). How do we address this issue? Should we block user from installing the app? or can we exclude it from roaming via some fslogix configuration? if everything gets stored in profile then it results in profile bloating right? how do we address configuration drift and avoid administrative nightmare if all users have their own apps and inconsistencies?
The apps get installed like they would on any other normal computer. They are installed onto the Session Host VM...not the profile.
Think about it this way...you have 2 computers at home...if you install TEAMS onto the 1st computer is it magically installed on computer 2...no it isn't.
You would need to install it on each computer you wanted that app on.
The thing that can make it a little more confusing is FSLogix disconnects the profile from the Computer.
So when you install the app, parts of that app might install into your profile path, but the application is still installed onto the session host Computer.
So if you want that app installed on multiple computers...you need to install it on each one...But wait... there is more.
MSIX App Attach will allow you to disconnect the applications from the computer as well...check out my video on MSIX App Attach - ua-cam.com/video/6kkPLFgPaN8/v-deo.html
Dean please help me understand on this... the only difference i see between shared image gallery and normal image is that the benefit of relicating across multipe regions and having multiple copies..apart from that updating images using shared image gallery doesnt have any benefit, we still create new session host with new version of image definitions, we can do the same by creating a new image as well without using shared image gallery... your initial statement says we can automatically update to new version, doesnt make sense... kindly explain
Hey Anand, a managed image is stand alone resource. Gallery images are contained in definitions, this adds the ability to replicate the image in a single region or across multiple regions, subscriptions, azure A.D. tenants and even to Azure stack all controlled from🎊
But if you only have 1 version of your image and don’t need to deploy more then 20 VMs at a time, then a managed image is good enough
@@AzureAcademy thanks a lot Dean
. So I understand the key benefit as replication.. if i have an image which i need to update monthly but dont have to replicate or dont need to deploy more than 20 vm, then i can still go with managed image right.
Yes
Is it mean I can have different session hosts inside one host pool?
If by different you mean can you have VMs that are built from different images in the same host pool...YES you can...however they should all be the same so the users have the same experience. So you will want to use a maintenance window to put some of the VMs in the pool into drain mode, then build new Session Hosts into that pool and throw the old ones away...then complete the upgrade cycle by repeating this process until all VMs have been replaced.
@@AzureAcademy Got it, thanks so much. Your videos are very useful, hope you can upload more. By the way, hope you can create a cloud migration series..
I do have a series on Azure Migrations that you can see here - ua-cam.com/video/_LGyZMwNIiQ/v-deo.html
Hi there, I have a few questions if someone is able to help please -
1) given this video is almost 4 years old, is there a newer way of doing things or is this still the way to do it?
2) Is there anything to "boot from image" such as Citrix PVS yet?
3) At the end of the video, the host pool is left with 1 host with an old image and 1 host with a new image. How would you update the old host? Delete it and build a new VM using the latest image in the same way? How would this work when you have a huge amount of hosts and going 1 by 1 isnt realistic?
Thankyou :)
Even though this is a 4 test old video the approach is still a valid one.
There is not a boot from image feature in Azure today, but stay tuned, something like it is coming soon, and I’ll have a video on it once it’s ready for the public
This new feature will also answer your 3rd question.
But right now, you would build new hosts then just delete the old hosts
Again…something new is coming soon to make this happen…stay tuned
@@AzureAcademy amazing quick response, appreciated, and this all sounds amazing, cant wait! :)
👍☺️👍
Anytime!
🤓👍👌
This is going to be a good one!
@@AzureAcademy looking forward to it. Have been using it alot recently. Drain down mode is really useful. Messing around with images. Adding hosts, publishing apps. It does the job. Our first one is live now and happy with it. Your videos definitely made it all the more possible.🤓
Awesome! Thanks for letting me know Richard.
This video will help you to keep the host pools up to date with the latest version of your image every time you build
Unable to deployment (join domain conflict) error plz suggest to resolve this issue
if you can't join your domain the issues are either permissions, or you can't contact your domain controller.
1. Be sure that your DNS server is listed in the virtual network DNS Settings
2. if your domain controller is not in Azure you will need a VPN or express route to get to it.
the other issue might be permissions. If the account you are using doesn't have rights to join a new pc to your domain
I have global admin privilege and vnet also check if possible u can check this issue remote session
having Azure AD Global Admin really has nothing to do with your Azure Subscription...or your domain controllers...
Are your domain controllers VMs or Physical
are they in Azure or on prem?
@@AzureAcademy I don't have any Domain controller
Well there's your problem...WVD Requires a domain controller because the VMs need to join a domain
Read through the WVD requirements page
docs.microsoft.com/en-us/azure/virtual-desktop/overview#requirements