WinRM Disabled. Impact on Discovery functionality?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2024 10:37 AM
Hope someone can help.
I am planning implementation of ITOM Discovery, Service Mapping and Event Management for a self-hosted customer and during initial technical spec discussions regarding MID servers, their infrastructure partner has advised me that WinRM has been disabled on their Windows servers as part of hardening requirements under CIS-L2.
As far as I can see, you can choose to use EITHER WinRM or WMI for discovery of endpoints, but THIS community post also suggests that if discovering CIM Storage Server, it uses WinRM.
https://www.servicenow.com/docs/bundle/washingtondc-it-operations-management/page/product/service-ma...
Question: Is this the only impact of WinRM being disabled? Is it an impact? Has anyone experience in implementing ITOM Discovery/Service Mapping/Event Management with a constraint like this and if so, did you have this or any other issues?
I would GRRRRRREEEATLY appreciate any input from people who have had experience with this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2024 06:20 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2024 03:26 AM
Hi Thomas,
What devices are in scope for discovery/service mapping? This will help you in deciding the overall impact.
Event mgmt will not have any impact with respect to WinRM.
