UNSOLVED

cshelley92

updated

14 years ago

C

cshelley92

13 Posts

0

31835

December 10th, 2012 13:00

Remote Task Failed -- WMI

Hi,

OME Version: 1.0.1.1253

We are reciveing the following error message while trying to push OMSA to a remote domain controller:

Results:   Insufficient privileges for WMI to execute processes on the remote system.   Check that the following are configured correctly: (a) The privilege "Replace a Process Level Token" in the Local Security Settings must grant access to the Local Service and the Network Service, and (b) Local Security Settings, WMI Security Settings, as well as any security settings that deviate from the default.C:\Program Files (x86)\Dell\SysMgt\Essentials\bin\\omremote.exe: Remote execution failed, status=3367: Unknown error.

  •  The firewall is turned off
  • Services are running
  • The service account used to run this is a Domain Admin
  • SNMP traps are set for the OME server on remote machine.

I attempted to push the update three times, all failed with the same message.

I watched the C:\Windows\Temp folder while pushing and saw the following files appear:

  • WindowsPreInstallPackage.exe
  • RemoveFiles.bat

Right after RemoveFiles.bat appears the task fails. This entire process fails within 1 minute.

Any help would be greatly appreciated, I have a task completion date of 12/14/2012

Thanks!

***** EDIT: I am trying to update from 6.5 to 7.1 using /qn install arguments.

 

  • DELL-Rob C

    4 Apprentice

    •

    2843 Posts

    659

    0

    Posted December 10th, 2012 15:00

    Hi there...

    This is an insufficient privileges issue. From the error message it looks like the user account does not have permission to execute a file on remote machine.

    The OMSA Deploy task user should have following access rights on the target:

    - User should be an administrator of the machine

    - User should have read, write and execute access under windows temp directory

    Does this help?

    Thanks,

    Rob

  • cshelley92

    13 Posts

    659

    0

    Posted December 11th, 2012 06:00

    Thanks for your reply, Rob.

    Unfortunatly that doesn't help as our Domain Admins are Local Administrators as well and they have full access to the disk.

    Thanks!

  • cshelley92

    13 Posts

    659

    0

    Posted December 11th, 2012 08:00

    Quick update:

    It seems we've narrowed the problem down to remote sites domain controllers.

    Thanks!

  • DELL-Rob C

    4 Apprentice

    •

    2843 Posts

    659

    0

    Posted December 11th, 2012 08:00

    Good to know.  Please keep us posted.  This info can be useful for other folks as well.

    Rob

  • cshelley92

    13 Posts

    659

    0

    Posted December 11th, 2012 09:00

    I will keep the thread up-to-date with findings. However, if you guys think of something that might be the issue, please let me know.

    Thanks!

  • cshelley92

    13 Posts

    659

    0

    Posted December 14th, 2012 08:00

    We finally have a solution to this problem.

    Do the following on target:

     

    Run secpol.msc:

    Impersonate a client after authentication

    Accounts:

    -Local Service

    -Network Service

    Replace a process level token:

    Accounts:

    -Local Service

    -Network Service

    Create global objects:

    Accounts:

    -Local Service

    -Network Service

    ----------------------------------------------------------------------------------------

    Windows 2003, from CMD prompt:

    net stop winmgmt

    rundll32 wbemupgd, RepairWMISetup

    cd /d %windir%\system32\wbem

    for %i in (*.dll) do RegSvr32 -s %i

    for %i in (*.exe) do %i /RegServer

    For Windows 2008:

    Net stop winmgmt

    winmgmt /slavagerepository

    cd /d %windir%\system32\wbem

    for %i in (*.dll) do RegSvr32 -s %i

    for %i in (*.exe) do %i /RegServer

    Hope this helps,

    cshelley92

  • DELL-Rob C

    4 Apprentice

    •

    2843 Posts

    659

    0

    Posted December 14th, 2012 10:00

    Thanks for this detail.  I'll look to see if we need to add a new FAQ.

    Regards,

    Rob