Getting LaunchWMI: Access Denied error after upgrading to Madrid Patch 3

[Mickey_Cegon]

Upgraded on 6/11/19 from London Patch 6 to Madrid Patch 3, and we now are getting the following error in Discovery logs:

launchWMI : Access is denied. (Exception from HRESULT: 0x80070005(E_ACCESSDENIED))At D:\MID_Prod03_1\mid.madrid-12-18-2018__patch3-hotfix1-05-09-2019_05-10-2019_1311.windows.x86-64\agent\scripts\PowerShell\WinRMAPI\ExecuteRemote\ExecuteRemote.psm1:122 char:9+         launchWMI -computer $computer -cred $cred -sourceScript $file ...+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,launchWMI

**********************

I thought maybe I had an issue w/my MID servers so I installed a brand new one, and no change. I was not getting this error at all prior to the Madrid upgrade. Has anyone else experienced this?

Thanks,

Mickey Cegon

FBL Financial Group, Inc.

[doug_schulze]

Hey Mickey!  Yeah, please open an incident with support on this one, they will get you straightened out...

[Mickey_Cegon]

Thanks, Doug! Appreciate the quick response!

Mickey

[VaranAwesomenow]

I have the same issue, raised an case with Hi support, not much of a luck yet.

But I attempted the following

1. Tried to implement the workaround suggested in Hi https://hi.service-now.com/kb_view.do?sysparm_article=KB0727945 it didnt work.

2. Ran the following command from my midserver to the target IP and I gave me response back as can be seen below, So it is not an issue with credentials.

C:\Users\XXXXXXX>wmic /node: xx.xx.xx.xx user:domain\xxx /password:xxxxx path win32_operatingsystem

BootDevice               BuildNumber  BuildType            Caption                                 CodeSet  CountryCode  CreationClassName      CSCreationClassName   CSDVersion  CSName        CurrentTimeZone  DataExecutionPrevention_32BitApplications  DataExecutionPrevention_Available  DataExecutionPrevention_Drivers  DataExecutionPrevention_SupportPolicy  Debug  Description  Distributed  EncryptionLevel  ForegroundApplicationBoost  FreePhysicalMemory  FreeSpaceInPagingFiles  FreeVirtualMemory  InstallDate                LargeSystemCache  LastBootUpTime             LocalDateTime              Locale  Manufacturer           MaxNumberOfProcesses  MaxProcessMemorySize  MUILanguages  Name                                                                            NumberOfLicensedUsers  NumberOfProcesses  NumberOfUsers  OperatingSystemSKU  Organization          OSArchitecture  OSLanguage  OSProductSuite  OSType  OtherTypeDescription  PAEEnabled  PlusProductID  PlusVersionNumber  PortableOperatingSystem  Primary  ProductType  RegisteredUser        SerialNumber             ServicePackMajorVersion  ServicePackMinorVersion  SizeStoredInPagingFiles  Status  SuiteMask  SystemDevice             SystemDirectory      SystemDrive  TotalSwapSpaceSize  TotalVirtualMemorySize  TotalVisibleMemorySize  Version     WindowsDirectory

3. I tried to attempt discovery using WinRM approach instead of WMI and it worked :), but I want to have an option to attempt WMI discovery as not all windows servers in the environment have WinRM capability.

Please let me know if you had any luck with Hi support.

[Mickey_Cegon · Accepted solution]

Doug Schultze came up with the solution for my issue. Our Windows credential record need the domain name before the user ID. So, DOMAIN\USERID was what worked. Please let me know if that helps you out.

Mickey Cegon