Here's a primer on remote WMI: https://msdn.microsoft.com/en-us/library/aa389290.aspx
In our environment, we basically run winrm quickconfig on all our machines, for those not joined to a domain we also add them to the TrustedHosts list. For machines not joined to a domain, there's an added difficulty if you are using the IP address instead of the Host name, it definitely offers a few challenges.
A good strategy is to get remoteWMI to work, then we integrate it in RDM. We like to use WMIC.
This is a lot of information to go over, please contact us at email@example.com for more assistance.
Access denied error.
Ensure the user account has the necessary permissions to access a computer remotely Securing a Remote WMI Connection (Windows)
You can also find troubleshoot tips in WMI Troubleshooting (Windows)
Error getting products informations.
Invalid Class WMI or WMI class not found on Windows Server 2003. On Windows Server 2003, Win32_Product is not enabled by default. You can enable it by following the steps provided in the link below:
Testing from a remote computer.
The WMIC command is used to test if you have access to the machine through WMI. You need to enter the following command;
wmic /NODE:"ComputerName" bios get serialnumber
Below, an example with other credentials;
wmic /NODE:"ComputerName" /user:"username" /password:"password" bios get serialnumber
Load from inventory doesn't work. Error getting Bios information.
This error can be many things please validate the following:
- Sessions must be RDP.
- The station must be on the same domain.
- The credentials must be in the Tools section of the session and be accurate.
- Test the WMI requests directly from the station to see if the communication is working.