WMI issues on Discovery of workstations

[taarik_rahaman]

Hi everyone,

One of our clients is having a large number of Discovery failures when running Discovery against workstations.   They are all WMI issues ("The RPC server is unavailable") and we can't figure out what the issue really is.

Here is what we tried thus far, without success:

• Console login (Discovery Windows service account can login to the console)
• Disabling Symantec Endpoint
• Verified Discovery account permissions (works on identical workstations in the same AD hierarchy)
• Tested outside of ServiceNow (fails on generic WMI testing tool as well…ServiceNow results confirmed).   WMI fails via compmgmt.msc and via wmitest tools. Same tests work perfectly via the same tools on machines where WMI is fine.
• Force update of group policies on affected workstation

Any thoughts?   Are we missing something?

Thank you!

[joe_steinfeld · Accepted solution]

Taarik,

Several things can cause this issue. If you have run generic WMI test either via command line or wbemtest then you know it is a basic WMI issue.   Try the following:

1. Validate you can RDP to the host from the Mid-Server to the problem host using your credentials. If this is this works you know your credentials are good. I think you have tried this, but want to validate.   If this doesn't work you know your issue. If it does go to Step 2.

2. RDP to Mid-Server and run the following command line and see if you get connected:

        - wmic /node:"TARGET IP Address" /user:"YOURDOMAIN/YOURUSERNAME" /password:"YOUR PASSWORD" path win32_operatingsystem

3. If this does not work, verify the following:

        - RPC and WMI Windows Services are enabled

        - Others have gotten this issue when time difference between Mid-Server and Discovered machines are vastly different. Check to make sure that machines are fairly to same time.

          - Check Windows Firewall is set to allow WMI.   Here is a link to this: Configuring the Firewall to Allow wmic | Windows 7 Portable Command Guide: Understanding the Windows...

Check these things and see if this resolves your issue

[joe_steinfeld]

Taarik, Sounds like your got your issue resolved. I am curious what the problem was?   Thx

[andrew_irwin]

If by any chance your client is a government customer there is also   possibility that a STIG setting made on the domain GPO could be the root of your issue. I've seen thIs issue more than once.

[taarik_rahaman]

Walter,

Sorry...trying to update this stuff between calls as I was just on with the client.   It turned out to be the Windows Firewall group policy.

Thanks joe.steinfeld@servicenow.com and andrew_irwin for your suggestions!

Taarik.