Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Hardware and Software Requirements for the WinCollect Host

 

Ensure that the Windows-based computer that hosts the WinCollect agent meets the minimum hardware and software requirements.

Hardware/virtual Machine Requirements

The following table describes the minimum hardware requirements for local collection:

Table 1: Hardware/VM Requirements for Local Collection by Using WinCollect

Requirement

Description

Memory

1 Event per second (EPS) or less: 12.5 MB

100 EPS or less: 27 MB

1,000 EPS or less: 97 MB

~5,000 EPS or less: 201 MB

Processor

Intel Core i3

Available processor resources

Approximately 20%, depending on CPU, EPS, and number of endpoints polled.

Disk space

3 GB of available disk space for software and log files.

6 GB might be required if events are stored on a schedule.

Note

WinCollect CPU and memory loads depend on several factors, including the number of events per second that are being processed and the number of remote endpoints that are being polled.

The following table shows resources that are used by WinCollect in testing environments with various hardware configurations and EPS counts.

Table 2: Comparison of Tested WinCollect Environments (local polling)

Profile

Type

OS

RAM

Cores

Avg FPS

RAM used

Avg CPU

High EPS

VM

Windows 2012 Server

8 GB

8

5000

200 MB

17%

Meduim EPS

VM

Windows 2012 Server

8 GB

8

300

25 MB

13%

Low EPS

Notebook

Windows 7

32 GB

8

<1

10 MB

0.5%

The following table describes the minimum hardware requirements for remote collection:

Table 3: Hardware/VM Requirements for Remote Collection by Using WinCollect

Requirement

Description

Memory

5 endpoints or less: 80 MB

250 endpoints or less: 293 MB

500 endpoints or less: 609 MB

Processor

Intel Core i3

Available processor resources

Approximately 20%, depending on CPU, EPS, and number of endpoints polled.

Disk space

3 GB of available disk space for software and log files.

6 GB might be required if events are stored on a schedule.

WinCollect CPU and memory loads depend on several factors, including the number of events per second that are being processed and the number of remote endpoints that are being polled.

Table 4: Comparison of Tested WinCollect Environments (remote polling)

Profile

Type

OS

RAM

Cores

Avg FPS

RAM used

Avg CPU

High EPS Low Device Count

VM

Windows 2012 Server

8 GB

6

3000

78 MB

6.5%

Medium EPS and Device count

VM

Windows 2016 Server

4 GB

250

2500

290 MB

14%

High EPS High Device count

VM

Windows 2016 Server

4 GB

500

5000

605 MB

10.75%

Software Requirements

Table 5: Software Requirements

Requirement

Description

Operating system

Windows Server 2016 (including Core)

Windows Server 2012 (including Core)

Windows Server 2008 (including Core)

Windows 10

Windows 8

Windows 7

Distribution

One WinCollect agent for each Windows host.

Required user role permissions for installation

Administrator, or local administrator

Administrative permissions are not required for remote collection

Note

WinCollect is not supported on versions of Windows that are designated end-of-life by Microsoft After software is beyond the Extended Support End Date, the product might still function as expected. However, Juniper does not make code or vulnerability fixes to resolve WinCollect issues for older operating systems. For example, Microsoft Windows Server 2003 R2 and Microsoft Windows XP are operating systems that are beyond the "Extended Support End Date”. For more information, see https://support.microsoft.com/en-us/lifecycle/search (https://support.microsoft.com/en-us/lifecycle/search).