locked
Get-CIMInstance Error RRS feed

  • Question

  • Hello Scripting Guys!

    I'm getting the following error when attempting: Get-CIMInstance -classname win32_computersystem

    No mapping between account names and security IDs was done.

    Is anyone familiar with this and how I can resolve this error?  I'm running the command on a Windows Server 2012 R2 system with Powershell v4.0

    Thank you!

    Thursday, March 31, 2016 5:20 PM

Answers

  • Post in MDT forum to learn how to use WMI with MDT.  There is no complete OS during most stages of deployment and the system may not be connected.  You will not be able to use a domain account under MDT for most things.

    The MDT forum will get you on the right track.


    \_(ツ)_/

    • Marked as answer by lsbruva Thursday, March 31, 2016 8:04 PM
    Thursday, March 31, 2016 7:51 PM

All replies

  • Are you running this on a remote system?  if not, make sure you have elevated rights.  If so, make sure you are authenticating correctly

    BlankMonkey

    Thursday, March 31, 2016 5:32 PM
  • We do not need to elevate for that command.

    The error suggests corruption in the local accounts structure. 

    Here are some of the very many causes of this error:

    • An account does not exist on domain member computers.
    • A SAM account name differs from its domain account name.
    • The client is   running a Multilingual User Interface Pack (MUI) that uses a different default language than the domain controller.
    • A SAM account name was renamed on the client computers


    \_(ツ)_/

    Thursday, March 31, 2016 6:02 PM
  • Ok... I think it must be that the account does not exist on domain member computers.  I running the script as task sequence during an MDT Deployment.
    Thursday, March 31, 2016 7:40 PM
  • Post in MDT forum to learn how to use WMI with MDT.  There is no complete OS during most stages of deployment and the system may not be connected.  You will not be able to use a domain account under MDT for most things.

    The MDT forum will get you on the right track.


    \_(ツ)_/

    • Marked as answer by lsbruva Thursday, March 31, 2016 8:04 PM
    Thursday, March 31, 2016 7:51 PM
  • Thank you jrv! I will.
    Thursday, March 31, 2016 8:04 PM
  • There is one other thing you can try:

    Get-WmiObject Win32_ComputerSystem

    It uses a different method of authentication.


    \_(ツ)_/

    Thursday, March 31, 2016 8:14 PM