RE: Errors applying group policy on client

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Bob Qin [MSFT] (bobqin_at_online.microsoft.com)
Date: 09/03/04 

Date: Fri, 03 Sep 2004 12:58:16 GMT

Hi Jerry,

I think perform a network trace can be useful to narrow down the cause. Due
to the complexity of this issue, we are unable to assist with this request
in the newsgroups.

For further assistance on this issue, please contact Microsoft Product
Support Services by telephone so that a dedicated Support Professional can
assist you further with your request. Please be advised that contacting
telephone support *will* be a charged call. However, if you are simply
requesting a hotfix, then charges are usually refunded or waived.

To obtain the telephone numbers for specific technology, please review this
web site:

http://support.microsoft.com/default.aspx?scid=sz;en-us;top

If you are outside the US, you can find regional telephone support numbers
at http://support.microsoft.com.

In addition, before you contact the PSS Support, please refer to the
following article to enable User Environment Debug Logging and send the log
to our engineer. They may find more clues in the log.

221833 How to Enable User Environment Debug Logging in Retail Builds of
Windows
http://support.microsoft.com/?id=221833

Thank you for using our newsgroup.

Regards,
Bob Qin
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.

--------------------
      From: =?Utf-8?B?SmVycnlU?= <JerryT@discussions.microsoft.com>
      Subject: RE: Errors applying group policy on client
      Date: Thu, 2 Sep 2004 12:37:01 -0700
      Newsgroups: microsoft.public.windows.server.migration
      
      Bob,
      I have done a bit more work on this. Made some changes to my
switches, which
      helped a bit. I still have problems with some clients.
      
      Some clients still fail even with the hosts file entry.
      Some clients work fine without the hosts file entry.
      
      Seems like this must be client configuration issue?
      
      Is the nbtstat cache persistant?
      
      These clients are getting rebooted each day, so if the cache is not
      persistant then applying that command probably won't help
      
      netdiag and addiag both came up clean - no problems
      
      Thanks
      
      
      "Bob Qin [MSFT]" wrote:
      
> Hi Jerry,
>
> I am glad to hear that the problem does not occur now.
>
> Based on my expriences, the error may occur when computers on the
network
> are not able to connect to the
> group policy objects in the Sysvol folders on the domain
controllers. It is
> possibly still a name resolution problem.
>
> As for the others client, does the problem still occur if you run
nbtstat
> -R to flush the cache?
>
> You can try to run "netdiag.exe" and "ADdiag.exe" to check if there
is any
> error.
>
> Best regards,
> Bob Qin
> 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.
>
> --------------------
> From: =?Utf-8?B?SmVycnlU?= <JerryT@discussions.microsoft.com>
> Subject: RE: Errors applying group policy on client
> Date: Tue, 31 Aug 2004 13:53:07 -0700
> Newsgroups: microsoft.public.windows.server.migration
>
> Bob,
> Thanks for your assistance.
> The share you refer to is accessible logged on as either
admin or
> user from
> the client.
>
> I modified the hosts file on a client as you recommend.
> The DNS already had a record corresponding to what you
described.
>
> (Same as parent folder) Host(A) 172.16.1.244
>
> Where 172.16.1.244 is the primary DNS, PDC Emulator
>
> The good news is that the problem seems to have disappeared,
I need
> to do a
> little more testing to be certain since this problem is a bit
> sporadic. I
> modifed four other clients that were consistantly having the
problem.
> I'll
> know for certain tomorrow morning.
>
> Now my question is - why does this work?
> And do I have to modify the hosts file for all my clients
(not too
> excited
> about that)?
>
> JT
>
> "Bob Qin [MSFT]" wrote:
>
> > Hi Jerry,
> >
> > Can you access the share of
> >
>
<\\hq.encoder.com\sysvol\hq.encoder.com\Policies\{31B2F340-016D-11D2-945F-00
> > C04FB984F9}\> from the client when the issue occurs?
> >
> > Now please try the solutions below:
> >
> > - Client side:
> >
> > Create an entry to the
c:\windows\system32\drivers\etc\HOSTS file
> > For example, Add the entry "10.0.0.2 domain.local" to
the file.
> > (Assuming 10.0.0.2 is the server internal ip, domain.local
is AD
> domain
> > name)
> >
> > - Server side:
> >
> > From the DNS, Forward Lookup Zone, create a Host (A)
record.
> > Leave the Name blank and set the IP to the internal ip of
the
> server. Click
> > Add Host.
> > You should see the new record "(Same as parent folder)
Host
> 10.0.0.2" in
> > the zone.
> >
> > After the changes, run nbtstat -R to flush the cache.
> >
> > If the problem still persists, please run the MPS
Reporting tool
> on both
> > the client and the server to collect the system information
for
> further
> > research.
> >
> > 1. Visit the following web page:
> >
> >
>
http://microsoft.com/downloads/details.aspx?FamilyId=CEBF3C7C-7CA5-408F-88B7
> > -F9C79B7306C0&displaylang=en
> >
> > 2. Download the file MPSRPT_SETUPPerf.EXE
> >
> > 3. Double-click MPSRPT_SETUPPerf.EXE to run the tool.
> >
> > 4. On your system a CAB file will be generated for your
convenience
> in the
> > %systemroot%\MPSReports\Setup\<Report Type>\Cab directory
called
> > %COMPUTERNAME%_MPSReports.CAB. The CAB file will contain
the
> reports
> > generated by the MPS Reporting Tool. Please send the cab
file to me
> by
> > email. (where %systemroot% is the Windows system folder,
such as
> C:\Windows
> > or C:\Winnt)
> >
> > Please send the result of MPS Reporting tool to me directly
at
> > bobqin@microsoft.com and I will do further research.
> >
> > Thank you,
> >
> > Bob Qin
> > 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.
> >
> > --------------------
> > From: =?Utf-8?B?SmVycnlU?=
<JerryT@discussions.microsoft.com>
> > Subject: RE: Errors applying group policy on client
> > Date: Mon, 30 Aug 2004 10:51:08 -0700
> > Newsgroups: microsoft.public.windows.server.migration
> >
> > Hi Bob,
> > Thanks for your response, sorry I'm a bit slow
responding,
> have been
> > trying
> > to figure this out.
> > DNS seems correct - most clients get DNS pointers
from DHCP
> and all
> > that I
> > checked were fine.
> > There are no errors in the NTFRS logs for either DC.
> > None of the clients that I checked even have a
DisableDFS
> entry in
> > their MUP
> > service key.
> > Just to make sure I created that entry on a test
system, set
> it to
> > false (0)
> > and tested. No difference.
> > Everyone group is present and configured the same for
the
> root drive
> > of all
> > clients I checked.
> >
> > I took one of the machines that consistantly has
problems and
> removed
> > it
> > from the domain. Then added it back in. No difference.
> >
> > Please bear in mind that this problem is not
consistant on
> all
> > machines.
> > Some of the clients do work correctly some of the
time, and
> fail at
> > other
> > times. Also it appears that the problem most often
occurs
> during
> > boot, in
> > many cases the client appears to correctly apply GP
when the
> > background
> > refresh interval occurs about 90 minutes after boot.
Seems
> like
> > startup is
> > the biggest problem area. Then there are a couple of
machines
> that
> > never seem
> > to get policy applied.
> >
> >
> > "Bob Qin [MSFT]" wrote:
> >
> > > Hi Jerry,
> > >
> > > Thanks for your posting here.
> > >
> > > First please ensure that DNS is configured
properly. Make
> sure that
> > you
> > > point the DC and clients to the same internal DNS
server.
> > >
> > > Please run "set" in the command prompt, and check
the
> LOGONSERVER
> > item. It
> > > is the DC that authenticated this user. Please
check if
> there is
> > any NTFRS
> > > error on that DC.
> > >
> > > In addition, did you check the other settings
mentioned in
> the
> > artilce of
> > > 314494? For example, Microsoft Distributed File
System
> service?
> > >
> > > 314494 Group policies are not applied the way you
expect;
> "Event ID
> > 1058"
> > > and
> > > http://support.microsoft.com/?id=314494
> > >
> > > Have a nice day!
> > >
> > > Regards,
> > > Bob Qin
> > > 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.
> > >
> > > --------------------
> > > From: =?Utf-8?B?SmVycnlU?=
> <JerryT@discussions.microsoft.com>
> > > Subject: Errors applying group policy on
client
> > > Date: Thu, 26 Aug 2004 12:43:04 -0700
> > > Newsgroups:
microsoft.public.windows.server.migration
> > >
> > > Hi,
> > >
> > > I recently upgraded our domain from NT4 to
W2K3. We
> have two
> > domain
> > > controllers and a mix of NT4 and XP clients.
> > >
> > > Many of the clients are logging errors in the
> Application
> > event log.
> > >
> > > Source: Userenv
> > > Event ID: 1058
> > > Windows cannot access the file gpt.ini for
GPO
> > >
> > >
> >
>
CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=hq,DC=enc
> > > oder,DC=com.
> > > The file must be present at the location
> > >
> > >
> >
>
<\\hq.encoder.com\sysvol\hq.encoder.com\Policies\{31B2F340-016D-11D2-945F-00
> > > C04FB984F9}\gpt.ini>.
> > > (The network path was not found. ). Group
Policy
> processing
> > aborted.
> > >
> > > I get this error for the User: SYSTEM, then
for the
> actual
> > user
> > > logging on.
> > >
> > > The problem is also a bit sporadic, for a
given
> client it
> > doesn't
> > > always
> > > happen. Some clients never exhibit the
problem, some
> always
> > do, and
> > > some do
> > > sometimes.
> > >
> > > I see there is a hotfix (Q314494) that might
be
> related to
> > this, but
> > > would
> > > have to apply to a lot of clients, and it
didn't seem
> like it
> > was
> > > quite the
> > > same. The hotfix indicated an event message
that
> ended by
> > saying the
> > > problem
> > > was "access denied" vs "path not found" in
this case.
> > >
> > > Has anyone seen this before?
> > > TIA
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
      

Relevant Pages

  • RE: Outlook does not find name in addess list - exchange
    ... For the client workstion's OS is a non-English version, ... contact the local CSS for support. ... Microsoft CSS Online Newsgroup Support ... Please check the RPC_Binding_Order registry value on the machine. ...
    (microsoft.public.windows.server.sbs)
  • Re: Two access points in same house
    ... disable the wireless client, wait a few minutes, turn on the wireless ... customers with lots of systems with identical SSID on each AP. ... Dlinks support people, they are the biggest asses I have ever tried to ... I recently had to ask for an unreleased firmware image from one ...
    (alt.internet.wireless)
  • RE: SOAP .Net client wrapper questions
    ... Async operation with the webservice ... a common cause is the XML serialization ... pregenerate some XML serialization assembly for webservice client. ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.framework.webservices)
  • RE: WCF Security Issue
    ... ** Is your WCF service designed to use domain ... both wsHttpbinding and netTcpBinding support message ... Then, for your WCF client, you can use the current logon user's credential ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: 64 bit C# trying to call a 32 bit CPP ATL Service
    ... the process space of the client application. ... HKEY_CLASSES_ROOT\CLSID registry key, ... We build a 64bit version of the ATL service, ... Microsoft Online Community Support ...
    (microsoft.public.vc.atl)