Managing Power Automate Desktop on Windows

1 Whitepaper: Managing Power Automate Desktop on Windows

Managing Power

Automate Desktop on

Windows

Summary: This playbook introduces you to the concept of managing lifecycle for Power

Automate Desktop, leveraging Microsoft Endpoint Manager tools such as Intune, SCCM and ring

deployment techniques to deploy, monitor and audit Power Automate Desktop. Watch the

video series for this playbook as well.

Writers: Thomas Barcenas (KMicro Tech, Inc.)

Technical Contributors: Apostolis Papaioannou, Ashvini Sharma, Costas Chamosfakides,

Gautier Chastan, Kathy Osborne, Kent Weare, Pranav Rastogi, Quentin Sele Barancy

Published: August 2021

Version: 1.0

This document is provided “as-is.” Information and views expressed in this document, including

URL and other Internet Web site references, may change without notice. You bear the risk of

using it. Some examples are fictitious and are for illustration only. No real association is intended

or inferred. This document does not provide you with any legal rights to any intellectual

property in any Microsoft product.

Table of Contents Forward ......................................................................................................................................................... 3

Prerequisites ............................................................................................................................................. 3

SCCM Deployment ........................................................................................................................................ 4

Requirements ............................................................................................................................................ 4

Set up network share ................................................................................................................................ 4

Install application on a test machine ........................................................................................................ 7

Build application package ......................................................................................................................... 8

Distribute application package ............................................................................................................... 27

Create device collection .......................................................................................................................... 33

Add devices to device collection ............................................................................................................. 41

Deploy application .................................................................................................................................. 44

Monitoring deployments ........................................................................................................................ 53

SCCM lifecycle management ...................................................................................................................... 55

Update to the latest version ................................................................................................................... 55

Ring deployment ..................................................................................................................................... 62

Intune deployment ..................................................................................................................................... 65

Requirements .......................................................................................................................................... 65

Create Azure security group ................................................................................................................... 65

Install application on a test machine ...................................................................................................... 66

Create content prep tool directories ...................................................................................................... 67

Build application package ....................................................................................................................... 68

Deploy application .................................................................................................................................. 71

Silent registration for machines .............................................................................................................. 78

Intune lifecycle management ..................................................................................................................... 80

Update to the latest version ................................................................................................................... 80

Ring deployment ..................................................................................................................................... 82

Forward These procedures will help guide you through the process of deploying Power Automate

Desktop to Windows 10 using either SCCM or Intune.

1. SCCM

a. Deployment – Consisting of the initial install of Power Automate Desktop onto

Windows 10 machines that currently do not have Power Automate Desktop

deployed.

b. Lifecycle Management - Consisting of the scenario where automatic updating is

either unavailable or disabled.

2. Intune

a. Deployment – Consisting of the initial install of Power Automate Desktop onto

Windows 10 machines that currently do not have Power Automate Desktop

deployed.

b. Lifecycle Management - Consisting of the scenario where automatic updating is

either unavailable or disabled.

Prerequisites • A Microsoft work or school account to sign into Power Automate

• An account with administrator privileges to sign into your Windows device

• System requirements:

o A device that runs Windows 10 Home, Windows 10 Pro, Windows 10 Enterprise.

ARM devices are not supported.

▪ Minimum hardware

• Storage: 1GB

• RAM: 2GB

▪ Recommended hardware

• Storage: 2GB

• RAM: 4GB

▪ .NET Framework 4.7.2 or later

• Read the terms and conditions: https://docs.microsoft.com/dynamics365/legal/slt-

power-automate-desktop

• Download the Power Automate Desktop Installer:

https://go.microsoft.com/fwlink/?linkid=2102613

• Reference https://docs.microsoft.com/power-automate/desktop-flows/install to verify

none of the command line arguments have changed.

SCCM Deployment

Requirements Step-by-step instructions on setting up your Endpoint Configuration Manager Site Servers and

Roles is outside the scope of this document. At a high level you will need the follow

prerequisites already configured to follow the steps in this document:

• Microsoft Endpoint Configuration Manager

o Running the latest servicing update required to manage your deployed Windows

10 version

o A reachable distribution point (or a fallback point) to distribute software from

• A network share which is accessible to SCCM where you can store application installers,

for example: \\<File Server>.contoso.com\sources\

Set up network share In this section, our goal is to get the power automate desktop installer copied to the network

share where it can be built into a Configuration Manager Application. We will need the full UNC

path for a later step when we build the application in Configuration Manager

1. View the properties of your Power Automate Desktop application installer and go to the

Details tab.

2. Make a note of the Product Version.

3. In your application installers network share, create a Power Automate Desktop folder.

4. Inside your Power Automate Desktop folder, create a subfolder with the version of Power

Automate Desktop.

5. Copy your installer executable into the Version folder.

6. Shift + right click your setup file, then choose Copy as Path.

7. Paste the path into a scratch Notepad; you will need it later.

Install application on a test machine This step is required to get the detection method settings for building the package.

1. Install Power Automate Desktop on a test machine.

2. Find the MSI product code in the registry at this location:

SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\

3. Copy the path and paste it into Notepad.

4. Copy the DisplayVersion and paste it into Notepad.

Build application package In this section we will create the actual application package we can deploy to endpoints.

1. Open the Configuration Manager Console and browse to Software Library and

expand Application Management.

2. Optionally, create a Power Automate Desktop subfolder under Applications; otherwise

you can use the root of Applications.

3. Right-click either your subfolder or Applications and click Create Application.

4. On the General screen of the Create Application Wizard, select Manually specify the

application information and click Next.

5. On the General Information screen, fill out the following fields: Name, Publisher,

Software Version, and Date Published.

6. Click Next.

7. We will not be using the Software Center in this package; click Next.

8. On the Deployment Types screen, click Add.

9. In the Create Deployment Type Wizard, select Manually specify the deployment

type information and click Next.

In the General Information screen, enter a Name and click Next.

10. Paste the network share information from Set up Network Share into the Content

location field.

11. Paste the following text (without the quotation marks) into Installation program:

“Setup.Microsoft.PowerAutomateDesktop.exe -Silent -Install -

ACCEPTEULA”

12. Paste the following text (without quotation marks) into Uninstall program:

“Setup.Microsoft.PowerAutomateDesktop.exe -Silent -Uninstall”

13. Click Next.

14. On the Detection Method screen, click Add Clause.

15. In the Detection Rule dialog box:

A. Select the Setting Type drop down and choose Registry.

B. Select Hive.

C. In the Key field, paste the following text (without the quotation marks):

“SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Unin

stall\{092D4935-1864-44F0-921C-374B4BF13126}”

D. In Value, enter DisplayVersion.

E. For Data Type select String.

2. Select This registry setting must satisfy the following rule to indicate the presence

of this application and set the Value to the version number of Power Automate

Desktop.

A. Click OK.

B. Click Next.

16. On the User Experience screen, for Installation behavior, select Install for System.

17. For Logon requirement, select Only when a user is logged on.

18. For Installation program visibility, select Hidden.

19. For Maximum allowed run time (minutes) enter 30.

20. For Estimated installation time (minutes) enter 15.

21. Click Next.

22. Do not change the Requirements screen; click Next.

23. Do not change the Dependencies screen; click Next.

24. On the Summary screen, click Next.

25. On the Completion screen, click Close.

26. You will be taken back to the Deployment Types screen in the Create Application

Wizard. Click Next.

27. On the Summary screen click Next and wait for the application to be built.

28. Once it finishes click Close.

Distribute application package 1. Right-click your newly-created application package and select Distribute Content.

2. Click Next.

3. On the Content tab, click Next.

4. On the Content Destination screen, click Add and select all distribution points where

you will be deploying Power Automate.

5. On the Summary tab click Next.

6. Click Close.

7. Select Power Automate and click Content status in the main pane to verify that your

content has been distributed.

Create device collection 1. Browse to Assets and Compliance > Device Collections.

2. Optionally, create a folder for Power Automate Desktop to organize any device collections

you’ll use in the future

3. Create a new collection by right-clicking the folder and selecting Create Device Collection.

4. In the Create Device Collection Wizard:

5. Name the collection, and make sure to include the version of Power Automate Desktop in

the name.

6. Set Limiting collection to All Desktop and Server Clients. (Optionally in more advanced

use cases, you can limit this to only workstations. Explaining limiting collections is outside

the scope of this document.)

a. Click Next.

7. In the Membership Rules tab, do not add membership rules for now. (The logic for

organizaing memberships will be covered in a later section.)

8. Deselect Schedule a full update on this collection, and click Next.

9. Click OK in the warning message.

10. On the Summary tab, click Next.

11. Click Close.

Add devices to device collection You can add devices as a direct rule, where you will tie a specific device to the device collection,

and it stays there. This is absolutely a viable method for deployment. The draw back to this

approach is that new devices won’t be automatically added to your device collection, so some

work will be needed going forward to maintain the correct device collections to make sure new

computers are added to the collections on an on-going basis.

More advanced deployments might make use of something called a “Query Rule” where you

filter by OS version, or even possibly create a device collection where it can automatically add all

devices that have Power Automate Desktop installed. Please check the Microsoft documentation

on creating Query rules for more information: Create queries in Configuration Manager

1. Browse to Assets and Compliance > Devices.

2. Find the device you want to add to the device collection, right-click it, and select Add

selected items > Add selected items to existing device collection.

3. Find the device collection you just created and click OK.

Deploy application 1. Browse to Software Library > Applications and find your Power Automate Desktop

installation package you created earlier.

2. Right-click it and select Deploy.

3. Add the device collection you created in the previous step (make sure to change the

drop-down to Device Collections from User Collections) and click Next.

4. Review the the Content tab, and click Next if everything looks correct.

5. On the Deployment Settings tab, change the Purpose drop-down to Required and

then click Next.

6. On the Scheduling tab, you may schedule the deployment for a specific time or you can

select As soon as possible. For this example, select the default (As soon as possible).

Then click Next.

7. On the User Experience tab, change the User Notifications drop-down to Hide in

Software Center and all notifications, then select Software Installation. Then click

8. On the Alerts tab, click Next.

9. On the Summary tab, click Next.

10. Click Close.

Monitoring deployments To check the status of a deployment, browse to Monitoring > Deployments then search for

Power Automate Desktop.

You should get a breakdown of how your deployment is doing across your device collection.

Keep in mind, these deployments are not updated in real time and you may need to wait several

minutes before the information is updated.

Once the installation is completed, you should see a successful deployment, as shown below.

SCCM lifecycle management

Update to the latest version 1. Follow all steps in SCCM deployment to build the application package with the latest

version. Your Software Library should then have a new application package with the newest

version, as shown below.

2. Right-click to edit the new application package and go to the Supersedence tab.

3. Click Add, then click Browse.

4. Select the old version you want to replace and click OK.

5. In the New Deployment Type drop-down, select the new version of Power Automate

Desktop, select Uninstall, and click OK.

6. Click OK to close the Properties window.

7. Deploy the new version to your device collection. It will automatically replace the old version

on the PCs in the device collection.

8. Optionally, after you are no longer deploying the older version on any machines, you can

remove any deployments for it by right-clicking the obsolete deployment in the

Applications section of the Software Library and selecting Delete.

Ring deployment Ring deployment is a methodology where you first deploy newer versions to select test, pilot,

and production groups. Basically, you deploy to a small number of endpoints, then a larger

number, and continuing for as many rings as make sense for your environment until you have

deployed to all users, as shown in the diagram:

To fully manage the lifecycle in SCCM, create three deployment rings for Power Automate

Desktop.

• Power Automate Desktop Canaries

• Power Automate Desktop Pilot Devices

• Power Automate Desktop All Devices

Power Automate Desktop Canaries will include a small number of closely-watched machines

(such as your test machine and maybe another IT member’s machine).

The Power Automate Desktop Pilot Devices group will contain a small number of users who

have agreed to be testers on new deployments. They should typically be power users who are

good at giving feedback if something isn’t working.

Power Automate Desktop All Devices will contain all devices onto which Power Automate

Desktop will be deployed.

Each ring is a Device Collection.

Deploy the production version first to Power Automate Desktop Canaries. Once all machines

have been tested, continue to deploy then to Pilot Devices. Once all those installs have been

confirmed and testing has taken place, you can finally deploy to All Devices.

In this way you can keep your users up to date on an on-going basis, all from within the

Configuration Manager Console.

Intune deployment

Requirements • Microsoft Win32 Content Prep Tool (https://github.com/microsoft/Microsoft-Win32-

Content-Prep-Tool/releases)

• Windows 10 Pro, Business, Enterprise, or Education version 1709 or newer

o Must be enrolled in Intune

Create Azure security group 1. Browse to https://portal.azure.com and sign in with your Admin account.

2. In the Search resources, services, and docs search bar, enter Azure Active

Managing Power Automate Desktop on Windows

Documents

Managing the Windows 7 Desktop Environment

Optimizing the Windows Desktop Marián Skalický Windows Client Business Group Lead Microsoft Slovakia s.r.o. Accelerating Deployment & Managing the Desktop

Parallels Plesk Panel 9 · 2018-12-05 · Linux Mac OS Virtualization Parallels Desktop Parallels Workstation ... • Offer powerful reseller hosting plans ... Automate your Hosting

Módulo 5 - Managing User Desktop With Group Policy

T2-6-A-New Approach to Managing Your Physical Desktop Infrastructure

Automate Your Status Reports with Project Online...Automate Your Status Reports with Project Online Matt Heger Managing Consultant Campana & Schott Wednesday, February 24 |10:00am

Desktop Reclaim: Automate Removal of Microsoft & Adobe Software

Make Your PC Do the Work for You with Microsoft Power Automate … · 2021. 7. 12. · Power Automate Desktop works with all kinds of applications. If you can run an app on your PC

Making the Windows GUI Work for You Who Invented the Desktop? Navigating the Windows GUI Configuring & Customizing the Windows Desktop Managing Files in

Automate your docs, automate yourself

AutoMate BPA Server 10 Installation Guide - …cloud.networkautomation.com/documents/v10/AutoMate... · AutoMate BPA Server 10 Installation Guide – Rev. 20150812 1 AutoMate BPA

Should we automate? - Institute for Manufacturing · Overview What is Automation? Why do we Automate? Where do we Automate? Where will we Automate? Should we Automate?

Fundamentals of ArcGIS Desktop Pathway - GeoSYSgeosys.com.mt/.../Fundamentals-of-ArcGIS-Desktop-Pathway.pdfThe tools for creating and managing geographic data, displaying data on maps

The Business Case for Desktop Virtualization · 2012-07-20 · BUSINESS CASE FOR DESKTOP VIRTUALIZATION 3 Introduction Managing Traditional Personal Computers The Advantages of Virtual

ÎNTRERUPTOARE AUTOMATE ÎNTRERUPTOARE AUTOMATE … · aparate modulare Întreruptoare automate 118 - 152 Întreruptoare automate cu protecŢie diferenŢialĂ 153 Întreruptoare diferenŢiale

Automate, Automate, Automate - Bridging the Gap Between Capture and Process

Chapter 5 - The Desktop & Start Menu Logging On to the System The Windows Desktop –Managing Your Taskbar –The Quick Launch bar –Notification Area –Windows

Microsoft India – Managing the Dynamic Desktop Whitepaper

Managing and Troubleshooting Desktop Storageptgmedia.pearsoncmg.com/imprint_downloads/informit/que/Bookpool...Managing and Troubleshooting Desktop Storage Terms you’ll need to understand:

Your desktop is everywhere! Herzlich willkommen! Alf Netek Managing Director