Specifically, we are going to cover how you can make additional modules available to you when utilizing the “Run PowerShell Script” activity in Power Automate Desktop. Having said that, if you only need a little customization, such as installing PowerShell modules, going the custom image route may seem like a lot of unnecessary work, and that’s exactly what this article is here to do: to help you avoid having to go that route.
If you do find yourself with a use case where there’s a lot you need to change about the image utilized, have no fear, as custom VM images are available, and will allow you to setup your image exactly how you need it. Now, while they’re inevitably very cool, there’s one caveat to them since you’re not managing virtual machines, you’re likely going to be using a default VM image that may not have everything you want and/or need on it.
VMs get spun up, as needed, to execute unattended jobs, which scale effortlessly, only utilize resources when you need them, and keep you out of the business of managing virtual machines.” Me (Matt Jimison) I like them so much I even quoted myself to share what makes them great: Hoping that you will find the above updates useful, please feel free to provide your questions and feedback in the Power Automate Community.I’ve been spending time lately doing proof of concepts with Microsoft’s Hosted RPA Bots (preview) and I absolutely love how cool these things are. The support of UI automation for desktop apps in a Citrix or Microsoft Remote Desktop Protocol (RDP) virtual desktop with the use of a lightweight agent (Power Automate agent for virtual desktops) has now become generally available for all users. GA of UI automation for desktop apps in a Citrix or Microsoft RDP virtual desktop These options are available either through the standard context menu, or via the new command bar that has also been introduced in the top section of the console.
0 kommentar(er)
