Skip to content

Commit 63211a6

Browse files
committed
edits
1 parent 0214a23 commit 63211a6

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

articles/defender-for-iot/organizations/detect-windows-endpoints-script.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -41,11 +41,9 @@ Before performing the procedures in this article, you must have:
4141
The script described in this article is supported for the following Windows operating systems:
4242

4343
- Windows XP
44-
- Windows 2000
45-
- Windows NT
4644
- Windows 7
4745
- Windows 10
48-
- Windows Server 2003/2008/2012/2016/2019
46+
- Windows Server 2003/2008/2012
4947

5048
## Download and run the script
5149

@@ -69,12 +67,11 @@ The script detects enriched Windows data, and is run as a utility and not an ins
6967

7068
After the script runs to probe the registry, an output file appears with the registry information. The filename indicates the current date and time of the snapshot with the following syntax: `[current date time]_system_info_extractor`.
7169

72-
Files generated by the script include:
70+
Files generated by the script:
7371

7472
- Remain on the local drive until you delete them.
7573
- Are overwritten if you run the script again on the same day.
76-
- The script also logs an errorOutput that will be empty if no errors occurred during the running of the script.
77-
- The script may create a few tmp.txt files during it’s run. The script takes care of cleaning <!-- deleting-->them at the end of it’s run.
74+
- Include an errorOutput file that is empty if no errors occurred during the running of the script.
7875

7976
## Import device details
8077

0 commit comments

Comments
 (0)