- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2024 06:44 PM
Hello All,
I'm new in ITOM. Please understand my stupid quistion.
I'm trying to discover Windows Servers by Windows MID server.
I made Win credential but it doesn't work.
I already disabled firewall both MID server and Win host.
And also test RDP connection between MID to Win host and Win host to MID, but fine.
Is there anything that I need to check?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2024 10:18 PM
Then it has something to do with the credentials you are using to connect from the mid server to your windows host. To troubleshoot this further, try running a remoting command from your mid server to your windows host. You can make use of PowerShell Invoke-Command to test this. Something like this :
Invoke-Command -ComputerName 'your windows os hostname or ip' -Credential Get-Credential -ScriptBlock {
hostname
}
Run this command and supply the credentials you were using to test it from ServiceNow. If you don't get the hostname of the remote machine returned as an output, you need to check your credentials.
Thanks & Regards
Amit Verma
Please mark this response as correct and helpful if it assisted you with your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2024 10:07 PM
It doesn't matter until you ensure that connectivity is established between your Mid Server and the Windows host. Can you check for connectivity first from your mid server ? If connectivity is established, check if you have WMI access on the Windows Host from the Mid server by running the below PowerShell command from the mid server :
Get-WmiObject -query "SELECT * FROM Win32_OperatingSystem" -ComputerName "Your Windows host Hostname"
Refer https://activedirectorypro.com/test-wmi-connection-with-powershell/
Thanks & Regards
Amit Verma
Please mark this response as correct and helpful if it assisted you with your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2024 10:13 PM
Thank for fast response,
"Get-WmiObject" command is seems like OK on both way.
MID to Windows OS and Windows OS to MID
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2024 10:18 PM
Then it has something to do with the credentials you are using to connect from the mid server to your windows host. To troubleshoot this further, try running a remoting command from your mid server to your windows host. You can make use of PowerShell Invoke-Command to test this. Something like this :
Invoke-Command -ComputerName 'your windows os hostname or ip' -Credential Get-Credential -ScriptBlock {
hostname
}
Run this command and supply the credentials you were using to test it from ServiceNow. If you don't get the hostname of the remote machine returned as an output, you need to check your credentials.
Thanks & Regards
Amit Verma
Please mark this response as correct and helpful if it assisted you with your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2024 11:23 PM
I got error from Invoke-Command and resolve the error message.
Finally, I can discover my Windows host.
Thanks a lot!
Best regards,
Hank.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2024 10:21 PM
Hi please check below things
Check Credential Configuration: Ensure that the credentials you've configured in your ITOM platform are correct and have the necessary permissions to access the Windows Servers. Make sure you've provided the appropriate username and password.
Check MID Server Configuration: Verify that the Windows MID server is properly configured and running. Ensure that it has network connectivity to the Windows Servers you're trying to discover.