Normally we update to started when the feature is in a TP… but this can’t be in a TP (as CAS isn’t allowed in a TP.) But the code is in TP. :)
We got rid of complex hierarhy of primary sites (bound to CAS) so only one PRI remained. Now as per MS suggestion - we want to remove CAS ( and there are other reasons to) . Migrating to new PRI seems to be lots of work and reconfiguration ( in our complex distributed network and branch office configuration) So just cuting out CAS would be much preferred. Please update.
Yes, the CVE and ADV would be very beneficial to include in Update properties.
123 votesstarted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, System Center Configuration Manager) responded
Changing status back to “Started” as there’s more work to do here. We plan to simplify adding requirements to DTs as well as complete the missing scenarios for detection methods in a future release. Stay tuned for more updates.
9 votesAndres Pae shared this idea ·
Tempted to mark this completed, now that we’ve released full blown powerBI integration:
Building reports & dashboards doesn’t get much easier than that.
Power BI is great, but it requres separate infra/licensing? I believe initial idea is to get it EASY way :)