RE: Possible Impersonation Issue?



Looks like I found the issue, it was with a seImpersonateClient GPO. It all
started when we tried to install SQL Reporting services, which wants the
local IWAM_ServerName account to be able to impersonate. When this GPO is
applied, there are impacts to several services.
> 1. when connecting to DC through compmgmt.msc, connection succeeds, but
> there is an error on opening the Event Viewer "Either a required
> impersonation level was not provided, or the provided impersonation level is
> invalid." This is done when logged in/connecting as a Domain Admin. But
> this happens on only two of the DCs. I can open the Event Viewer on all the
> others.

This can be remedied by adding NETWORK SERVICE and LOCAL SERVICE to the
Impersonate GPO, stopping the Remote Registry service, then de-configure the
service to logon with NT AUTHORITY\LocalService (I just changed it to
NetworkService), click apply, click ok when told the Network Service is
granted the logon as a service right, and start the service. Then, go back
into the service properties, and go through the same exercise to return it to
LocalService. This re-registers the service with the new permissions. Note
that just restarting the service did not achieve the same result.

> 2. WMI scripts that I have used for months started failing on all DCs. I
> have done extensive troubleshooting, from the technet WMI faq. I am
> connecting through DCOM, but all scripted WQL queries fail. Using
> WBEMtest.exe, I can connect remotely, and enumerate classes. I went into WMI
> Security, and gave both the Domain Admins and even myself explicit "full
> control" permissions, and restarted the WMI service, scripts still fail.
> Makes no difference if I run scripts from admin workstation, termed into the
> DC, or logged in to the DC console. Opening WMI control (from the WMI
> Control properties in the MMC) gives Access Denied errors for the
> Win32_Processor and Win32_OperatingSystem. I can configure security locally,
> but not remotely (this is by design ?) I have rebuilt WMI by deleting the
> repository directory, and re-registered the executables and the dlls. No
> help.

This was remedied by putting NETWORK SERVICE in the GPO. When you connect
to WMI, you may authenticate to DCOM as you, but your queries run against WMI
in the NT AUTHORITY\NetworkService context. Found this in one of the WMI
logs, a query by NetworkService kept failing.

> 3. I can no longer connect remotely to the registries on the same 2 DCs as
> in #1 above. Remote Registry service running on both the admin workstation
> and servers.

This was remedied by the fix in no. 1 above.

Hope this helps someone else!
Cheers!
.



Relevant Pages

  • RE: Help! Biztalk has left the building... ConfigureFramework prob
    ... was a security error with the NETWORK SERVICE user accessing the MSVCR71.DLL ... When I provided permissions for the NETWORK SERVICE, ... Looking at my development server, ... > Have you checked or are you familiar with setting permissions to a WMI ...
    (microsoft.public.biztalk.general)
  • Re: unexpected failure during the setup - help!
    ... We have checked a lot of settings about WMI. ... Support via telephone so that a dedicated Support Professional can ... Please first install the update 917805 to update the component Cluswmi.dll ... The "Remote Registry Service" is running on both nodes of the cluster. ...
    (microsoft.public.sqlserver.setup)
  • Re: XP Firewall Status via SMSSCCM?
    ... wmi area. ... a firewall setting via GPO, that the GPO is applied to that box. ... instead of a MOF edit you could instead use Desired ...
    (microsoft.public.sms.admin)
  • Re: Is there any way to print a list of the GPOs in a domain?
    ... error when checking WMI, plus I cannot use any WMI based inventory programs. ... Find out more about Desktop Policy Manager at ... experts I have shown the GPO to can figure out what part if it doing it! ... you can use my free GPMC cmdlets quite easily. ...
    (microsoft.public.windows.group_policy)
  • RE: GPO and WMI Filters
    ... Please let me know which GPO you used. ... Please let me know which WMI you used. ... Developer newsgroups since this newsgroup is primarily for break-fix ... PLEASE NOTE the newsgroup SECURE CODE and PASSWORD were ...
    (microsoft.public.windows.server.sbs)

Loading