RE: Access Denied for Event Viewer or Regedit

ADDITIONAL INFO-

I also found this article 840634 entitled
"You receive an "Access denied" or "The network path was not found" error
message when you try to remotely manage a computer that is running Windows XP
Service Pack 2"

The article describes exactly the behavior that I am getting, I mentioned
that I use a GPO to make the setting, but I also tried the command line
option 1, and received an OK message that the command had completed.

The event log shows nothing when I attempt to connect to the workstation and
get the "access denied"

THanks
J

"Ken Zhao [MSFT]" wrote:

> Hello,
>
> Thank you for using newsgroup!
>
> From your post, it seems that you have two issues as below:
> 1. You are encountering the same symptom which described in KB892192.
> However, you are not able to find the registry key winreg in
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers to
> set.
> 2. Remote Desktop works just fine, but Help and Support does not, it just
> prompts me to log into the workstation after detecting the user, but wants
> to log off the user if you attempt to log on.
>
> You are using two different features in Windows XP. It seems that these two
> questions are unrelated. Please understand that our newsgroup is an issue
> based service, meaning we usually respond to one question/issue per post.
> This will lessen the confusion for both of us, as well as ensure that our
> results are accurate and not a result of a test for a different question.
> Therefore, I will work with you on the first question in this post.
> Regarding the additional question, please open a new post so that the
> dedicated MS engineer can help you on it in a more efficient manner.
>
> For the first issue, please help me confirm the following information first:
> 1. Does the issue (lack of registry key) only occur on the machines with
> OEM Windows XP Pro?
> 2. Does the issue only occur on the specific registry key? What about other
> registry keys?
>
> If the problem only occurs on the machines with OEM Windows XP Pro, I
> suspect this issue should be related to OEM. Since original equipment
> manufacturers (OEM) that preload Microsoft software on the computers and/or
> peripherals they sell provides all support for those Microsoft products.
> Since OEM has customizes the Microsoft software for your specific computer
> system and is, therefore, I suggest you first contact the OEM manufacturer
> to see whether they are able to provide some help on this.
>
> At this moment, I also suggest you manually create the following registry
> keys in the problematic machines to see if it can help:
>
> Key Name:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
> Class Name: <NO CLASS>
> Last Write Time: 2004-12-6 - 16:53
> Value 0
> Name: Description
> Type: REG_SZ
> Data: Registry Server
>
> Key Name:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
> \AllowedPaths
> Class Name: <NO CLASS>
> Last Write Time: 2004-12-6 - 16:53
> Value 0
> Name: Machine
> Type: REG_MULTI_SZ
> Data: System\CurrentControlSet\Control\ProductOptions
> System\CurrentControlSet\Control\Print\Printers
> System\CurrentControlSet\Control\Server Applications
> System\CurrentControlSet\Services\Eventlog
> Software\Microsoft\OLAP Server
> Software\Microsoft\Windows NT\CurrentVersion
> System\CurrentControlSet\Control\ContentIndex
> System\CurrentControlSet\Control\Terminal Server
> System\CurrentControlSet\Control\Terminal
> Server\UserConfig
> System\CurrentControlSet\Control\Terminal
> Server\DefaultUserConfiguration
>
> Hope the information helps!
>
> Thanks & Regards,
>
> Ken Zhao
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>
> --------------------
> | Thread-Topic: Access Denied for Event Viewer or Regedit
> | thread-index: AcXu51iP68TKX985Tqi5u6/vswFOpA==
> | X-WBNR-Posting-Host: 209.217.222.70
> | From: "=?Utf-8?B?U211cmZtYW4=?=" <smurfman@xxxxxxxxxxxxxx>
> | Subject: Access Denied for Event Viewer or Regedit
> | Date: Mon, 21 Nov 2005 14:03:04 -0800
> | Lines: 32
> | Message-ID: <6F225F11-01EE-4584-8F01-D52296F4C0F9@xxxxxxxxxxxxx>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.windowsxp.help_and_support
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA02.phx.gbl
> microsoft.public.windowsxp.help_and_support:600687
> | X-Tomcat-NG: microsoft.public.windowsxp.help_and_support
> |
> | After upgrading several Windows 2000 Pro machines to Windows XP Pro and
> | installing SP2, and all of the updates as of 11/21/2005, I am noticing
> some
> | strange behavior.
> |
> | One is that when I attempt to connect to the Event Viewer or the Registry
> of
> | another machine, I receive and access is denied error message. When I go
> to
> | the machine and look at the event log, I am not seeing anything in
> particular
> | that points to such a problem.
> |
> | I looked at KB 892192 which was related to XP pro and W2K3, it fits the
> | error to a "T", but when I traverse to the
> | HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers and look for
> | Permissions under the winreg setting, it does not exist...
> |
> | The second part to this is that Remote Desktop works just fine, but Help
> and
> | Support does not, it just prompts me to log into the workstation after
> | detecting the user, but wants to log off the user if I attempt to log on.
> I
> | am not sure if this is related or if this is another issue.
> |
> | The machine is part of a domain, and takes a Domain Firewall Policy,
> | machines that are OEM for XP Pro behave just fine, and everything works
> just
> | fine.
> |
> | I am connecting from an XP Pro SP2 machine to the same, and each machine
> | that has been upgraded, behave the same way.
> |
> | Also, the HLKM... that I talked about above, does not exist on any other
> XP
> | OEM or otherwise machine. And GPEdit reports that the settings are in
> fact
> | alking place as expected for these machines as well.
> |
> | Thanks
> | J
> |
>
>
.

Relevant Pages

  • RE: Access Denied for Event Viewer or Regedit
    ... Does the issue (lack of registry key) only occur on the machines with ... If the problem only occurs on the machines with OEM Windows XP Pro, ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: KB967715 Not installed not offered anymore
    ... different from the set of machines on which the old revision is offered. ... personal machine but I can tell you the registry key it is suppose to ... Programs *and* it is not being offered by Windows Update now, ... to install the update again since March 1st. ...
    (microsoft.public.windowsupdate)
  • Re: Huge Planned Windope Migration Put On Hold!
    ... machines, using a ghosted image based upon the OEM version that ... this OEM version of XP pro, that I can't even begin to tell you. ... > improperly admined non-secure Windows systems, ... require user admin privileges to ...
    (comp.os.linux.misc)
  • Re: Huge Planned Windope Migration Put On Hold!
    ... machines, using a ghosted image based upon the OEM version that ... this OEM version of XP pro, that I can't even begin to tell you. ... > improperly admined non-secure Windows systems, ... require user admin privileges to ...
    (alt.os.linux)
  • RE: Change licence key from OEM to VLK
    ... In order to covert an OEM license ... -Insert your VLK Windows Installation CD ... -Continue through the setup until it detects another Windows Installation ... able to convert these machines to virtual machines, ...
    (microsoft.public.windows.server.setup)