Problem with GPO propogation to Terminal Server (2000)

[Sean Aitken]

Hi!
We're having a problem with our Terminal Server / Active Directory
configuration that is preventing a GPO from being applied to the
Terminal Server box. Following lots of docs and getting assitance from
the AD admin, we have confidently created an OU, placed the server in
that OU, created a GP and applied it to the OU.. on the Terminal
Server, however, the following error is showing up when we turn on logging:

USERENV(dc.270) 18:11:16:125 ProcessGPO: ==============================
USERENV(dc.270) 18:11:16:125 ProcessGPO: ==============================
USERENV(dc.270) 18:11:16:125 ProcessGPO: Searching
CN={EA9F4588-ECB1-4E39-9CC1-6DAAFD91F27F},CN=Policies,CN=System,DC=tekelec,DC=com>
USERENV(dc.270) 18:11:16:125 ProcessGPO: Machine has access to this GPO.
USERENV(dc.270) 18:11:16:125 ProcessGPO: Found functionality version of: 2
USERENV(dc.270) 18:11:16:140 ProcessGPO: Found file system path of:
<\\tekelec.com\SysVol\tekelec.com\Policies\{EA9F4588-ECB1-4E39-9CC1-6DAAFD91F27F}>
USERENV(dc.270) 18:11:16:140 ProcessGPO: Found common name of:
<{EA9F4588-ECB1-4E39-9CC1-6DAAFD91F27F}>
USERENV(dc.270) 18:11:16:140 ProcessGPO: Found display name of:
<Secure TS Policy>
USERENV(dc.270) 18:11:16:156 ProcessGPO: Found machine version of: GPC
is 0, GPT is 0
USERENV(dc.270) 18:11:16:156 ProcessGPO: Found flags of: 0
USERENV(dc.270) 18:11:16:156 ProcessGPO: No client-side extensions for
this object.
USERENV(dc.270) 18:11:16:156 ProcessGPO: GPO Secure TS Policy doesn't
contain any data since the version number is 0. It will be skipped.
USERENV(dc.270) 18:11:16:156 ProcessGPO: ==============================
USERENV(dc.270) 18:11:16:171 GetGPOInfo: Leaving with 1
USERENV(dc.270) 18:11:16:171 GetGPOInfo: ********************************

I found one posting where a person reported a similar problem, but it
was against a local GP. Does anyone have any idea why our "Secure TS
Policy" isn't propogating???

TIA!!
-Sean

 

[Steven L Umbach]

GPO's can take up to two hours to propagate to a computer. A reboot and user
logon/logoff will speed that way up. Look in Event Viewer to see if any errors are
showing. Quite often dns misconfiguration is a reason for Group Policy not working
correctly. The domain computer must point only to domain controllers running AD dns
for the zone as their preferred dns server. Run gpresult on that computer to see what
it reports as far as OU placement and what computer/user policies are being applied
and the last time they were applied. If it looks incorrect, run netdiag from the
support tools on that computer looking for any failed tests/errors/warnings that may
help pinpoint the problem --- Steve