WMI Collection Configuration #1607
-
|
Hi, I was wondering how to handle the WMI connection for cases where the NETBIOS name and the machine name of the target SQL server are different? The SQL collections are working fine using the machine name specified in source connection config but it seems WMI is trying to connect via the netbios name which isn't working (where machine name and netbios name is different). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
The NETBIOS name should be the actual name of the computer. 
The NETBIOS computer name might not resolve across domains, but I think you will struggle to get WMI working across domains. For WMI to work, the account needs to be local admin. There is more info in the WMI doc. WMI can be disabled and most things will work without it, but check the doc to see if there is anything that is important for you. I'm not sure what the issue is with using the NETBIOS name, but creating a host file entry for the NETBIOS name on the computer where the service is running might allow the service to find it. |
Beta Was this translation helpful? Give feedback.
-
|
I think the issue is where we have server names that are above the 15 character limit. I added entries to the hosts file for the affected servers as you suggested and that has indeed fixed the issue. Thanks very much. |
Beta Was this translation helpful? Give feedback.
The NETBIOS name should be the actual name of the computer.
The NETBIOS computer name might not resolve across domains, but I think you will struggle to get WMI working across domains. For WMI to work, the account needs to be local admin. There is more info in the WMI doc. WMI can be disabled and most things will work without it, but check the doc to see if there is anything that is important for you.
I'm not sure what the issue is with using the NETBIOS name, but creating a host file entry for the NETBIOS name on the computer where the service is running might allow the service to find it.