Re: Applying GP's to 2000 professional in 2003 domain

All I'm trying to change ( so far ) is

DNS Suffix Search List
Password Protect Screen Saver
Screen Saver Timeout

You got it on the first one. It leads to the question : "How do I centrally
define the DNS Suffix Search List for my 2000 PRO boxes ?"

The GPO does lock the password protect setting for XP & 2000 PRO, but only
locks the timeout for XP. A 2000 PRO user can still change the timeout. Is
this a bug or feature ? This setting is support in 2000 PRO SP1 and I'm
testing w/ 2000 PRO SP4.

I'mk seeing some errors in userenv.log that I can post.

ProcessGPOs: OpenThreadToken failed with error 1008, assuming thread is not
impersonating

I don't know which GPO this applies to though. The entry is after it checks
the local group policy.

"Roger Abell [MVP]" wrote:

Are you certain that the policy settings you are attempting to use
are ones that apply to Windows 2000 ? as shown at bottom of
the policy dialogue in gpedit


"KH" <KH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F288B165-51FF-4523-AF39-6CB62CA76009@xxxxxxxxxxxxxxxx
We've setup a new domain - only 2003 domain controllers.
We've successfully migrated 2000 pro and XP workstations to the domain.

We've setup some simple group policies we want to push out initially.
They're applying correctly for the XP workstations, but NOT for the 2000
pro
workstations. I can't find an error in the Event Viewer and when I run
gpresults it claims that my group policy is being applied - but it's
obvious
it isn't.

Neither computer nor user policies are being applied.

There are no error messages in any of the Event Viewer logs.

FYI, we still using Novell NetWare for file and print services. Migration
away from that will come later. So, I have the Novell Client installed
on
all my workstations.

FYI(2), in preparation for setting up firewall rules to push out for XP
SP2
workstations, I followed the steps on Technet for updating my GPO to
include
settings for XP SP2. I only updated my company specific GPO. I didn't
touch
the Default Domain Policy nor the Default DC Policy.

I don't believe we've ever been able to successfully apply a GPO to a 2000
pro workstation. The domain has only been up and running for about a
month.



.

Relevant Pages

  • Re: Applying GPs to 2000 professional in 2003 domain
    ... Screen Saver Timeout ... A 2000 PRO user can still change the timeout. ... the local group policy. ... We've successfully migrated 2000 pro and XP workstations to the domain. ...
    (microsoft.public.windows.group_policy)
  • Re: Workstations looking for Old Policy
    ... What evidence do you have that the "new" policy is not being applied. ... that GPO in SYSVOL is missing. ... > Windows Platform Support Team ... >> Our Windows XP Pro workstations are looking for an old policy that was ...
    (microsoft.public.win2000.group_policy)
  • Re: Strong Password Group Policy not working
    ... It sometimes gives you a little more info on why a gpo wasn't applied. ... >I have one Windows 2003 Active Directory domain with Windows XP and Windows ... the policy is not applied to any of the workstations. ...
    (microsoft.public.win2000.active_directory)
  • Re: Group Policy not taking effects
    ... It sounds like you misunderstand the way in which Group Policy works ... ... There are two major components to a GPO ... ... > My problem is that my GPO's is not taking effects in my workstations. ...
    (microsoft.public.windows.group_policy)
  • Re: OU design--Rabbit
    ... > applied to users when they login to the terminal server only? ... Normally one would expect the same policy for users ... The user is going to receive the same GPO calculation ... >>> seperate security templates for workstations, domain controllers, ...
    (microsoft.public.win2000.active_directory)