Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. IT Analytics Help
  3. Section VII. Data Collector Installation and Configuration for Cohesity NetBackup
  4. Centralized Data Collector for NetBackup - Prerequisites, Installation, and Configuration
  5. Step-5: SSH/WMI
  6. Windows Data Collector: WMI Connectivity

Windows Data Collector: WMI Connectivity

WMI is only used for connecting to a remote Windows Primary Server from a Centralized Data Collector or another subsystem that requires WMI. WMI uses DCOM for networking. DCOM dynamically allocates port numbers for clients. DCOM's service runs on port 135 (a static port) and any client communicating with a host connects on this port. The DCOM service allocates the specific port for the WMI service.

Click here to know how to set up a fixed port for WMI. The WMI Proxy Service is installed by default, as part of the Data Collector installation on a Windows server. Customers must work with their Windows Hosting Team and Domain Admins for setting up WMI for their specific version of Windows and in alignment with their domain policies.

Testing WMI connectivity

Installing the WMI Proxy service (Windows host resources only)

Feedback

Was this page helpful?
Previous

Linux Centralized Data Collector: SSH

Next

Testing WMI connectivity

Feedback

Was this page helpful?