Re: Intermittant GPO failure to apply
- From: "NickC" <NoSpam@xxxxxxxxxxxxxx>
- Date: Tue, 18 Oct 2005 10:21:37 +0100
Thanks Charles, I will try that and see if that solves the problem or
whether it comes back again during the 90 minute GPO refreshes.
For the archive and anyone else reading this I created an input file called
'No.txt' which contains N<enter> and put the following at the end of our
SBS_LOFIN_SCRIPT.bat:
GPUpdate /force <No.txt
Nick
""Charles Yang [MSFT]"" <v-chayan@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:$BcdmLr0FHA.1188@xxxxxxxxxxxxxxxxxxxxxxxx
> HI Nick,
>
> Thanks for updates.
>
> Just as I referred, this issue will sometime occurs and relate to hardware
> design issue. Although you have updates the NIC drivers, but it should be
> the hardware design issue, so we can not resolve the issue from our side.
> The root cause of the issue should be the network package failed to pass
> the NIC interface because of the hardware problem. It will not occur all
> the time as some time the NIC will work on normal but some time not, that
> why we consider as a pure hardware design issue.
>
> So we suggest you add the gpupdate on the logon script, if you still have
> concerns on this issue, it is your best interest to call CSS. It might
> help
> resolve the issue more clearly:
>
>
> To obtain the phone numbers for specific technology request please take a
> look at the web site listed below.
>
> http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
>
> If you are outside the US please see http://support.microsoft.com for
> regional support phone numbers.
>
> Thanks for your understanding on this issue.
>
>
>
> Best regards,
>
> Charles Yang (MSFT)
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
>
> ======================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check
> the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In
> doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> =====================================================
> 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: Intermittant GPO failure to apply
> | thread-index: AcWk9+ULF20LFFoARryxF9znlfwpuQ==
> | X-WBNR-Posting-Host: 65.118.104.18
> | From: "=?Utf-8?B?ZWNob2JvYg==?=" <echobob@xxxxxxxxxxxxxxxxxxxxxxxxx>
> | References: <#0yb8FPlFHA.1608@xxxxxxxxxxxxxxxxxxxx>
> | Subject: RE: Intermittant GPO failure to apply
> | Date: Fri, 19 Aug 2005 12:55:05 -0700
> | Lines: 32
> | Message-ID: <3EB8022F-87FF-4180-A744-657E6A8965B0@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.windows.server.sbs
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:146022
> | X-Tomcat-NG: microsoft.public.windows.server.sbs
> |
> | Nick,
> |
> | I'm not sure if these will run under sbs, but I went through the same
> type
> | of trouble a while back under 2k server. The tools I used were gpotools,
> | frsdiag,sonar, and dcdiag available from microsoft. My problems were
> flaky
> | DNS from an abandoned server, and sysvol shares pointing to a different
> drive
> | in the registry.
> |
> | Each one showed me a different piece of the puzzle..
> |
> |
> | "NickC" wrote:
> |
> | > We have a problem on our workstations whereby around half of the time
> the
> | > GPOs do not apply correctly but running 'GPUpdate /force' always
> temporarily
> | > fixes the problem. Sometimes I can get all the workstations GPOs
> working
> | > correctly then a few hours later they start failing without even
> rebooting!
> | > Sometimes the machine boots and the GPOs are applied even before a
> user
> has
> | > logged on, is that correct? When are GPOs supposed to be applied?
> | >
> | > This manifests itself in Windows Firewall problems when the Firewall
> | > settings Group Policy does not get applied correctly and the Firewall
> | > reverts to its XPsp2 defaults. When that happens I find that the
> server
> | > cannot remotely manage these workstations, in fact they can't even be
> | > pinged.
> | >
> | > Any suggestions on how I can diagnose this problem?
> | >
> | > Nick
> | >
> | >
> | >
> |
>
.
- References:
- RE: Intermittant GPO failure to apply
- From: "Charles Yang [MSFT]"
- RE: Intermittant GPO failure to apply
- Prev by Date: RE: Two ISA questions-1
- Next by Date: RE: DHCP
- Previous by thread: RE: Intermittant GPO failure to apply
- Next by thread: Re: Join computer to domain via vpn or SBS connection
- Index(es):
Relevant Pages
|
