DA is able to create pilot collections in MECM for us. However it would be good if DA could break the pilot collections down into smaller collections.

This would mean that we could deploy a FU to a percentage of devices identified for pilot rather than the whole collection (or need to figure out a manual way to break the Pilot collection up into smaller chunks)

Deploying to the entire pilot collection could result in hundreds of machines with a particular application failing and requiring regression. Smaller target collections would help to build confidence

It would be nice to be able to create deployment plans using powershell. The manual process of creating individual deployment plans via the portal is time consuming, and when working with the need for multiple deployment plans targeting different collections this becomes a cumbersome process. I can currently create and populate all of my collections via powershell, but I then have to manually create each individual deployment plan.

What network traffic and/or bandwidth impact will the Desktop Analytics tool generate when collecting and sending information to Azure.

Can this be enabled over a VPN connection?

Cheers

When will the Desktop analytics be available for Intune , It was shared in Ignite 2019 that it will be supported however don't see any update

Why have you not implemented a search feature in Desktop Analytics?

I want to add a selected device to the pilot group but do not want to manually search for it over 233 pages to find one single device.

For the current setup it is only possible to have one pilot collection from DA. It would be cool if you somewhere at the prepare phase could pick number of pilot rings. That way you can have somewhat a more "secure" deployment flow for your updates if anything would go wrong.

I've noticed, that once certain version of Windows goes out of support, it's marked red in the adoption chart on the whole timeline instead only from date it's support ended.

As if this version was out of support also few months ago.

I would suggest to show such devices as "red" only from date when they are actually out of service.

We are trying to migrate from Win 10 1809 to 1909 and while checking compatibility details software like Symantec End Point protection, Cloud Strike and others are showing compatible however while running actual upgrade, we could see SEP and Cloud Strike blocking the deployment.

Same behavior we have observed with Win 10 1909 to Win 10 20H2.

A button of some sort to grab all the drivers that "needs remediation" or after you have reviewed all the drivers right on the DA azure site.

On the main application Identify importance page, add columns with drop downs so that multiple applications can be reviewed at once without needing to open the app blade.

When reviewing applications it is more efficient to leave the App versions details turned off but when an app requires a more in depth look turning this on causes the current view to be reset.

It would be nice if when you are viewing an app in the blade there was a slider that when enabled showed all the versions with their details.

Under the apps view in addition to version it would be useful to see the bitness of the app versions. For example if your doing a migration from a 64 bit app to be able to track and monitor the cleanup or target for cleanup. For example we have had a lot of Teams 32-bit getting installed and we don't want any 32-bit Teams in our environment and block it via GPO but they keep getting installed.

We have an internal process to define pilot machines. All these machines are member of a collection that is synchronized to Desktop Analytics. Pls. allow to select a collections to be included in a Pilot. Microsoft recommendation can go on top.

on the Home page you show enrolled devices out of number of devices but you don't show what devices are having issues?

How are you supposed to fix these devices if you don't know what devices are having issues?

Owner should be selectable from Azure-AD in the "Manage all assets-table".

Owner is very useful in order to keep track of who's responsible for testing. But it's hard to remember everyone's name in a large organization. You should be able to browse for the owner in Azure-AD when you edit an applicaion.

When you select a deployment plan, you can see when the snapshot has been created. It would be nice to see in what time zone the info has been collected. Is it the local timezone, UTC, PST?

The "Plan Assets\Drivers" view does not allow to filter by the "Drivers Needing Remediation" categories (inbox, import from WU, inbox+WU...).

Such column will simplify quickly identifying all the drivers that need to be imported from WU in one go, instead of going one by one looking at their details.