From 7437215d639a55add42476c1915d060536a7a90b Mon Sep 17 00:00:00 2001 From: Marc Shepard <37675325+marcshep-msft@users.noreply.github.com> Date: Tue, 10 Apr 2018 11:45:27 -0700 Subject: [PATCH 1/2] Update windows-analytics-get-started.md Added instructions on how to initiate a full scan without the deployment script. --- .../deployment/update/windows-analytics-get-started.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/windows/deployment/update/windows-analytics-get-started.md b/windows/deployment/update/windows-analytics-get-started.md index 3775d77bac..87dfb6337b 100644 --- a/windows/deployment/update/windows-analytics-get-started.md +++ b/windows/deployment/update/windows-analytics-get-started.md @@ -127,7 +127,6 @@ Use a software distribution system such as System Center Configuration Manager t ### Distributing policies at scale There are a number of policies that can be centrally managed to control Windows Analytics device configuration. All of these policies have *preference* registry key equivalents that can be set by using the deployment script. Policy settings override preference settings if both are set. - >[!NOTE] >You can only set the diagnostic data level to Enhanced by using policy. For example, this is necessary for using Device Health. @@ -155,4 +154,10 @@ For more information about Internet Explorer Security Zones, see [About URL Secu ### Distribution at scale without using the deployment script -We recommend using the deployment script to configure devices. However if this is not an option, you can still manage settings by policy as described in the previous section. However, if you don't run the deployment script, you might have to wait a long time (possibly weeks) before devices send the initial full inventory scan. +We recommend using the deployment script to configure devices. However if this is not an option, you can still manage settings by policy as described in the previous section. However, if you don't run the deployment script, you won't benefit from it's error checking and you might have to wait a long time (possibly weeks) before devices send the initial full inventory scan. + +Note that it is possible to intiate a full inventory scan on a device by calling these commands: +- CompatTelRunner.exe -m:generaltel.dll -f:DoCensusRun +- CompatTelRunner.exe -m:appraiser.dll -f:DoScheduledTelemetryRun ent + +For details on how to run these and how to check results, see the deployment script. From 5a561f171107c040f919ca09ccec92d069387aa5 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Wed, 11 Apr 2018 14:27:50 -0700 Subject: [PATCH 2/2] Fixed typo --- windows/deployment/update/windows-analytics-get-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/windows-analytics-get-started.md b/windows/deployment/update/windows-analytics-get-started.md index 87dfb6337b..cec30d4e05 100644 --- a/windows/deployment/update/windows-analytics-get-started.md +++ b/windows/deployment/update/windows-analytics-get-started.md @@ -154,7 +154,7 @@ For more information about Internet Explorer Security Zones, see [About URL Secu ### Distribution at scale without using the deployment script -We recommend using the deployment script to configure devices. However if this is not an option, you can still manage settings by policy as described in the previous section. However, if you don't run the deployment script, you won't benefit from it's error checking and you might have to wait a long time (possibly weeks) before devices send the initial full inventory scan. +We recommend using the deployment script to configure devices. However if this is not an option, you can still manage settings by policy as described in the previous section. However, if you don't run the deployment script, you won't benefit from its error checking, and you might have to wait a long time (possibly weeks) before devices send the initial full inventory scan. Note that it is possible to intiate a full inventory scan on a device by calling these commands: - CompatTelRunner.exe -m:generaltel.dll -f:DoCensusRun