Re: XP workstations will not apply GPO software install but 2000 WS do

From: Herb Martin (news_at_LearnQuick.com)
Date: 01/14/05 

Date: Fri, 14 Jan 2005 11:54:06 -0600

"bbuchen" <bbuchen@discussions.microsoft.com> wrote in message
news:24BE27F6-DD98-4C2D-B1CB-9F81CB88424A@microsoft.com...
> Hello,
>
> I have setup an OU with a GPO that will install Outlook 2003 by Computer.
> This works great for win 2000 workstations but for any XP ws
(Professional)

> I get the error upon boot up that it could not contact the DC therefore
the
> GPO install will abort. Any ideas? I suspected a problem with DNS
> but I have check it and seems fine. I am able to log into the WS with a
AD
> user and

Such (failure to authenticate and thus load GPOs etc.) is almost
always a DNS issue but it can be a more direct authentication or
permission problem.

> I am able to ping, nslookup all systems on the network including the DC
> without any problems.

This does argue for eliminating DNS as the culprit,
but let's first say that INTERNAL clients must use
ONLY the internal DNS servers in their NIC->IP->
DNS server properties.

How about permissions? Are the install files (the MSI etc.)
located on a server with Share or NTFS permissions that
do not allow the XP machines (accounts) to download the
files?

If you used something like "Authenticated Users-READ" this
should not be the problem.

Does it really say it "cannot contact the DC" or does it use
the Server name (for the DC) in the context of trying to
download the FILES?

There is a difference (the DC doesn't actually have to hold
the files distributed through the GPO instructions, but the
key here is to isolate WHAT is failing.)

It sounds like permissions but that seems unlikely to be
messed up. 

-- 
Herb Martin
>

Relevant Pages

  • Re: Software install not installing on some systems
    ... software install, but --- that computer is still not installing. ... Group Policy Infrastructure failed due to the error listed below. ... That sounds like a DNS error. ... I checked the forward/reverse on the DNS servers to make sure the ...
    (microsoft.public.windows.group_policy)
  • Re: AD and DNS
    ... Easiest way is to make the zones AD integrated and install the DNS service ... then configure secondary DNS servers for the clients. ... >>>> You would need to install DNS on the second Domain Controller! ...
    (microsoft.public.win2000.active_directory)
  • Re: Strange Problem(s) After Installing Security Update 818529
    ... > through the automatic updater (and I went ahead and let it install, ... I'm a DNS neophyte and installed DNS simply because it is ... Do not use ISP's DNS servers in any internal machine properties. ... If you need Internet resolution, use a forwarder that you would individually ...
    (microsoft.public.win2000.security)
  • Re: Domian Controller DNS Settings Question
    ... forwardst he request to any of the other DNS servers. ... DNS, then the rest of the DCs become useless while they cannot find ... Internet name resolution is something you'll have to decide, ... When you install DNS on DC2, BEFORE the install should the DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: laptops connect at work but not at home?
    ... they dont seem to take on the internal DNS ... > grayed-out with those DNS servers set, ... > to explain it another way, i'd like the GPO to set static DNS servers ...
    (microsoft.public.win2000.dns)