GPO fail

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Jimmy (jwhk001_at_hotmail.com)
Date: 11/18/04


Date: Thu, 18 Nov 2004 16:56:24 +0800

Hi, everyone

The server is Windows 2003 Standard Server and the client is Windows XP
Profesional with sp1. I created one OU (namely is High) and then created
one Group Policy Object - 123 under this OU. Furthermore, I add one
workstation from Active Directory to OU.

I used gpresult command to check this XP workstation. I found that the
result is shown on GPO is applied with Default Domain Policy not for OU

In the server's GMPC, I have already been linked with OU and workstation.

How to fix it. please help.

Thanks
Jimmy



Relevant Pages

  • RE: Event ID: 1104
    ... Please ask the problematic user logon a good workstation, ... <One of the client desktops, running Windows XP w/SP2, was experiencing ... <Windows cannot perform filter check for Group Policy object ... <The associated filter cannot be found. ...
    (microsoft.public.windows.server.sbs)
  • Re: Access server using PP and domain account
    ... With Windows XP using the windows authentication isn't strictly the credentials you use to login to the workstation. ... user account is setup on domain in which project server resides ...
    (microsoft.public.project.pro_and_server)
  • Printer driver-related network delays
    ... I've got a Windows XP LAN comprised of several workstations and printers. ... Every time someone on a workstation tries to print to a network printer from ...
    (microsoft.public.windowsxp.print_fax)
  • RE: Spoolss.exe using lots of CPU on NT clients of Windows 2003 Server
    ... As the Windows NT is not a fully compatible client on SBS domain, ... Windows Server 2003 Domain ... driver for Windows NT on one NT workstation to test. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS Client Connection Problem
    ... I understand that you encountered a Windows ... XP Pro SP2 workstation cannot access SQL Server when the workstation have ... What's the exact problem symptom of the problematic workstation cannot ...
    (microsoft.public.windows.server.sbs)