Windows Management instrumentation Command Line
Updated: January 21, 2005
- Parameter not valid
- Value map does not contain the input value for this property
- RPC error on the unsuccessful connection to a computer or node
- Query fails or is slow
- Output is not properly aligned in rows and columns
- Localized version of WMIC is not available (in some Multilingual User Interface (MUI) or Language Interface Packs
- XSL files on Windows XP Professional are not supporting arrays
- Input parameter is of OBJECT type
Parameter not valid
Solution: You must specify the name, user name, and variable value when you create an environment variable.
Value map does not contain the input value for this property
Solution: You can interpret the value for an input parameter by referring to the schema information, the method's description qualifier in the corresponding Managed Object Format (MOF) file, or to the MSDN description of the method.
Some schema information can be retrieved using WMIC, for example:
- wmic:root\cli>alias OS list full /format:table
- wmic:root\cli>process call /?:full
RPC error on the unsuccessful connection to a computer or node.
Solution:
- Ping computer's IP for the availability of the computer.
- Disable firewall on computer.
Cause: The computer has UNIX, Linux, Windows 95, Windows 98, Windows Millennium Edition, or Windows NT 4 operating system that has no network-enabled WMI or WBEM support.
Solution:
- Enable WMI or WBEM support in the operating system.
- Deploy operating systems with network-enabled WMI or WBEM support.
Query fails or is slow
Solution: Narrow down query using Named parameters or WHERE clause. For example:
- wmic:root\cli>Alias OS list brief
- wmic:root\cli>nteventlog application get /format:list
- wmic:root\cli>UserAccount where "Domain='DomainName' and Name='UserName'" get /all
Output is not properly aligned in rows and columns.
Solution:
- Increase Screen Buffer Size for Command (CMD) window.
- Use WordPad.exe instead of Notepad to open large text files.
- Use more criteria on query to display only necessary information.
- Use a custom XSL file to display custom formatting.
Localized version of WMIC is not available (in some Multilingual User Interface (MUI) or Language Interface Packs)
Solution: Use the /LOCALE:ms_409 switch to set up English Locale as the default.
XSL files on Windows XP Professional are not supporting arrays
Solution: Use XSL from the Windows Server 2003 family to query other computers, including Windows XP Professional
Input parameter is of OBJECT type
Solution: Use the following command to set sharing of the c:\test directory for three users:
WMIC SHARE CALL Create "","test","3","TestShareName","","c:\test",0