Powershell: MID Server isn't Windows. Unable to run ScriptRunner.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2017 01:40 AM
I have a VM where Mid Server is installed. I have installed AD on the same VM. I used the windows activity - 'Change Service State' to start/stop a Windows Service and 'Create AD Object' to create an user in AD. Whenever I raise a request (the workflow has the corresponding activities), I see a message 'Powershell: MID Server isn't Windows. Unable to run ScriptRunner.' in that particular activity. Can someone please let me know what it means?
Am I correct in understanding that MID Server cannot be a VM or I cannot carry out any operation in a MID Server?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2017 02:22 AM
Hello,
So the VM on which the MID server is installed is Windows or other?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2017 02:24 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2017 03:10 AM
Its Windows
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2017 05:47 AM
Hello,
Thus message usually appears in discovery when having MID server installed on an OS other than Windows.
Now, for me it os not clear what precisely you are trying to achieve, maybe more details would be useful on this.
See however the docs
mentioning what MID server does.
The Management, Instrumentation, and Discovery (MID) Server is a Java application that runs as a Windows service or UNIX daemon. The MID Server performs the following tasks:
- Communicates securely with the ServiceNow instance to determine what Discovery probes to run.
- Runs Discovery probes on the local network to gather data on network devices
- Sends Discovery probe results back to the ServiceNow instance for processing
Note: MID Server communications are initiated inside the enterprise's firewall and therefore do not require any special firewall rules or VPNs.The MID Server is used by the following applications:
- Discovery
- Orchestration
- Import Sets
- Altiris
- Microsoft SMS/SCCM
- Avocent LANDesk
- HP OpenView Operations
- Microsoft System Center Operations Manager (SCOM)
- Borland Starteam Integration
- Microsoft MIIS
- Service Assurance