{
	"id": "9ef00054-e62b-485a-abaa-13afd74cc44b",
	"created_at": "2026-04-06T00:15:44.317737Z",
	"updated_at": "2026-04-10T13:11:31.591614Z",
	"deleted_at": null,
	"sha1_hash": "9ad6a003d7f750d61d40ccd23e1e7ebd5e1f0fdb",
	"title": "Windows Remote Management - Win32 apps",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 38665,
	"plain_text": "Windows Remote Management - Win32 apps\r\nBy stevewhims\r\nArchived: 2026-04-05 22:47:17 UTC\r\nWindows Remote Management (WinRM) is the Microsoft implementation of the WS-Management protocol,\r\nwhich is a standard Simple Object Access Protocol (SOAP)-based, firewall-friendly protocol that allows\r\ninteroperation between hardware and operating systems from different vendors.\r\nThe WS-Management protocol specification provides a common way for systems to access and exchange\r\nmanagement information across an IT infrastructure. WinRM and the Intelligent Platform Management Interface\r\n(IPMI) standard, along with the Event Collector service are components of the set of features known as Hardware\r\nmanagement.\r\nThe intended audience for Windows Remote Management is IT professionals—who write scripts to automate the\r\nmanagement of servers—and independent software vendor (ISV) developers, who want to obtain data for\r\nmanagement applications.\r\nTo obtain management data from local and remote computers that might have baseboard management controllers\r\n(BMCs), you can use: WinRM scripting objects; the WinRM command-line tool; or the Windows Remote Shell\r\n(WinRS) command-line tool. If the computer runs a Windows-based operating system version that includes\r\nWinRM, then the management data is supplied by Windows Management Instrumentation (WMI).\r\nYou can also obtain hardware and system data from WS-Management protocol implementations running on\r\noperating systems other than Windows in your enterprise. WinRM establishes a session with a remote computer\r\nthrough the SOAP-based WS-Management protocol rather than a connection through DCOM, as WMI does. Data\r\nreturned using the WS-Management protocol is formatted in XML instead of as objects.\r\nThe Intelligent Platform Management Interface (IPMI) WMI provider is a standard WMI provider with classes\r\nthat obtain BMC sensor data from computers with the appropriate hardware. You can access IPMI data by using:\r\nthe WinRM scripting API; WMI scripting; or COM APIs.\r\nWinRM is part of the operating system. However, to obtain data from remote computers, you must configure a\r\nWinRM listener. For more information, see Installation and configuration for Windows Remote Management. If a\r\nBMC is detected at system startup, then the IPMI provider loads; but even if not, the WinRM scripting objects and\r\nthe WinRM command-line tool are still available.\r\nAbout Windows Remote Management\r\nA collection of articles about: the public Microsoft Web Services for Management (WS-Management)\r\nprotocol specification; WinRM architecture; relationship to WMI; hardware management with the IPMI\r\nprovider; and WinRM configuration and installation.\r\nUse Windows Remote Management\r\nhttp://msdn.microsoft.com/en-us/library/aa384426\r\nPage 1 of 2\n\nA collection of articles about how to use the WinRM scripting API to manage hardware.\r\nWindows Remote Management reference\r\nContains the scripting interfaces defined by WS-Management automation. Also contains class definitions\r\nof the WMI classes created by the IPMI provider and classes that communicate with the IPMI driver to\r\nobtain baseboard management controller (BMC) data.\r\nSource: http://msdn.microsoft.com/en-us/library/aa384426\r\nhttp://msdn.microsoft.com/en-us/library/aa384426\r\nPage 2 of 2",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"origins": [
		"web"
	],
	"references": [
		"http://msdn.microsoft.com/en-us/library/aa384426"
	],
	"report_names": [
		"aa384426"
	],
	"threat_actors": [],
	"ts_created_at": 1775434544,
	"ts_updated_at": 1775826691,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/9ad6a003d7f750d61d40ccd23e1e7ebd5e1f0fdb.pdf",
		"text": "https://archive.orkl.eu/9ad6a003d7f750d61d40ccd23e1e7ebd5e1f0fdb.txt",
		"img": "https://archive.orkl.eu/9ad6a003d7f750d61d40ccd23e1e7ebd5e1f0fdb.jpg"
	}
}