Richard Parmiter

Virtualisation blog and Knowledge Base

  • You are here: 
  • Home
  • Resultant Set of Policy/gpresult: access denied error message

Resultant Set of Policy/gpresult: access denied error message

Posted on October 16th, 2008

When running a Resultant Set of Policy from the Group policy management Console (GPMC) the following error is displayed:

Also, the following ‘access denied’ error appears when running gpresult.exe from a command prompt on the server:

Running on other servers seems okay, but on these specific servers there is a problem.

Resolution

This can be resolved by doing the following:

cmd
c:
cd\windows\system32

regsvr32 /n /I userenv.dll

cd\windows\system32\wbem
mofcomp scersop.mof

gpupdate /force

Tested as working on Windows 2003 x64 Enterprise Edition. (and it doesn’t even need a reboot)

  • Digg
  • StumbleUpon
  • del.icio.us
  • Facebook
  • Yahoo! Buzz
  • Twitter
  • Google Bookmarks
  • Add to favorites
  • FriendFeed
  • Google Buzz
  • LinkedIn
  • Live
  • MySpace
  • Reddit
  • RSS

Tags: , , , , ,
Filed under Scripts/Reg, Windows 2003 |

7 Responses to “Resultant Set of Policy/gpresult: access denied error message”

  1. ecticon Says:
    March 19th, 2009 at 5:40 pm

    This worked for my problem. Thanks. Microsoft KB was suggesting a hotfix. You show’d them.

  2. RP Says:
    May 11th, 2009 at 12:43 pm

    Another issue, but the following message in event viewer:

    Source: WSH
    Event Type: Error;
    Event ID: 1;
    Event Text: Citrix Monitoring Script Event 2 Citrix MetaFrame Compute Event Rate: Can’t read farm or zone name from registry: Received error: 0x80070002: Invalid root in registry key “HKLM\SOFTWARE\Citrix\IMA\RUNTIME\Neighborhood”.

    means that the Citrix WMI provider (MOF) needs to be re-registered.

    From a dos prompt, change to the following directory: Program Files\Citrix\System32\Citrix\WMI

    and run:
    for /f %1 in (‘dir /b *.mof’) do mofcomp %1 (note %%1 if scripting)

    This will re-register all the Citrix MOF’s.

  3. RP Says:
    May 11th, 2009 at 12:55 pm

    This script can be used to re-register all the MOF’s on a 64 bit Citrix Server:

    pushd c:\windows\system32\wbem
    sc pause winmgmt
    for /f %%1 in (‘dir /b *reposit*.’) do rd /s /q %%1
    sc continue winmgmt

    pushd “c:\program files (x86)\citrix\system32\citrix\wmi”
    for /f %%1 in (‘dir /b *.mof’) do mofcomp %%1

    pushd c:\windows\system32
    regsvr32 /s scecli.dll
    regsvr32 /s userenv.dll

    pushd c:\windows\system32\wbem
    for /f %%1 in (‘dir /b *.dll’) do regsvr32 /s %%1
    for /f %%1 in (‘dir /b *.mof’) do mofcomp %%1
    for /f %%1 in (‘dir /b *.mfl’) do mofcomp %%1

    popd
    popd
    popd
    popd

  4. IMA crash & CriticalSectionTimeout value | Richard Parmiter Says:
    July 8th, 2009 at 1:08 pm

    […] Associated problems appeared to be that WMI was breaking regularly. The MOF databases could be rebuilt to resolve this (as per this article RP492) […]

  5. MNEsther Says:
    April 18th, 2012 at 11:58 pm

    YAY! Thank You! Worked on Winblows 2003 Server R2 Standard Edition SP2 (x86)

  6. Cristiano Monteiro Says:
    December 3rd, 2013 at 7:28 pm

    very good boy! problem solved
    thank you

  7. Maksimcum Says:
    August 29th, 2017 at 6:31 pm

    продажа курительных смесей
    детское гей порно
    купить наркотики в украине
    зоофилы смотреть
    курительные смеси доставка
    проститутки воронежа
    купить наркотики в украине

Leave a Reply

*