![]() For example, your Target collection uses a collection with a Windows 7 membership rule. These collections continue to sync as their membership changes. Make sure to include pilot and pilot exclusion collections. These collections are available in the Desktop Analytics portal for grouping with deployment plans. Select specific collections to synchronize with Desktop Analytics: Select Add to include additional collections from your Target collection hierarchy. If needed in your environment, set to Yes. It's the full set of devices that Configuration Manager connects to the Desktop Analytics service.ĭevices in the target collection use a user-authenticated proxy for outbound communication: By default, this value is No. Target collection: This collection includes all devices that Configuration Manager configures with your commercial ID and diagnostic data settings. Use terms to easily distinguish multiple hierarchies in your environment, for example: test lab or production. Use it to differentiate between different hierarchies, and to identify collections from separate hierarchies. ![]() On the Collections page, configure the following settings:ĭisplay name: The Desktop Analytics portal displays this Configuration Manager connection using this name. Select Next to continue or Previous to make changes. The Available functionality page shows the Desktop Analytics functionality that's available with the diagnostic data settings from the previous page. This behavior can make it difficult to identify and assess devices. If you don't send the device name, it appears in Desktop Analytics as "Unknown". Starting with Windows 10 version 1803, the device name isn't sent to Microsoft by default. Secret Key validity period: choose either 1 year or 2 years from the drop-down list. By default this value is Change the default to one of the following recommended formats: ![]() It's in the access token used by the Configuration Manager client to request access to the service. Īpp ID URI: This value needs to be unique in your Azure AD tenant.HomePage URL: This value isn't used by Configuration Manager, but required by Azure AD. For more information, see Create and import app for Configuration Manager.Ĭonfigure the following settings in the Create Server Application window:Īpplication Name: A friendly name for the app in Azure AD. If you can't create the app from this wizard, you can manually create the app in Azure AD, and then import into Configuration Manager.
0 Comments
Leave a Reply. |